skysight-inc/HackerNews huggingface dataset:
I just signed up, and I gotta give it to you that the look and layout of your site is very very nice :) Everything is very clear and from my five minutes of browsing the archives I cant personally find a single thing to criticize.

I read in other comments here that it´d be great to have a summary for each link. But I imagine that would be tedious and time consuming. Personally I think the titles of the links do just fine :)
Do you monetize this in any way, or are you planning to?
I suspect that a lot of anti ruby / rails people are happy to have the occasion to prove that the language and framework that they didn't want to learn is ...bad... and are posting these news all around the web... with that small grin in their mind... fair enough... but rest assured, Ruby & Rails haven't even came close to the end of their ass-kicking :)
The only thing lost by losing the NAT is obscurity... which really isn't security. You should still have your firewall in place.
You can clear the subscribe box on focus rather than just on click.
Reproduction of work sometimes goes by the name "provenance." 1. Record what you want to do. 2. Record how, when, where, by whom it was done. 3. Include ability to run it again. (Exact reproduction is understood to be impossible given everything that can vary in the hardware, OS, and software.) There is an encoding format for provenance, called Open Provenance Model, that can function as a guideline for how to record actions faithfully.

A good example is VisTrails, a workflow application. If you use it to make an image, then you can click on that figure in a PDF, and the URL leads to an online record of what made the image, which downloads to your local machine and runs. You can pick up where the author left off (software, data, internet permitting). Running every program under such a workflow is cumbersome or impossible, though, but it's work in the right direction.
There seems to be a pattern emerging in all of these 'disruptive' business models, whether it be Bitcoin (banking), AirBnb (hotels), or Uber (cabs). We look around and see these industries burdened by regulation, which tends to create entrenched players and which seem to us to be inefficient. So we create similar peer-to-peer equivalents, only to start rediscovering the reasons for all those regulations in the first place. I would argue that one reason mature industries seem inefficient to us is that it's been so long since we've encountered the problems the regulatory 'inefficiencies' were meant to address, that we've forgotten why our ancestors put them in place. Peer-to-peer is not a new idea, it's how things worked back before we started using government to solve the problems inherent in the peer-to-peer model.
Elastic tabstops - a better way to indent and align code
The warranty is what makes this really attractive. I rolled the dice, getting two from ebay, and managed to luck out.

Now I can recommend these to people who are less able to cope with dead pixels, etc. Have to love monoprice for doing to monitors what they've done for cables.
Why is the comment greyed out only because some stupid jerks are not agree? What the hell? What if 99% of the clever people are agree? But clever people are still 5% of the human mass. This is a wrong ranking system, this is a dictatorship of the stupid. I am going to think of this as of the 'rejection therapy'. I am not going to conform the public's opinion anyway, just don't give a rat's ass.
I'm giving the newsletter a shot. As far as summaries, I can see how it could clutter the flow, maybe there is a way to put them out of the way of the main flow? Optional hover? It's a great place to expose a bit more 'curation' value if it can be done without causing problems.

I would also mention, one huge reason I use hacker news is for the comments. If the summary could just mention a couple major topics of discussion, e.g. the 'good stuff' it would make a summary useful to me there as well.

More broadly, I noticed that all your links are the articles, with companion comments. You do have a few 'ask HN' and similar thread posts, but perhaps consider highlighting those occasional remarkable discussion threads on their own, or quoting excellent posts. I've saved more than a few HN comments myself, and a couple great quotes at the end could be a nice 'wrap-up' and bring some of the community discussion feel to the format.
I don't believe it is cultural, I believe it was based off shortening 'mankind' to 'man'. However, I'm not a linguistics specialist and have no idea the roots of the phrase, but I've come across it in many contexts.
Why is a ~130-column line of code necessary a bad thing? I'm not saying it's good and that we should shoot for any specific number, but I don't see why shorter necessarily means better.

Disclaimer: I've been doing this for all of ~5 years so I have no experience with older terminal-style programming.
Maybe I`m biased because I write C on a daily basis, and only noodle around with Python occasionally:

- Having a standard line length is awesome. I can fit 3 80x4 terminals on my 1920x1080 screen, and I never have worry about anything overflowing or wrapping. You could pick a different length, if you`d like, but 80 is convenient.

- I`ve seen the `you can set tabs to whatever you want` argument before. It`s obviously at odds with the 80-column rule, because if you open it with the wrong config, wrapping everywhere. This happens disproportionately to new users - new hires and interns - and it`s a big pain to explain every time. Then they turn around and hit space 4 times anyways.

Your code style rules should definitely match your language. The author seems to be complaining that C-style rules don`t apply to Python. You`d think he would`ve realized when they started talking about wrapping if blocks in {}
Sure. I was headed in the direction of the FDIC not changing much about robberies.
Introducing BitTorrent Surf
Mono is an option for the current generation to learn one less language. Outside of Windows it's not the default language for anything except Unity3d so curious kids who grow up with tablets might not have much reason to learn it.
Be sure to keep hilarious endorsements like

