skysight-inc/HackerNews huggingface dataset:
People, avoid driving on roads, especially after dark. There's too much risk involved in your negligent handling of several thousand pounds of metal for it to be worth carelessly ending the life of somebody simply going about their business using public infrastructure that they pay for and use in a manner much less obtrusive and obnoxious than your own.
>Is it possible to have an API-first public company? It's sort of like asking if it's possible to have an open, api-accessible data-warehouse (I think the answer is no, but maybe I'm wrong).

Unless you're charging for access to the APIs, you're going to have to generate the money to keep the lights on somehow. For linkedin, it's paid access to more user data and advertising, so it's understandable why they put the website first.
(I work on Standard Treasury).

Yes! We need a new logo. Know any good designers: https://news.ycombinator.com/item?id=6014763 ?
The article doesn't mention it, but it looks like their intent is to charge a $40 per year subscription fee for the service. The site is down, though, so I'm having trouble verifying that.
Vast markup language, Knuth's TeX, and more so Metafont, provides a huge space as 'carrier medium. For eample, kerning alone, using float/real values far beyond what a human eys can tell. Off the top of my head, ... no, I won't try to guesstimate the dimensions of this carrier medium giant play room single-handedly. It
gets messy describing what appears odd and questionable. The foo.tex could potentially grow arbitrarily large.

No compression here, as html, the Tex source is larger than what we view.

Another carrier medium layer to consider:

Per longish decimal variables, eg, in \kern, there is also

arithmetic encoding(See wikipedia)

which maps any size foo onto a real value in (0,1). I think there is a proprietary/patent troll war on this.

Choose natural language with many digits/decimals, tables of sports statistics. A stego, in C I think, around 15 yrs ago, created a familiar baseball sports page with decimal tables. ...etc
I've seen this done with the on-the-wire protocol of scientific measuring equipment. It's hardly just for RPC (which HTTP increasingly resembles anyway).

The point is, the ability to "type" a protocol is irrelevant to how modern distributed software gets developed. Maybe it mattered in the days when comms were at 300 baud, machines had kilobytes or perhaps megabytes of core, and the Mark I eyeball was the best way to debug machine-to-machine comms, but these days we have tools that can decipher binary wire protocols for us. Performance and adaptability are far more important now than human readability. That war has been lost.
I'm worried about the amount of reddit like comments in HN.
What exception makes "barring interstates" okay but not "barring roads with a speed limit >X"? Not saying I necessarily disagree, just trying to understand your reasoning.
On my work laptop, I have 3GB of memory, and having Chrome with Google music, Gmail and work stuff open takes up over 50% of that. Gmail and Google Music alone take up >200MB each.

So, now I'm using Firefox, and Firefox running Gmail + my work is about 700MB, or >50% reduction in memory usage over Chrome.

Additionally, I'm using Spotify desktop, which consumes about 80MB of RAM while streaming, over the Google Music webapp, which takes 200MB+.

RAM may be improving quickly for new generations of mobile devices, but many businesses still purchase the minimum specs for their employee's machines, and this sad little 3GB laptop is not even multiple years old yet.
I don't think you've harmed anything. The story's all over the place by now, anyway. I am similarly sorry for the loss.
Perhaps "Learning how to write a lisp-like language" is a requirement? Or perhaps it's low memory usage and fast start-up time for short-running tasks. Does it matter what he chooses for his own project?

I kinda like Clojure, but I don't think it would occur to me to default to it every time someone mentions the word 'lisp'. Not because it's not an adequate language, but there are downsides to using it for some jobs.
The solutions are not simple and quick. But could yield results over long term. I have practiced this. As an ex-copywriter I have had my writing critiqued by creative directors many times. So I state this as someone who learnt a little about written communication.

- Review material written by non-native speakers. Look for cultural anachronisms, cliches, grammatical errors etc..before all this one has to ensure if the message is functionally correct. Provide feedback. Can't emphasize how important this is. Everybody wants to be good at communicating. So tell them why you find it wrong. That would become a guideline to be followed.

- Suggest what material they should read to become proficient in using your target language. Reading good literature and comprehending it, somehow deepens ones understanding of how to use a language.

- Let them practice. More pointed feedback you give along with opportunities faster they learn. Expecting progress without this is just wishful thinking. You should not blame the other person!
Aussie restaurateur Paul Mathis invents new letter of the Alphabet
Have any of these even been solved yet?
Umm, no. You're both changing the subject, and baiting me with words / opinions that aren't mine.
> no one reporting on or writing about this has all the facts yet

yep, that is implicit in the lack of an official and conclusive report. But I have spent 10 minutes reading the article waiting for something interesting, and he just says nothing apart from wait for the official info, dont speculate. which is the default mindset of many. but yes, there might be a whole lot of other people who needs to read this carefully ;)
If a car swerves to avoid a cyclist and hits another car...
Now there's an opportunity for disruption. A paypal alternative that doesn't suck. Sign me up
Article 13 of the Universal Declaration of Human Rights [1], to which your home country is likely a signatory.

