skysight-inc/HackerNews huggingface dataset:
People drive under conditions that they shouldn't, I know kids that wont wear a seatbealt and never follow rules in general.

What I'm trying to say is that, same as with alcohol, people are still going to do it. Legalization won't change how people feel the effects of pot affect their driving.
Loosely related, how do you pull this off? Given that interviews effectively take up whole days, I feel like it'd be really tough for me to routinely work four day weeks and everyone at the office be OK with it.
God forbid you let people work from home.
Every Team’s Chances of Winning in Every Minute, According to Gamblers
Meet Jack the Plumber/ Philosopher (2013)
Hey, it has a cool name and it's made by Facebook. It must be state of the art tech, right?

Trolling aside, Flux really doesn't bring much to the table. It's trying to solve the pain caused by two-way-binding by forcing state to flow in one direction through an event bus, reinventing MVwhatever along the way.

You can already do this stuff in Angular (et al) if you stick to a few firm rules for how to structure your app.
Israeli cable reveals S Africa missile theft cover-up
Exciting New Features Announced by Aspose.BarCode for Cloud SDK for Ruby
"What does that mean?"

All I really meant is known commodities with proven track records in kid's learning and edutainment properties. Reading Rainbow (cited in the blog post) is a good example. Disney might be another hypothetical example.

"I'm one of those minecraft weirdos and I can authoritatively say based on many hours of entertainment viewing that Direwolf20 and Pahamir have never said anything non-G rated, at least in their team video series so far as I've seen. So that's boring and no point discussing."

I'm not saying these folks aren't kid-friendly. I certainly didn't mean to draw a qualitative distinction between, say, Disney and Direwolf20. I didn't mean to create a category "kid-friendly" in which these sorts of creators do or do not fall. I was speaking more broadly -- and speculating, as I mentioned -- about what Google seems to be up to.

All of this is speculation on my part, based on having closely followed this space, having followed YouTube/Google's job listings very closely over the last four or five months, and having had casual chats with friends at Google and YouTube.

"So video training a 3 year old to walk around the house saying "damn it" randomly is not going to fly, but how about a kid who's in his last months of preteen? Especially if the video is 99.9% G rated?"

My understanding is that Google is focused very specifically on the young, young demo. A 3-year-old fits into what I understand of their thesis; an 11-year-old might not. But again, this is my best guess. I can neither speak on Google's behalf, nor claim any special knowledge above and beyond what is publicly available.
Illegality doesn't help, but there are jurisdictions where marijuana is legal. In fact there are plenty of studies, but the answers are so disparate that the original study authors reasonably chose not to factor them in: depending on whose studies you believe, a couple of joints a day could be a bit more likely to induce lung cancer than a few cigarettes, pose a negligible risk or even mildly reduce the risk if you're already smoking the tobacco.

A bigger (although not entirely unrelated) problem than legal status is that controlling for appropriate variables is an absolute minefield when studying usage of something as heavily correlated with certain demographics, behaviours and attitudes as cannabis.
Working with WaitCondition on AWS’s CloudFormation
Yeah, I'm feeling like the quotes should be around "Hacked", and not "Encryption"
Everytime I see the Flux architecture I wonder what does it bring to the table that a reactive programming library like RxJS or Bacon.js don't? It seems Flux is just hacking together well-defined concepts in these libraries.

* Stores could use Observables instead of EventEmitter

* Components become Observers by subscribing to Observables which is extremely similar to setting up Listeners.

* Instead of Actions through a Dispatcher, Actions become Proxies (or Subjects in RxJS terms or Buses in Bacon.js terms) that Stores subscribe to and Components push to.
I think he's talking about doing this on such a scale that it has a measurable impact on the trend.
Because this isn't really a vulnerability. It's "if you completely control the device that is sending/receiving encrypted messages, you can read the messages."

There's literally no way to defend against this attack. About the best they could do is show a warning like "Warning: The version of Android you are using contains vulnerabilities attackers could use to take control of your phone. Please update your softw... buy a new phone to get the latest version of Android."
- he's figured out the KVM issues, their lack of support for some mandated hypervisor APIs and other bugs

