Cube6392

he knows the nfl is stealing the value he creates. he doesn't need to pay them

i think some big project, something really important, needs to migrate for the masses of devs to move too

signal has been eroding it's trustworthiness, and all the stuff you said is why myself and most folks keep using it despite its downsides. in a perfect world more of us would be working to make xmpp a viable option for most people but as it stands it's a touch too technical for the average person's mom and dad, who are ultimately who you have to appeal to

telegram did something important by being the first mass market "private" messenger that people were aware of. it has outlived this usefulness by nearly five years now. even the things that replaced it at this point are getting run into the ground and require replacing.

how'd you do that?

Sure yeah. I think corpos suck, too. That's why I don't prefer 1password. But Firefox puts their passwords into a file, too (two actually). Key3.db and Logins.json, both with known locations, and encrypted using AES-256-GCM which is... Decent but I prefer to go a little more hardened. The thing with keepass is the following:

1. Its open source, no corpo
2. The file encryption you select can be as hardened as you want
3. No one but you need know the location of your file
4. It offers 2fa which Firefox password manager doesn't
5. Firefox password manager is more susceptible to social engineering attacks is mainly what I was worried about but it seems like you've got a good handle on it.
6. You don't have to integrate keepass with the browser to use it

But I want to make it abundantly clear. @[email protected] has not recommended storing your passwords in a file. They have suggested storing your passwords in a mechanism that can be as secure as your hardware is capable of securing and keeping the location of that up to your own decision making.

But also. Promise me this. If you're going to keep using Firefox as your password manager:

1. Don't use sync. That's run by Firefox's corporate arm, Mozilla PBC
2. Use a primary password of at least 32 characters
3. Consider rotating your password on a regular interval, like on your birthday

Cover the G logo with a pop socket or some shit. No one will give enough of a shit to desire your phone. Buying used always denies OEMs sales so its always good to buy used

Using the internet without an adblocker is genuinely dangerous. Everyone really should be using uBlock Origin. Using a web browser that prevents uBlock Origin puts you in danger

If you use a deterministic password manager, make sure you make your master password strong

In-built password managers for browsers are straightforward to crack. Like… Terrifyingly easy. It's much better to use something like Bitwarden, Vaultwarden if you don't trust Bitwarden, 1Password if you really want the reassurance of paying someone for trust, or KeePass if you don't trust anyone at all (I, personally, fit into this category).

Messengers are not protocols. They use protocols. Most XMPP clients use the same encryption scheme Signal does only without being dependent on a single specific server, allowing users to spread out. I recommend reading about the differences between targeting developing a platform and developing protocols. Once you do, you'll see XMPP+Encryption in a better light than anything like Signal. The main problem in the current moment with XMPP+Encryption us that it isn't where the people are. Us tech weirdos can start the push into that space a little bit, but we need "Normies" to adopt to, and for that we need to be clear on what were talking about. Comparing XMPP to signal doesn't make sense. Comparing Cheogram to Signal does. And in the latter, cheogram frankly blows Signal out of the water for real privacy and security considerations

I immediately had my suspicions this article might contain some bullshit when I saw it was published by the new oil...