skysight-inc/HackerNews huggingface dataset:
> And where is that?

To censorship[1].

[1]: http://www.bbc.co.uk/newsbeat/article/33280133/apple-removes...
A Peek Inside Google’s Efforts to Create a General-Purpose Robot
It's possible to use the App Store anonymously. For example, Apple allows users to create and use accounts via Tor. And it accepts gift cards, which one can purchase with thoroughly anonymized Bitcoin. Getting devices anonymously is the hardest part. Paying cash for used devices is probably the best option.
For more sites that support U2F (or how to bug them to add support): https://news.ycombinator.com/item?id=10315888
I can explain some of the reasons behind this in video games. Design is hard and in some cases impossible because you want the game to be everything to everyone regardless of their play style or level of competence. This is why you get so much optional content and every decision you make has trivial or superficial consequences. Imagine mario kart rubberband mechanic outside of racing games. If done well it gives you the feeling of agency and achievement whatever you do, if done poorly you feel like the game plays itself. I remember when my innocence was shattered when I was given the task to write code that would subtly "fix" user inputs to do the "correct" thing. Makes my laugh today but back then it felt wrong for that reason.
I think "consumption" is baked into American culture.
Most people are not going to save, period.
What I always fail to understand about Wasabi: why did they keep the code in the source language and compile to CLR object code, instead of running the same parser with a different codegen target, to transform the PHP wholesale into valid C# once, and then overwrite the codebase with that?
Thanks I'll try it next time I drive. Unfortunately in my city Google Maps is the only app that provides public transport directions.
Experian breach may have exposed 15M T-Mobile records
Security? What security?

Every single release with iOS has been totally broken security-wise, as can seen from the existence of jailbreaks.

Apple doesn't even require seeing the source code, and so there is no way they can stop malicious applications written to evade detection from getting to the App Store.

And thanks to their policy you must browse with Safari WebKit, which is a nice juicy ~40% browser share target.

Of course, both Android and Windows Phone are broken too, since they also expose oversized monolithic kernels written in C to random applications, but at least Android doesn't require you to give up freedom to get non-security.
Please, no 1-year cliff for co-founders. And the ceo should have the exact same terms as rhe other co-founders.
I'm at
I was talking to a manufacturer of fuel pump payment terminals and he was commenting that in the US we have spent the last 10 years training customers to dip their cards into the terminal and remove them before pumping fuel. Now the cards are going to be clamped in the terminals (in 2017) and not available until after the pump is returned. He guaranteed that it will be a nightmare with people leaving their cards behind at the pumps.
The terms don't say you can't produce software destined for a fork of Android, they say you can't fork the SDK tools themselves. Amazon was never in violation of these terms, and save for Google's proprietary SDKs (Play Services), Fire OS has always been fully API-compatible and "binary-compatible" (in the bytecode sense) with the Android platform release it is built upon. Amazon has never distributed the Android SDK tools, let alone forked them.

So I guess I'm not sure what this example proves.
It's a great blog post, but be careful what you wish for. If you have true preemptive threading as in Java or Go, a race condition can happen anywhere. I suspect many JavaScript developers would be sad about not having atomic event handling by default and having to learn to code much more carefully.

Even in Java UI frameworks like on Android or Swing, you have an event loop with a single thread, and when spawning another thread you have to deal with special communication layers [1]. True multithreaded UI's seem like an area for research.

[1] https://developer.android.com/training/multiple-threads/comm...
Locus | Full Time | ONSITE, VISA (Bangalore, India) | http://locus.sh/

Locus is hiring Engineers and Data Scientists.
At Locus we have an ambitious goal of Scheduling & Tracking the World transport movement. We are aware of how audacious the goal is, but we have made our initial strong footholds and have the path to move forward. Founded by a team of ex-AWS engineers, comprising of graduates from premier Indian Tech/Science Institutes (IIT/BITS-Pilani/TIFR), Locus is funded & mentored by the most respected investors and ex-entrepreneurs and have product validation with actual paying customers.

Engineers: We have always maintained a small, but high-caliber engineering team, and we are now looking to make a couple of additions to the same. We are hiring for mobile, backend & front-end. We are tech stack agnostic. We would prefer to have a look at your GitHub repo or a mobile app that you have built, over your academic/educational qualification. We are a founding team of engineers, and understand that good engineering is part science part art, we would like to provide you the tools for the science and the time for the art. We are expanding the team to build the next version of our true multi-tenant platform with a few thousand events happening per second.

