But what is the actual PROBLEM with Mastodon?? Said one hundred dozen people over several months of threads here. So I wrote it up.

It's too long, but we got bad doors, stilt-walking French shepherds, water bugs, a bunch of @/[email protected] quotations, What The Fuck Is Up With Bluesky, and more.

https://erinkissane.com/the-affordance-loop

I would bet actual money that I've got some nuance of Mastodon's functionality wrong in there so when you see that please do lmk. I thought about asking instance-running friends to preview it but I've taken up enough of their time this week.
@kissane The part about which replies you see isn't 100% accurate, but an accurate description of how that works would be longer than the current post, so 🤷‍♀️

@annika
@kissane
yes this. you are right on with pretty much all of this, and love the piece, but one minor correction here:

If you are looking at replies to someone else’s post, you will only see the replies that come from instances that your instance already has a federation relationship with.

More precisely you will only see posts that come from accounts that someone on your instance follows. You don't get all the posts from all federated instances. (edit: and there is a ton more subtlety with eg. blocks and how different instances do federation and etc.)

Agreed its a way bigger problem than ppl realize. I really need to merge this and make it default instead of a button. one janky, low hanging fruit way to #FetchAllReplies is to abuse the search function: ask the OP instance what replies it knows about, then go and search for all of those

https://github.com/NeuromatchAcademy/mastodon/pull/8

[feature] fetch all replies by sneakers-the-rat · Pull Request #8 · NeuromatchAcademy/mastodon

Adds a button to the bottom of an expanded status to fetch all replies from the OP server (or as many as they will give us). Example: https://neuromatch.social/@jonny/109582537808504261 Context: h...

GitHub