500 Internal Server Error - Beehaw
beehaw.org

I’m sure people here can empathize with having all the tech wizards get burnt out and leave, and all the various teething problems but this is a bit much… lemmy has its issues but plenty of sites larger and smaller than beehaw are getting on just fine. Perhaps the lib sysadmins are just going back to brunch?

  • pooh [she/her]@hexbear.netEnglish
    1·
    1 year ago

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

    Sounds like they don’t like federation and just want to isolate their own instance. Why couldn’t they just defederate instead of going through the process of migrating to another platform? Is it really that difficult to do?

    EDIT: Thinking about this a little more, it seems like the admins (or admin?) have a very specific idea of the kind of community they want, and are getting frustrated when everything isn’t perfect to their vision, whether that’s lemmy code or other instances they are federated with. Then they complain and contribute nothing towards making the fediverse better. I guess what I’m saying is that they really do seem to want a walled garden that’s perfect to some idealized community that only exists in their heads, and I don’t think communities really work like that.