https://github.com/LemmyNet/lemmy-ui/issues/1863
https://github.com/LemmyNet/lemmy-ui/issues/1559
https://github.com/LemmyNet/lemmy-ui/issues/1544
A couple different ones regarding 2fa
https://github.com/LemmyNet/lemmy-ui/issues/1863
https://github.com/LemmyNet/lemmy-ui/issues/1559
https://github.com/LemmyNet/lemmy-ui/issues/1544
A couple different ones regarding 2fa
Some people have reported being able to add TOTP from mobile. Most people that reported on desktop have the same issue. It's a lemmy thing, not just the instance. Lemmy needs to have you validate your TOTP before committing it to your account so you don't get locked out for turning it on but not being able to actually add it.
@[email protected] you are tasked with securing your network, please list all websites that should be blocked by default.
Thanks for the insight, that's good to know. What do you do if you need to move from one organization to another (it seems to be only allowed to move from personal vault to organization, not org -> personal or org -> org)
Same here. I added it to Keepass, then opened a private browser and tried to log in and it wouldn't take it. So one of 2 things:
I went ahead and removed 2FA so I wasn't locked out of my account if I get logged out somehow until this is fixed.
Catch the error and dump the response body to see what you're getting. Might just be the server is overloaded and not responding with the expected JSON. The full body should give you more clues
I'm going to read about GitHub being down (with a link to this repo) on Monday, aren't I?
I haven't spun up an instance, so I don't have a good idea what the DB looks like, but are IP addresses captured on either account signup and/or vote casting?
It's isn't a silver bullet, but it's prohibitively more expensive to spin up instances to cast votes for bot users versus running through a script on a single machine. If you've got an IP you might be able to pinpoint bot activity and the accounts associated with it (until they get smarter, at least)
Yes, captcha is the default minimum that should be implemented.
Also reasonable is to log account creation with IP and timestamp, which allows retroactively remove offenders if patterns occur, or [more easily] determining if 500 account signed up within 5 minutes from a single IP.
While kind of a pain, but fairly efficient: require a phone number with text verification to enable an account.
Yes I know there's ways around each of these, but it makes it much harder to spin up many accounts through rudimentary means.
Comment / post ratio is useless as well for this though.
Looks like I pretty busy, totally real server by the aforementioned metric
CrowdStroke