le__el

joined 1 year ago
[–] le__el@lemmy.world 6 points 10 months ago

Open a post, then touch the three dots at the top to open the menu, then go to sort and select the one you want.

For some reason, lemmy.world dont like the old one, but all the others work

[–] le__el@lemmy.world 3 points 1 year ago

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

[–] le__el@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

Just tried on some browsers in private/incognito mode and all worked when not logged in.

But then I logged in, and the problem appears again. After some testing, I found that the problem seems to be on the default comment sort.

When set to old (which was my default one) I have the error, but when using any of the other options (new, top, hot), the comments display correctly.

EDIT:

The same happens when using mlmym.org to visit the lemmy.world instance. When set the comment sort do old, I got the error. Changing to new, it works.

But using mlmym.org on others instances I tried, it always works even when using the old as default.

[–] le__el@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

Same issue here, checking on devtools there's an error 500 on the main page load

[–] le__el@lemmy.world 1 points 1 year ago

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.

[–] le__el@lemmy.world 13 points 1 year ago (8 children)

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

[–] le__el@lemmy.world 1 points 1 year ago

Thanks!

If you use the Redirector addon, you can make it automatically redirect to page zero every time you went to page 1

[–] le__el@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

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

[–] le__el@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

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.

[–] le__el@lemmy.world 4 points 1 year ago

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

[–] le__el@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (3 children)

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.

[–] le__el@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

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)

view more: next ›