For all the janky looking URLs I get from eggs that only have like twenty tweets, half of them janky looking URLs, I don't believe anything is trivial for Twitter's spam filters.
> Ironically, there's a Nissan car that does enable and disable the limiter based on the GPS detecting it being on a race track or not. But they're transparent about it.
That's so indescribably worse than just killing that process the mind boggles. Breaking in a simple, predictable, and detectable way vs. corrupting data and hoping (excuse me, "praying") nobody notices.
Spying on all of the email isn't simple either. When there's a will and a bottomless font of taxpayer money in the name of national security, there's a way.
Yes, this is pretty common for printers installed in service desks at the airport. However, they tend to not have overly-branded stock because in the irregular circumstances you tend to get a pass from a service desk, you might be rebooked on a different carrier, and would therefore have a mismatched boarding pass.
Usability. One time pads have been around forever, are provably secure, but a pain in the ass.
Modern symmetric ciphers solve the "you need to securely exchange as much key material as you wish to send data" using mathematical formulas to stretch key material. Asymmetric ciphers use mathematical formulas to fix "you need a secure way to exchange keys."
Unfortunately, the math can't be probably secure, only believed secure and proved insecure.
Re-ordering tokens in the Google Authenticator app is janky as hell too, and the only way you'll know if it's going to work is if the regular view switches to one with subtly different font sizes.
Authy's not without its rough edges, but it never looks that bad.
From down-thread, regarding Google Authenticator:
e.g. setting up 2-factor with MS with the same email you use for Google will overwrite the Google one unless you rename it.
Sterilize & release programs for feral cats work; the sterilized cats compete for the same resources as unsterilized ones, but are more effective and longer-lived because they don't have to support reproduction. This not only means that the sterilized cats won't reproduce, but the unsterilized ones will have a harder time, and reproduce less.
Secondary Indexing Improvements: Query results are now sorted and paginated, offering developers much richer semantics
So the results can be sorted but are not stored in sorted order in the secondary indices?
Secondary indexes are stored sorted on disk, but segmented per vnode. Previously, they wouldn't be sorted before being returned to a client.
Suppose you're querying for "Bananas" through "Bavaria"; the node that contains "Bassoon" could return its first result before the node containing "Bananas" and "Barons", which would, in old Riak versions, result in out-of-order results.
Disclosure: I work at Basho, and have been working on riak-ruby-client updates to support the 2i improvements.
This "poison" is easy to deal with - just go again next year and win it.
At what cost, though? From DHH's post:
When you expect to win, it’s merely a checked box if you do — after the initial rush of glory dies down.
Winning isn't everything, and in fact can mean very little. Spending exorbitant sums of money (LMP2 isn't cheap) and risking your life (not everyone who started Le Mans on Saturday lived to finish) might not be worth it.
The credits at the end state that most of the actresses were hired through a firm in Portland, so I'd assume he's in Oregon, where summer days aren't 90°F.
> Oracle's files are based on the tzinfo files, and are just as vulnerable. If anything, more so because Oracle has a lot more money than the tzinfo maintainers.
Oracle's got enough cheddar to take it to court or settle out-of-court like their business depends on it.
That's one of the reasons Java ships its own; if some systems have different or absent system databases, Java's should still act the same as it does anywhere.
Lawyer-resistance; remember the situation a year or so ago when the tzinfo files were the subject of a patent claim? Oracle's weren't at risk because they have lawyers on retainer.