jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Please don't do this here. In more ways than one, as you'll find out if you read https://news.ycombinator.com/newsguidelines.html.
I'm pulling it down now. I can't run it either.

Because I found it interesting, and as an explanation of why I can offer no link: It's in an m3u8 file (UTF-8 m3u playlist). Which links to other playlists, apparently by bandwidth. So I grabbed the largest, and found 938 .ts links. So I'm pulling them, grabbing mplayer (not sure how I was missing it...), and I'll upload the merged result when it all finishes :)

edit: or, if you're adventurous, and can queue up just shy of 1000 videos to play nigh-seamlessly (or want to do it yourself). This should be the high quality set:

curl -LO http://27c3.cdn.undsoversum.de/saal1/saal1_umts-000[14880-15817].ts

followed by something like this to merge them all: (from http://www.misterhowto.com/index.php?category=Computers&... )

//edit: doesn't work for me (jumpy video & audio in result), but YMMV and it's a start:
mencoder -oac copy -ovc copy -idx -o output.ts $(ls *.ts)
//probably needs to be streamed in somehow... Hmmmm.... been too long since I fought with mencoder, I've forgotten most of it :\

edit2: crud, none of the binaries are working properly for me. Gotta compile from source, which'll take far too long for me to do tonight, sorry! The above `curl` is about the best I can do for you right now.
This is a great talk; Bernstein is a surprisingly excellent public speaker with solid timing.

You can get most of the points he raises from the foils of previous talks on his website, but, the high points:

* DNSSEC offers DDoS attackers 30+ : 1 amplification for attack traffic; at reasonably low deployment levels, it allows a 200> node botnet to saturate most websites on the Internet. It does this while not actually securing end-user DNS queries, which themselves (his point, not mine) aren't what users need secured.

* Prior attempts to secure the Internet with crypto protocols have failed in predictable ways, ranging from TCPcrypt's "try to encrypt without authenticating" to DNSSEC's "try to authenticate without encrypting" to everything's "try to secure the Internet with stuff that takes a million lines of code just to express the crypto in" to "standardize protocols with crypto mechanisms that real cryptographers have declared off limits over a decade earlier".

* Your conception of the speed of public-key crypto is warped by how slow SSL is; 256 bit elliptic curve crypto, which hasn't degraded in security for almost 25 years, is so fast that you can rekey 10 million sessions every 10 minutes on standard PC hardware.

* That being the case, there's no excuse not to bake fast modern crypto into HTTP so that it's simply always there; Bernstein has created a TCP-friendly alternate transport protocol that does exactly this.

* It's a bad idea to have individual trusted roots, whether they're SSL CA's or DNS roots. Instead, bake public keys directly into URLs or hostnames ("nym-based security"), use CNAMEs and aliases to make things more user-friendly, and secure the end-user connections to the DNS instead of trying to sign every DNS record.
That's fine, but plenty of atheists/agnostics/other non-Christian folk celebrate Christmas (at least in the gift buying sense, which is what you care about).

So for people who do celebrate Christmas, regardless of religion, of course the more specific "Merry Christmas" would beat the generic "Happy Holidays."

Of the folks who don't celebrate Christmas, but do celebrate a gift-buying holiday, Hannukah is pretty important. My gut tells me that Jewish folks are a big portion of this segment, and running the experiment 3 weeks after Hannukah would pretty much kill any chance of conversion for them.

Still, the takeaway from your experiment is solid: if you're running an email campaign 4 days before a major holiday, go ahead and focus on those who celebrate it.
In the case of Big Business, it can't happen soon enough.

I have to note that this is the sort of thing that the "cypherpunks" foresaw back in the early 90s. I'm not sure this is the form in which they foresaw the death of big governments and big business, but crypto certainly enables the whole Wikileaks thing.
They're not mentioned or enumerated because it's not popular to provide those things. When people get in positions that are ostensibly powerful, they more often than not cherish their position of power, and things that seem to trivialize that power, like hands-off delegation or allowing real flexibility, are not seen as pleasing, even if they produce better results in the long run. In many cases, even if you have someone in control of a certain group who is not threatened by proper management, his boss or his boss's boss will find such a style of governance ridiculous and think that the good manager is slacking off all day because he's not nitpicking or ordering around his employees, because the boss or the boss's boss is one of the people described earlier.

I once worked for a great manager who was canned after eight months because his boss couldn't understand non-egocentric management techniques.

Management consultants don't sell this advice because management consultants don't make money by producing good managers, they make money by making their clients happy and getting referrals, and advice like 3 and 4 does not please very many "powerful" people.
Right click, open in Incognito works if you are using Chrome.
Looking through Amazon comments [1], there seems to be some agreement that Ariely's studies lack any statistical significance.

Are there any solid statistics-backed intro books to Behavioral Economics?

[1] http://www.amazon.com/Predictably-Irrational-Revised-Expande...
Citation? Neither of these wikipedia articles makes such an assertion: http://en.wikipedia.org/wiki/Vodka, http://en.wikipedia.org/wiki/Vodka_infusion. There's certainly no shortage of what I've always heard called 'flavored vodkas' on the shelves of any liquor store I've been to lately. What do you call them?
ok, so I've done over the years my fair share of using all sorts of JS charting libraries. So far, Highcharts comes at the top.

Along the way, I've seen a plenty of new libraries popping up, but none so far, has matched the quality of Highcharts.

But this seems... just... too good. Gotta give it a try. I wish I was fluent in Chinese. :)
Another analysis-free justification. Here, lets give every person $100. Assume some people are pure consumers and some are providers. Every dollar a consumer spends is going to be taken away in tax, because it has to be given back to the consumers again next year. The part I've neglected is that the providers are also consumers so the money will circulate among them under some circumstances. That means the tax rate could be less than 100 percent. I have yet to see anyone do a proper analysis of this to see if and how it can even work. The stupid analogies and hand waving have to stop though.
Well, zip came after tar, so it probably followed tar's order (as did the `jar` command which even follows tar syntax). Now, consider the `ar` command, which came before tar, for which the analogous command would be

