![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
BoarAvoir [they/them]A
Rate limit error, which means you were trying to do whatever caused that error too fast/too often. If you still recall, what were you trying to do when it came up?
My first guess would be comment, which does have a surprisingly stringent rate limit (if I’m reading it right, 6 comments per 10 mins). Don’t panic, it should always subside with time.
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.
Maybe relevant in the post apocalypse if we lose the ability to make PV solar. otherwise completely irrelevant for most applications
aren’t two or maybe even all 3 of the people in that picture firmly gen Z? Anyhow idc generations are fake and everyone is cringe