Yes, from what I've seen there are a some people who are concerned about others impersonating them on other instances.
If you log in to any App for Lemmy, they also have access to your Email.
Yes, this. No point in using a VPN/Tor if you disconnect even just for 1 second. That's all they need.
Figuring out if two posts are identical is going to be a challenge
I think I could deal with duplicates pretty easily by checking if different properties of the post are identical, the more are the less likely it is that the post will be shown.
I think a bigger problem is the comments. What if a user reposts a post from r/astronomy on lemmy.world to c/astronomy on lemmy.ml? Which one do we show, and what do we do with the comments of the other? Merge them together, or just leave them? Maybe show a button on the post when there's a duplicate und the user can switch instances?
Lots of figuring out to do, but it sounds fun!
Edit: The Group-by-Hashtag thing is also a good idea! That would of course make the whole thing less of a headache, but to make that work a lot of users need to do that.
Yes, very good idea! When users create a group, they can select keywords to search for and then the App could make a best guess and then show a list to the user where they can select the ones they want or don't want in the group.
Ah, sorry if I'm being unclear.
I was thinking of combining the user's original password with a random 32 Character string and hash that combination. So basically salting the User's password with random strings. That should work out to multiple passwords I can use.
Thinking of it bcrypt does exactly this, so just running bcrypt a couple of times should be sufficient, no?
Security wise if there was a breach, an attacker would still only have a couple of hashes, none of which are the original password and they can't dictionary attack due to bcrypt.
Also, if an instance was hacked, the worst case would be that the attacker gains access to the hash (if the instance stored passwords in plain text and didn't also hash them themselves).
I'm really tired right now so maybe none if this makes any sense, but I think it does lol.
Thanks for letting me know, I'm still new to Lemmy :).
I'll put this on the roadmap of my App if you don't mind
takes notes for my own App 👀
Very good point! I think @[email protected] has a good idea on how to circumvent that.
I could make my own database with hashed passwords using postgreqsl and RLS, which is pretty secure. The User then decrypts the hashed passwords once on login and is simultaneously logged into multiple instances of Lemmy to get the JWT of each instance, which is then stored in SessionStorage or even in a Cookie if the User wants to which would make this a one-time process.
On signup the User could just register to one instance and then I just generate random 32 Character passwords and hash them with the Users' password, then get the JWTs and if cookies are enabled the that would only have to be done every year or so (or when the User deletes the Cookies).
This whole process is seems pretty easy, especially if you've done something like this before and I'm betting some other App Dev is already taking notes lmao.
Edit: Let's also do a thought experiment on what data will be leaked if I did this 1:1 and the database gets somehow hacked:
For each User:
- Username (=> Gives away that you use Nemmy)
- Hashed Passwords (=> Hashed passwords cannot be read if you don't have the original Users' password until we have access to quantum computers which can literally crack the encryption algorithm)
I fixed the bug. Justice has been brought to that Cat photo!
I think at some point I'm just going to accept that I can't detect all image types and call that a feature lmao