There is a lot of discussion happening in the background of our project here. We could not anticipate all of the challenges that we were going to face a few years ago. One of the reasons for this was because we had no idea what our choice of a platform would bring.

Specifically, we chose Lemmy as the software that we would use to launch our endeavor to attempt a safe space for marginalized persons online.

In the first year or so, this choice was completely successful for a very small number of users. And then we all experienced an enormous influx of users when Reddit announced/implemented their shutting down of third party apps.

Since then there has been a huge number of people that have joined the Beehaw project. This tsunami of users initiated technical problems, and otherwise, that we could not foresee.

Thankfully and fortunately, we have had a couple of incredibly knowledgeable persons that have swooped in to ’save the day’ and keep this site running.

Unfortunately, these persons will NOT be able to continue to support the Beehaw project much further. They have life commitments and other factors, including careers and family life, that will prevent them from contributing to our project in an ongoing fashion.

All that being said, Lemmy (the software that Beehaw runs on) development is incredibly slow and is riddled with problems that makes administration/moderation very painful.

Therefore, we are left with some options that may feel uncomfortable to us. For example, we may want to consider leaving the Fediverse for another software platform that does NOT include ActivityPub. To explain, Fediverse/ActivityPub are very positive concepts on the foundational level. However, the Beehaw project is struggling to include this because most of our moderation/content/ethos is being jeopardized from OTHER federated instances (i.e. it, mostly, is NOT coming from within our own Beehaw registered user base).

The aforementioned persons, that have ’swooped in to save the day’, have been discussing/working with us to come up with the best solutions that would enable the Beehaw project to continue while NOT needing incredibly experienced/technically adept persons around.

Right now, we are testing alternative software platforms and evaluating them based on everything that we want Beehaw to become in the future.

Thank you all for your continued support of the Beehaw project and entrusting us to make this happen.

You are viewing a single thread.
View all comments View context
26 points

If there are moderation issues, wouldn’t it be easier to recruit more moderators?

No. The tools needed for successfully moderating Lemmy federated items, is severely lacking. The primary devs do not seem interested in making this area a priority either from their own efforts, or others submitting PRs for such. More moderators won’t help when the ability to moderate isn’t there.

permalink
report
parent
reply
8 points

Makes me wonder if a fork will happen in the future. Wonder if offerings will be much different a year from now, and if options like kbin will be more polished by then.

permalink
report
parent
reply
13 points
*

Everyone wants a fork. Nobody wants to be the fork.

We need a small group of motivated and skilled developers to get together and decide “we’re doing this”, and actually go beyond announcing an empty Git repo. (i.e. actually have some usable code to show for)

Dealing with a codebase as janky and large as Lemmy is unfortunately beyond my skillset, otherwise I’d love to get involved myself.

permalink
report
parent
reply
4 points

All fediverse code is weird. Lemmy is extra weird on account of being written in a systems language

permalink
report
parent
reply
4 points

Everyone wants a fork. Nobody wants to be the fork.

Rust and ORM makes changes incredibly slow and even recent editions like sanitizing for JavaScript exploits have been buggy.

We need a small group of motivated and skilled developers to get together and decide “we’re doing this”, and actually go beyond announcing an empty Git repo.

Lemmy had one major thing that kbin and other apps did not have in 2023… a working API. And that happened to be what Reddit decided to start charging for in May. Kbin is right now adding an API, but it isn’t compatible with Lemmy. Lemmy could also use a streamlined API, there is opportunity right now to make a combined Lemmy and kbin API since federation normalizes a lot of the features between the two. I hope people see this opportunity that is open right now and the one big strength.

permalink
report
parent
reply
8 points

I don’t think a fork would be a solution to this problem. The problem is not that the maintainers don’t accept contributions, but that no one is making the necessary contributions.

permalink
report
parent
reply

Chat

!chat@beehaw.org

Create post

Relaxed section for discussion and debate that doesn’t fit anywhere else. Whether it’s advice, how your week is going, a link that’s at the back of your mind, or something like that, it can likely go here.


Subcommunities on Beehaw:


This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

Community stats

  • 357

    Monthly active users

  • 767

    Posts

  • 18K

    Comments