so it would seem that mastodon doesn't really have UI for threads, doesn't support QTs, and doesn't support search of posts except for hashtags

for being ostensibly a clone or replacement to twitter, it doesn't actually have the features needed to support the way i use twitter

@acidshill yeah there were a few design decisions made explicitly to be different from twitter for a variety of reasons, some of which i agree with but many of which i dont

1. re search, yeah its different from twitter, but specifically here its just disabled bc i havent set up the infra for it
2. there's a masto fork that supports QTs, i'm thinking of adopting it (its also just a rendering diff, just paste the link in a toot)
3. yeah the threading UI is uhhhh not great

@pee_zombie the forking also seems like potentially a problem? like, i think it's good that instances can do things differently and still talk to each other, but i strongly suspect that it's gonna cause issues when they're using different sets of features, different design, different assumptions for how things work

@acidshill not really, its already been happening for many years. it works bc there's a common underlying specification, ActivityPub, with multiple implementations (Mastodon, Pleroma, GoToSocial, PixelFed etc). the entire point of the fediverse is that you can use whatever software you like

@pee_zombie yes, and i also notice that whenever i've used or played with mastodon, i've never seen uhh RTs or whatever from non-mastodon servers

maybe that's just because the userbase is smaller? but there's a difference between mere protocol compatibility and actual functional integration of data/content posted on different platforms