reposting here b/c people were wondering: the COMPLETE list of paths to get something into the federated timeline Show more
@nightpool oh cool, so in fact the toots number could actually just be numebr of times this user has done something someone on your instance liked. Does that apply to followers in some way as well? It's so maddenly complex and subtle, I love it.
@rateldajer yes, it's just followers on your instance in the web app, as far as I know. it might request follower numbers at some point?
reposting here b/c people were wondering: the COMPLETE list of paths to get something into the federated timeline Show more
@trwnh I understand this, but the thing I was talking about is something else.
the specific behavior here is:
- User A@A makes a post (1)
- User B@B replies to post 1, making post (2)
- I'm user C@C, and I follow user B, so *post 1* appears in C's federated timeline. post 2 doesn't because it's a reply.
You can see how that may be confusing?
@nightpool i suppose but it's no big deal. you can unhide replies, really the most you can say is that a@a shows up in c, it's a lone tweet, that's kinda the point of crawling the federated timeline in the first place
@nightpool like... lemme put it this way. why would you stop a graph search before reaching the end of a path? it's not a bug, it's just a quirk
@trwnh No, but the intuitive user understanding of the federated timeline is that it is *only* second degree connections. (A shares a server with B who follows C) This breaks that.
@nightpool that's not at all implied nor is it something i ever thought to assume. why wouldn't 3rd-degree connections be included? even linkedin does 3 degrees
@trwnh it IS a big deal, because it's a third degree connection (I might not even follow B—just someone on my server has to), and it breaks the user's expectations for what the federated timeline should be.
@nightpool the federated timeline is all known messages from all known users on all known instances
what other expectation is there?
@trwnh there are so many ways that messages can get "known" that this is impossible for users to understand though.
Second degree connections is an easy affordance that makes the software comprehensible.
@nightpool @trwnh got it. maybe there should be a rule that once a post is pulled on then all other related posts subsequent to it that are available from instance.....?.?.?...A also get pulled over.
To be clear, everything except the first option only loads ONE status ONE time—not the entire feed of that user.