

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.
We have been blocking requests with empty user agent for a long time, its odd that it would stop working now.
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).
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?
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.
Ah its more complicated than I thought. We also have a similar or same feature on the roadmap, when I get to that it can federate with Piefed.
Neat, it federates. Seems to work similar to a normal community, so it should be easy to follow these feeds from Lemmy.
Originally account deletion would always delete your posts, comments and everything. This was changed in 0.19 to make the content deletion optional (otherwise a lot of posts and comments would disappear unnecessarily). Unfortunately we forgot to add the new option to the user interface for 0.19, but it was added probably around 0.19.4.
Its hard to say why the federation didnt work properly, maybe there was a network error, or a bug in older Lemmy versions that got fixed in the meantime. Or there is still a bug which only happens in some cases.
You may be running apt upgrade
in another terminal, or it didn’t complete properly in the past. Anyway it cannot install packages so you need to fix that.
When deleting the account did you mark the checkbox “Delete all posts, comments and uploaded images”? Lemmy.world is running an old version so its possible that this is missing. Without that it is expected that only the profile gets deleted, while content is still available.
As for federated account deletion this is implemented and covered by test cases and should work in theory. However it is always possible that there is a bug. It would be helpful if you could open an issue with exact steps to reproduce. Use enterprise.lemmy.ml and ds9.lemmy.ml to test the latest version.
NLnet. However they only fund specific types of projects, and there are many open source maintainers who are not interested in money (usually they have a well-paid job already).
That would take a significant amount of work to implement, and we dont have the resources for it. But all the code is open source, so youre welcome to give it a try yourself.
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.