We will be down for ~30 mins. If you can't get in after an hour, check our Mastodon or twitter for updates, or try force refresh, clearing cache, etc.
EDIT: doing another quick hotpatch. You may see some interruptions
Hexbear users when a button's color is updated to a slightly lighter shade.
Swapping the positions of the reply and cancel buttons as a joke was not okay
Yay! Thank you! Mad respect to our hard working peeps who keep this place going
This feels like when someone moves all the furniture slightly out of place.
thumbnails are misbehaving, but the files are not actually missing, just intermittently some fail to load, devs are looking into it.
Some Pictrs URLs are returning a 404. Either Pictrs itself or a reverse proxy cache is having a normal one, e.g., https://hexbear.net/pictrs/image/5984351f-519c-4d2b-8271-fb97a57d5d14.jpeg
That one could have just been submitted while services were in the twilight zone, though
Edit: Scratch that, I'm seeing 404s from image posts (not just thumbnails) from 10-12 hours ago.
for sure missing some, maybe it was posts by people not realizing the server upgrade was happening, and tried to post mid server downtime?
Just so everyone knows, this is just a code upgrade again. Federation is not enabled yet. Our very next goal is to fix what we need to in order to enable federation. A big part of this will be moving the domain from https://hexbear.net to just https://hexbear.net.
A big part of this will be moving the domain from https://hexbear.net to just https://hexbear.net.
Out of interest, why is that a problem?
not a problem, just something to be aware of. we are doing it to make things cleaner and simpler when federating.
Oh I think you misunderstood me, I was interested in what the technical reasoning behind it was.
Is it because hexbear user tags are currently @JamesConeZone@hexbear.net so changing that would make it JamesConeZone@hexbear.net?
causes federation/mobile app confusion (if user types in the wrong one their app can't load the site properly. easy to handle in browser, less easy with apps in the mix that don't follow redirects) and makes user tags longer.
Makes sense. I guess apps don't care about htaccess unless the dev specifically writes it in.
I was talking about 301/302 redirects from the web server. browsers don't need to read htaccess files either, otherwise clients could simply choose to ignore the configuration contained in them which is often security sensitive. They are just used by apache to store directory-specific configuration. Lemmy instances generally use nginx anyhow tho.
i got jump scared, i thought you were gonna announce moving our domain back to chapo.chat
If we wait a little longer we could probably buy
reddit.comand move back there.Moving hexbear back to
reddit.com/r/chapotraphousefor a joke was NOT okay!
If it stays https://hexbear.net instead of https://hexbear.net at first, then we won't be blocked by instances that have already blocked https://hexbear.net like beehaw
Going to start a reddit tier shitfit because the admins are forcing pfps on me with this stupid little mouse guy
People should be aware that there are some pretty solid lemmy 3rd party clients that now work with hexbear post-update that you should try out.
Android:
- Liftoff (Something is bugged here right now- check out the two below)
- Jerboa
- Connect
If some of the iOS users here could chime in I'd appreciate it.
Memmy for Lemmy on iOS is rapidly becoming the spiritual successor to Apollo. It's good.
both Mlem and Memmy are on the app store now. idk which one to choose
I'd recommend giving them both a shot and see which one you end up liking more
Yeah it’s familiar for me since I used to use Apollo. A fair amount of bugginess still though, and some design choices I really dislike, but overall it’s very good. Haven’t tried Mlem yet.
If you can explain to me how to get jerboa to work with hexbear please please please lmk
- From within Jerboa click the hamburger (3-line) menu in the top left.
- Either click where it says "Anonymous" or on your current account if you have accounts on other instances.
- Click "Add Account"
- In the instance form- type hexbear.net
- Fill in user/pass
- Login
The www. part is required because of some bug somewhere. That's probably what issue most people were having.
Let me know if you're still having issues after this.
Using Jerboa here since Liftoff doesn't work, it seems to drop the www part so it isn't redirecting correctly on their end and throws an 301 error.
if the dev just used the URL as entered it should work lol. trying to be helpful like that always breaks some edge case like hexbear where www. is the main domain and hexbear.net is a redirect.
This is great, love Jerboa. Pretty similar to RIF with the right settings
Yes, I think the only trick might be having the www on hexbear.net. writing this reply on jerboa
Liftoff unfortunately is still not working for me. Posting this from Summit which also feels pretty RIF.
Huh, that's weird. It worked on test.hexbear for me but not on the main site now.
I may not even care though because Summit is looking extremely good and feature rich so far. Though I don't know if it can do custom emojis.
if babushkot above is to be believed it seems to be stripping the www. off of the provided domain name. dev probably hardcoded that to be "helpful".
I actually like the new look better. I think people might not but I like it.
Also emoji test
It looks like removed comments are causing some problems.
When a comment gets removed, it apparently no longer has a place-holder comment "removed by mod" like it used to. So now threads will have the "1 more reply->" sign, but if you click on it, you just get the infinitely spinning bear head.
Another thing, if you are reading a thread (one that you arrived at by going directly to a comment instead of the post first) and click "Show context->" and the context was actually a removed comment, it just reloads the part of the thread you were already on and you can't get any further context, even comments that were further above the removed one. This makes it not only harder to tell that there were comments that mods removed, which maybe is the point, but it also makes it so a lot of good, not-removed comments can't be read either.
I just checked and it's not just comments removed by mods, but also the "deleted by creator" comments. Unless I'm missing something, that means whole threads can be essentially disappeared if someone early on in the reply chain decides they don't want it to be visible anymore. Not just the stuff they wrote themselves, but the rest of the chain. That's.... not good.
Found a small bug. I just typed out a long reply to a comment, but before posting it I clicked to upvote that comment. Doing so deleted everything I had typed.
sadly, upstream does some weird shit with handling state during a api call.
