3 ms·
> Bonus: I add another link to each toot that opens it in the instance of its author, where I have access to the full reply chain, of which my own instance ofte
by mst 3y ago
> Bonus: I add another link to each toot that opens it in the instance of its author, where I have access to the full reply chain, of which my own instance often captures only a subset. A very simple solution to one of Mastodon’s unfortunate limitations that are due to federation.
I ... would not have expected this to be the case.
However, as per https://github.com/mastodon/mastodon/discussions/22608#discussioncomment-4775167 https://github.com/mastodon/mastodon/discussions/22608#discu..., I can see how it ended up that way and while it'd be nice if something triggered an on-demand fetch as discussed by other people later on, that can be added Later(tm).
- chrisnight 3y agoThis is definitely a primary problem with Mastodon and other fediverse software. However, I will mention there is a problem with the idea of fetching replies from the parent post’s home server that makes it hard to solve. The primary idea being that a user trusts their home instance, but don’t necessarily trust other instances. If you fetch replies from another server, you are trusting that server to send you real, valid replies, from other servers. You could verify the replies, but this would be an expensive operation to do automatically. As such, a malicious server could create phantom replies that don’t actually exist, and your trusted, home server would serve these to you. Currently, your home server only shows likes and replies it can validate (it heard it from the server that did it), but once you trust another server, you add a unnecessary middle man for some extra convenience