"Hacker Newsletter is great. It's reduced the time I spend on Hacker News from several times per hour to several times per hour plus the weekly newsletter."
-Jason Seifer, Founder of Scheduling, Host of The Ruby Show

That's what just convinced me to sign up.

AFTER EDIT: And now that I have signed up, the usability suggestion I have for the archived issues is to make sure that each issue in the archive links to the previous issue, and all but the most recent issue in the archive links to the next issue. That's the expected browsing capability on most permalinks.

VERY IMPORTANT: Style the archives links to distinguish visited from unvisited links.

http://www.nngroup.com/articles/top-10-mistakes-web-design/
Sadly this link doesn't seem to work anymore. The about-page is broken?

But i had this open in a different browser some minutes ago and it seemed quite impressive. Especially the encoding on the fly, as that is something I experimented with on my own mini-project (https://github.com/onli/music-streamer, ruby with sinatra, plain html5-audio). I'll have a look at your code how you did it, but I wonder if that would work with a low-end homeserver (i'm targeting a pogoplug). On what hardware did you test that?
I'm not so sure anymore. My industry is being saturated by Helvetica-designers and people with absolutely no background in traditional design, and who have absolutely no design sensitivity for accessibility; and who fear risk because it has been so tightly coupled with their next paycheck. Anything that seems risky gets lumped into one category, because it is economical to play it safe, come what may. Two-tone, single-column, this or that. My industry is becoming hyperfashionable, and morally so. It's beyond me how so many designers I see today whore out the same pallid, lifeless sans-serif fonts, and they don't even set their font-stacks properly. So it's monocultural design, with a tyrannical twist that depends on things like CSS's !important. It's like most of you are force feeding your 11pt fonts and insipid Microsoft fonts down the world's throat. -- And you want to ask what failure is as if you don't know? It's whoever will not follow the trend, in a certain material, financial sense.

Failure may be individual, but the conditions are defined by the industry in which it occurs. And honestly, all those designers/developers who are cookie-cutting their careers make failure habitual for those who actually decide to take risks and be thorough-going. We have so many designers/developers who need to make a quick buck, that their "streamlined" notion of things make it difficult for people who actually have talent to genuinely nurture that talent, because they have to compete with Frameworkers and (CSS) Foundationers.

Talk about that. Failure is defined by the suffocation of talent in a capitalistic mindset.
Crazily, I have also built a (rudimentary) similar project out of Flask, Backbone, and HTML5 audio (and Mutagen, of course). It's a piece of a larger music-management puzzle:
http://beets.readthedocs.org/en/1.0rc2/plugins/web.html

Anyway, zx2c4's project is obvious slicker than mine.

It's somewhat crazy that all the people on this thread saying "hey, me too" are only now finding each other. I think there are some pretty clear opportunities for collaboration here. In particular, I think it would be prudent to informally standardize a REST/JSON API for music collections so these tools can interoperable. (I'll send you email about this, zx2c4.)
I really do appreciate your overall point and caution, BUT I wouldn't exactly hold up the Feds or Fortune 500 companies as icons of rapid innovation (yes i too have worked with them and speak from grey hair - much of which was torn out weeding out useful info from reams of Reasearch documents :)

The OP, has clearly touched on something, given the activity here, so kudos to him/her!

I dont think you should have been downvoted, lest we prevent open and honest discourse. That said I would not laugh at blind ambition, however naieve; I'll bet on that over inaction any day!
Ah, ic. Maybe this is a way of beta-testing a larger roll out?
I still have to disagree. Covariance turns generality into specificity, so any argument that states "monads are uninteresting here because they are very general" should be paired with, "except in the dual case in which they are very interesting because they are very specific."
Quickly search through your photoshop layers (CS5)
This vulnerability went from disclosure to exploit extremely quickly. The CVE was published on the 8th. I can't speak for them, but in the process of trying to update, we ran in to some issues with therubyracer (a core component of the Rails asset pipeline) and libv8 (the library that therubyracer uses to embed the V8 engine). It was extraordinarily bad timing, and it slowed down our update process by almost a day while waiting on a new version of therubyracer and libv8 to hit.

