this post was submitted on 12 Feb 2025
7 points (100.0% liked)

Embassy of Hexbear on Lemmygrad

71 readers
31 users here now

Hexbear's Diplomatic Mission to Lemmygrad

founded 1 week ago
MODERATORS
 

Granted it's not much money. Just to see if the account that's been outbidding everyone will outbid me

you are viewing a single comment's thread
view the rest of the comments
[–] CarbonScore@lemmygrad.ml 1 points 6 days ago (2 children)

I don't really see how this was a completely preventable issue. The person who owns the domain said they would keep it up, then they didn't.

[–] 666@lemmygrad.ml 2 points 6 days ago (1 children)

From what I was told the person was hard to get a hold of. Why didn't anyone start asking questions when that first started occuring?

[–] TheOtherNakoichi@lemmygrad.ml -4 points 6 days ago* (last edited 6 days ago) (1 children)

If you were asking me personally it's because I don't really care. I love the people there but we have weathered worse storms in the past. All the people I care about just hang out in other spaces instead.

[–] blunder@lemmygrad.ml 5 points 5 days ago

There is no worse storm than site admins enabling cyberattacks on comrades... not even close. This isn't "should we stack rocks"

[–] Philosoraptor@lemmygrad.ml 1 points 6 days ago (1 children)

It was preventable in the sense that the admin team probably should not have continued relying on a single point of failure who had already shown themselves to be unreliable and prone to vanishing for extended periods, but I think it's also not really a blameworthy mistake. They assumed good faith in people who had helped to set up the site and pay for the infrastructure, which is understandable. It's a learning opportunity for sure and very preventable in hindsight, but not really anybody's fault I don't think.

[–] CarbonScore@lemmygrad.ml 2 points 6 days ago* (last edited 6 days ago)

Sure, but without a complicated legal entity, "the person who controls the DNS" will always be a single point of failure. Questions maybe should've been asked earlier, and backups put in place, but nothing about the issue was preventable.