Conversation
Notices
-
AAAAHHH WOW!!! HOLY SHIT!! Using Not-Mastodon makes me *really* frustrated that Mastodon doesn't have conversation_id legacy support! Oh! Why! What an interesting post! I wonder what post it's in response to! Oh? It's a Mastodon user? I can't figure out who they're talking to?
My fellow Mastos, I highly recommend hanging out on this side of the fence for a bit and you'll quickly have empathy for everyone upset about interoperability issues.
- ghostDancer likes this.
- 御園はくい and Cristóbal repeated this.
-
@shel welcome to the outside of the cave
-
@shel is a brilliant scientist who is, for whatever reason, forced to investigate the fediverse from a mastodon instance. They specialize in the networking protocols and acquires, let us suppose, all the physical information there is to obtain about what goes on when someone makes a post, or replies to a thread, and use terms like 'groups', 'no caching remote media', and so on. They discover, for example, just which word combinations from the post stimulate the Wernicke's area, and exactly how this produces via the central nervous system the contraction of the finger muscles and pressing on the keys that results in the posting of the sentence 'gnusocial does what mastodont'. [...] What will happen when @shel is released from their mastodon instance or is given an account on plateia? Will they learn anything or not?
-
@shel Are you sure it's Mastodon's problem, not GNU social's problem? ;) As far as I know…
I think it's second. It used to not be visible on GS, because there were simply a few very populated instances. If you had your own single-user instance that GS behaviour could make you mad, because you were sometimes missing 70% of conversation, when people unknown to your instance (not followed by you) were replying to someone (followed by you) taking part in same conversation as you do. One of the main features listed on Mastodon's GitHub is actually a fix for that problem.
> Federated thread resolvingIf someone you follow replies to a user unknown to the server, the server fetches the full thread so you can view it without leaving the UI
Now, with 1000+ Mastodon instances, many of them somehow connected to GS, that problem (or feature, how some people call it) is just much more visible.