[1] http://daccess-dds-ny.un.org/doc/RESOLUTION/GEN/NR0/043/88/I...
Why should I have to respect you more than a car

This is a disgusting perspective, and you clearly have never ridden a bicycle significantly for practical transportation or else you might be able to relate to some of the comments from myself and other cyclists in this thread.

You should respect me because I am exposed, riding a machine with few to no safety devices. It's the same reason I drive particularly carefully around motorcyclists. I do respect them more, so to speak, because they are at far greater risk on the road than car drivers. I want to see that they reach their destination safely, and I know the odds are stacked against them by distracted or arrogant drivers.
tbrooks, unfortunately it will be a couple of months until the products are ready for developers. Sorry! We're in contract negotiations and then we have to do the integrations. We might build sandboxes in a few weeks, but that only helps so much.
Bitcoin Foundation Appoints Jon Matonis as Executive Director
Interesting point, but as per the chart[1] and discussion in the article, the relative memory footprint does have a big effect on performance. This is mostly felt when you get more complex object graphs. If the GC only needs to run once when you finish your calculation, it only needs to sweep once. If ram is limited and the GC is forced to run 100 times, then it must sweep 100 times. This is a lot of extra work and is the main reason why GC can be slow.

In the case of HN, it sounds like you have more than enough RAM already, so you are not hitting the 'worse case' of GC that gets hit often in javascript on last generation mobile phones. The symptoms to the user are very similar to 'disk cache thrashing' and can be as bad as multiple second pauses.

You're very correct in that increasing heap size too far is also a big problem, as running GC on 64GB of ram can take seconds - freezing up everything else while it runs. There are a number of guides on tuning the JVM on servers to avoid this. The new JVM GC algorithms are also very good at this situation by default, imo.

Finally, on the issue of RAM speed: phones generally have a fixed amount of space dedicated to RAM - the 2GB chip on my S4 is the same as a 512MB chip on an older iPhone. This generally means that it is just as fast to access the 2GB of ram on an S4 compared to the 512MB on older devices. So at least on mobile, RAM speed is fairly closely related to RAM performance. I can't seem to find the benchmarks I saw earlier on this at present, anyone can confirm or deny with numbers?

