• 220 Posts
  • 382 Comments
Joined 8 months ago
cake
Cake day: July 18th, 2024

help-circle



  • Yeah. I hesitated a little to post the story because to me ActBlue belongs more to the problem set than the solution set. It’s also very weird that this article brags about all their success level, which against the current backdrop of events presumably means that they are bad at winning elections but good at raising money, which should not be the metric.

    I do think it’s pretty newsworthy that they are struggling, not because they’re an integral part of an apparatus which doesn’t give a shit about working people and keeps losing elections as a result, but because the legal structures of the country are being weaponized against them. That’s definitely not going to decrease the power or influence of the donor class. But also, you’re not wrong.

























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