@dimillian I still have access to Threads (UK) but I much prefer Mastodon. Once it gets tags and a chronological feed that would close the gap, though I don’t think it’d have the intimate feel of a small instance like ruby.social.
Though if it gets good search and network-wide finding posts by tags (pre-federation anyway) that would make it better in some important ways.
@Migueldeicaza I wish .social was as fast as Threads. What make Mastodon a bit sluggish is that it’s not that fast. Still wondering if I want to replicate the Threads simple UI.
@dimillian the other issue with mastodon is that discussions take a long time to spread out. So I get replies hours later, and it sort of breaks the conversation.
@Migueldeicaza@dimillian from my experience that’s due to people catching up later cause of the timeline vs. seeing immediately the relevant conversations because of the algorithm.
@Migueldeicaza@dimillian I have noticed that Mastodon notifications are sent out with a significant delay. Since I’m on a less-mainstream server, most messages directed at me come from other servers (all thumbs up for the toot.community instance, though).
@dimillian@Migueldeicaza I have a feeling if Mastodon (not just .social) grows in scale, it will need to be rewritten in something that is not Ruby on Rails.
@dimillian Tu n’y as plus accès du tout ? Moi, c’est seulement certaines réponses dans des conversations. Sinon, j’ai toujours autant de « spam » pas toujours « safe for work »…
Add comment