skysight-inc/HackerNews huggingface dataset:
This lawsuit is not about what drivers want, it is about class-action lawyers and a named plaintiff getting paid out. You are right to say that the lawsuit will not benefit drivers, but the lawyers here are not looking to help the drivers at all. The 730M figure was the largest amount for which the lawyers could get a class-action case certified against a wealthy company.
The official AE site is here: http://www.artifact-eval.org/ . It details the process and the design behind it. People who want to understand the philosophy are welcome to contact me (http://cs.brown.edu/~sk/).
An even better—or at least more informative, if less 'hooky'—title might be "We don't like EME" (https://en.wikipedia.org/wiki/Encrypted_Media_Extensions), or, slightly less snarkily, "EME will prevent the next iTunes".
You're looking at this the wrong way. The question is not "does reality match this model?" but rather "how well does this model match reality?".

You never know exactly to what exact extent your map matches the territory. But you can have a pretty good idea. Like, we know (to the extent that we can "know" anything) that models predicting the Sun will rise tomorrow match reality better than those which don't. We know that models which predict that turning on a switch will cause the lightbulb to emit light are more accurate that those who say that it's magic or mysterious.

To quote Feynman:

> We’ve learned from experience that the truth will out. Other experimenters will repeat your experiment and find out whether you were wrong or right. Nature’s phenomena will agree or they’ll disagree with your theory. And, although you may gain some temporary fame and excitement, you will not gain a good reputation as a scientist if you haven’t tried to be very careful in this kind of work. And it’s this type of integrity, this kind of care not to fool yourself, that is missing to a large extent in much of the research in Cargo Cult Science.
it is going to leave a sore taste in their mouthes and they'll never consider it when it actually is useful
Atlassian announces huge revenue growth but profit slump
A Practical Guide to Lasers for Experimenters and Hobbyists
It's not anti-immigration posts that cause an issue, it is posts that contain racism and incitement of violence. Those posts have real world consequences, and are of questionable value when it comes to civil discourse. Thus, Facebook doesn't create a chilling effect if they censor those things, which is why they are cooperative.
I may have misread it. The subject is SS7 security and here's the parent comment:

"broken beyond repair... infact it being a walled garden is the only security it ever had."

bogomipz countered with how robust the protocol is. Your critique is true if bogomipz was only countering the words "broken beyond repair" with no context. In context, though, the counter would imply disagreement with the security claim.

"isn't claiming that SS7 is secure. Nobody thinks it is."

Hopefully true. :)
I'm a partner at a global law firm. We handle these pretty routinely for both publicly traded and private companies alike. There are some funky theories in this thread. Happy to help if you want to get in touch.
Serious question, is there really laws against social media sites or aggregate sites putting a bias in what they choose to display? I'm not sure I see why this argument is valid.
Just a tiny bit of background, since I thought to myself "Pharo—where have I seen that name before?"