[1] http://sealedabstract.com/wp-content/uploads/2013/05/Screen-...
Bikes injure pedestrians fairly often. My understanding is they rarely kill (though I'm happy to defer on either to someone bringing actual statistics to the table).
Minor nitpick: bicycling also endangers lives. And even though it doesn't happen often, reckless cycling habits may endanger motorists' lives too (by e.g. causing swerving through unpredictable behaviour). I say that as someone who commutes to work by bike.
Scale? I thought the use case was modest load?

Either way, I do 30K/sec queries on a single redis instance on a small instance - the performance is quite exceptional.
The argument is accurate in so far as the Glass has the same camera and network and processing capabilities--what is ignored is everything else. I rather suspect you and I are on the same side here.
LinkedIn app asks for permission to impersonate you?
LinkedIn lets apps request to "Send messages and invitations to connect as you." FounderDating is one app that requests such permissions. Does this seem a reasonable risk? (Seems sketchy to me.)
IcoMoon - Custom Built and Crisp Icon Fonts, Done Right
While it is kind of a sad PR stunt from someone with a 14 year old hipster child at home, it is kind of cool if you look for the ways people try to smuggle goods and weapons onto flights.
I would rather they react positively by opening up their iCloud API for web application for third parties. Apple already has such in place as can be seen from their cloud apps at icloud.com.
I would also love it if streaming transcoding were possible with this API.
I agree 100% on binary being a bad idea in HTTP spec, largely because of encoding and going backwards. But also binary and fixed lengths lead to harder to stream situations, chunked problems and being less approachable which leads to less innovation I believe. I'd argue HTTP clients/servers are better at dealing with buffer overruns because it isn't so set to a fixed length and more based on better defensive content messaging.

Many of the complaints on HTTP are really complaints about MIME messaging which the entire internet is really built on (standards anyways) and has ran pretty smoothly for a very long time. Approaching improving HTTP by addendum like SPDY is a better idea. Or possibly transporting it better over streamed protocols like SCTP: http://tools.ietf.org/html/rfc6525 no need to modify the packaging/messaging format.

MIME/HTTP/HTTPS are very flexible and if you want binary can be added in and has been in multipart, EDI/HTTP/AS2 and other RFCs use this. Multipart isn't used as much because it is more problematic (used heavily in email and custom protocols) so making the whole spec that way would be bad overall. The points on the OSI layers is very key, let's not revert to binary + base64 everything just to get data across the wire. You can put anything in there, basing it in text and human readable is always a good idea. That is really what this whole layer is about. Binary type of movement pushes us back to the days of non standard blobs, problems that http messaging then content as xml then json solved by standardizing readable exchange of data. When you are exchanging data in a standard way it should be very basic to minimize problems not collude. Throwing out all of MIME just to speed up HTTP when other protocols exist for any needs that are faster (real-time, attaching files, streaming etc) is a bad idea. Also changing support from HTTP < 1.0, to 1.0 to 1.1 had many problems, unless this adds considerable benefit, changing it adds more problems.
According to the laws of California, driving or biking makes you a "driver", but does not make the bike a "vehicle", it's a "device". You are still subject to the laws of the road, though.
I agree this is a much saner way to think about it.
Disclaimer: I work for OneLogin, but do not speak for OneLogin. :)

--

For sure. It's no coincidence that before recently moving to OneLogin from a short-term contract at Gap corporate, my biggest pain at work was getting access to do my job.

I think it took a week of onboarding to get on WiFi and in the ticketing system. I worked at Gap for six weeks (everything but the systems are pretty cush). The entire time I had an insecure password set by a network administrator because the password reset form was broken.

I had access to my Gap Exchange account for nearly two months after I left - longer than I worked there.

Perimeter-based security typically leads to a situation where the people who need to get their job done can't conveniently, but anyone with half a cluestick can waltz in.
If I ever get back into biking to work I'm gonna get a bike-cam.
Yeah, not at all.
> Just because you perceive the public roads as "car roads" and driving as "normal" doesn't make it so

Why not? The roads were built for cars. Driving on them isn't just "convenient," it's exactly what was intended to happen. Don't get me wrong, there should absolutely be more bike lanes and other considerations so that cyclists can travel safely. But, the infrastructure in its current state is definitely built around automobiles, and mixing bikes in is dangerous.

I just spent 4 days commuting around Chicago on bike, so again, I'm all for it. But, as a cyclist, I think you have to approach it like you're in someone else's territory and subject to their whims. I don't believe an indignant "this is my road too" attitude is going to do you any favors.
Active Directory Federation Services (ADFS) can be used as a SAML 2.0 Identity Provider (iDP). This goes back to the introduction of ADFS in Windows Server 2003 R2.
I think you are definitely the outlier here. Most people I have seen using Dropbox store some documents there, not even all of them. Just those they want to have synced.

