It's been a long journey since we announced this back in December 2021. Welcome to the new Hexbear!
If When you encounter a bug, please report it here. Please give us as much detail as you can (how to reproduce the bug, the platform/browser you're using) so it's easier for us to fix!
Known Issues :
A list of issues, not exhaustive or in priority order. We're looking into all of these and will be deploying a variety of hotfixes over the next few days/weeks with fixes.
🚨 A lot of these are bugs that exist in upstream Lemmy 🚨
- On some errors, infinite rotating spinner with no error message
- Includes resetting password via password reset link
- Can't navigate away when text is entered
- Issue logging out if initial pageload was not on homepage
- Reporting posts does not work in portrait mode on mobile. Temporary workaround: rotate to landscape mode
- Jerboa broken due to api changes
- Inline gifs/images are able to render way too big
- portrait mode for tablet width/aspect ratios probably should not show sidebar, too much wasted space.
- disabling "Show Read Posts" in user Profile hides featured/pinned posts from the homepage
- Highlighting then clicking reply to automatically quote includes "undefined" before the quote.
- Sitewide Featured Post titles turn blue when moused-over, becoming illegible on the blue background
- comment permalink is too easy to misclick when aiming for upbear or username.
- Post shown occasionally changes out from under you while browsing, comments remain the same
If you are open to volunteering, we are looking for frontend developers who can help figure out and fix some of these UX issues. If you think you can help, please send Layla a message on Element (@layla:chapo.chat). None of this is possible without your continued support. If you enjoy the site, please consider donating via our Liberapay or Patreon :hexbear-retro:
Edit: sorry for the second spurt of downtime folks, we are trying to solve the performance issues
Hiya! It’s not really easy to get Hexbear working on most apps. The log-in URL requires us to use “hexbear.net” instead of “hexbear.net” which causes links from clicking on usernames/communities to load as [usename]@hexbear.net.
I posted a bug report on Memmy’s GitHub to get their thoughts and they suggested I reach out here.
That is currently correct behavior. Because our site's creation predates federation as a feature in lemmy (it may have been in development when we launched, not sure, but it was far from finished), it was configured by the previous dev team primarily as a website first with no consideration towards theoretical future federation or mobile apps, and they chose hexbear.net as the base URL that other URLs redirect to (well originally chapo.chat, but I wasn't privy to that). Changing this base URL requires a major database migration and can't really be done at all after federation, so we plan to change it before federation to just hexbear.net for the reasons you mention.
Edit to add: The reason we don't accept requests from both the root and subdomain is (at least previously) it caused posts to be submitted with different domains, so in the database we would get some with hexbear.net, some with hexbear.net, and some with chapo.chat even. We could probably configure it to redirect just UI requests to www. and not API requests, but given we are fixing the root issue soon anyhow, it likely won't happen in the meantime.
The only thing I noticed that the Memmy developer got wrong is that we "configured federation with hexbear.net". We have federation disabled entirely, and actually some of the activitypub code may even be commented out on our current version, I'd have to ask a dev to be sure. The bottom line is if they are accessing content via activitypub instead of the HTTP API I wouldn't currently expect that to work, but it should after federation if I understand ActivityPub correctly (we will have an allowlist, not wide open federation, so not sure how that affects things for end user clients. I'm guessing/hoping not at all.)
Thanks for taking the time to make a bug report, and to reach out to us! Hopefully this will all be resolved soon.