It's fixed
(thank you for letting us know)
Hi, thank you for reporting this issue! sorry it's taken a bit to work its way to the relevant people. It should be working now, assuming you are not currently rate limited and you don't require multiple retries to get the 2fa code right.
a little inside baseball
So the issue is, lemmy doesn't have super granular controls on various API rate limits, there are only like 7 categories but there are many more API endpoints than that. For reasons I cannot fathom, the /login endpoint uses the same rate limit as the /register endpoint (for applying for a new account), which we keep pretty low to prevent registration spam, etc.
In addition, 2FA logins require 2 calls to /login, since the first one has to come back with a response telling the page to display the 2fa prompt, and then a second request is sent with the 2FA code.
Long story short, there was recently an attempted "raid" of the site by some trolls, and in preparation the /register rate limit was lowered further than normal, to only 1 per hour. This had the unintended effect of making 2FA logins impossible, and has now been increased. In future our devs may change the login rate limit to not track /register, but for now 2FA should be working again, though if you mis-type the code you may get rate-limited for an hour until a more permanent fix is in place.
New pronouns require a small amount of dev time to add, but it's pretty easy normally. My bigger concern would be the ongoing rebase of our customizations onto lemmy 0.19.6. I've asked in the dev chat!
surprise! we browse the trans mega!
sie/hir has been added, give them a shot!
As others have mentioned, that was implemented in a hurry due to tightening up security and safety around embedded images. I've brought it up to the devs to hopefully rectify, as if an instance is trustworthy enough to federate with (aka, not actively malicious) then it is probably safe to show their embeds (behind a blur).
At the latest, this restriction will go away when lemmy upgrades to pictrs 0.5 which will support proxying image requests, but unless there are objections from the rest of the team we will likely add all federated instances to the image allowlist before then.
Also dosent all modern operating systems have extracting files Just build in regardless of the format?
No.
yes! Movie night going on now at live.hexbear.net
You can get it on archive.org. I've done so once or twice
BoarAvoir
0 post score0 comment score
The domain name was originally registered with Sav.com, a particularly scummy registrar known for sniping and auctioning off dropped domains. As it turns out, they aren't any kinder to their own customers than anyone else, and without sufficient warning (seemingly in violation of ICANN policies), they sent our domain to be auctioned off when a scheduled payment didn't go through, kicking off a frenzy of anti-communists trying to buy it.
Specifically, a registrar operating in good faith will generally disable resolution of the domain after it has expired, to alert the owner/users that it is expired and in the grace period to renew, but Sav does not, preferring to take domain owners by surprise and let the domain fully expire, forcing them to compete on the open auction to get their domain back.
Somehow, we managed to transfer it out of Sav to a less scummy registrar during the auction, recovering the domain for free. However, the 2 weeks or so where we were operating off of chapo.chat as a backup domain ended up causing a lot of technical headaches and roadblocks to re-enabling federation, hence the delay.