Having said all that, if our upgrade holdup had taken any longer than it did, we would have implemented one of the mitigation strategies.
I didn't mention Rails in the title because most of the commands aren't Rails specific.
Algerian Hacker Who Hacked 217 Banks Arrested in Thailand
http://url2png.com
This seems more like an exercise in advertising than in trust. And with a 9% response rate, it just might be a successful one, if the reviews generate enough sales.
Works perfectly on Chrome (24.0) but nothing happens on Firefox (18.0).
For getting around linux I've found no better helpers than manpages and the cheatsheets by Peteris Krumins[1]. I notice this isn't offered as a pdf or image, is the idea that someone will come and visit the site when their server is in trouble? That said, I didn't know about some stuff here like scriptreplay -- thanks!

[1]: http://www.catonmat.net/projects/cheat-sheets/
> The system was not breached, no passwords were compromised (they are salted and multiple times hashed anyways)

When they say "multiple times" I hope that means they're using PBKDF2 or bcrypt, because if they were simply using SHA1 then their users are even more doomed.
For what it's worth I think it serves my purposes very well. I would suggest being mindful of trying to add features that could ultimately clutter it.

I love the categories you put submissions into; one way to both provide a helpful feature to subscribers as well as prevent them receiving too much information that they're not interested in (clutter) would be to select specific categories you wish to receive a newsletter for when you sign up your email. Modularization is good.
This article might interest you:
http://www.forbes.com/sites/alexknapp/2012/05/18/nikola-tesl...
BitTorrent announces Chrome Extension for torrent discovery and download
Thanks. Can I ask what OS are you using and what mouse?
This reminds me a lot of the scheme that conference organizers set up. They might charge $5,000 for you to attend because that way you know you'll be with other high caliber people. They use money as the filter and just happen to profit as a result.
Is there a way to do an optional hover in email? You can't pass js
As a Microsoft employee, I'm not aware that we ever claimed anything otherwise.

Also, that headline is some incredible link bait.
Well, I'd say it's highly language dependent, and a matter of sane preceding white space rules. Going by column count, ObjC or Java would be a million miles away from, say, C or Haskell.

I would argue that that's a mark against the former, but if you're using languages like them it's silly to try and fit everything into 80 characters. You still need a strict rule, btw: sooner or later some jackass will be putting in 200+ if you're not careful, which is insane in any language because it's utterly unreadable.

It has to do with how the eye physically moves: you want a given block of logic to be as square as possible, so moving from one portion of it to another, on average, minimizes the amount of distance your eye has to travel.
That quote is taken a bit out of context methinks.

As much as I might dislike or distrust the man, and might consider $100 worth the chance to send a one-off drunken insult, I can see that intended as self deprecating humour. I do it about myself all the time: "what sort of fool would trust the likes of me with that" said to the person who has just indeed trusted me with what-ever "that" is, for instance.
No need for a workaround, you have Optimistic Locking (via lock_version field)

It raises an exception in case you try to update stale data.

http://api.rubyonrails.org/classes/ActiveRecord/Locking/Opti...
Actually, there usually is a "Ask HN" section... but if there isn't any good ones or if they end up in other sections then it doesn't show. It is funny, at the beginning there use to be tons of them and then over the last year those started to thin out, but that seems to be reversing again here of late (which is good!).
This is true. A lot of times the process goes:

1. Here is a paper about some interesting things we've been looking at, here is what we know, here are some ideas we are building on. These tend to be presented at conferences, as a "what do you guys think?" sort of introduction for the larger community. It is nice, because other researchers can then tell you if this is actually new, or just a repeat of an idea (that was hard to find because it used different terms and went nowhere), or something worth looking into, or the old "hey, here's some pitfalls I see from my expertise".

2. A couple more conference papers with results building on the ideas in the seminal paper in 1. These are just to keep awareness of your work to others in the field, get feedback, and to play the game right - you get much less credit if you don't have a history of showing you've been working on this for a while when someone comes along and "scoops" you.

3. Actually interesting/important work. This is the type of paper that the OP calls "groundbreaking". After all that work (see documentation over the years), here is something pretty awesome!

Another facet of this process:

When doing research, you have no idea what you are doing. I mean, you have expertise and goals and hypothesis/theory, but you don't know how it will pan out. You don't know if you suddenly find a spot where a left turn is required. So publishing about these new things is a good idea. Other people in the field can benefit from just that. Further, in my experience, each small result tends to spawn more questions/investigatory tracks, etc than it closes. So a lot of papers with honest "future work" sections are great places for grad students and others new to the field to dive in and get their feet wet. They can follow some of the tracks the original researchers just had no time for, and help fill in gaps.

Finally, the self reference is a good sign, because it establishes you aren't just some person coming out of left field with $BIG_IDEA (which looks a bit crack-pot-esque...)
That's not devops - that's system administration. Not complaining; it's still a well-presented list.
Wow awesome link. That fully blows my mind.
per the spec, subsequent requests return the same content