- then found the existing powerpc pmap (physical memory management) code wasn't very SMP friendly

- also found the PS3 hypervisor layer isn't thread-safe

These are some of the reasons that I care about NetBSD (which runs on some 56 architectures with its single codebase) so much -- the real-world work supporting real-world architectures can pay off everywhere -- it's not just academic work or nostalgia/eccentricity.
Your prose exhibits that rambling not-to-the-pointness that I often encounter when interacting with habitual blunters.
It can take a bit of unpacking, but someone with some sort of college level physics and mathematics background can use Wikipedia to get a basic understanding of what they are talking about.

They are basically saying that the quantum mechanical 'strangeness' of light can be explained with classical, deterministic, physics. It is not necessary to have a separation in which quantum mechanics predominates at one level and trumps classical mechanics.

It call all be understood as movement of 'particles' of light (photons) on an underlying wave.

http://en.wikipedia.org/wiki/Magnetic_flux_quantum

http://simple.wikipedia.org/wiki/Magnetic_flux

http://en.wikipedia.org/wiki/Flux_tube

http://en.wikipedia.org/wiki/Quantum_vortex

http://en.wikipedia.org/wiki/Wave_packet

http://en.wikipedia.org/wiki/Maxwell%27s_equations

http://en.wikipedia.org/wiki/Differential_equation

http://en.wikipedia.org/wiki/Polarization_%28waves%29

http://en.wikipedia.org/wiki/Bell_test_experiments

http://en.wikipedia.org/wiki/Fluid_dynamics

http://en.wikipedia.org/wiki/Pilot_wave

http://en.wikipedia.org/wiki/De_Broglie%E2%80%93Bohm_theory
I still think Flux will be handy for holding global UI state. Such as visible notifications, sidebar state, etc.
Having people constantly walking behind you is incredibly distracting.

Interesting. I'm exactly the opposite. When I see people walking in front of me it's a total distraction. It makes it almost impossible to concentrate.
100th Merlin 1D engine flies on Falcon 9 rocket
I guess the carriers are scared enough of Apple Pay that they're willing to work with Google now.
I am not even a security novice, but isn't getting root on the devices basically a game over? The suggestions the author hard to encrypt the stuff in memory and on disk would just add a extra step for the attacker to find the key? If they key had to be entered by the user every time the attack can just wait until the user does so? If thats too hard... just monitor the user.
With root you can just wait and take screen shots... (as the author shows) which would work for any thing the user does ever and is simpler?
I'm not sure about your takeaway from that link. In the Summary:

"For example, the results of this study suggest that if a randomly-selected driver in his or thirties and a randomly-selected driver aged 85 or older were to drive equal numbers of miles, the older driver would be over 1500% more likely than the younger driver to be responsible for and die as a result of a crash, and about 220% more likely than the younger driver to kill an occupant of another vehicle or a non-motorist.

However, drivers in their thirties drive approximately 217% more miles on average than drivers aged 85 and older do. Without statistical adjustment for what occurs naturally, a randomly-selected driver aged 85 or older is about 720% more likely than a randomly selected driver aged 30 to 39 to die in a crash, but only about 0.8% more likely to kill an occupant of another vehicle or a non-motorist, over the course of a year."

I haven't gone back to review what the author means exactly by "statistical adjustment for what occurs naturally"
At my last job we had open floor plans.

The top boss has his own corner office. It was all glass so he can keep an eye on everyone.
Also neat that you really can recompose the entire conversation, as the timestamps are clearly available in the DB.

Offset 0056e1c, 0x54ba8a1d is unixepoch 1421511197 - which is January 17th, at 16:13:17GMT - which, given that the author is in Tel Aviv (GMT+2), corresponds with the 6:13PM timestamp for 'Shlookiedo' seen in the photos.
Perhaps because the attacks/exploits were more against the device/OS and not against the app itself?

It is unsurprising that text can be found unencrypted in memory---even while during rendering it has to be decrypted somewhere.

The only mildly surprising/troubling thing was unencrypted data stored in the file one disk on the phone.
How to Hustle – A mailing list for hustle tips
A large part of why different teams end up building the same thing is it's not actually the same thing. The details are frequently different is subtle but important ways.

