Me: "It's bad and confusing to users that Mastodon doesn't show you all replies to a post (including from accounts or servers that you or your server didn't block)"
Mastodon stans
Me: "It's bad and confusing to users that Mastodon doesn't show you all replies to a post (including from accounts or servers that you or your server didn't block)"
Mastodon stans
@jsadow Same reason, if no one on your server follows someone on the server a post was made on, you'll never see replies or search results from it.
@thomasfuchs I still can't figure out why the search function doesn't find all of the hashtags on all non-blocked servers 🙄
@thomasfuchs I don't know where you got the Question Dog edit, but I am totally saving it.
@jan It’s not eventually consistent though, replies from server C just aren’t visible to people from server A looking at a thread from server B, if no one from server A is following anyone on server C
@thomasfuchs Designing a distributed system is a trade-off between strong and eventual consistency.
Mastodon is eventual consistency, meaning the network offers high availability but possible temporary inconsistency.
Thats the reason why you see same answers from different people from different instances.
A system which supports ACID transactions must choose a form of consistency as framed by CAP.
@jan Yeah, as I said, it's broken. :)
@thomasfuchs For transitive relations between servers you have 3 options:
1) Eager loading: You replicate and cache lots of posts, server admins complaining about storage.
2) Lazy loading: You load the posts on click, it takes time, users complaining about UI/UX.
3) No loading: Just a subset of posts gets loaded, admins are happy and users complaining about missing posts.
Current solution: You open the thread on the original server.
Needless to say, we have lots of room to improve. 🙂
@fuzzykb I made it, you're welcome to use it
@dheadshot not if you're looking at replies on a post on server B and no one from your server (A) is following anyone on a reply from server C
This predominantly affects people from small or personal instances -- making Mastodon essentially unusable because you can't read threads
@thomasfuchs
I thought it did?
@dheadshot I’d love an “unfuck thread” button in Mastodon 😂
@thomasfuchs Oh, there! Fedilab 2.x breaks the spec and fetches them anyway and the latest version has a button to do that, so I rarely have that issue, but I can see how it causes problems for most users...
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.