Isn’t app development a recurring cost? It’s not like you just work on it for a bit and just forget about it once you got a version out. Especially if it’s using a service (lemmy) that is still in development and is constantly changing.

I get that on hot after only 5 posts. Everything after that is a minimum of 1 year old, and only the first 3-5 post are recent. It’s kinda funny reading the comments on those posts as there are a lot of lost people commenting on it right now, thinking it’s something recent.

I don’t know about it. Look even at the usernames. It’s @[email protected], it’s structured like an email. Even for instances, /c/piracy is not a thing, it is [email protected] in Lemmy world. Even Mastadon has the same structure of name@instance.

Every community has their own sets of rules, own set of moderators and culture. If you don’t like how one is moderated, go to another one (basically how reddit works too, except there you need to change to name to make an alternate community)

Regarding not being able to make new communities: We’re all federated. What’s wrong with making a community on a different instance with your lemmy.ml account?

I’m not the person you’re replying to but I have a fun answer for how I did it before I moved to password managers.

I used to have just a single password, normal-ish password. Reasonable length, some numbers in there, random caps. But in order for me to have unique passwords on every site without losing track of all the unique password, I added the first and last letter of the name of the service at a specific point inside the password. My password was cryptic enough that if you would see it you wouldn’t immediately notice it. But for me it meant I had a single strong password that was easy to remember and unique for every service.

I’m still kind of proud of that one, even though I don’t use that method anymore.

See my response a few comments down this thread. I found the counter and password-template too. I don’t have an iphone so I can’t test the app, but I very much think this app stores the ‘settings’ (counter, template) to generate the password. Based on what the api and CLI can do… it has to, surely. It also has the ability to retrieve a custom password.

Of course the webapp in the link doesn’t do all of that. You’re stuck with 1 password in 1 format. Unless you change your secret and then all your passwords change.

In practice it can be anything though. It just gets thrown in one of the hashing functions. They way they describe it:

user-key = SCRYPT( user-name, user-secret )

site-key = HMAC-SHA-256( site-name . site-counter, user-key )

site-password = PW( site-template, site-key )

Which is kinda interesting, they mention site-counter and site-template. The counter indicates you can set it to a different value to get a different password for that site. But then obviously every time you want to recall that password, you have to set the site counter correctly. I guess the app will remember this, but the web version obviously doesn’t. But the gimmick is that it doesn’t store anything, but it seems for the app to work it does need to store the settings to generate your password.

And also there is a site-template, which seems to hold various ways to generate passwords. Long, medium, short, pin, etc etc. With or without special symbols. It even mentions ‘saved personal password’ so I guess it can save custom passwords? Hopefully encrypted though.

That sorta addresses the concerns I have. But obviously that means you need the app, the website doesn’t do all those extra things. And if you loose the app you loose your custom site counter and template.

Also, the CLI version seems to happily store the username and secret on your pc? Or at least lets you read it from a file, so…

(I haven’t actually used the app, just going through some docs and source code here)

So basically a fancy hashing algorithm to get the same password for the same information you give it. Neat idea but I am not convinced yet.

If your Spectre secret gets somehow leaked (and your full name could easily be found), that’s immediately all your current and future passwords leaked. Now, this would in theory also be a problem with regular password managers that live in the cloud. Though smart ones hopefully add 2FA or similar before they let their users log in. For offline password managers the hacker would need your secret + database to get your password. That’s a lot harder. Spectre takes one of those items away, because the ‘database’ is their algorithm which literally runs on their webpage. All they need is a single password.

What if a site you use leaks your password and you have to change your password for that site only? Spectre won’t help you with that, as it will still give you the (burned) password. So you manually have to remember which sites use Spectre for passwords and which ones don’t.

Have any services that have been provided to you with a set password you can’t change (eg: some service your job uses), Spectre won’t help you with this as it won’t hold any custom passwords. Have any weird services that requires a specific length and/or forbidden characters Spectre does? Good luck, Spectre can’t help you here either. It’s not a password manager.