Data Scientists: We wish to push to edge of what is possible, and advance the field of routing problems itself. If Travelling thief, Knapsack, Capacity planning and other optimisation problem excite you, we are looking for you. We are team of PhD scientists and engineers with background in stats, working on building faster & more scalable implementation of NP-hard problems, or even a combination of a few NP-Hard problems.

While we have pizza, beer, whisky, drones, oculus rifts, raspberry PIs on the house, the biggest perk we provide you is a remarkable team. We would love to spend our most productive years, around people with great intellect and unbridled enthusiasm. In the spirit of keeping you at your productive best, we give you free fully furnished housing with internet, food & laundry taken care of, and your choice of tech gear. Read more about what we value and our work culture at http://locus.sh/careers
> you need a $500+ scale to dose it accurately enough to keep a human from overdosing.

No you don't. It's not hard at all using milligram scales < $50. I do it all the time with various substances... including caffeine.
I brought Fogbugz into two organizations (100+ accounts) as a QA Engineer and it worked great -- when it came to bugs.

When we started doing agile (and then "Agile" ... ugh) development the entire process broke down. There were no (good) plugins that could do kanban and moving features from state to state to state dramatically increased the size of an items log. That, along with the friendly, and then suddenly not so friendly filtering lead to our team dropping the product and moving to Jira.

While Fogcreek's "Fastbugz" was a gallant effort in modernizing the application stack and speeding up page loading time, it fell short as it didn't functionality support feature _and_ bug management.

I should note, we had reached out to Fogcreek with all of our requests and critiques but they weren't interested in hearing us out passed the usual account or customer service manager.
If I don't use my phone (5S) it will make it three days. But if I am sitting around surfing the web, using Snapchat and Facebook, I can burn the battery up in six or seven hours. I get up at 7am and I've had days where I was at 20% by 1pm if I used it enough.

Then you have the mystery usage when the phone gets hot to the touch just sitting in my pocket and I can almost watch the percentage drop.
The iCloud hack was enabled by the automatic backup feature that despite storing very sensitive information didn't provide adequate security for doing so. If there were actual precedent for Apple caring about their users privacy, there would be outrage over this rather than being trivially dismissed.
The Joyful, Illiterate Kindergartners of Finland
Self Tuning Texture Optimization
What a Family Movie Can Teach Us About Passwords
The Machine that Indexed the Bible (1955)
Setup OS X 10.11 El Capitan Developer Environment Node.js Io.js After Install
Slow storage (HDD instead of SSD) would also make a huge difference.
Do you really want to inherit autogenerated code? I doubt the autogenerated C# would be nearly as easy to understand or read as the original Wasabi code. I also think writing CLR object code, if it's anything like writing assembly, would be much easier to generate than C#.
You may want to consider renaming your library. There's already a very popular lib with the same name: https://github.com/caolan/async

Edit: it appears that the caolan async lib came out after yours. Sorry for the confusion.
this could be worth a look if you want something a bit more 'modern' looking

http://www.telescopeapp.org/

good idea though :-)
The Android dig at the end is wrong. I don't know what he means by "basically turn everything off and turn your $600+ phone into a dumb phone" but an Android phone is still very usable in low battery mode. Basically it dims the screen, slows the CPU and limits background data syncing. Probably the same thing the iphone does.
Well it conflicts with what we've heard from multiple sources.

I thought I recalled Obama saying that all meta data was stored. Regardless...

How did they detect when a US citizen was using a phone abroad, or a terrorist using a landline phone in the USA? Identities are not tied to phones.

Furthermore, how secure is the system they used? Can adversaries tap in to the NSA database? Is the filtering "hard wired" or is it something that is programmable and how susceptible is it to bugs, viruses, or hacking? How trustworthy are the people that control this data? Is it possible that anyone that works at the NSA is not trustworthy and might defect? Such as Edward Snowden?

These are important questions. Even with 'filtering' there is a lot of questions to be asked. And I doubt all them have great answers. The point is, there is a system in place to problematically spy on any phone conversation at any time among other things. Even if they use it "for good," that should be very concerning for anyone that knows that programming secure systems is mostly an effort in futility. Especially for the government who can't even code up a CRUD healthcare website without issue - and that the system is completely closed source not allowing others to review it.

Which brings us to another issue - why was this secret? Isn't this the kind of thing that should be approved by USA citizens? And publically verified for safety and security? This alone is so concerning.

I'm happy you think "filtering" makes all of these questions a non-issue though.
Analysis of Selfish Bitcoin Mining Strategies
New Innovations to Curb the Ebola Epidemic (2014)
Technical users are members of the public, too.

