aboutruby
aboutruby on Hacker News
I think most people (including me) didn't like the 1.4 to 2.0 "transition" (e.g. not a single ounce of backward compatibility, basically Angular 1.4 was abandoned)
In my experience, most APIs requires a 1-on-1 association between the application's user and the API user (if some information about the user, and associated records, are stored in the external service).
I think the correct keywords for this would be "tool assisted continuous scrapping"
It's a series of illustrated articles (linked at the bottom)
> Deliveroo has blamed the breach on cybercriminals getting hold of login details “stolen from another service unrelated to our company in a major data breach”.
> This is despite the company not asking customers to enter a Card Verification Value 2 (CVV2) code when making orders, a card security system designed to ensure that someone ordering something online has physical possession of the card used to pay for it.
More info on an article from November 2016: https://nakedsecurity.sophos.com/2016/11/25/fraudsters-eat-f...
BBC's Watchdog documentary: https://www.bbc.co.uk/programmes/articles/3ZMjkWFfDZQ8zFYQJL... (with response from Deliveroo)
Seems to me like some of them got laid-off and some got reassigned.
I'm not doing PHP anymore, but never heard of PEAR, everybody seems to use Composer since quite a while. Seems like the transition happened in 2014-2015.
One interesting bit is that it could be linked to a medical condition of Employee 2 (peacemaker for instance). And an employer can't ask about an employee medical records.
Kind of misleading as it requires a native application (the bridge).
Same as people using goo.gl URLs
> a malicious mirror could still exploit a bug like this, even with https. But I suspect that a network adversary serving an exploit is far more likely than deb.debian.org serving one or their TLS certificate getting compromised
Exactly, this is far more easily exploitable because apt is using HTTP by default instead of HTTPS
May help with general spam. I think regulating groups would be a much better idea:
Possible limit of messages per day/hour/minute
Possible limit to certain members as "viewers"/"spectators"-only
Possible threading (otherwise responses about a certain information are just buried / mixed)
The foot example with Samsel Linear YGB is simply amazing!
I wouldn't put so much trust in this unknown package manager, Chcolatey or Homebrew on Windows would be far better choices.
There are also two buttons next to it: "OK, accept all" and "Personalize". In "Personalize" you can allow/deny all and/or specific services.
You need to have Facebook enabled for instance if you want to use the Facebook sharing button at the bottom (same for Twitter).
And everything is disabled by default.
So it does seem like the correct way to do it.
Should be HTTPS by default just for the privacy of downloading packages without any intermediaries knowing the package names. It could easily be collected and used in attacks against users of vulnerable versions.
Also oversized to compensate for the low price-per-kilogram
If I knew about it I would have bought one and told everyone I know to buy one.
Great idea. For some reason it kept removing my semicolon after I used the time-traveling.
Did you expect to have most of the information in the world available on demand? Anywhere? And be able to communicate with anybody anywhere? I guess it's hard predicting the future
http://www.paulgraham.com/ecw.html
When will people rent Hacker News accounts?
I thought "Oh! Exactly! That is definitely his type of humor, makes so much sense". Especially the actual accounts he quotes are often very small and quite specific.
I'm very surprised they didn't find him based on the least quoted people's followers actually.
From Wikipedia: "The test fails when browsers become compliant with current CSS collapse and margin standards."