This is an implementation of Smalltalk. I thought that it was the new name for Squeak (http://squeak.org), but apparently it's rather a fork: https://en.wikipedia.org/wiki/Pharo#History .
One of the companies I started a few years back was born in the back of the highway 17 Express, a bus with cramped seats that blazes down a really windy road at 60 mph. It even has wifi (for some parts of the ride). After that, working on airplanes was easy. You just need to fight a bit for elbow room and hope you aren't seated between two obese people. If you're really lucky, the person in front of you will be too concerned with others to lean their chair back...but even if they do, it's workable.

Probably helps that I'm fairly scrawny though.
I could be totally wrong, I don't read a huge number of CS research papers, but aren't most published CS papers fully self-contained? They contain the algorithms or ideas within them. Perhaps in pseudocode, but fully reproducible.

The little experience I have is in computer graphics publications and (less) distributed systems publications. Graphics papers very often have data sets and code that go along with the paper. These are nice, and it would be awesome to have a common and well-known way of publishing all that together with the papers, but they are just examples. Mike Hoye's comparison to the loss of greek fire doesn't seem applicable to the idea of reproducibility by publishing code and dependencies. The meat is in the paper!

Same with my experience in distributed systems papers. I can implement Paxos at any time using only the Paxos PDFs I've saved. Companion code is nice, and again I'd be fully supportive of a system which gave permanence to not ony the papers but companion artifacts... but the paper is the important part, isn't it?
KiCAD does seem to have a tediousness problem. The tutorial shows a process for creating a new parts library which requires far too many steps - saving some random part into a new library to create it, telling the part designer about the new library, and starting from a blank part which has text in the way of what you're creating.

Also, moving something by holding "M" and dragging with the mouse seems a holdover from the DOS era. Of course, if you don't like that, you can remap the hotkeys. That's so open-source.
>The web and FB has made us dumber- we point and click and no longer have to search and think.

That is a bold and baseless statement.
Ah, sounds like Erlang/Elixir would be a better fit since the BEAM is the king of lightweight threads/processes.

You said C++ so that's why I suggested Rust, generally a GC tends to preclude spaces where C++ excels which is why I would think you'd want to try something other than Go.

On the Rust side there's things like mio for fast io but coroutine/light threads aren't really a focus afaik. I would still think you could get solid performance (and much better memory use, see Dropbox's replacement of Go) with an event based Rust system although that's not really my area of expertise :).
One little fact to shed some light on the scale of money flowing. Microsoft was caught paying under the table for shilling Xbox one exclusives, FTC released documents mentioning $15-30K _per one short video_ from Youtubers in 50-100K subs range.

YT ad revenue is nothing compared from what you can milk while astroturfing.
Not tracking namespace accurately is Git's biggest weakness and would most probably be BK's best argument for getting a tryout. With Git, renaming a file and editing it at the same time tends to make a mess of the history and cause much pain. You can say just don't do that, but I say it happens, and it should just work.
Many languages restrict or eliminate the use of pointers. C doesn't. So, it exposes whatever model it expects underneath to its users.
First thing that popped into my head when reading this title was Silicon Valley.
I hear, from people that would know, that it has a lot of bugs that were fixed internally but never made it into an open-source release.
I think the argument could be made that python 3 is an example of "great engineering" and (in hindsight) "poor customer understanding".

Python 3 is the polar opposite to Linus' meltdown on not breaking user space see: https://lkml.org/lkml/2012/12/23/75

Sadly I like Python 3 and wish it was more popular.
Advertising cannot maintain the Internet
Harmonic Patterns in FOREX Trading World – Free Education Classes
That often means "getting the bones" right, but occasionally cutting corners to get stuff done. If your focus is having a good product, which frankly it most of the time should be, then done is better than perfect.
Please don't post unsubstantive comments.

Especially about downvoting, which the HN guidelines explicitly ask users not to do: https://news.ycombinator.com/newsguidelines.html
I've been through this kind of thing. It's very unpleasant, frightening even. Hang in there!

From your critical incident report here there was no inappropriate physical contact or attempted coercion between these two people. Make sure that's correct. If your senior HR person or some other executive of your company is experienced with this (meaning: has done it before) have her/him conduct an investigation. If you don't have experience in house get your lawyer to do the investigation. Get it done; don't let it sit.

Base your decision about disciplining or terminating the guy with bad boundaries on the results of the investigation. Ask your investigator how to confront him, and follow that advice. As hard as it is to imagine right how, anti-harrassment discipline is a dish best served cold, not hot. It's also best served promptly.

You need to do the anti-harassment seminar. You need to let your whole team know this kind of stuff is not condoned or ignored in your company, because it's not who you are. Your lawyer's office can probably provide the seminar. (Our lawyers did a great job with our seminar.)

You need to establish a policy about harassment if you don't already have one. There are plenty of good template policies around. If you work with a payroll service they probably have one you can use. And you need to require all your people to take the seminar. It should be part of your onboarding process.

If you sack this guy don't worry about a wrongful termination suit. Do what's right for your business. You'll have the investigation paperwork, and the state commission on such matters will very likely look at it and say "case closed," if the guy bothers to go after you.

Also don't worry about people in your company worrying about who's going to get whacked next. Just make it clear that respect, civilized behavior, and good interpersonal boundaries are a vital part of your company culture. You could even go so far as to say "no aholes."

Good luck. But you won't need luck. You'll just need the strength to get through it, which you have.
Having made that jump over the past few months, I should warn you that KiCad has some very annoying rough edges. It's basically a bunch of FOSS PCB-related projects wedged together into a single launcher, which has then been spot fixed as individual problems got too annoying for individual users. Once you get used to it the main workflow is pretty alright, but there are a lot of facepalm-worthy 'features'.

Each program has its own (sometimes slightly, sometimes wildly) different UI, right down to things like selecting and moving objects. In addition, the PCB layout component has three different selectable "rendering engines", each of which has its own UI and available feature set inconsistent with the others. (Hint: OpenGL rendering enables the interactive routing features which speeds things up immensely.)

Information is transferred between programs via intermediate files, creating a lot of busywork to export/import changes. (For instance, to go from a schematic in eeschema to PCB ratsnest in pcbnew, you have to annotate components, run CvPCB to associate components with PCB footprints, generate and save a netlist, load pcbnew, and read in the netlist. Any name collisions with existing footprints will cause the conflicted footprints to not be updated.

Importing/vectorizing images from outside sources is byzantine and scaling images after import is poorly or not supported.

It crashes from time to time, especially in the PCB editor. Get used to spamming ctrl+s regularly.

Also, the part and footprint library management is insane and needs a rewrite.

Basically it's got all the ingredients for a great CAD package but it needs a single guiding force to turn it into a consistent, reliable tool.
> I see. And when those leeches lend capital for a new startup effort that otherwise wouldn't happen... allowing a business to form, a product to develop, an industry to blossom, on an accelerated timescale, what then? Would you still brand this role a parasite?

How is that qualitatively different from a medieval lord who chooses to permit peasants to work his fields for their survival, in exchange for growing wealthy off the fruits of their labor?

The rich graciously permitting the rest of us to share a small portion of their wealth, so that we can work to make them more wealth while incidentally keeping a bit for ourselves, is the basis for much of our society; but that doesn't mean there's no other way to do it, nor does it make them inherently virtuous.

(I'm not saying they're inherently monstrous, either. Many capitalists may be well-meaning and try to use their money for good, and that is laudable. But don't pretend that the mere fact of having and investing money makes one a hero.)

> I realize that this sort of anticapitalist nonsense is currently fashionable in university

It's been fashionable in every place and time where abusive capitalists have existed.

> but the irony of it being spouted on ycombinator (which might have something to do with investors, after all) is really quite amusing.

The header up there at the top of the page says "Hacker News". It's fashionable right now to imagine that every hacker yearns for a West Coast startup and loads of venture capital, but it's not actually true.
Moxie: there's a third alternative to centralization and federation which nobody is talking about on this thread: P2P. I'd be interested to hear your thoughts on what pitfalls someone (me) might encounter trying to implement a peer-based messaging system. I've got a lot of learning to do before I feel qualified to actually write code for such a project, but it's something I'm actively working toward.
The NSE was Suns attempt at a grand SCM system and it was miserably slow (single threaded fuse like COW file system implemented in user space). I did performance work back then, sort of a jack of all trades (filesystem, vm system, networking, you name it) so Sun asked me to look at it. I did and recoiled in horror, it wasn't well thought out for performance.

My buddies in the kernel group were actually starting to quit because they were forced to use the NSE and it made them dramatically less productive. Nerds hate being slowed down.

Once the whole SCM thing crossed my radar screen I was hooked. Someone had a design for how you could have two SCCS files with a common ancestry and they could be put back together. I wrote something called smoosh that basically zippered them together.

Nobody cared. So I looked harder at the NSE and realized it was SCCS under the covers. I built a pile of perl that gave birth to the clone/pull/push model (though I bundled all of that into one command called resync). It wasn't truly distributed in that the "protocol" was NFS, I just didn't do that part, but the model was the git model you are used to now minus changesets.

I made all that work with the NSE, you could bridge in and out and one by one the kernel guys gave up on NSE and moved to nselite. This was during the Solaris 5.0 bringup.

I still have the readme here: http://mcvoy.com/lm/nselite/README
and here are some stats from the 2000th resync inside of Sun:
http://mcvoy.com/lm/nselite/2000.txt

I was forced to stop developing nselite by the VP of the tools group because by this time Sun knew that nselite won and NSE lost so they ramped up a 8 person team to rewrite my perl in C++ (Evan later wrote a paper basically saying that was an awful idea). They took smoosh.c and never modified it, just stripped my history off (yeah, some bad blood).

Their stuff wasn't ready so I kept working but that made them look bad, one guy with some perl scripts outpacing 8 people with a supposedly better language. So their VP came over and said "Larry, this went all the way up to Scooter, if you do one more release you're fired" and set back SCM development almost a decade, that was ~1991 and I didn't start BitKeeper until 1998. There is no doubt in my mind that if they had left me alone they would have the first DVCS.

Fun times, I went off and did clusters in the hardware part of the company.
Very nice introduction to KiCad - also for people with a background in other CAD tools like me.

It's awesome to have a short but complete example of the whole process. KiCad definitely has some room to improve in terms of UI/UX flow, so that was very helpful.
In a C compiler implemented for that architecture, copying a value of memory line size could very well use an instruction that does it all at once if the registers are large enough or a DMA intrinsic is exposed. Really that's the point. C is like a near-asm language that standardizes across ISAs with the opportunity for the compiler, libraries, or programmer to do something more clever on a specific system. It requires dedication and patience, but in the end is generally a good middle ground for low level work.
Freedom of speech (in the US) online shouldn't be taken for granted.

During the aughts, treating political and opinions blogs as donations in kind, and therefore subject to campaign finance rules, was pushed pretty hard.
I think the reaction of this thread is a little over the top. Lets calm down and be professional and adult before we convict someone based on scant information. I know it is fun to rail on someone but firing a person is not a minor issue and could potentially destroy someone's career.

The information we are presented with is minimal. This is perfectly understandable but it means that no one in this thread has anything like enough detail or context to make any judgement on firing someone.

What if the man was simply making a pass at someone he liked but unfortunately was clumsy and inept at doing so? Should it never be possible for a man to ask a woman from work out on a date? What if the woman has a reputation of being a social justice warrior that hates men and loves any excuse to complain about any perceived slight. We have no idea on the ages or marital statuses of the two people. What if he is a married middle aged man with three kids and she is a young intern? That makes it sound a lot more creepy. What if they are both single and the same age and seem to have the same hobbies? Does that change things a little? You cannot judge this scenario based on a couple of sentences from the OP.

My point is not to defend him, I have no idea if he is a predatory creep or a good guy that made a simple mistake. But then neither does anyone else here. Get a lawyer so you can follow a sensible policy of sitting down with the accused and ask about his side of the story. Depending on the response determines your next action.
Microsoft doesn't support Windows 7 any more, why should WhatsApp?
You don't have to hold 'm', you can just press it while hovering over a component. Just like you can in the schematic except the hotkey is 'g'. Or you can do in the OpenGL PCB renderer (but not the default renderer) with a simple click-and-drag. Oh and you can't undo/redo in track laying mode even if you're not laying a track.

The user interface is insanely fragmented, is what I'm getting at.
I thought it was a bug in the specification? (Older joke.)
The docs explain the module system (https://github.com/antirez/redis/blob/unstable/src/modules/I...) but it doesn't quiet explain what the system is for. I couldn't quite get that from reading the blog post or the doc page. Specifically:

What kind of modules did you have in mind when designing this? Are any of the below possible?

* ldap backend login system

* multi-tenant redis

* alternate db format/file system.

* implement a new redis data type. say built-in date support

* can i implement new commands and operators on said data types

An of course, thanks for this fantastic software. We use it everyday. Will read in more detail about this over the weekend :-)
Great to see this finally happen... However, for 'us' Git remains a keeper.
Amazon DSSTNE: Deep Scalable Sparse Tensor Network Engine
Referrals don't change your position in line. We are letting people in generally first come, first-served.

We use the VIP code because there are some times when you need to let someone in immediately (important partner, people that might be able to help us test a specific feature, etc.)

I think that in general incentivizing people to share by giving them a bump in line feels unfair.
Except the New York State model in the parent post seems to suggest they ARE employees.
It's not the same because neither one of those is essentially the only global news network whereas FB, and vkontakte to a much smaller degree, is the only social network with news which has a global virtually monopolistic shop.
This is buried but in case anyone reads it, the real reason to open source BK is to show the world that SCM doesn't have to be as error prone or as complicated as Git. You need to understand how Git works to use it properly; BK is more like a car, you just get in and drive.
If you are a maximizer – how do you make decisions?
Recently had a strange decision circumstance, I had to choose if I would go for a weekend course or not. There were reasons for why I would really go, but also wariness that it could go wrong and I would be stuck there. It was not the classical choosing among endless alternatives case, but as a maximizer the emotional state was very similar. The same creeping uneasiness, the relentless scanning for any possible detail/hints how it would go. This numbing feeling that I somewhat perhaps could do better, but all of this without the actual alternatives, indeed more like staying with the default.

What I would be interested is what others found useful in this situation, what had worked for you? What kind of thinking ends you up with a state, where you are content and satisfied with your decision? (I'm actually not fan of the numerical/utility/probability idea, I'm more into what would be a mental process, step-step framing and processing the alternatives/context, I'm just not sure how)

Taleb had a quote about this which I really like, he said that if we have more than one reasons to do something, it's quite probable that we are trying to convince ourselves to do that thing, and deep down we probably have some reserves. If the case is that we need to be robust to error, eg. deciding to marrying someone, it's better to just not do it. But in my case it's obviusly not this kind of big decision, and indeed probably a good source of learning experience, but also exactly the "convincing myself" case, so how one decides?
http://www.goodreads.com/quotes/715415-if-you-have-more-than-one-reason-to-do-something
I was wondering if these exist. My last counter of D-Wave is they could be using a good algorithm with specialized ASIC's or regular HPC hardware in a cluster. As in, they're certainly accelerating things but making up the quantum part. That possibility has to be eliminated.

That there's classical algorithms that might get a similar speedup, esp if on custom hardware, validates my prior concern.
Apparently a human-readable homoiconic language is still an unsolved problem...

In 0.17, commands and subscriptions mean that, not matter how deep you nest components, you can still send and receive messages to/from the outside world (i.e. ports).
Wayne pointed to some stuff over on the reddit thread.

As for size it's csets * files, as that gets big, Git slows down faster than linear, we're pretty linear.
In mobile, it's not intuitive that adding synonyms populates them below. I found myself pushing it several times and thought it was broken.