• 7 Posts
  • 76 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2024

help-circle




  • I feel like this is an example of how the core dev team running on an instance that basically just has 3 of the admins do more or less all the moderation for the entire site is not ideal. This type of feature is probably one of the most-requested pain points for most people who run most servers, but my guess is that it’s basically completely invisible to the .ml team why it would even be needed, because their model works fine for them, so why would they.

    Of course they’ve got a right to work or not work on whatever they want, but if their goal is success and good moderation for most servers this type of scalability and teamwork enabling thing is super important.







  • Your “friend”, huh

    Stop acting in ways that violate the social contract and stuff like this will stop happening to you. I have no idea, but I strongly suspect that it’s exactly what it looks like: You’re blocked wholesale from the instances in question in some way which doesn’t show in the modlog.

    I don’t even really know how to trace back through all the hall-of-mirrors of what original behavior led to what drama led to what sanctions led to what further drama. Regardless, step 1 is to just openly ask, hey what behavior should I be doing, what should I not be doing. And then just go from there and cooperate with the other people on the network to do the first and not the second. Lemmy is pretty frickin lenient with anyone who is willing on some level to engage with that whole process openly.




    • I would give it a similar but distinct name, and just be aboveboard in the docs about where people can find the original project, what the differences are, and about what’s going on. As long as you’re open about what’s up I think it would be hard for any reasonable person to take offense if you prefer a less unixy style of output or whatever.
    • I would create an issue on the original project just explaining what you like and what you implemented in the new one, and saying you’re happy to contribute although the changes may not be wanted et cetera. Just be honest. You’re fine. More communication is usually a good thing.
    • git is powerful. It’s worth learning about the concepts if you do decide to invest the effort. You don’t have to get into a crazy workflow, but having your own ongoing branch and being able to merge/rebase changes from upstream as they happen can make your life easier. However, like a lot of tools from that type of toolbox, it can also make your life a lot harder if you’re not certain of what you’re doing, so YMMV. I would try to read a specific guide about how to set up the workflow you want, not just the reference documentation. Git has a ton of features, 90+% of which you don’t need, and many of its core features are called strange things or work in an unintuitive way.






  • Hm, I would try just changing it back first. Use geekroom.tech. Any community or anything that federated or went into the database, with one of the other hostnames, is probably cursed now, and best just deleted and never looked back on. But, if you try to reinstall, you won’t be able to keep geekroom.tech as the domain at all, you’ll have to pick a new one (or just use a subdomain like lemmy.geekroom.tech).

    Once stuff is federated out from one install under some given domain name, it’s pretty much immutable from that point forward. It probably shouldn’t be that way, but that is the current state of things with ActivityPub being the way that it is unfortunately.



  • Hm, I saw no posts on your instance for !rDataHoarder@geekroom.tech, so I tried to make one on my instance to see if it would show up, and now your server’s giving me an internal error viewing that community. Do you know what’s up with that?

    I think the time period during which whatever-it-was was making things not work, may have left your federation of communities in a borked state. One thing you can try: Unsubscribe from some particular remote community from all users on your instance (so your instance will request to stop getting updates). Then, resubscribe, and see if you start getting updates again. The initial request to get updates might have gotten swallowed by the brokenness.

    This might be a good question for the devs, also. Both because they can help more and because they should know about it as an issue (whether or not it was caused by some Cloudflare thing and whether or not it was your “fault” in setting it up, both of those questions I have no idea.)