this post was submitted on 03 Jan 2023
19 points (100.0% liked)
Lemmy
12538 readers
4 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is a really good question.
For micro-blogging, the only one of those that's internal to your service, is "boosts". The equivalent for lemmy, would be cross-posts on communities you already follow, where the url field is either your local copy, or the federated link. Someone would x-post a link from another community, you'd see it, then subscribe to it.
A better answer to your question tho, would be a global community discovery service. Someone could either write one, and @nutomic@lemmy.ml has also written a lemmy-instance-crawler for join-lemmy.org to do the same. We could also potentially expand what join-lemmy.org shows, to list the most popular communities globally, and for each instance.
Since communities aren't tagged, the only real way to look through them would be by popularity tho. But it would at least be a centralized place to see every known community on every known instance.
Lemmy is way better than Mastodon for content discovery, which is one of the biggest reasons I wish that lemmy supported "self-posts", i.e. posting to your own timeline.
being able to cross-post "mastodon-like content" directly on lemmy would really help content discovery, make attributions simpler, and make lemmy the undisputed champion of the fediverse!
You might want to look into kbin then. It includes both.
I went from thinking "Why on earth would you want self posts?" to "Wow, how does lemmy not already have self posts, they would be a killer feature" as I read your post :)
<3
The cross-posts for a given post are not federated. This means you will only see cross-posts in cases where you or someone else on your instance already follows the communities where it was posted. So they dont help for discovering content on a new instance.
Any reason for this other than "didn't think about it"? It seems like a great way to help newer/smaller instances discover content that is on unknown instances.
Crossposts are only implemented in the frontend (using search afaik). The backend doesnt know anything about this concept and so cant federate it.
I've love to see a third party search that shows communities by name, instance and subscriber count!
It doesn't have to be a full text search of the contents, just a searchable listing of communities!. Combine that with the ability to configure my own instance in settings on the search site. It would let me click on a link in the search results and be redirected back to my own instance, ready for a single click subscribe to the remote instance!