Often building a single piece of software to assist 4 teams is several times more difficult than simply rewriting that code for each of the teams. Sure, that’s not always true, but for such generic needs you can generally use or start an open source project.

IMO, the best of both worlds is to have an architecture team that approves designs created by a developer team. Ego often gets in the way, but the advantage is ‘Architects’ can keep track of wider segments of the organization when you treat them more like building inspectors than building Architects. With the added advantage that they can help teams cross pollinate vs. trying to come up with an ideal design in a vacuum.
Hey everyone, I just posted the first blog post and sent the first email out on the mailing list.

Here is the Medium Publication: https://medium.com/how-to-hustle

Here is where you can subscribe to the mailing list: https://tinyletter.com/How-to-Hustle

Feel free to provide feedback and criticism!
This article and your observation remind me that there's a huge gap between ways in which bugs might be "shallow".

If Linus's Law and so on really did rely on people encountering the bugs by chance in everyday use of the software, it's no wonder (in hindsight) this doesn't help with a lot of the security bugs we face, many of which would never be triggered randomly in normal use, but rather require constructing elaborate attack scenarios. Even those that might occur by chance are not likely to be repeatable, and so not likely to get reported or analyzed.

Maybe this points to a change in our prototypical concept of a "bug". When ESR first wrote "The Cathedral and the Bazaar", I would have associated "bug" with something like "the TIFFs produced by program A can't be read by program B", or "program C seems to crash if you have a non-ASCII filename", or "program D drops its network connections if more than 65536 packets are received". Today, I would associate it with something like "an attacker who sends a certificate containing an extension with invalid ASN.1 encoding that follows one or more syntactically valid extensions that are marked Critical and that are unknown to the user-agent can get remote code execution" or "an attacker who sends an XML payload that is parsed correctly by library A and incorrectly by library B due to discrepant handling of Unicode escaping can request operations that should be forbidden".

Well, a literal hot-off-the-presses example would be a bug in handling multibyte characters in the regular expression library in Flash Player, which was exploitable:

http://googleprojectzero.blogspot.com/2015/02/exploitingscve...

In other words, these bugs are often complicated artifacts that require research to find and malice to use -- not annoyances and breakages that are frustrating end users every day.
BLAST can handle many more cases than the method listed here...
Appops. Supposedly there as a test system for apps. I guess to see if they would crash in case of malformed data from sensors etc.

Some OEMs, like Huawei, offer similar functionality on their products.
> That's complete bullshit.

Why? Because you say you say so? You got down-voted because you equated the word "Gun" to "Murder" and "Kill". That is what I call bullshit, and fear-mongering, and just plain old FUD.

> What on earth are you going on about? ...

Acting as if using the term "Gun" is a negative because of it relation to violence does a disservice to any and all anti anti-gun movements. There is no way around it. You might not believe in gun control yourself (and that's irrelevant in any case), but this attitude is nonetheless part of the problem. People should be taught to understand and respect guns, not to fear them implicitly.

> When did the mere questioning of the name of a product ...

You didn't just express the dislike of the name, which by the way would have gone down better with me and most probably with everyone else, but compared it with a totally over the top "names" that do a have a definite negative connotation.

You say we're overly defensive, but that would be incorrect. Most people just down-voted you and moved along. I decided to go ahead and tell you why you got down-voted and explain why your comment goes down in a sour manner, after which you decided to defend your position at any cost. The only one with a defense reflex and overly defensive behavior is you.
Yeah...it doesn't feel like a true vulnerability...feels like just padding the "vulnerability" counter :p
Congrats on shipping! The game looks great. Do you mind if I port this to Android? (with due credits of course) :)
Can't do that, we looked at the VPN logs and no one ever logged in.
The answer is (effectively) none.

In other words, for a typical $15mm exit, as an employee (meaning no preferred stock, and thus subject to a 50% tax rate on exit), you need to own ~13.33% of the company (pre-dilution, and thus, pre-Series A employee) to net $1mm and make you a millionaire. Of course, most companies go through plenty of dilution. If typical dilution is half, you therefore would realistically need to own more than 25% of a company to net $1mm on a $15mm exit.

