But what if it does exist? But your have an email server on the same domain? Or what if that domain is being malicious and masquerading as a Lemmy instance to steal your credentials?
I’m not sure how that would work. When you sign in you can use your username or email. So if you type example@domain.com there is no way to know if you’re trying to login to the instance at domain.com or login with your email ending in domain.com, to some other instance.
Edit: and it can’t just assume and try domain.com first, because then if it’s not what the user intended then you just sent your login credentials accidentally to a random domain 🙃
I've told them that "in the first screen there is a button that is very difficult to notice, allowing you to use a pre-existing Lemmy username. Find that semi-hidden button, click it, and you can login."
This is the first I’ve heard of any problems with this screen, so please encourage them to reach out directly, or post in this community.
Thanks! Also noteworthy, for those instances using lemmy-ansible (should be most) this release should fix video streaming for Safari clients (videos refusing to play), and enable progressive streaming for all pictrs videos (before in chrome/firefox/native players they would have to finish downloading before playing).
For those instances using a custom nginx reverse proxy with caching enabled, please enable the slice module! After upgrading to 0.19.10 feel free to ask me and I can help out to check to make sure it's working properly.
It’s not a voyager issue, it’s a Lemmy issue, the link didn’t federate for whatever reason. Maybe an edit that op made to add a link didn’t federate, I’m not sure. You can check by the opening the comment with Lemmy-ui on Lemmy.ca vs lemmy.world.
But what if it does exist? But your have an email server on the same domain? Or what if that domain is being malicious and masquerading as a Lemmy instance to steal your credentials?