HL3

It sounds like military service with cameras 😆

I wonder if it is somewhat related to that?

https://discuss.grapheneos.org/d/5235-stepping-down-as-project-leader-of-grapheneos

Now do it with IPv6 😅

Looking through the rest of the comments, I think there were already enough explanations.

Making the accusation towards Lemmy that admins can see passwords in clear text is misleading.
It suggests that this is different from other platforms, which it is not. All admins can get your password from/for their respective websites. Either by logging the traffic before the password gets hashed or by modifying the application so that the password gets transferred in plaintext. This applies to Lemmy, Facebook, Google and literally any other service where you enter a password.

What you are saying is somewhat misleading 😒
But did you know over 50k people can see your Facebook password 🤔

But seriously, everything you send to a website/server can, of course, also be seen by it.
This has always been the case everywhere. I am a little surprised that this is suddenly something new…

Seems to be really similar to the issue mentioned here: https://lemmy.world/comment/706146

Otherwise, let’s hope that we can fix the last issues tomorrow 🤞

Which browser are you using?

You tried the workaround mentioned in https://lemmy.world/comment/705707
It is actually about a different issue but it still might be worth a try.

Which browser/system language are you using?

I assume you already tried to clear the browser cache? ^^

I think that’s a feature. But not 100% sure 😅
But honestly, I like the look. If it is a bug, it should become a feature 🤣

Welcome!
I hope we can make this place even better together :)

I’m sorry, you are absolutely right!
He was working on a different issue, but I honestly didn’t give them much attention because I was investigating the cookie issue.

The issue regarding the API endpoint could be “fixed” by reenabling the registration.
The still-existing cookie issue is reported (https://github.com/LemmyNet/lemmy-ui/issues/1740) and @sunaurus@lemm.ee even fixed it already (https://github.com/LemmyNet/lemmy-ui/pull/1741)
We’re now just waiting for it to get merged

For everyone experiences issues during the login,

This is caused by an issue in the latest RC of the Lemmy UI. It’s already been reported, and ruud will probably decide how to deal with it tomorrow.

The current workaround
Make sure you are on the main page (https://lemmy.world) and not looking at any posts or something like that before hitting the login button.
If you encounter other issues, please make sure to clear the browser cache. The latest upgrade also made changes to the API, which can cause issues with the cached version of the website.

https://github.com/LemmyNet/lemmy-ui/issues/1740

But the cookies are set just for the path

Mh… the login endpoint seems to work

Could you please share some more information?

Mh… some people said they tried a password reset
But I can’t confirm if this is working

I can’t speak for him, but I assume that 0.18.0 was no option due to the missing captcha, but he still wanted to benefit from the performance improvements included in 0.18.1 :)

Clearing the browser cache should fix the issue :)

EDIT: It seems to be a lemmy bug. So, it’s not related to the browser cache.
Working on it…

So, you think a public stream showing all backend infos including credentials to databases and stuff like that, is a good idea? 🤔

There are currently some issues with wefwef
With the upgrade also came some API & Backend changes. Wefwef is working on adapting to it, as far as I know.