No employee receives 25% equity of a company - single founders are lucky to have 25% when they exit. First hires / founding team are lucky to get between 2-5%. Assuming 3.33% (which is still high), dilution and taxes, you're now looking at a $120+mm exit to become a millionaire as employee #1.

What is the likelihood a company exits for $120+mm? For YC companies, 10% have exited (54 out of 548 according to YC List). Of that, only 3 have ever exited over $120mm, which represents ~0.5% of all YC companies. Many are still active and valued over $100mm, such as AirBnb and Instacart, but again, since they haven't exited in your 4 year time slot assigned to the problem, we can't say what they will be worth, or if they will even exit or IPO in the next 4 years.

So if you manage to land a first employee spot at a coveted YC startup, you have less than a 1% chance of becoming a millionaire in four years from that company. So your typical startup after series A is virtually impossible by the odds. Therefore you either need to (1) start a company or (2) earn a high enough salary (or mixed income sources) to save aggressively that you can be a millionaire in that time.
I'd definitely say American drivers, as a whole, are less prepared for and take too lightly the responsibility of driving a car. It is far too easy to get a license in this country: My test consisted of me, at sixteen years old, going around a suburban block with very little traffic at about 35 miles an hour, followed by a brief parallel parking test (a test I consider far less relevant than, say, being able to merge on a busy freeway at high speed). To qualify for this test, I only had to purchase an online driving course and fill out forms claiming that my parents had been me with me while I drove - none of which required time with a trained instructor.

Contrast this with China - one of the countries that you listed as an example of having bad drivers - where to obtain a license you need to pay the equivalent of a few thousand USD for a rigorous driving course in an isolated area (you can't even drive on the road before you have your license; learner's licenses do not permit you to drive on public roads). After this, you are still under some limitations until a year after you've obtained the license.

In addition to this, the more aggressive driving culture of China involves many more vehicles jostling for smaller spaces than would be the case in America. The skill and spatial awareness of the vehicle necessary to cope with this sort of environment is far greater than that needed to deal with even the most demanding driving environments of America.

We are definitely more laid-back and polite in driving than China (and I would prefer that any day) but more skillful? I highly doubt that.
= About Python regexes =

Aiui "The Future of Python Regexes" SO answer at http://stackoverflow.com/a/7066413/1077672 written by regex (and Perl) expert Tom Christiansen (and last updated by him in 2012) is still good info.

In brief, https://pypi.python.org/pypi/regex appears to be the path forward for Python. This engine is much closer to the power and Unicode compatibility of Perl 5's default regex engine.

= About Perl 5 regexes =

Aiui the default Perl 5 regex engine is significantly faster than the 're' regex feature included with Python 2. I don't know how it compares to the new 'regex' module.

