1,857 karma · joined October 2, 2014
As for Amazon, I like them too. I know they have a lot of cheap Asian stuff. But sometimes, that is exactly what I want (cheap but good DC stick welders).
I guess the issue is with the knock-offs and dangerous items on Amazon. That's fraud. No question about it. Walmart does not have this issue at all. Amazon should do something about it.
Edit: I am w8rbt on twitter as well.
http://algorithmics.lsi.upc.edu/docs/Dasgupta-Papadimitriou-...
Also, it seems to be mostly in rural areas. Some drivers keep the buses at home during the school year. And, these are large, full size buses. If you live in a medium sized or large city, it's probably different.
"There are only two kinds of languages: the ones people complain about and the ones nobody uses."
Bjarne Stroustrup's FAQ: Did you really say that?. Retrieved on 2007-11-15.
Perl 5 is Perl 5 everywhere.
If you need software to scale to hundreds of millions of users, then you probably need people who have CS degrees to think about your hard problems and how best to optimize them and which ones have no polynomial time solutions for all inputs (problems to be avoided or worked around somehow).
I can do RSA by hand (on small messages), quickly tell (with only pencil and paper) what 2^1027 mod 3 is and do Euclid and Extended Euclid by hand to find multiplicative inverses (in one pass). But I can write code that runs pretty well, too, and I can do that with or without a CS degree. So can most people.
Edit: This is solely for password vetting during account creation and password reset (which will remain free/no-cost in the API).
Some kid recently tried to have OpenPGP support deprecated from Golang's crypto-x package. And that's fine, but do not pull stunts like this without offering a concrete, working and widely adopted replacement. Otherwise, they are just that, publicity stunts with a lot of sound and fury but no solution. That's not helpful to anyone.
A more mature thing to do would be to suggest deprecation in 3 to 5 years and offer a plan of how to get there with other specific tools (some of which do not exist today).
If the data is not end to end encrypted, then it is public.
Everyone should understand this.
Edit: We went with individual purchases because the group license was way too expensive. Had we paid for that, then we could have shared the docs with upto X employees.
P.S. People often made fun of me for carrying the dumb phone. I'd always quip, "I'm too smart to use a smart phone." Feel free to use that quote when defending yourself ;)
We should all do away with password complexity rules (except minimum length) and simply test a large, comprehensive exposed password bloom filter for membership. It's very fast (constant time) and efficient and if the test returns no, then it's safe for a user to select that password.
Here's the code: https://github.com/w8rbt/bp
Also note that this approach satisfies the updated (June 2017) NIST 800-63-3B password vetting guidelines.
Metadata is very powerful and is captured on every network. It's a byproduct of the requirements of the network and its protocols. How many bytes were sent? To where from where? How long was the session? etc. They may not know what the data contained, but they'll know everything else down to the second.
It's trivial to unscramble hashed dictionary words with 123! or 2019! appended to the end.
Google should somehow note that distinction as it is important.