o7

No probs!

Erps, my bad.

With a few more additions, lemmy could serve as a good replacement. We already have a Forum / NewComments sort which is perfect for question / answer type communities. We could add a feature to make default sorts for specific communities, so they would feel less fast, or possibly a sort that brings zero comment posts (IE meaning unanswered), to the top.

The reputation and “accepted answer” features from SO are a lot less important than threaded comments can be, especially since questions often need new answers every year, making the “accepted answer” pointless.

To update everyone:

In getting ready for the upcoming lemmy release, we usually deploy a test release here on lemmy.ml (the dev instance) for a few days, to discover any issues for a large production server, so other people don’t have to.

We found a performance issue with this one, so we downgraded back to 0.19.3, and restored from a database backup made a few hours ago.

I apologize for the few hours of downtime that caused today.

Okay we’re back! Sorry about the downtime, was ~40m.

If they are banned from that community, they won’t be able to post.

Federating instance bans is a separate thing for far later on, but I recently added a “hack” that bans you from communities local to the instance you were banned on, and those should federate.

Everyone should see how incredibly important this project is, and its potential. Wikipedia is yet another US-controlled and domiciled site, with a history of bribery, scandals, and links to the US state department. It has a near-monopoly on information in many languages, and its reach extends far outside US borders. Federation allows the possibility of connecting to other servers, collaborating on articles, forking articles, and maintaining your own versions, in a way that wikipedia or even a self-hosted mediawiki doesn’t.

Also ibis allows limited / niche wikis, devoted to specific fields, which is probably the biggest use-case I can see for Ibis early on.

Congrats on a first release!

The thing that really gets me with these, is that we are 2-4 devs working on software used by over 40k ppl. It is absolutely impossible to please everyone, and fix every issue, there just isn’t enough of us.

Oftentimes we ask for ppl to do the open source thing, and contribute a PR, and many of them do.

Anyone can look at our github profiles and see how busy we’ve been, and how many moderation related issues we’ve been working on, this is all out in the open. Yet writers of these articles somehow never bother to look, or reach out to us for questions. The amount of entitlement and second-hand rumors is really dissapointing.

No probs!

We’ve talked about it elsewhere, on github and one of these Q and A’s, but the main thing is that these things can be easily gamed. IE: making a ton of fake users to vote for a malicious mod.

There’s a ton of ways that could be exploited that I can’t think of rn. I’d rather not stress test them in lemmy.

Mostly recharged from that now.

To add, lemmy.ml’s entire DB compressed as a xz with -0 strength is about 3.7 GB. But that also includes the activity tables which aren’t vital.

There are open issues to see report counts, and view all reports for an item. They’ll likely be finished this year.

To me, AGPL is the most pragmatic choice. As a hard copy-left license, it enforces derivative works to adopt the same license, unlike the more open and “soft” copy-left licenses that let corporations capture and digitally enclose your labor as they see fit.

We’re no different from 99% of open source projects: there are a lot of one-off contributors that just do a feature or two they’d like to have, but the vast majority of work is done by a handful of core devs. This is why you should always base your infrastructure and decisions to support those devs, rather than cater to one-off contributors.

We could definitely use some help with ideas there. Lemmy currently has ~40k active users, and it should be able to support more than ~1 average dev salary, especially if we want to take on a multi-billion dollar company with hundreds of employees like reddit.

Its unfortunate that we (and it seems like 99% of other Rust projects), do their issue tracking on github. We have multiple mirrors set up for Lemmy, so the code is safe from takedowns, but the issue tracker is a concern.

The main issue I’ve had is: if we migrate, I want that migration to be permanent, and for me a requirement for that is federated collaboration. I’ve had codeberg remove a torrent project of mine to comply with German law, and gitlab has most of the same problems of github. Self-hosted gitea instances work, but many people just don’t contribute to them when they have to make an account on each one.

You’ll see below that Lemmy’s two main devs are in favor of migrating our issue tracking to forgejo, once federation gets reliably up and running.

I’d also be in favor of moving to Forgejo once federation gets fully functioning, and reliable.