Pay cash when available, keep cards for when it’s not or it’d be a hassle (your discretion).
Pay cash when available, keep cards for when it’s not or it’d be a hassle (your discretion).
I’ve noticed that too. Is it related to covid you think? As in it was like this before and now we’re returning to normal progression as people rebuild social connections and lose time. Or is it that the whole dev economy is changing with layoffs and such that devs are leaving the industry altogether? Or something else even?
Spray paint until it stops getting replaced
+1 for syncthing.
Always get the version of the gadget with replaceable batteries unless you want a brick in 3-10 years. Additionally, prefer 18650, AA, AAA batteries, and keep some rechargeable ones around.
It’s not the biggest, but it still is a concern, and is exceedingly easily mitigated.
It at least used to be adaptive because at one point it went to 500$ for me, then changed back down a couple months later.
For privacy.com:
On credit freezes:
My favorite was the password set screen allowing up to 64 characters, but login fails if the password is over 32 chars.
iMessage is encrypted in transit by default when talking to other iPhone users, and 95% of my contacts use iPhones. That is the ONLY reason I use an iPhone.
Only when they leak or get thrown out. If they’re still working they’re not leaking, but maybe drawing more power than needed.
I second Matrix, though I’ve been waiting for e2ee direct p2p (the Dendrite project) do be worked on for a while. Having something like that, that’s truly decentralized while secure and hiding metadata where possible, would be a dream.
To help with this in the future, you can also create several fake results sharing your real name. Stuff like a blogger with one post not in your writing style, etc… This will dilute searches with disinformation. Removal of real data is important, but you can also confuse anyone looking.
Password Entropy = length * log2(possible_chars). So this would actually add 7*log2(10) => 23 bits of entropy, assuming the attacker knew that this section was numeric, or ~45 bits if they didn’t.
For anyone curious: Current best practice is a minimum of 100 bits, or 16 characters assuming only letters, numbers, and special characters. The recommended minimum bits increases every year with computing power.
(Area code) 867 5309
It already has an account, and nobody who gets that number keeps it for long, it may not even be assigned anymore because of how much spam it probably receives.