-
@MitchW Thank you for sharing, this is very interesting. I am tempted to migrate everything to Micro.blog, but haven’t been brave enough yet, in part because Mastodon gives me more choices in clients than MB. Also, while I can live without reposting and favoriting, they’re a big part of Mastodon culture, so I hesitate to give that up. All that said, the idea of aggregating conversations on MB, Mastodon, and Bluesky in one place is definitely attractive. Really appreciate you sharing your experiences.
-
@manton I was on a flight to Chicago and heard someone refer to him as, the “Deep Dish” pope, definitely made me chuckle. For anyone reading this who may not get it, deep dish is a kind of pizza famously from Chicago, just like the new pope.
-
@manton I have colleagues that have been told that they MUST find ways to use AI or they might want to start thinking about working elsewhere. I can’t describe the awesome impact this has had on employee morale. Urging people to be open and curious makes sense to me, but when people fear for their jobs because they haven’t figured out how to use something they may not even need, it’s just wrong on so many levels.
-
@manton I love keyboard shortcuts, they’re an accessibility win for me but even bettor, an efficiency boon. That said, I also love consistency and having cmd+s do something in one tab and something else in another would potentially be frustrating. Even worse would be if you got cmd+s working with Safari, but not in other browsers, or if there were inconsistency between operating systems, especially iOS/iPad OS/Android and of course Mac OS/Windows. Ultimately, I don’t think there’s a perfect solution that will make everyone happy, probably the best thing to do would be to make sure it’s somehow easy to access the keyboard shortcut list somehow, and that you have an easy way to gather feedback. For example, cmd+? brings up a help modal with the keyboard shortcut list with a submit feedback button or similar.
-
@manton I also worry about the accessibility implications of this a bit: For better or worse, screen readers look at pages, mainly through their underlying structure, in the way that bots do. As such, they aren’t able to tell if a link is truly visible, or if it’s just in the DOM. This often leads to me thinking there’s an error or modal present on screen when it’s not, it’s just in the DOM and so the screen reader assumes it’s there. Dealing with bots while not breaking accessibility is admittedly a real challenge as any techniques screen readers might use to better understand what’s going on could also be used by the bots.
subscribe via RSS