Most attendees didn’t expect “100x cooler” to translate into “we’ll post spam in your feed as soon as the RFID badge senses that you’ve entered the show", but that seems to be what happened.
More accurately, it
Not here it isn't. As per RCW 46.61.755:
(1) Every person riding a bicycle upon a roadway shall be granted all of the rights and shall be subject to all of the duties applicable to the driver of a vehicle by this chapter, except as to special regulations in RCW 46.61.750 through 46.61.780 and except as to those provisions of this chapter which by their nature can have no application.
RCW 46.61.750 through 46.61.780 cover:
750 - penalties
755 - the above
758 - required to use hand signals
760 - move use a seat
765 - must not cling to vehicles
770 - must keep as far right as is safe to do so
775 - must not carry anything that requires two hands
780 - lamps and reflector requirements
No where does it permit a bicycle to pass a vehicle that's stopped waiting for traffic on the right side of the vehicle. They could pass on the left if passing were permitted, but not split between lanes (that would be passing on the right of the left lane cars).
Games do not by definition, have a winning state and conversely a losing state. Many do, to be sure. You might want to read up on the philosophy of games a bit. I can recommend Huizing's Homo Ludens as a good starting point. Even of the definitions listed on Wikipedia's entry for Game, many of the definitions do not mention a winning state.
When it comes to handling ice, it's all about the tires, not the drive train. If you mean snow or wet, then yes, the drive train makes a big difference.
Next time take a day off once you have the game, it's installed, and the servers are not on their knees. It might be a few days later but you'll get your day's worth.
You generalize about NYT employees' but deride generalization in general.
So you are saying the people that pay back the cost of their eduction did not work for it, but the ones that were given money they didn't have to repay worked for it. Both groups worked for it.
Unless things have changed very recently, the US government allowed you to file a form informing them of the taxes you paid to your resident country and deduct that amount from your US taxes. If you lived in most of the civilised world, that meant you paid more than the US rate anyhow and had a US tax liability of $0.
When you get old enough to drive, and try driving a car with essentially no steering (because the power steering pump is no longer providing pressure) and little brakes (ditto for the brake pump)... you'll understand.
Power steering is completely useless at speeds over 30 km/h and power breaks will get you a good two more firm applications of the breaks before they lack the power to assist. I recommend more driving experience before you abuse others with your faulty theoretical knowledge.
I would say no, putting sensitive data on a machine that's shared with others is a bad practice no matter how you do it.
Yes, of course, but that would be a pretty bad design. If some third-party is storing my credentials, I'd rather have to re-authenticate when they plan maintenance than have them store sensitive data unencrypted on disk.
It wouldn't be all that secure in-memory, but an SQL injection attack won't reveal it. It's marginally more secure. I was merely answering the question about what a potential key to that field in the database would be.
Under a requirement to pass this password to a third party when "linking accounts" (that is, making requests of the third party on the user's behalf). It could be stored encrypted in the database, but with what key?
If the user is passing a clear-text password, you could use that as the key for their other passwords. Use your stored hash to validate their password, use their password as the key for their third-party data.
If the user-agent is passing a hashed password, use a different hash as the key for third-party data. Send both hashes to the server, which uses one for authentication and the other for decryption of the third-party data.
The only problem with this not effecting you is that it very well might. Those stores that you go to six months after release to get a game for $20 are unlikely to survive very long when their biggest revenue producer (i.e. used-game sales) vanishes.
"Most people would like to be delivered from temptation but would like it to keep in touch." -- Robert Orben