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
this post was submitted on 11 Feb 2025
486 points (97.6% liked)
FediLore + Fedidrama
2529 readers
734 users here now
Rules
- Any drama must be posted as an observer, you cannot post drama that you are involved with.
- When posting screenshots of drama, you must obscure the identity of all the participants.
- The poster must have a credible post and comment history before submitting a piece of history. This is to avoid sock-puppetry and witch hunts.
The usual instance-wide rules also apply.
Chronicle the life and tale of the fediverse (+ matrix)
Largely a sublemmy about capturing drama, from fediverse spanning drama to just lemmy drama.
Includes lore like how a instance got it's name, how an instance got defederated, how an admin got doxxed, fedihistory etc
(New) This sub's intentions is to an archive/newspaper, as in preferably don't get into fights with each other or the ppl featured in the drama
Tags: fediverse news, lemmy news, lemmyverse
Partners:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.