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) 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

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

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..

The internet

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 :)

I bet his instances will be one of the few actually federating with them 😔

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.

Reading this, I wonder if we talk about the same Debian 😆

HL3

Multiple people were able to reproduce this.
So, the assumption that the screenshot is fake is probably wrong.

Altogether, please don't take screenshots as proof of anything.
They are always subjective to how much you trust the source they are coming from.

See https://pleroma.envs.net/objects/5ed98350-328b-42ff-8005-4137fea8642d for a more complete statement.

1. No, he was just de-federated with absolutely NO previous communication.
2. There is still no real proof that Eris actually is racist at all. Everything is always "someone said/claims".

1. I am not aware of any further communication. T1C says there was no communication about it and I am not aware of claims from .art that state otherwise.
2. That is ridiculous. Yes, it's their decision if they wanna federate with firefish.social or not. But accusing someone to support/accept racism needs some proof baking it.

Please try to clear the browser change
The new version is doing some of the API calls differently, which may cause issues with the old/cached version in your browser

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

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

I would not say, people absolutely trust corporations.
You can probably ask any stranger o the street if Facebook is trustworthy and they all would say something about FB doing weird stuff with their data.

They all know!
But people have a limit on how many issues they can care about.
We decided that privacy is an issue, others might decide that the issues their sister is facing in life are an issue, or just how to pay the next month's rent.

So, they just use Facebook, google and co. because that is what works, what is there and done. No time to think any further about it!

So, if you wanna get wide adoption for privacy-friendly alternatives, stop solely selling the privacy aspect. The fediverse is great, but all the people who care about the benefits of it are already here. Now try to reach those who don't care that Twitter is a mess, they are just there because all the others are too.
They use it to communicate and not because it is great. The same applies to most other platforms too.
I liked Reddit because it's one platform where you find literally anything! You wanna talk about energy drinks? There is a subreddit.
You wanna know what this thing is you just found on the street? Just post a picture someone definitely knows!

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 🤞

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 🤣

In general, yes. Lemmy 0.18.1 does federate again with kbin, mastodon and all the others.

But I think there are still some issues with lemmy.ml and kbin.
Not exactly sure why, but I have them informed already 🙂

I wonder if it is somewhat related to that?

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

0.18.1 changed the limit to one hour. So, hopefully, this issue is soon solved for everyone :)

Mh.. the login endpoint seems to work

Could you please share some more information?

https://inwx.com

But the cookies are set just for the path

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.

Which browser/system language are you using?

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

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.

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

Clearing the browser cache should fix the issue :)