That’s also more or less the default for Dropbox, that’s how it’s set up and guides its users. It’s just some folder in your user folder, not even the documents folder. By default you have to actively think to put stuff in there.

I think you might just have a wrong picture of who uses Dropbox. Storing IM conversations or even all of your documents on there is quite esoteric.

Also, if you think of a typical home computer of someone who has a job then there aren’t going to be many files on that thing. A few letters to cancel something or other (but even that is done mostly by email these days), photos, videos and maybe some music (but many people don’t put that in their Dropbox because there is just no space) … that’s not much. You don’t need to create files to go to Facebook or read the news or get weather info or watch the stocks (minus Facebook that’s exactly the stuff my dad does on the family laptop and I installed Dropbox on both PCs in their house to keep their rarely changed documents folder in sync).

Yeah, students probably have more documents but I have even seen those only use Dropbox for collaborative stuff – not all the rest they do.

It’s not that those people don’t get value from Dropbox or don’t use it, they just don’t need it that often.
It is if you're storing JSON blobs for contacts and simply send it up to a cloud storage service. It would be last-to-write wins, in this case. Supposedly, Dropbox would handle this sort of scenario.

Of course, this is assuming you weren't using a database (even a NoSQL DB) and simply updating the changed fields, which is probably how you'd realistically handle this situation.

EDIT:

Taking a closer look, it seems like the Datastore API is more of a way to synchronize multiple databases/stores (in essence). One stored locally on a phone (that can be changed, in their example, in airplane mode), one in the cloud, and one on the desktop, or anywhere else your app runs with the Datastore integration. While there are relatively simple ways to locally queue changes made while offline, and then sync them up to a master database in the cloud when the network comes back, Dropbox's Datastore seems to do this for you without you having to worry about it.
How the word hacker got corrupted
No it doesn't. Yield sign has a meaning, and it's not go through oblivious to surroundings at full speed. It is slow down and make sure it's clear. If it's not clear, it means stop.
Masao Yoshida, Nuclear Engineer and Chief at Fukushima Plant, Dies at 58
U.S. Government Continues State of Emergency Declared in Response to 9/11
The entire file is resent.
Distributing your public key with your facebook profile is fine, but that won't teach (much less convince) your friends to use it.

Perhaps you could wire up some sort of "facebook app" that would have people talking to you encrypt their messages to you with your public key, but I doubt you could really implement that in a way that would prevent facebook from getting the plaintext (or at least make me confident that they could not). You would also need some sort of browser-side extension to decrypt, or have to copy-paste the messages to decrypt.
I used to drive a bike trafficked roads, even at night, but I stopped doing this after almost hitting a biker while driving when I realized how hard it is for a driver to see and avoid bikers in traffic or for bikers to go through heavy trafficked area safely.

Driving a bike through traffic or on a trafficked road at night or driving through a bikers area is basically the same as driving while drunk and stoned at the same time, only you don't realize it until you get hit by a car or you hit a biker with your car and its too late for both of you then (though if you do it, have at least the freakin decency and humanity to call an ambulance before running from the scene!)...
I always assumed it wouldn't work incrementally, but it seems to sync my 200MB tc file too quickly to be uploading the entire thing when I make a small change. Perhaps someone who actually knows something about encryption can speak to this. Does every byte in an encrypted volume change when a piece of data changes? I guess that would be too inefficient to be the case, no?
The SimpleSAMLphp project has been useful to me. It includes code for both a SAML Identity Provider and Service Provider.
I'd figure the inefficiency cost of ascii vs binary http headers over yottabytes of packets every year would add up. It hurts your bandwidth, it wastes electricity on the wire, and it wastes processing power. An insignificant smidgen on average, but add it up and it would probably be substantial.

