

It is an issue for the open source projects discussed in the article.
Lemmy maintainer
It is an issue for the open source projects discussed in the article.
Cache size is limited and can usually only hold a limited number of most recently viewed pages. But these bots go through every single page on the website, even old ones that are never viewed by users. As they only send one request per page, caching doesnt really help.
Some of these will be available in Lemmy 1.0:
Unlisted
which is not included in All feed, and Private (only approved followers can view/post)We have been blocking requests with empty user agent for a long time, its odd that it would stop working now.
Even if we sold out, at most they could get control over lemmy.ml and the git repository. Other instances are under no obligation to upgrade to new Lemmy versions, and could switch to a forked project if needed. The vast majority of Lemmy isnt under our control at all (which is the major difference compared to Reddit).
I also use Freshrss (version 1.24.3 via Docker). Tried a feed from lemmy.ml just now and it loads without problems.
There are no specific requirements, it seems the upload simply failed. Try to upload again, and if it doesnt work contact your instance admin.
This will be implemented in the future.
Can you check what user agent is used to fetch the rss feed? We blocked empty user agents as well as names of different bots due to AI crawlers.
There is also a button for “view source” on the website (between downvoted and reply).
The documentation will get much better with 1.0
Are you logged in on those instances? Resolving a community name like that requires a network request, if you are not logged in it doesnt work.
Not sure how this works, anyway Ive set it up. I assume the bot login is required in order to auto-fetch remote communities to lemmy.ml?
It seems to work fine, maybe its because your instance is outdated.
Good point about the url search, I made a fix for that.
Not sure what exactly you mean with the community search. For example this query shows a couple of relevant communities.
Opened an issue: https://github.com/LemmyNet/lemmy/issues/5458
Hmm so the Feed
actor mainly consists of a following collection and uses Add/Remove activities. This really sounds like it should be a Collection
and not an actor.
Opt-out on the other hand for public feeds specifically is something that I support. But then good luck having that supported on lemmy where almost all communities exist.
Lemmy already has a setting community.hidden
so that communities dont show up on the All feed. But this is not easy to access at the moment. I can fix that.
This proposal could totally backfire though. There will be users paying 5 Euro per month and then demand on the issue tracker that major changes get implemented overnight. Or people who contribute with good bug reports that are unable to pay money, so problems remain unfixed. There might be a way to balance things so it works out, but that will take time. In any case its worth experimenting with different approaches to get open source betterfunded.