Skip Navigation

Posts
111
Comments
902
Joined
6 yr. ago

  • Its hard to say because these things always take longer than expected. Now we are finally getting to the point where all the breaking database and api changes are almost finished. After that it will take some months to update lemmy-ui for all the backend changes and new features, and the same for all other apps. Then a testing period to fix all the problems that come up. So maybe around autumn for the final release, although lemmy.ml and some other instances may upgrade some months before already.

  • 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.

  • 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.

  • Thanks for the heads up, I applied it to lemmy.ml just now.

  • Youre welcome! This are only some very minor changes, because the development branch has diverged a lot from 0.19, so larger backports are almost impossible now.

  • Yes exactly, only some minor backports.

  • Some of these will be available in Lemmy 1.0:

    • #5478: different community visibilities, including Unlisted which is not included in All feed, and Private (only approved followers can view/post)
    • #5038: some more site settings for voting
    • Plugins RFC: allows arbitrary restrictions for voting and posting
  • Permanently Deleted

    Jump
  • 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.

  • Permanently Deleted

    Jump
  • 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.

  • 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).

  • Normally you can paste the blog url directly into the rss reader and it will find the feed automatically.

  • 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.

  • It seems to work fine, maybe its because your instance is outdated.