That's not the sense in which HTTP GET is idempotent. The spec says nothing about returning the same content. In fact, servers are free to return uncacheable content that changes on every GET request, and many do so (for example, a page that contains the current time is a valid HTTP GET response). The HTTP definition of idempotence only applies to side-effects on the server.

You can formally reconcile this definition with the mathematical definition as follows: an HTTP request is expected to cause some operation on the server (an operation is a function with the same domain and range). This operation takes the server from one state X to a new state Y. Since HTTP GET is supposed to be idempotent, if you make a GET request to a server in state X, it is free to transition into some state Y != X, but if you reissue the request to the server in state Y, it should remain in state Y.

So basically, an IMMUTABLE function in PostgreSQL is trivially idempotent in terms of operations on the server, in that it can have no effect at all on the state of the database. But as far as mathematical properties of the function go, it does not need to be idempotent.
Get back to me when you're done or in the midst. I'd love to do a Q&A for my blog about those type of "boot camps".

colin@learntodev.com
If an article on HN was interesting enough for you to click on it, I would bet that you have a comment that would contribute to the story.

Your non-programmer background is most likely an asset on HN, simply because you can offer a point of view that most others here can't.
You cannot leave your site open to a pre-auth remote code execution vulnerability while you wait for fixes to the asset pipeline or to any other component of Rails.

I don't know that that's what you're saying you did but we need to be glacier-blue-ice-clear about this. Nobody gets to wait on bugs like this. You patch or workaround immediately or, most probably, you shut your app down.
Fascinating. Also not to be ignored: the psychological blowback from the parents' stress and anxiety. Anyone who has dogs or rides horses can tell you - if you're confident and focused, the animal is too. If you're skittish, scared, overly concerned or stressed, the animal will be too. Growing up as part of a generation like this must have been subconsciously traumatizing.
OK, comment has been deleted, I therefore edit mine out.
That's oversimplifying things a little.

Say I build a website and fill it with content you want to see. I'd run Google Analytics to track popular content etc.

You're saying my default choice is to no longer have analytics on my site at all?

Agreed, all these other solutions are rubbish. But your solution isn't a good solution either.
If you want to get free security research from the best in the business, running a bitcoin exchange seems like a lovely way to do it. Just keep good logs to a write-only device.
I've been navigating using OS maps on my iPhone for over a year now using ViewRanger. To "download" an OS map you still have to pay - ViewRanger license the data from the Ordnance Survey. They charge you so that they can pay OS for the maps.

But it's all quite seamless and convenient - you "download" pack of a tokens from the App store, and then "use" them to download map tiles as and when you need them.

I'm not sure what an iPhone map written by OS themselves would give me that ViewRanger does not do already.

I wonder what their motive is? i.e. why isn't the current model of "licensing" the map data to third party app writers sufficient?
Brilliant point. It's a case of experimenting with the balance of freedom vs regulation.

Perhaps it's not vital that a hotel(or taxi) is licensed today, because we can easily see its realtime feedback from previous users. But then again, perhaps those users don't notice that there is no emergency lighting and the fire alarm is disabled, or that the driver has multiple convictions for dishonesty.
I run a single ad pretty much every issue, mainly served up by the great people at LaunchBit. That works well, but I'm looking into some other addition ways to monetize it just so I can fund more projects that I want to do. :)
i think you're misunderstanding slightly why this is important.

it's not surprising for small stars to live a long time (they burn quite slowly). what's surprising is that we don't see any older than about 14 billion years old.

so that suggests that the universe is only that old.

and really, to astronomers, that's not surprising either, since the universe is known to be that old from other measurements.

what's actually surprising is that this star matches the universe's age so closely when it contains some elements other than hydrogen or helium. since that implies that it wasn't one of the first stars made (which would be pure hydrogen and helium), but a star made from remnants of other stars. so it is at least "second generation". so there must have been some stars of short lifetime before it. and it's actually tricky to fit that in, given how we think stars are created and how the universe evolved (the real problem is that the hydrogen starts out fairly evenly spread out and needs time to clump, under gravitation, to form the first stars - the density fluctuations that describe this are constrained by observations of the microwave background, which is quite smooth).

[some more background to make this consistent: the universe "started" as hydrogen; large stars, which live a short time, can make other elements than helium from hydrogen; small stars, which live a long time, make only helium from hydrogen.]
I generally disapprove of >80 width lines, but there are some cases in which they don't bother me, and that is boilerplate-ish code that you generally don't have to read all of to understand what it's for. For example macro-heavy C++ header definitions where each line ends in the same massive pile of definition.

The important bit for me seems to be that the stuff you have to read and understand should be in the <80 area.