this post was submitted on 11 Feb 2025
149 points (98.7% liked)
hexbear
10331 readers
284 users here now
Hexbear Proposals chapo.chat matrix room.
This will be a place for site proposals and discussion before implementation on the site.
Every proposal will also be mirrored into a pinned post on the hexbear community.
Any other ideas for helping to integrate the two spaces are welcome to be commented here or messaged to me directly.
Within Hexbear Proposals you can see the history of all site proposals and react to them, indicating a vote for or against a proposal.
Sending messages will be restricted to verified and active hexbear accounts older than 1 month with their matrix id in their hexbear user profile.
All top level messages within the channel must be a Proposals (idea for changing the site), Feedback (regarding non-technical aspects of the site, for technical please use https://hexbear.net/c/feedback), or Appeals (regarding admin/moderator actions).
Discussion regarding these will be within nested threads under the post.
To gain matrix verification, all you need to do is navigate to my hexbear userprofile and click the send a secure private message including your hexbear username.
founded 4 years ago
MODERATORS
Hello users of hexbear, or shall i say chapo.chat, we fucked up, and i fucked up like three times making this post.
Yes, hexbear.net has expired. Yes, we were aware of this possibility. We have gradually lost contact with the access owner (prior admin) for the domain registration. We attempted to make a migration plan, but we were disarmed by the reappearance of the party in question in September 2024 and repeated assurances that they would a) transfer credentials and b) continue payments until they were able to do the former.
We accept full responsibility for this. We should have been more aggressive about this and continued our alternative despite these reassurances. This is our fuck up, and we can't offer anything besides our continued apologies and our plan of action going forward and an explanation of what happened:
Over the time of chapo.chat and hexbear.net the admins that purchased the domain, established the donation accounts, and the server accounts have left. One of the primary admins has gone inactive and returned many times, over a year ago some of the newer admins began asking the older admins to give full access to the domain, servers, and donations. These requests were not met, despite warnings of this exact event.
At the moment we do not have access to hexbear.net and there is a strong chance we will not get it back without participating in the auction, which is already over $300. Choosing to abandon the hexbear.net domain will cause federation problems and considerable technical issues which would lead to potential extended downtime.
During this downtime we would be reestablishing access to the new domain (or hexbear.net if we win the auction), access to server ownership, and donation accounts. This would be distributed among a number of admins so that we can prevent this from happening again.
Chapo.chat has the same access problem that led to the current state of hexbear.net so it is to be considered temporary.
I will do my best to answer questions
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Admins can correct me (edit: I stand corrected, see below), I think this should at least kinda work as a temporary bookmark replacement, since it will redirect you to the current legit hexbear domain. Currently, if you go to http://37.187.73.130/ in your browser, it will HTTP redirect to https://chapo.chat/. But emojis and probably some other things won't work since they're hardcoded to download from hexbear.net.
But long term, bookmarking a static IP address isn't as safe as using the domain name, because a) there's no verification that the machine serving you 37.187.73.130 is the one who can prove it owns hexbear.net (or chapo.chat), leaving you open to a variety of attacks, b) the hexbear IP doesn't have to stay static. The safest way is to navigate to the domain name and use HTTPS so that your browser checks that the server giving you the page also can prove it's the server that owns the name.
Won't work in all cases because when you connect via HTTP you send the server the IP/Domain as part of the request to see the page.
CloudFlare IPs host multiple domains, and if you send the IP CloudFlare won't know where to actually send you.
ah that makes sense! I didn't realize it was some shared IP/tunnel situation