ar cr test.a test/test.txt
If you only want one server, why not just rent a dedicated server from a colocation company? Alternatively, have you tried speaking with sales at some colo providers? Generally they can be very receptive and accommodating. I would focus on smaller players who provide quality customer service as a selling point. Check out webhostingtalk.com for some good leads, or even repost this question there.
Can someone who is informed on this shed some light on its shortcomings? I know this is new, but the article on the bill is a bit too supportive that it feels highly biased. I can't help but feel that the line about collection on foreign enemies for WMD's is some sort of loophole. I agree with bkurtz--its surprising how few people care about Snowden's revelations.
People value 'feeling safer' far more than 'being safer' or 'having rights'. This is the classical problem of not appreciating what you have until it's gone.
Rosen's discrete math book recommended in this article is pretty good. His number theory text is also great (used it in my number theory course, it was better than the instructor). Avoid the 6th edition, not worth the extra cash. Link: http://www.amazon.com/Elementary-Number-Theory-Kenneth-Rosen...
Yes, I was kind of imagining pointing to something on the phone when I wrote that, which of course did not come through in the comment...
The Soviets never had 10k strategic weapons. And even big strategic nukes (5MT) would not have a lethal radius of 30 miles. Even if you were outside, naked and facing it.

A well built bomb shelter would be very effective at reducing the lethal range of nuclear weapons.

Most of the stockpiles during the peak of the cold war were tactical nuclear weapons with low yields designed for the battle field.
> When he was growing up, Spartz said, his parents made him read “four short biographies of successful people every single day. Imagine for a second what happens to your brain when you’re twelve and this is how you’re spending your time.”

I'd be interested in seeing his list of recommended books. (It's difficult to find good biographies that are also concise.)
I think you might be falling into the trap of overt generalization.

I agree that remote removes critical bandwidth for cross team communications.

On the other hand, lots of programming projects are parallizable to n crafty individuals who need colocate only once in a while to " totally sync their mindstate" and can communicate effectively enough in the mean time using other ways without loss of critical bandwidth if the need for that bandwidth is not needed.

Not all teams need the same kind of cross individual bandwidth. Of course loss of colocation leads to loss of serendiptuous talks to create novel insights but if the insividuals working together were located far apart in the first place then they might not be working together at all if not remote.

Personal anecdote to give a practical example:

I recently moved to another team within the same organization working on the same product but on a different level. The team from where I moved developed the stuff that got CI:d to customer builds and it would have been really difficult for me to imagine working remotely there as the work required often going around the floor asking about stuff (lots of undocumented legacy).

My new team focuses on tech and middleware and creates libraries for downstream to consume. Programmers work on their own libraries and I can go on for days without requiring input from anyone. On this team I could easily work remotely.

Based on my experience I would claim it depends on the designed team duties wether remote works or not. And I think this means that team organization must be tightly coupled with the software architecture design. I have no idea which should drive which but I'm pretty sure any changes in one should also be consciously reflected in another.
VyprVPN from Golden Frog is an excellent choice, and their support is 24/7/365 if you have connection issues.
The media certainly is not glorifying this enterprise. I read the New Yorker article as a massive, massive indictment of Spartz's business model.
Maybe I'm off base, but in this day and age I can not imagine writing a new compiler and runtime without at least 100% branch coverage and automated fuzz testing and actually asking people to use it.

