Its similar to Lemmy in many ways, so like Lemmy posts are redundantly mirrored across instances, the same is true for Ibis articles.
Getting Wikipedia federated would be great, but it will take a long time for Ibis to be ready for that scale.
Lemmy maintainer
Its similar to Lemmy in many ways, so like Lemmy posts are redundantly mirrored across instances, the same is true for Ibis articles.
Getting Wikipedia federated would be great, but it will take a long time for Ibis to be ready for that scale.
For now my focus is to make it federate with Lemmy and the rest of the Fediverse. But you’re welcome to open an issue for that kind of feature.
Lemmy’s AGPL license doesnt allow forking the code into a proprietary server. All changes need to be open source as well, otherwise the operator can get sued. So a proprietary Lemmy software would have to be developed from scratch which would take a long time.
Thanks for linking my project. Im happy to answer questions about it. Also here you can find the git repo.
Maintainership of a free software project can be very taxing so it’s refreshing to see attempts to address that that aren’t intrinsically at odds with the free software movement. Remember that users of free software have no entitlement to anything other than source code. There is no requirement in any free software license that a project have maintainers, take bug reports, accept pull requests, offer support, etc.
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.
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.
This is my second baby, the first one is three years old. So in my experience it’s much more fun once the child can go to the playground, starts to talk and gradually learns to do things independently. Though there are also difficulties, and of course every child is different.
Twinkle twinkle little star. It’s neat because there are versions in almost every language.
My baby celebrating her first birthday. Soon she will be able to start walking and eat normal food, so it will be much less effort to take care of her.
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).
Normally you can paste the blog url directly into the rss reader and it will find the feed automatically.
Funny, as a German speaker who learned Spanish its exactly the other way round. Here people already start responding to what you say before you can finish the sentence. And generally people love to talk very fast.
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?
There is an API so you could write a script to import any kind of data.