Communities not existing on all instances is a big problem.
Fediverse
23
Beiträge
13
Kommentatoren
0
Aufrufe
-
I love this leave it up to the individual. Someone who knows how to code please do this.
Piefed feeds: https://lemmy.dbzer0.com/post/38733273
A few options
- https://piefed.social/ - flagship instance
- https://piefed.zip/ - lemmy.zip team
- https://piefed.ca/ - lemmy.ca team
- https://feddit.online/
-
Piefed solves that issue: https://piefed.zip/post/100161
All comments from 5 crossposts in a single view
A few options
- https://piefed.social/ - flagship instance
- https://piefed.zip/ - lemmy.zip team
- https://piefed.ca/ - lemmy.ca team
- https://feddit.online/
There's also the pretty new: piefed.blahaj.zone
-
There's also the pretty new: piefed.blahaj.zone
Indeed, thanks!
-
Example, Lemmy.ml and Lemmy.world have duplicate communities aren't connected at all. So we are artificially isolating groups more and making it confusing for would be converts.
Short and too the point
One of the things that I'm experimenting with is to have "communities that can follow communities". So, if community A follows community B, then it can re-post anything that has happened on Community B.
If you do it "properly", it doesn't even need to be a lot of data duplication because the "follower" community would just be creating
Announceactivities.The only thing that is making me hold out on this experiment is because I am 100% sure that some people will see their posts on a community they never interacted on and they will panic on the grounds of "mah privacy" or something silly like that.
-
oh thank you for this. That helps that specific issue.
Federation fixes most of it. I can follow the big community that's become the main one and still the smaller ones with their own focuses and views.
-
One of the things that I'm experimenting with is to have "communities that can follow communities". So, if community A follows community B, then it can re-post anything that has happened on Community B.
If you do it "properly", it doesn't even need to be a lot of data duplication because the "follower" community would just be creating
Announceactivities.The only thing that is making me hold out on this experiment is because I am 100% sure that some people will see their posts on a community they never interacted on and they will panic on the grounds of "mah privacy" or something silly like that.
How would comments happen? Would they not get back to the original poster?
-
One of the things that I'm experimenting with is to have "communities that can follow communities". So, if community A follows community B, then it can re-post anything that has happened on Community B.
If you do it "properly", it doesn't even need to be a lot of data duplication because the "follower" community would just be creating
Announceactivities.The only thing that is making me hold out on this experiment is because I am 100% sure that some people will see their posts on a community they never interacted on and they will panic on the grounds of "mah privacy" or something silly like that.
Hi! We should chat.
NodeBB also does this, and currently still does. A category (group actor) can follow another category (also a group actor).
It essentially is synchronization of categories using 1b12.
Proof of concept does work but it needs reworking in some ways. The largest issue is that Lemmy itself doesn't understand when a group actor tries to follow a community.
-
How would comments happen? Would they not get back to the original poster?
Sorry, but this will be a bit too technical...
The thing is that Lemmy (at least, others probably do the same) don't treat the Linked Data as the canonical representation, they work by translating every message with an as:Activity to their own internal representation in the database (with separate tables for
Posts,Comments andPrivateMessages).This means that all it takes for a Lemmy instance to treat a post as "new" comment is to produce an "as:Announce" attributed to the "follower" community, and then all instances will process it as a new post/comment/vote.
-
Sorry, but this will be a bit too technical...
The thing is that Lemmy (at least, others probably do the same) don't treat the Linked Data as the canonical representation, they work by translating every message with an as:Activity to their own internal representation in the database (with separate tables for
Posts,Comments andPrivateMessages).This means that all it takes for a Lemmy instance to treat a post as "new" comment is to produce an "as:Announce" attributed to the "follower" community, and then all instances will process it as a new post/comment/vote.
Alright, so
- A - Origin community
- B - Other community
- C - following community of A & B
User posts to A, a "as:announce" on C is generated. A user replies to the post on C. Will user A see the reply? Will someone looking at the post on A see the activity on C?
-
Alright, so
- A - Origin community
- B - Other community
- C - following community of A & B
User posts to A, a "as:announce" on C is generated. A user replies to the post on C. Will user A see the reply? Will someone looking at the post on A see the activity on C?
Yes. When the reply is posted to C, it is sent to A. A then sends
as:Announceto C, as well as any other communities that follow it.B seems to be irrelevant here.