Regexes in Perl have the advantage/disadvantage that they are syntactically integrated in to the language (a disadvantage if you don't like it being integrated).

Since Perl 5.10, a different regex engine can be plugged in and used without requiring any change in code that uses regexes (unless an engine uses a different syntax of course). (But it takes a lot of effort to package a regex engine up for use with Perl 5.)

A given regex engine can be extended using the overload module. Extending is relatively easy.

= About Perl 6 regexes =

A whole new ball game, two decades ahead of Perl 5 regexes.

http://en.wikipedia.org/wiki/Perl_6_rules

http://doc.perl6.org/language/grammars

https://github.com/moritz/json/blob/master/lib/JSON/Tiny/Gra...

Generally matches Perl 5 regexes feature-for-feature but with a much cleaner syntax. More importantly, unifies regexes and grammars.

Currently way slower than Python or Perl 5 regexes. Supposedly will eventually (5 years? 10?) incorporate all the key optimizations in the Perl 5 engine and become faster than Perl 5 regexes.
I like the numbers. What's the font?
Agreed, though I actually think that this happens earlier in the decision tree. A lot of people with the talent to be top software developers never enter the field in the first place, as part of a rational market response to pay, career prospects, and working conditions (keep in mind, we're talking about an academically talented and hard working group of people here).

I don't think it's open offices per se (though they aren't exactly improving the appeal of software dev jobs), so much as the employment conditions that lead to imposing open offices on a class of worker that so clearly benefits from a quiet, focused environment.
Misleading title.

Based on the article content, a single quoted sentence, the CIO doesn't say that.
Big thanks to Bruno for making beautiful humanoid robots.
Yeah, the inherent advantages of self-driving cars look set to moot these debates within the next decade.
Cannabis has a ridiculously high LD50, everyone knows that. When I think "is cannabis safe" I'm not wondering if I'm one day going to smoke so much weed that I keel over dead, I'm wondering if habitual marijuana use would lower my IQ/damage my lungs/etc.
> What always ended up happening is that said CEO/boss would then informally requisition the shared conference/meeting room as their own personal office ..

... and it's followed down the chain, by VPs requisitioning "war rooms". If your bloody "war" is lasting more than a week, it's not a "war" anymore!
I agree, but in this context I think that it's a valid criticism as their business model is a sort of 'all things under one roof' delivery system that should be prepared to offer a simple delivery like this one ate a competetive price/timeframe. I'm definitely not saying that people starting a business, particularly one in a service capacity, shouldn't expect to have to adapt with growth. I suppose the main point I was making is that prior to launching you should ensure that you are fulfilling your core functionality to at least a market-comparable level.
Precisely. Also perhaps why Telegram didn't respond.

This is an OS-/device-level attack---not an app exploit/attack.
Degenerate nucleotide matching (using this method) is only possible with 4 bits of data.

If BLAT is using this method for counting matches, I'm unaware. The algorithm is reliant on storing nucleotides in 4 bits, so I doubt it uses this exact method.
One of the most elementary self-defense concepts is that you don't leave your back to a door, the classic US example being Wild Bill Hickok: https://en.wikipedia.org/wiki/Wild_Bill_Hickok#Death_at_Dead...

I personally want everyone behind me to be known, with entries where strangers can come from somewhere in my direct or peripheral vision range. Or a loud enough door that I can hear someone opening it.
If the only people agreeing with you are Glenn Greenwald, Socialist Worker and Esquire, then maybe your argument has a problem.
Closed-source requires enough commercial incentive by one firm to look at it.

Or a motivated attacker to reverse it for exploits.
Noteworthy, technically Noteworthy Bold
Applying Lessons from React JavaScript Conf at Social Tables
This video summarizes the engine's exploits:

https://vine.co/v/OQTB6FK7ADV
The 100th Merlin 1D rocket engine helped launch #DSCOVR to deep space. From CA → TX → FL → space, it’s had quite the ride.
> build team rooms for up to eight people instead of large floors with lots of people.

This is the right way to do open office planning. Consider Conway's Law. Teams are organized horizontally by how the system is designed by logical or physical system boundary. And you let people move from team to team to get good cross-functional ability and understanding.
With the rake tasks, you're better off learning "rake -T" (list all rake tasks that have a description). You can find the one you need in there, and the most common ones will soon sink in via osmosis as you use them regularly.
wake up (no alarm)
kiss wife off to work
masturbate
watch GMA
eat cereal or something
nap
shower
brush
find cleanish clothes
Hi-Ho Hi-Ho, it's off to work I go.
Of course the firmware could hash itself. The question is what value is there in trusting and untrusted component to tell you it's trustworthy.
Yeah, so he's using heads-up hand strengths. So how well QQ fares vs all other hands, for instance, but only one hand at a time. (It's not QQ in a pot with 9 other hands.)

Then he computing weighted hand strengths based on frequency of opponents playing a hand. So now QQ doesn't win as often, given that the opponent doesn't play 27o very often so you don't actually get to win hands vs 27o (they don't occur).

BUT to determine how often an opponent plays a given hand, he's using the IRC poker database, which is full-table hands. So we see that people play K7 infrequently, for instance, which is true at a full ring game. But in a heads-up match, K7 is played very, very frequently. 85%+ I'd say, but easily 75%. [1]

[1] I played heads-up poker professionally for a few years. I logged millions of hands.