If you want to treat users like infants, then you should hereby completely forfeit any and all rights to complain about "tech shortages" and technical illiteracy of end users.
Having to "memorize" the idea of assuming bounded key size is fine.

What's not fine is selectively making that assumption without being aware of it, resulting in a situation where the kewl kids recite back "hashtables are O(1)" with no understanding of why, or what different assumptions you have to make to get there, resulting in an exception-laden body of knowledge. That's not what rigor looks like.

One time I was asked for the run time of a random-line-getter function for a file that seeks to a random byte and fans out to the line breaks. I said, "well, that would depend, not on the file size, but the line length, and it would be linear in that."

He "got me": "Wrong, it's constant." Indeed, if you implicitly assume that relevant parameter is file size, and don't understand the implications of "does not depend on ...", then you can compare answers against an answer key and regard someone as wrong for not saying exactly that.

"Hashtables are O(1)" results from exactly that lack of rigor, where it's all a game of which password to spit back, rather than "can you identify the constraints on solving this problem?"
An easy way to connect with what's going on right now. Join the world
This took me a second to understand:

The scenario in question has Protected Site A vulnerable to an XSS attack, but protected from it due to their CSP not allowing scripts from foreign domains (only trusting scripts from `trusted.example.com`). This is what CSP is for: it's not for what you expect to serve, it's for protecting against what you don't expect to serve.

In the theoretical attack content-addressable scripting could open up, the user visits Malicious Site B, which loads a malicious script with the hash `abad1dea`. The owners of Malicious Site B use their XSS attack to insert the (simplified) HTML `<script src="https://trusted.example.com/payload.js" hash="abad1dea">`. If Malicious Site B tried to insert a direct link to their payload at `malicious.example.com/payload.js`, it would be blocked due to the site's CSP - however, if the site trusted the fact that it's seen `abad1dea` from `malicious.example.com` as evidence that it could get the script from `trusted.example.com`, this would open up a vector allowing Malicious Site B to run the `abad1dea` payload in a way that would not be blocked by the CSP. This is why the UA still has to make the request, even though it already has the content.

With the behavior that's been specced, a request will be made to `trusted.example.com` which will either 404 or give a different script, causing the XSS attack to be blocked by the page's CSP.
It's not like we have a free worldwide labor market anyway. No one is enslaving those workers, they only choose to take that job.
Well, it is what they eventually did, after ten years. With tons of tweaks to make it spit out natural-looking outputs. I just don't understand why they didn't go that way from the start.
My phone has a low power mode (Sony Z3) which works the way he's describing the iPhone feature. It also has a super low power mode that turns it into a dumb phone so perhaps that's where he got the misguided notion that Android turns into a dumb phone in low power mode.
I think an opportunity to mentor/teach at a place like GA would be golden, and would probably land me some place I'd actually like to be-- I've just run into so many problems with not having something tangible saying I know what I know and can do what I can do (I've never once had an interview that asked me to share or describe my own code and work, even though I've provided it and asked to talk about it). It could just be isolated instances with the companies I've interviewed with, but its still a problem I've had.)

The places I'm interested in working at probably wouldn't care much about me not having a degree in CS, but I would like the benefit of having someone outside of myself and my work stand behind my resume. I'd like to think GA will give me that benefit of the doubt when I go to apply for jobs I really want.

I could be mistaken, however.
Do It Yourself: An Artificial Intelligence
Having used FogBugz, JIRA, and RedMine, as a developer, my order of preference is:

1 - fogbugz

2 - redmine

3 - jira

I actually found myself pretty comfortable with Redmine's UI and its integrated wiki. Fogbugz was very easy for me to use, but I last used it ~7 years ago.

It may be possible to get JIRA configured so it works nicely, but in general I find I am always running into some kind of workflow issues. It does work, it just seems to take more effort and sometimes me or my teammates come up with ways to work around things that are broken or just not smooth and that we don't have access rights to debug or fix.
"Please don't bait other users by inviting them to downvote you or declare that you'll probably get downvoted."

https://news.ycombinator.com/newsguidelines.html
See previous discussion (1700 days ago!):

https://news.ycombinator.com/item?id=2180623
My understanding is that to implement the Cast SDK in an Android or iOS app, one must link a closed source binary.

On Android, it's Google Play Services, while on iOS it's a custom Cast binary that Google provides to developers to link in their apps. Due to this, almost all apps that support Cast are on iOS, Android, or Chrome because closed-source binaries are only distributed for those platforms.