It is a gut wrenching feeling when code crashes in production and it is my compiler to blame. It seems so much more shameful to me then if a library or service of mine crashed, not that that isn't shameful as well.

Do I need to loosen up?
I've worked both onsite and remote as a software dev / data engineer. I started out onsite. There are major disadvantages to remote work:

* Amount you learn from the office community is orders of magnitude lower than onsite. If you're good at pushing yourself to learn new things, that can help, but your knowledge will almost certainly end up less diversified living remotely. You're just not exposed to the company's tech challenges as deeply, yet that's usually one of the main reasons for working at the company.

* You don't necessarily get top projects, but rather perhaps good projects that fit remote work. Taking a remote role almost certainly hurts your career if you want to compete with traditionally onsite roles.

* You likely don't get to participate in hiring or shaping the culture in a substantial way.

* You'll have a much harder time building the network needed to get access to key resources (e.g. data, people, etc).

* Your company better have a nice VPN or you're going to be doing a lot of systems-oriented stuff for yourself. It can be fun but can slow you down.

* You're probably more likely to be laid off.

The company I worked for started offering remote much more frequently due to recruiting and retention problems. I don't think the net result had a very positive impact on the Eng org. In particular, a lot of junior people were allowed to go remote for retention reasons but they didn't end up doing much in that role-- they would have been much better off just joining a different company (either local to them or one with a much much stronger remote culture).

Agree with the poster that PG's essay has some holes; seems orders of magnitude less polished than his older essays.
I was part of a virtual team many years ago, before all these tools existed. I was the only one on the West Coast, not in a position to meet others face to face -- at least not more than once, for a conference I attended -- and was the newest to the group, younger than most of the others, etc. There were several dimensions in which I was an outlier for the group. Ultimately, it ended on something of a sour note. I was basically accused of being a "traitor" for doing my actual job. I and the person at the top had very different ideas about how things should be handled and my domain expertise was not really respected. (After my departure, the project that had benefited the most from my input kind of died back down again.)

I spend a lot of my time online and I have taken a lot of online college classes. When I had a job at BigCo, I got in the habit of emailing my questions to my immediate boss, whose role included answering technical questions. For various reasons, I was unable to master the art of catching her at her desk or whatever. Emailing worked better for me.

I and some of my teammates got transferred to a new team that initially did not have someone in the technical role she filled. Until the new team got their own technical lead, we were all still assigned to our old lead. Other teammates of mine who were used to having face-time with our lead were incredibly frustrated. My transition was quite smooth. I rarely needed face-time with her to get good results. I just continued emailing my questions as usual. I also was not particularly "likable." I was quite ill at the time and not at my smoothest socially. I also just come from a more formal cultural background than the people I was surrounded by. I was not interested in being too schmoozy. In the short run, this seemed to hurt me a bit. But once I got transferred to a new team, it was to my benefit: Getting my questions answered had been a purely professional function, not something rooted in being friendly or whatever.

So I think there are good points on both sides of this argument. I see several really good comments here falling on either side. And I think the disconnect probably has to do with some social thing that can be fostered remotely but many people aren't good at it. As we develop more online/virtual/long distance cultural practices, I think this will become less of a divide for some people.
I agree, and if anyone can suggest an accurate, neutral title, we'll change it.
It will still be bad for the adoption of Bitcoin as a trading currency. If I have a Bitcoin that is worth $1 today but will almost certainly be worth more than that in a month, what is my incentive to give you the Bitcoin? Wouldn't it be smarter for me to just give you $1 directly via PayPal?

As it stands the only reason to use Bitcoin currently is for shady deals, novelty, and speculation. I find it laughable that Bitcoin advocates laud the increase in the currency's value as a good thing. It is most certainly not a good sign for a currency when it's value increases dramatically over time such as the Bitcoin has.
By the way, why did Rackspace send me there? For those who don’t know, I’m a full-time employee of Rackspace which is the world’s biggest web hosting company.

Scoble has a day job at Rackspace?
"Verbose" is not the same as "long." It means using many words when a few will do. Grellas's posts are long, but they are not verbose. Their length comes from the fact that they thoroughly cover subtle concepts. They have remarkable clarity, which is the opposite of being verbose.
"None can remember a password like "J4fS<2", which evidently mean that it will be written on a post-it note."

That's bullcrap. Few will remember this password, but most can if they try. My work domain password is over 8 characters in this level of complexity and it took me about 10 minutes to get used to typing it, a day to fully get it into muscle memory. If you ask me what my password is, I'd have to type it out.
In `A Theory of Fun`, Raph Koster writes about games being learning and teaching tools. When my brother and I would play 'soldiers' growing up, we were safely simulating, and learning from, what it would be like to be a warrior (evolutionarily, a useful identity). I always like the idea that Candyland was a game game -- it's a game to teach kids how to play games.

