After this, the part where he trespass and try to open the locked door without any authorization got even more creepier… :|

That info is public available on kbin (this post was federated from kbin.social).

On lemmy, I believe only the admins have access to this info by looking at the database itself.

Actually, hello.1@gmail will go to hello1@gmail.

The one you are thinking I believe is hello+1@gmail will go to hello@gmail

I personally had to use a fork version that added a delay between each edit, because the original one were skipping some messages due it “going too fast” on the api

If you try to make another non nested comment (or reply directly to your original post) and it show up on beehaw, we can be sure that the federation is running and the comments (and nested comments) that involves the defederated instances are all completely banned from there.

EDIT: Catch42’s comment also didn’t show up there yet, so the federation seems to be is a big laggy.

EDIT2: And now Catch42’s commented showed up there, so the federation synced up and the comment thread that involved any user from defederated instances didn’t show up.

Just got your reply here on lemmy.world and only the top message seems to be on beehaw. My reply and your sandwiched reply both apparently didn’t show up there

Replying from lemmy.world to check :)

EDIT: Shortly after the post, it was sent to the original kbin instance.

After 8 minutes, my reply apparently didn’t make it to beehaw, so I assume all new comments from lemmy.world users, even on posts of third instances, are really banned on beehaw.

Have you tried to go to login page, fill in with your email only and click on forget password? If this work, maybe there’s also some issue not related with the password complexity

EDIT: (I mean, if you at least got the email verification)

I also had the same issue on my first login (the email was verified, btw). The login button just went spinning and nothing happens. Trying the login on Jerboa gave me invalid credentials (it wasn’t a mistype, because I used a password manager).

The workaround I did was to do a password reset and use a simpler one (was 50+ chars with special chars on, then changed to 32 chars and no special chars).

Not sure if what fixed was the reset itself, or the new password.

After this, the login went smooth on both the website and the app.

EDIT: And when posting this, the post submit button also kept spinning (the more than 200+ chars issue). But trying in a new tab, the message was actually sent.

And some minute later, on the old tab the message was sent, but the OP post changed from the “improvements and issues” to “The inability to post multiple pictures is holding Lemmy back.”, but the comments below mine where for the “improvements and issues”, while the comment above where to the other thread.