Yesterday I posted about rss.ponder.cat, with communities automatically fed from a selection of RSS feeds. Today I made !meta@rss.ponder.cat, with:
- A sticky-post roadmap of the RSS feeds that are already available
- A place for people to request communities to be added
- A place for me to post announcements about new communities
I don’t plan to spam !newcommunities@lemmy.world with every new RSS feed, but I figured I would let people know the location of the community that will get announcements about new RSS feed communities, in case they want to subscribe to it.
Cheers!
Yeah this doesn’t make much sense to me either. The sudden influx of duplicate posts across Lemmy over the last couple of days makes it seem a little weird.
Can you give some examples? I don’t want it to become botspam. If the RSS bot is creating duplicate postings, then I may need to fix or adjust something.
Speaking as the operator of u/Auto_Post_Bot@social.packetloss.gg … I think it’s kind of inevitable with the current design of lemmy for folks that browse “all” instead of subscribed … and in some cases local.
As an example, Auto_Post_Bot posts news post to !zed@lemmy.world and !zed@programming.dev (the latter is recent per request from the admin over there, as they don’t want centralized communities)… So if your instance is “subscribed” to both, it’s going to be a “duplicate” post in the “all” feed.
On lemmy-ui if both posts are both “visible” in the feed they will be compacted into one post if they share the same link meaning there wont be a duplicate post (unless you paginate and theyre on different pages)
Some other frontends such as sync dont do this though but they really should
That’s kind of a strange design choice itself because it means that one community is kind of “hidden” … but only sometimes.
Very interesting though, thanks for sharing that.
The links to the other posts show up below in a cross-posted to section so you can still access it if you want. The limitation on it needing to be the same page comes from this handling happening on the frontend instead of the backend. Ideally imo backend should handle it like how it handles the cross-posts displayed when looking at the post itself
Yeah, I’ve been thinking it might make sense for Lemmy post to be … almost “tabbed” when they’re link post. So if the link for several different posts is the same you end up with “tabs” for the other communities, that swap you between the titles, descriptions, and comments sections from those communities (and possible a “merged”/“all” tab that lets you see comments from all communities).
Probably a toggle somewhere for “just communities I’m subscribed to” vs “all communities my instance knows about” as well.
I’m not sure how exactly to make that look pretty, but I’m confident it can be done.