Quick note... some users are having issues with verifying registration if they miss the initial link. I was able to get kbin to resend mine by sending a password reset, but some users can't reproduce that. Just so you're tracking.
Hey not sure if this is the proper venue for this, but is the REST API expected to be functional? The root endpoint (e.g. curl ‘https://kbin.social/api’) works, but then all the others (e.g. curl ‘https://kbin.social/api/magazines’) fail with a 500.
At first I figured it was just a “kbin.social is overloaded” issue, but the behavior seems consistent across a few different instances (karab.in, kbin.lol, some others I forget).
Figured I’d check if the API is, y’know, implemented/enabled/whatever before I try and repro/submit an actual useful bug report.
@ernest wanted to report a beehaw thread being broken. See here. apparently they used hashtags in their thread title which is allowed there, and it broke for some lemmy users and ended up in kbin's microblog section rather than showing up as a proper thread.
When I do an action on the site after like an hour, it takes me through the dumb cloudflare thing. I'm already logged in, why do I need to go through it every freaking hour?? This is an AWFUL user experience. I say "remember me" not "forget me in an hour"
Not great that this requires a new account on a service most people won't already have :( I tried logging in with GitHub and it did that thing that I really hate federated logins doing where they go "yeah go ahead log in with your credentials from another site SIKE YOU HAVE TO TELL US YOUR EMAIL ANYWAY"