It's a really spectacular book; I learned a lot from it despite not being a game designer: http://www.amazon.com/Theory-Game-Design-Raph-Koster/dp/1932...
For future events, you expect to schedule a meeting / appointment at [Local Time] on [Date] at [Location]. If a time change happens between now and the future event (e.g. daylight savings time), it doesn't matter from the perspective of the meeting because you have a fixed time.

So, I would for future events record [Local Time], [Date], and [Location]. Then make sure I have a [Location] -> [Time Zone] table. [Local Time] and [Date] would probably be combined into one field. The crux of the problem is shifting rules on time zone (and location is my time zone determinant), so recalculation for other time zones is going to have to be dynamic. Storing UTC or UTC offset doesn't help the problem and actually creates a false solution.
You don't have to use posix to suck less you know, or do you?
Sorry about the length of this reply, I lack the time to make it shorter.

>> Have we learned nothing about the separation
>> of concerns, of content from layout?

> You're whole argument violates this separation
> of concerns! By typing two spaces, you are
> inserting layout concerns into your content.

That turns out not to be the case. The two spaces I type are not for layout, so they are not violating the principle of separation of concerns. They are for production and processing of text. I find it trivial to type the two spaces, they match my thought processes as I type, and they make automated parsing and processing of the text by ad hoc scripts easier. In other words, they are fit for purpose in improving my productivity, exactly matching the primary concern - efficient production of written output.

> If layout is the concern of the render, then
> your editor should increase the visual distance
> between sentences if that is what you need, for
> example with an option to override the font's
> typographical parameters or one to add extra
> sentence spacing for mono-spaced fonts.

How it appears in my editor is not the point I'm making. It's fine in my editor, and it suits the way I work. If typographers say that printed works should not have two spaces after the period, then that happens after I've produced my text and it goes for final render. Therefore having two spaces in my text is not a problem. Well, should not be.

Layout is the concern of the final rendering system. While producing my text, whatever helps me produce it faster is of value, and having two spaces between sentences helps me. It's not a visual thing, it's a programmatic thing. I'm frequently running scripts over my text, and things like two spaces makes things easier. Saying that my editor should increase the visual distance between sentences is entirely missing the point. The two spaces is not a layout issue.

Typographers might dictate while the final renderings should be like, but they should not dictate my production processes. Personally, I find that text produced to the recommendations of these professional typographers who have studied these things and produce work they declare to be better is, in fact, for me, often less attractive.
Then I guess we differed on what 10x meant.
Indeed,

The article seems a confused mishmash of various possibilities and so paints various absurd possibilities like this.

Bullet trains are slower than planes and more expensive than container ships - much of China's bullet train building has been to facilitate internal transport and as make-work infrastructure creation. China building-up overall rail infrastructure might bring more trade with various Asian nations but a number of other factors still have to come together for this. China still isn't a first world nation by any means - China's vast industrial capacity is focused on "final assembly" and so China still is dependent on other nations for things like, say, the chips that go in the iPhones it assembles. The situation doesn't resemble "a new empire flexing its muscles" or similar rot.
Because if you're going to screen every request and response in context for appropriateness, you don't actually save any money running a chatbot over just using humans.
Atlassian has a wide market share because their pricing is relatively cheap and most of the paid competitors suck.

It’s not innovative to buy an innovative company/product, if all you’re going to do with it is reinforce your own mediocre products.
There's also the allure of the local restaurant/store/etc versus the national chain, that everyone can see all around them even in the present day.
> Hummingbard is dependent on Dendrite, the second-generation Matrix homeserver written in Go. Features like spaces and threading have only been implemented on Dendrite. Note that it is a forked repo with a temporary patch for paginating threads.

Pretty interesting. I was putting a little effort to get a Dendrite homeserver running a month or two ago and it was non-trivial at that time for me - but evidently the author feels it's stable enough to run an experimental project like this.
UTC has leap seconds by definition. Conventional POSIXish epoch time is a little more complicated – typically, the length of a second varies.
Matomo https://matomo.org/
>talked about the actual main purpose of the device in more depth, >which is, waking you up at the optimal time.

I would not trust a reviewer of a gadget site about that. I would not trust any reviewer in fact. This is a claim on people health and well-being and if you want to be serious about that you better try to publish some study with data rather than anecdotes.
Two years and all I got was this stupid blog post.
My point is things like acquisitions are pretty chaotic. Think of all the crazy acquisition stories you have heard this week on HN alone. Seems a little immature to start throwing the word "deserve" around when this could've been as simple as a minor miscommunication. Way to demand perfection from the outside.
To add on, it's also how you handle the failure and learn from it. You can fail and not learn from your mistakes and repeat a cycle of horrible failures.