Imagine how amazing the PR would have been if the title had been: “User gets spectator seating for a SpaceX launch in return for lost handle”
Imagine how amazing the PR would have been if the title had been: “User gets spectator seating for a SpaceX launch in return for lost handle”
I can often dig into the source and quickly figure out what’s broken.
And for the 99.9% of humanity for whom that is either impossible, or a dreadful slog,
On Windows, I’m usually shit outta luck. Gotta trawl through tons of messy forums and bullshit SEO-optimised blogspam sites
While this^ is a practical option… This^ is a practical optionof hu
I mean, didn’t they fuck everyone?
I have regular nerd-arguments about it:
“All they have to do is break two of your passwords, and they can reverse-engineer your passwords!” - Maybe, if they have a super-computer… “It’s so much work” - Once. It’s so much work once. Then, it’s much easier than loading software or digging out a dongle every time you log into anything up until you decide to change all your algorithms… “What happens if you forget?” - What happens if you forget?
But my ex was really crazy. You gotta hear this!
It’s nice to see the right starting to eat their own like the left does…
This is the situation I’m in. Half-a-dozen clients in the energy and automotive industries, each with multiple security regimes and short timeouts. Passwords mutate with time and I stay sane…
I don’t like to keep any security stuff in “the cloud”, written down anywhere, or even on my own devices. It’s too easy to lose everything after one security breach.
Instead, I use password algorithms seeded from both the service name/identifier and one or more private passwords. This lets me keep thousands of service/site unique passwords in my head just by memorizing twenty or so words.
I’ll support Senators not having a dress code when there isn’t one for anyone else working in Congress…