That is always my stance on things - if one computer is going to run something, write it in python, make it bleed memory, just make it work. If it is going to run on a million, you have to consider the raw power waste of inefficient programming. If it is going to run on trillions of devices for decades, your choices are few in my mind.
Digital Ocean down again/
second try with this service, and saw the same sudden-death, sigh. https://digitalocean.com
To be fair to the 1962 NASA, they did say "women", not "girls." It's still blatant sexism, but there's need to hyperbolize.

Unless of course all you care about is generating linkbait.
The right approach is to encrypt before pushing down the wire - it's useless if Dropbox just encrypts on their end.
The Art of Unix Programming by Eric Raymond makes an excellent argument for textual protocols in Chapter 5:

http://www.catb.org/~esr/writings/taoup/html/textualitychapt...
Same day delivery is getting really crowded: Amazon, Ebay Now, Yelp, Postmates, Walmart and probably others.
Where do you live? There aren't even any roads with speed limits < 30mph here in Rochester, New York, and it's the same in Buffalo. What you're proposing up here would mean banning bicycles on all but specially marked bicycle paths.

Especially in the city, it's prohibited to ride on the sidewalk; you must use the street even where there are no specially marked bike lanes. So, what you propose seems particularly outrageous to me; the only remaining options to get around the city would be having a car or using public transportation (or going on foot.)
> Mobile web apps are slow because they're secure, precisely for the reason that they cannot examine or manipulate underlying system memory.

By that logic, they'd better start writing OpenSSH in JavaScript, unless they want to compromise every server in the world. Oh no!

Secure doesn't imply slow. Not even sandboxed implies slow. Mobile web apps are slow because their runtime has more layers of functionality and is more complex -- therefore, it requires more processing than a native application.

> Manipulating memory is fundamentally a bad desktop practice incompatible with the way that JavaScript—i.e., untrusted software—is distributed.

This simply isn't true. Native Android applications also can't manipulate memory; how are web applications more secure than those? And if they aren't, why are they slower?
I wonder how many TSA empoyees it takes to run an Instagram account.

All kidding aside, I wonder what mega IT company won the bid to run the Instagram account.
But then how will the mob exact justice?
Bitcoins Soar In Value In Argentina Due To Capital Control Laws
It's the same pattern that every similar company goes through -- open and inclusive, increasingly to closed and defensive.

Aside from outside services increasingly being blocked from constructively accessing LinkedIn's API, the company is becoming more insular in the other direction as well: Where once it allowed you to configure an external blog that could be itemized as stories on your own profile (which seems like a perfectly logical integration point if a LinkedIn profile were considered a central point of professional information), LinkedIn dumped that in favour of a invitation only siloed-data approach.

No thanks. Where once I saw LinkedIn as an interesting Rolodex, increasingly I am getting an impression that one's career is in a bad place if feeding the LinkedIn beast is an important activity.
it probably always will be - so long as the man / woman imbalance with dating doesnt even out!
1. Sarcasm meeting sarcasm; HN truly has turned into hell.

2. Trying to fit an HTTP field parser into one line is not the way to win a programming argument.

3. One ASCII character names? 255 (edit: 37 alphanumeric) possible headers, of which only a few might correlate to what you'd expect? You're trolling me now.

4. Yes, software bugs happen! It's crazy I know. But let's go ahead and assume that the security holes that still plague applications today due to design flaws are not the same as a couple off-by-one bugs decades ago.

5. By virtue of the algorithm, compression works better the more you have of the same thing. You won't have 70KB of headers to compress at once; more like 400 bytes. The compression of individual header groups each time will not benefit from the previous data's compression, as TLS or SPDY might do. The eventual overhead would not only be larger than a bitstream but take more CPU to decode.

6. Not only are they inefficient, they add complication to the parsing of the protocol, which is one more thing an application can mess up. Not only is it slower, it's more prone to errors. A VPN does not fix that. Perhaps you should focus on real solutions to real problems versus quoting what decade network application programming began in.
A database of fake UIs from movies
Tiny Utah-based ISP makes a name for itself by rebuffing government snoops