I know that many people don’t like complex or intransparent recommendation algorithms.
Currently, there are “subscribed”, “local” and “all” categories (at least in the default lemmy web UI).
I would like to change this to include custom topics (“listings”). They are a custom way of choosing content (in case of Lemmy listings). In Lemmy, custom listings appear just like standard listings (API-wise), just that instead of “https://discuss.tchncs.de/?dataType=Post&listingType=Subscribed&sort=Active” you have “https: //discuss.tchncs.de/?dataType=Post&listingType=list:[email protected]&sort=Active” or something.
Listings could either be lists of communities and other listings. Consider this simple text file to describe a listing for a memes-topic: (that contains 2 communities, everything on 1 domain, and another sub-listing)
c:[email protected]
c:[email protected]
domain:memes.net
list:[email protected]
Or they could take their data from an RSS stream or similar external source.
Multi-communities are already completed in the back-end, and front end will be done shortly.
thanks! are multi-communities anything like sql virtual tables? i.e they appear as one community to the reader, but are the result of querying multiple communities
No they don’t use sql views, they’re built using an in query (which we still have to see how performant that’ll be, and is pretty much the same problem as subscribed communities, needing to sort and filter based off joined data)
You can see them in action here: https://github.com/LemmyNet/lemmy-ui/pull/3521
thanks!