|
Top-level
@Silv @gracjan @fishcharlie @nf3xn > This is a quirk of ActivityPub, not specifically Mastodon. There are currently projects in the works to remedy this, and I think a few fediverse software already fix this behavior using server side workarounds. Is this issue currently solved in Lemmy? 3 comments
@falcon @gracjan @fishcharlie @nf3xn Update: It appears that Lemmy solved this issue. On Mastodon the user is considered the first-class actor, but on Lemmy the community is the first-class actor. Communities send a public announce whenever they are interacted with. This allows remote instances that are federated with the community to have full visibility of all posts, comments, and interactions from remote users. @falcon @gracjan @fishcharlie @nf3xn Technical goodness: Oho, I found this well of knowledge. it's a great read if you want to get into the nitty gritty weeds of how Lemmy federation works. The devs did a great job with the architecture of Lemmy, even if the user experience can be a bit strange at times. https://join-lemmy.org/docs/en/federation/lemmy_protocol.html |
Gregory's Server
@falcon @gracjan @fishcharlie @nf3xn
I think Lemmy solved this, but there are not enough federated activity to make this apparent to me.
The documentation has significantly improved since I last attempted to run a Lemmy Instance. You may find some of your curiosities answered here: https://join-lemmy.org/docs/en/introduction.html
I'll update this thread after I do some testing and find a conclusive result.