(oh, right…bird flu)
(oh, right…bird flu)
The Twitter-to-Mastodon migration is like going from beta testing the Fediverse to production. Just like a public beta always turns up issues that were missed during development, when going to production you suddenly have a *huge* pool of new users who are going to use the system in ways you didn’t anticipate and haven’t already accustomed themselves to its quirks.
And that turns up a lot more things you need to fix!
Some thoughts on features/user experience for Mastodon and other Fediverse software, based on usage and discussions I’ve seen lately:
1. Missing replies aren’t just an inconvenience, they’re a big problem. Instances really do need to reach out and check for additional replies when someone views a post. I’m not sure how to balance the extra network traffic. Maybe just have a manual “check for more replies” button.
2. Quoting is better than screenshotting. I can read quotes on any size screen. So can screen readers.
3. Lack of quoting hasn’t prevented flame wars or dogpiling, and it there’s no indication it reduced them either. If you don’t want to embed an entire post, at least generate a preview like you would to a website with suitable metadata. And let any third-party clients know they can fetch the message themselves and not hand it off to the web browser.
4. If you really want to keep some friction in the quoting process, don’t add a button, but add the preview/embed on display.
5. Link previews should be generated and displayed during composition, without interrupting typing. Whether the preview gets federated along with the post or re-generated at the destination is another debate.
6. User discovery on third party clients needs work, and autocompletion really needs to be part of the composition UI.
7. Remote interactions on posts that aren’t in the app *really* need work.
8. Basic interactions (profile, follow, like, boost, reply) should Just Work(tm) between different federated software, even if they don’t recognize all the same post types or display them nicely. You can always fall back to displaying a link to the source, like Mastodon does with Article types.
9. Mastodon ought to at least *try* to display Articles as long as the formatting isn’t too complex or the length too long.
10. Mastodon’s “Your admin can read your DMs” notice should make it clear that *most* messaging software has this issue, not just Mastodon.
11. Federated hashtag searching is also more important than the inconvenience I used to think it was.
12. I’ve seen several mentions of the need for local-only posts (which some platforms have) and mutual-followers-only posts, and I totally agree with both.
13. (Added 1/23/23) I want to be able to bookmark profiles, so I can mark people/groups that I want to occasionally interact with, but don’t want to follow all the time – but when I do want to look them up or mention them, I can be sure I got the name right.
The flood control basin has been partly restored for stormwater infiltration and as habitat for native plants and migrating waterfowl, bounded by a city park on one side, baseball fields on the other, and hills all around. The city is currently expanding the basin while the water level is low.
I made a huge mistake in my article on how to post to Mastodon through IFTTT.
I gave the wrong directions on what to put in the Application Website field in Mastodon. It just needs to be
https://ifttt.com. It isn’t used for identifying the source to your Mastodon server as I thought it was, but appears as a link when the post is viewed by itself on the web. If you followed on my mistake, I highly recommend (1) removing the URL from your Mastodon config and just putting in ifttt.com and (2) going into your Webhooks settings at IFTTT and generating a new key. I feel horrible that I messed this up, and I am so sorry to everyone I steered wrong.