Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.
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.
Sorry, fixed
It doesn’t take calls for murder or genocide. In Germany you can have your house raided for posting a meme which calls the minister of economy an idiot. The same minister of economy who doesn’t know what a bankruptcy is, and whose entire working experience is as an author of children’s books.
In another case the office of an opposition newspaper was raided, all their computers and even office chairs were taken away by police. All under the pretense that it was an ordinary association and not protected by freedom of the press. However courts found that this was unjustified, and so police had to carry all the items back inside a few days later.
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).
I havent noticed any problems with instability, at least for web server development it is stable enough. But it may be different in other contexts like embedded. And its true that many libraries still have 0.x versions.
??? Rust 1.0 was released 10 years ago and since then there have been no breaking changes.
Mainly SEO spam with text copied from other sites and lots of ads/referral links to make the owner a profit. But after thinking about it more, those would be rather easy to filter based on ad code in the HTML.
A much bigger challenge will be the ranking of search results. When searching for a term and there are 100 pages in the index that contain it, which of these pages should be shown first? Google developed the Pagerank when they started out, so that might be a good starting point to research further.
This sounds like a very interesting idea. I agree that Yacy doesnt work, when I checked it out years ago it was a completely bloated mess. Not sure how viable how your idea is, because Im not familiar with webrings, and not sure how the federation will work. Anyway the main challenge for this project will be to actually give useful search results, both early on when there are very few crawlers, and also later once spammers try to abuse it.
Funny, Mastodon just posted a similar thing about creating a foundation. But the problem is, the existence of a foundation does nothing to prevent billionaires from controlling social media. For billionaires its very easy to donate a few hundred thousand USD to the foundation and gain influence that way. I expect that Bluesky will be fine for the first years (maybe like early Twitter), but sooner or later the foundation will take decisions that the users dont like, and there is nothing they can do about it.
In my view, the only way to avoid influence from billionaires is to avoid any large centralized structures. In the Fediverse there are dozens of platforms and thousands of instances. Even if a billionaire were to take control over a couple of projects or large instances, people would create forks in a matter of days. Some admins would block these corrupted instances, and their users would barely notice that anything changed.
So Bluesky is just trying to repeat something that has already failed. The Fediverse is the future, but it will take a long time for most people to understand that.
Sounds like you are familiar with this topic. I dont have time to work more on this particular aspect (there are lots of other tasks like comment support, federation with Lemmy, etc). But contributions are definitely welcome, preferably directly to leptos_use
so that others can benefit and its easier to maintain.
It uses the browser preference for light/dark theme by default. After you click the theme toggle on the site, it keeps using that chosen theme by storing it in a cookie.
Seems unlikely, but maybe it will happen in many years if Ibis shows that its possible and desirable.
Right I will also have to make a template with these common parts of the release announcement. Instance blocking is not implemented yet, but it uses the same federation library as Lemmy so that will be easy to add when its needed.
I would be happy to give an interview, but so far no media seems particularly interested in Lemmy.
The network is called Fediverse. I don’t see the need for a separate term, there also isn’t a “Tootiverse”.
Thanks that is a bit better. Unfortunately people who have already read the article wont see the update, and even people who read it now may not read all the way to the end, and still leave with a negative impression. Still its better than nothing.
To get an idea how most Lemmy users feel, have a look at this thread. Practically every comment is positive about Lemmy, you can hardly find any negative sentiment. And certainly no one cares about this image deletion issue, which proves that the complaints of a few individuals are completely blown out of proportion.
We don’t have the capacity to implement all the features users ask for, at least not without additional contributors or waiting a long time. So it’s better to implement it as a bot.
The cleanest solution seems to be the one described in my previous comment, so you get an archived community with all the original content, correct usernames etc. And make a new community for new posts. Or have the bot create new posts and comments with the same content, and credit the author in markdown body. But that seems like a worse solution in many ways.