- cross-posted to:
- meanwhileongrad@sh.itjust.works
- cross-posted to:
- meanwhileongrad@sh.itjust.works
Auction: https://www.sav.com/auctions/details/7073489/hexbear.net
Not sure what will happen, but seems to be a Fediverselore event for sure
Update: post from hexbear admin on chapo.chat: https://chapo.chat/post/4468531
The rest of the Fediverse should put together a GoFundMe to buy the domain, and stick up a page with links to donate drones to Ukrainian soldiers, and care packages to families of Uyghur muslims detained in concentration camps in China.
I’d rather people just fund their instances or the developers
I wonder if the high bids will actually go through or if it’s just trolling. Definitely weird to give such big amounts of money away for a joke outside the space where it’s needed.
Honestly I’d donate. Would love to see them seethe.
So right to the pockets of Adrian Zenz?
Couldn’t somebody buy it and change it to force all the assholes out and then change things to make it a proper instance?
Idk how federation works, but I imagine the domain name isn’t the only thing that ties the instanses together together?
I could be wrong
nah they could, theyd just change it to their ip address, like the domain vendor deleted their ip address from the records when they didn’t pay
That’s not how the Fediverse works. Instances are per domain, not per IP address. You can change IPs however often you want, as long as your domain points to the right server.
It would still be a different instance behind that same domain name
That doesn’t matter to fediverse software. Any new instance on hexbear.net would have errors when trying to federate with other instances, and it probably wouldn’t be able to do so at all. But even if it did manage it, what are you expecting to do to mitigate the errors that arise from other instances referencing users/threads/posts/comments/communities/modlogs that existed on the old instance, but do not exist on the new one?
Yeah, that’s what I was talking about. It would be a different instance that doesn’t have the same database as the original one.
Ah, I misunderstood that you were arguing in favor of a new hexbear instance as well.