Comment on we need more users
gandalf_der_12te@discuss.tchncs.de 1 week agoso you are saying that each author should represent their own community that they populate with posts each time they post something
Comment on we need more users
gandalf_der_12te@discuss.tchncs.de 1 week agoso you are saying that each author should represent their own community that they populate with posts each time they post something
rglullis@communick.news 1 week ago
I am not sure whether “represent” is the right word here. What I mean is that all posts have a “recipient” (the audience).
For Mastodon, you have public posts where the recipient is literally a “special” audience, called
https://www.w3.org/ns/activitystreams#Public. If you want to see a private message to alice, you just change the “audience” to contain only thehttps://example.com/aliceactor URI.To post to a community, it’s the same logic: if you are posting on
fediverse@lemmy.world, then the message has “lemmy.world/c/fediverse” as the audience. This message is then sent to lemmy.world and processed.gandalf_der_12te@discuss.tchncs.de 1 week ago
Ok, so from a user’s perspective, where would Mastodon content appear in your Lemmy feed?
rglullis@communick.news 1 week ago
You do understand that I am describing a whole different client, right?
There is no “Lemmy Feed”, just “posts sent from individuals to a group” vs “posts sent from individuals that are broadcasting without any specific audience”
How this presentation layer would work would be entirely up to the developer/user. I can envision people that might prefer to have a separate threaded-view for group posts like we have in most forum sites, but I can also envision people that will prefer each post appearing in a “feed”, like what Facebook does for groups. I can also envison such an application providing a “image gallery” for people tthat want to see only pictures, like Vernissage does.
My point is, it would be completely up to the user how to see the data.