Amazon would have to make special arrangements to include the Cast SDK on Fire OS. I still don't think this excuses them from bringing a proper Amazon Prime Video app with Cast support to iOS and (Google's) Android.
What metric are we using to determine who "won" here?

Did Jira "win" just because OP likes it better?

Because both companies are private, we don't really know how much profit either product has made.
From the linked HN comment:

> the C# code was not human-readable
> your cow-orkers hate it, and by extension, you

I'm guessing you meant this as a joke, but such jokes come across as personal attacks, which are not ok here.
> No, it's a big cost every time you pass a threshold, which happens an infinite number of times, because big-O assumes numbers can be arbitrarily large.

Yes, it happens repeatedly. But it's not a big cost on every operation. Instead, it's a bigger and bigger cost, that happens more and more rarely. Averaged over the run, it's insignificant.

> As long as the max number size is orthogonal to the number of elements n, you can assume a bound on the time for an addition operation, and then it becomes a constant in your run-time expression with respect to n.

But it isn't necessarily orthogonal. As you deal with more and more elements, it's probably true that those elements will get correspondingly large. But maybe they won't be! The point is, we've decided that that is not a significant issue, since it's not part of most algorithms involving addition.

> All true, but the spec for big-O doesn't say "assume away stuff that doesn't matter in practice"

Of course it does. Everything is built on axioms and assumptions; things that are relevant to the problem, and things that are not.

> When you make inconsistent, varying assumptions between problems, you're not doing STEM anymore; you're doing memorization, the kind of thing STEM isn't supposed to be like.

I have no idea where this came from, but it's neither relevant nor accurate. Every STEM field requires a significant amount of memorization, and any application of a STEM field requires understanding what is relevant to the discussion at hand, and what is not.

The point of any system—Big O included—is to understand a problem. The cost of the hashing operation isn't relevant for understanding the performance characteristics of hash tables. Maybe your hashing function is O(log N), and so lookups are O(log N). Maybe your hashing algorithm is O(N^2), and so your lookups are O(N^2). Neither tells you anything about how your hash will perform.
No, there WAS an agreement between Japanese car makers to limit the HP of their vehicles. Even the GTRs, Evos and Imprezas left the factory with approximately the the same stated HP figures. They could then be reasonably easily tuned to produce ludicrous amounts of power.
Turing Email Makes Checking Your Inbox as Fun as Using Slack
As far as I know the users didn't. Which is to say that the App Store doesn't provide much more security than e.g. a black list. Androids problems are more than anything having a fragmented ecosystem.
High Fidelity -- San Francisco, CA -- Fulltime, ONSITE but work from home friendly.
High Fidelity was created in 2013, our mission is to create a new kind of virtual reality platform.

Team High Fidelity has a deep legacy of expertise in software development, social entertainment, peer-based recognition systems, community development, and workforce mobilization.

We believe that both the hardware and the internet infrastructure are now available to give people around the world access to an interconnected Metaverse that will offer a broad range of capabilities for creativity, education, exploration, and play. And by using all of our computers together in an open shared network, we can simulate this space at a far larger scale than would be possible by any single company or centrally hosted system. By using a range of new hardware devices like the Oculus Rift, HTC Vive, Samsung Gear VR, Leap Motion, PrioVR, Sixsense, and depth cameras, the experience of exploring these worlds can be incredibly immersive and the interaction with others lifelike and emotional.

We are looking for software engineers with solid experience in C++ and Javascript to help us build the Metaverse. Openings can be viewed at http://highfidelity.com/jobs. To apply, email us your resume or LinkedIn profile. Sample code and links to things you’ve built are most welcome.

hiring@highfidelity.io
> If we assume XSS, an attacker could simply inject whatever they want.

An attacker can inject whatever they want, but they can't run whatever they want. That's the purpose of a Content Security Policy: the problem isn't the content of the script being run, it's the context in which that script is being considered.

Because different scripts are given different permissions (eg. access to cookies) based on their domain of origin, the existence of said content must be verified to be true in the context in which it asserts its presence.

It's not a cache-poisoning attack so much as it is a cache-use attack, but it is a legitimate attack.
It's very clear there's been frustration from their brand around customers using their Prime Instant Video product. I've been targeted with ads, marketing emails and even direct mail to use the service. It's clear they want more eyeballs on the thing they're giving to prime members for free.

In the end, all it would take to get me fully on board is a native XMBC plugin.