Are those login attempts per user, or overall API logins?
a';DROP TABLE users;
What surprises me most is that using interstellar, I can log in to piefed.ca just fine:
Beta Track [697] d0aef95
So I can get to the login page on preferred.social, which is the piefed testing instances with all the newest features, there I get the voyager popup that support is experimental etc., so maybe that can rule out device/general connectivity issues?
I just got an update from google play this morning, though the version number is still 2.37.0, and I still get the error. On both piefed.social and .ca, no idea. I don't even get to the login screen, the error comes when I select the server and click "next".
Tested logging in to Lemmy, which worked just fine - sending this very comment through Voyager.
Would it help if I share my logs?
I think I'm on the same discord as one of the admins, let me check.
I'm getting the same error with piefed.social though, just tested - I don't have an account there, but the error comes when I select the server, before even being promoted to enter my credentials.
It's essentially a clone built on python instead of rust like Lemmy, but they added some other features like advanced moderation tools.
And the more important factor for many is that piefed is not developed by some hardcore communists who disclosed that funding the development of Lemmy automatically co-sponsors lemmy.ml and lemmygrad.org, which host vile Russian apologetics and other nonsensical propaganda, and censor free speech.
I'm unable to log in with my existing piefed.ca account (which works with the interstellar app).
No real explanation given, just a generic error.
Haven't used voyager before, so it's not an older app or missing update, I went straight into the beta.
About 7-8 days, my water boiler broke in mid winter, and I just couldn't do cold showers at below freezing temperatures. Ended up boiling water and washed at the sink, went pretty alright tbh.
Nah that was Windows XP, where the hard drive was not encrypted by default, and the password was stored in a hashed file on the computer itself, freely accessible via any boot stick. Actually cracking it still took some time (below 7 characters a few minutes, 7 about 1h, 8 chars up to 24h, longer... LONG). But if it was a common word, then a dictionary attack with a long enough word list (most word lists have like 400k words or so) would get it in seconds either.
The funny thing with Windows XP was that since none of the data was encrypted, you could simply delete the password hash and set a flag in the registry and you would boot right into Windows with no password at all, and were then prompted to set a new password. That didn't work since Windows 7 anymore.
In that case this shouldn't have been an issue, I tried from my home wifi and mobile without VPN, and nobody else in my household is using PieFed or Lemmy.