I have a #Fediverse #ActivityPub question:
-
I have a #Fediverse #ActivityPub question:
Why doesn't my client ( #mastodon or #pixelfed ) automatically load the comments from the original page so that all comments are visible?
Is there a technical reason? -
I have a #Fediverse #ActivityPub question:
Why doesn't my client ( #mastodon or #pixelfed ) automatically load the comments from the original page so that all comments are visible?
Is there a technical reason?@treefit that would overload the server with too much information, unfortunately.
-
B beaware@social.beaware.live shared this topic
-
@treefit that would overload the server with too much information, unfortunately.
@beaware@social.beaware.live @treefit@fosstodon.org yes and no. I'm working on a solution for this.
NodeBB for example will automatically do this (providing the other end supports it). When posts are retrieved from NodeBB to NodeBB the entire topic is visible.
-
-
@treefit that would overload the server with too much information, unfortunately.
-
@eigenstil @treefit correct.
Fediverse works by follow relationships on an instance basis, meaning if a user on another server isn't followed by anyone on your server, none of their posts will show up. So it requires someone on your server to follow the "replier" on the other.
Hope that makes sense.
-
@beaware@social.beaware.live @treefit@fosstodon.org
The individual replies would be fetched from their original server. I just tested a random Mastodon post with 12 replies, and it was split 3 on mstdn.social, 3 on mastodon.world, 2 on mastodon.social, and 1 each on mstdn.ca, social.esmarconf.org, infosec.exchange and todon.nl - so no one server should get too many requests (and the more replies from one server a post has, the more likely that server can cope with the traffic.
-
@eigenstil @treefit correct.
Fediverse works by follow relationships on an instance basis, meaning if a user on another server isn't followed by anyone on your server, none of their posts will show up. So it requires someone on your server to follow the "replier" on the other.
Hope that makes sense.
@BeAware @treefit Yes, that's easy to understand, thanks for the explanation.
Basically this means, I/my instance only sees comments in a thread, from people that are "known" to my instance (because someone on my instance is following them) or they have an account on my instance. Otherwise I have to take a look at the original post on the original instance.
Right?
PS: I suppose some apps (maybe #Fedilab) initially pull all comments together from all instances. But I'm not 100% sure.
-
@BeAware @treefit Yes, that's easy to understand, thanks for the explanation.
Basically this means, I/my instance only sees comments in a thread, from people that are "known" to my instance (because someone on my instance is following them) or they have an account on my instance. Otherwise I have to take a look at the original post on the original instance.
Right?
PS: I suppose some apps (maybe #Fedilab) initially pull all comments together from all instances. But I'm not 100% sure.
@eigenstil @treefit yep, that's 100% correct.
Some apps are able to see comments from original post, but that's because it's the client reaching out to the other server, not your server reaching out, if that makes sense.
-
@beaware@social.beaware.live @treefit@fosstodon.org
The individual replies would be fetched from their original server. I just tested a random Mastodon post with 12 replies, and it was split 3 on mstdn.social, 3 on mastodon.world, 2 on mastodon.social, and 1 each on mstdn.ca, social.esmarconf.org, infosec.exchange and todon.nl - so no one server should get too many requests (and the more replies from one server a post has, the more likely that server can cope with the traffic.