skysight-inc/HackerNews huggingface dataset:
My pirating days are behind me now, once you start trying to create content you realize how difficult that can be and appreciate much more that content creators deserve compensation for their efforts.

That being said, this is bloody hilarious to watch! The authorities will go through months of court cases and spend a tonne of money to seize one domain, and minutes later the service pops up with 6 new ones.

Now they are going to begin the painful, expensive, difficult process again, and in a few months we will read that ThePirateBay.vg etc has been seized, with the top comment being a link to the new one.

I'm enjoying the show!
We sell SSL certificates and we're quite proud of it.

> can't offer SGC certificates

We could sell SGC products today if we wanted to - we have the API keys, a partner account with another certificate provider (not Digicert), and a node module written for the relevant REST API. We don't want to.

> are basically whinging that their competitor is marketing their certificates on a feature people don't need.

Marketing certificates on a feature people don't need - and making it seem as if they need it - is wrong.

> That's basically par for the course when selling to businesses, especially where non-technical people are in a position of deciding whether to buy, and which vendor to chose from.

Being common does not make it right.

If you think it does: what's the name of your startup? Your bio is empty, and I think most of HN would be interested in knowing the name of a business that thinks this is OK.

Furthermore it's not 'par for the course': many other CAs don't sell IE5 support as hard as Symantec does. Here's DigiCert writing against SGC (we use DigiCert as our CA) https://www.digicert.com/sgc-ssl-certificates.htm, here's their competitor GoDaddy writing against SGC: http://agrihortico.com/freedownloads/SGC.pdf
SSL will never be good, Encryption which only a few can afford is mostly not good. Also most SSL Providers have their seat in USA, which also means that we NEVER knew if the encryption could be decrypted.
Encryption which will be held by any "bigger" company will also have this flaw, even from germany or any other european company (any company in any country will have that flaw). The only encryption that would work, would be self made encryption, which is barely supported by browsers.
http://en.wikipedia.org/wiki/DNS-based_Authentication_of_Nam...
Both posts have their merits; the OP is more succinct.
One possible approach to this problem is to separate day-to-day management from staff budget/pay negotiations. If you're employing line managers who are worth only $90k a year and have the attitude you describe, someone else needs to be making those staffing decisions. That doesn't necessarily mean you shouldn't be employing those line managers, but you need to think carefully about the nature of the role. The traditional all-in-one hierarchy probably isn't appropriate in that situation.
And let's not forget point four: If you want me to stick around, getting more responsibilities (usually via promotion) should be easier to achieve within than without.

I know more than a few engineers who work at larger companies who have climbed up the ladder by switching outside and back.

And no, they've not acquired magical properties in a short stint elsewhere, outside of the "working elsewhere" property.

You can't complain about missing loyalty if you enforce it as a career path.
In long run, company culture and employee loyalty wins. But I have yet to find one.
To that I would add that if you improve control slightly but the average number of people an infected person infects remains more than 1, the disease will continue to spread exponentially. And beyond that threshold, the relationship between how well it spreads and the course of the epidemic is chaotic.

The example that I like to use is that if you are good about washing your hands, your odds of not catching a seasonal flu improve. But if everyone is good about washing their hands, then the flu spreads slower, there are sick people around you longer, and your odds of catching it might or might not wind up better.
Unicorns will happen. My partner is working with a PEI-based startup (spun off from local Uni) that has a good many clients, a well established niche and probably more programmers working for them then any other company on the island that isn't a body shop.

Doesn't stop them from being special snowflakes rather than a thriving ecosystem. Contrast with a place like NYC or SF where there's funding, support, mentoring available and a wide pool for hiring. In PEI, the second biggest challenge after finding someone is retaining them lest they leave the island to make 50-70% more in TO.
I'd love to hear more discussion on the statement "My thought is that party rounds tend to leave companies without an investor who cares enough or has pockets deep enough to bridge the company when necessary."

I did a party round, mainly because we could do it in a fraction of the time it would take to get a lead. And we did have a couple deep pockets come in. It worked out for us, but I could see it going the other way. Would love to dig in more.
Your manager should make more - because nobody should be a manager of software devs who is not a software developer himself and should be able to command more than a young engineer.

You shouldn't get to be an officer unless you were first enlisted.
Why I don't do coding tests
What's the best use case for this? I've seen lots of requests but I'm struggling to find a really good scenario beyond just avoiding the work of normalizing into regular DB tables and all the schema management that comes with it (which isn't necessarily a bad thing).

Any top level fields can just be made columns and we already have 1:M and M:M mappings done well in relational tables, is it purely just being able to serialize into 1 field and then query on that? Why not just use a document database then?
author here, thanks for checking this post out and happy to answer any questions.
> I understand how IO can be made explicit, but I don't understand how it can be made pure.

Expressions with IO in them do not "do" IO, they declare a composable specification for how IO is to be done.

When one of those expressions is "main", the runtime will do that specified IO (which, in the case of programs with nontrivial IO, will itself be composed of several other IO actions) when the program is run.

All the expressions containing IO are pure, because what they return every time they are called is the same specification of an IO action comprised of lower-level IO actions.

Values in the IO monad aren't the results of performing IO, they are procedures, in the imperative sense, that do IO. The "main" function of a Haskell program -- because it returns a value in that monad -- returns such a procedure, which the runtime executes.
10 Best PHP Frameworks of 2015
While it has nothing to do with the invention in the article (which is just about restructuring cabin airflow): air in an airplane is constantly introduced from outside, pressurized taps from the compressor inside the engine(s). Pressure is maintained at a set level by a valve that controls how much air escapes the plane. Most airliners will also have a recirculation/filtering/conditioning system.

http://en.wikipedia.org/wiki/Environmental_control_system_%2...

If that's what you're asking. Not entirely sure.
Gosh, and that's ... hard? Image processing and compression is the easiest type of problem to solve. The algorithms are well documented and available.

Also, for your benefit, the formats listed all have different usages, and encode the different channels with varying precisions. They also have different compression artifacts and perform better or worse using different samplers.
Coinscope: Discovering Bitcoin's Network Topology and Influential Nodes
If you would've otherwise read a book. Had the ability to pirate not been available, a non-zero number of individuals would've paid. Hollywood is stupid thinking everyone would have otherwise paid. But anyone who insist that everyone pirating would've read a book instead is making the same mistake.
Sharemoji Keyboard (Android) – Brand new emojis that can be used in any app
I read it more as referring to the way the engineer approaches the problem vs what time of day they work.

An engineer who starts hacking away a solution and keeps at it 90+ hours a week (or whatever amount) but then because of this burns out and looses interest in 2,3 or 6 months is not as valuable as an engineer who can consistently keep working at something until the product is delivered. The engineer that is burned out probably won't be able to last X years at the company, and since the author is trying to somewhat maximize the time the employee stays the "burn-out approach" engineer is not desired.

Kind of like that other article that popped up in HN a few weeks ago that basically said "discipline over motivation", which I read as "it's better to be able to work 2-3 hours a days every day for 5 years, than being able to work 15+ hours a day for 3 weeks".

Obviously your opinion might vary as to how useful this strategy is, but I think it has a different meaning than just "an engineer that works at night".
This article is partly about the longevity of startup dev teams.

Here is a simple true fact:

If your hiring pipeline isn't diverse (in a bunch of different ways, but in particular in the ways that represent "the opposite of the approach you just spelled out for building up a team"), then it may be fast and effective, but it is also brittle.

Every team loses people, no matter how carefully designed they are. Companies with huge traction and close-knit management teams where everyone likes each other lose cofounders. People leave, for all sorts of reasons.

On brittle teams, when one person leaves, a whole bunch of people follow.

You want to build a team that is resilient to one or two people leaving every once in awhile. Diversity --- not in the "Benetton ad" sense, but in a more fundamental sense --- is an extremely good mitigating strategy.

You may not care about team resiliency and longevity; "throw it out the window" to get to release and all of that. I think that's a bad plan (getting to a reasonable successful first release only to have your team implode is not a really good use of your very limited window of time to build companies in, is what I think), but that's neither here nor there.
7 Mistakes You’re Making in Your Programming Career
I'm not after free content, I'm after accessible content.

This discussion is basically about how content industries, with all their clout, are somehow unable to match the usability of some dudes with a bit of spare time.
Exactly what i was going to say. We have chosen to let the W3C define protocols. We can always take Chromium or FF and add the needed protocol and the W3C has no validity anymore.

This is the same for the DNS system. We have chosen to let the system be run like it is. But systems such as OpenDNS and Tor has proven that there are workarounds (with their own set of issues). The question basically boils down to having enough of a userbase for the new system to go mainstream.
It's amazing how many developers willingly giving up their entire tech stack in exchange for a proprietary one.

If it was MSFT trying to pull this off, would the reaction on HN be as positive?
I'm amused by how "an exit" is frame as "traditional" when it's such a recent and still such a rare strategy among new (and not just startup) businesses.
In startup mode, I expect companies to do whatever works. Google's initial decisions were correct. Later, they dedicated expensive teams to inventing brand new solutions for about every aspect of their operation. That's when my critique apples. For instance, they might have looked at expensive NonStop, identified what they could copy with COTS tech, and made a cheap knockoff. They could've done the same with prior MPP or cluster tech which already scaled to thousands of nodes with open source management tools and microsecond latency. Much more efficient than web stacks, too. The one example I saw of them copying and improving past methods was Google File System. As I predicted, that good choice laid foundation for awesome stuff such as BigTable, Spanner, and F1.

NoSQL movement's origins are highly debatable. Here's what I saw in its beginning: an explosion of articles on the subject after a few success stories about big companies doing massive scale on cheap servers. Zealots argued that mature, strong-consistency solutions had problems. So, instead of fixing those, we should just ditch them and strong consistency for The New, Great Thing. The only time I even saw a real analysis of cost-benefits was a few articles which focused on a narrow class of applications where data consistency didn't really matter. So, my conclusion was that the movement was two things: 95% a social phenomenon that happens with each IT fad; 5% a result of weaknesses of relational model and tools. That last part makes sense and is why I've always opposed RDBMS's.

On your last point, do you have a citation that shows weak consistency databases offer enough integrity for "majority of use-cases?" I thought the majority of use cases for databases were protecting data that's important to a business: orders, billing, HR, inventory, customer information, and so on. I usually just tell them to use PostgresSQL and that covers it with high reliability. If you really can back your claim, though, I'll be glad to start transitioning my R&D toward designs that trade against integrity of data.
wat the fuk
Yep, I'm interested in this model, but finding it very hard to effectively evaluate all the permutations. This is hugely exacerbated by the fact that nothing really seems complete, so pros and cons could either be due to different design decisions, different priorities, or different levels of maturity, and it's very difficult to tell which.
This is good general advice for any job. It's not healthy to work at any company where you don't like your superiors, company culture, and the work itself.
You are building a business, not trying to save the world.
Managers should rarely have sole power over the people hired on their team, for exactly that reason. It's easy to fall into "empire building" mode, and you want checks and balances for that.

Salary envy is just a minor side problem of that approach. One of the bigger issue is that bad managers surround themselves with yes people, compounding any possible damage.
Dijkstra doesn't do any work, he's been dead since 2002.
Where do your Senators stand on surveillance?
My lord, I just don't agree at all with this article. The author parrots his source, who seems to think the entirety of the problem is "engineering culture".

It is absolutely not. That assertion - seemingly the crux of the article, if you take the perspective of the primary source - is total nonsense. There are definitely issues in engineering culture, and some good ones are mentioned. But the actual, and most material problem, is in the business culture - not paying employees their actual market value, consistently, and then balking at those employees when adjustments are asked for.
Big life changes: a 5-part self-assessment
It's a self fulfilling prophecy though. If you want to be important you have to act important.

Yes, nobody cares about your commit messages until there's a bug or a major refactor. By then, if the commit messages suck, it's too late to do anything about it.

"Programs are meant to be read by humans and only incidentally for computers to execute"

Is never more true than when you're trying to fix bugs or make improvements. A project you can't improve is a dead project.
Rethinking Static Sites
Sounds like you're talking about Westport Video Mania. A couple friends and I go to that store about twice a year to browse around. Each time we're there, nearly all other customers that come through the front door go straight to the back room. After a few years, we finally decided to see what was on the other side. It was like the Tardis of porn...I don't know how they fit a whole other video store in there.
Java is the best programming language – here are 7 reasons why
Maybe it's not just because you are more exposed to germs on the plane. One possibility is that air on planes is quite dry, and you are not drinking enough, which would stress your system. Or there can be a combination of conditions that get you sick.
You are assuming that a Privacy Policy is legally binding, it's generally accepted as not being.

In the example, Amazon can do whatever it wants with the data.

Data submitted to almost anyone online (maybe with the exception of large companies or companies specifically designed to not track data) should be considered public unfortunately.

I have seen some states recently put in place laws to protect this data from being made public or sold carelessly, but for the most part it is unregulated as far as I can tell.
Wake me when they have a device that supports 4k@60fps smoothly. I have yet to see one do so on Kodi.
Oddly enough, Tumblr doesn't seem to support HTTPS for subdomains, so Instagram's is just http://instagram-engineering.tumblr.com/
That source points to this at the bottom.
Yeah, that made me see red. Just money? Money is food in my mouth, money is attention from a qualified doctor in a good hospital when I get ill, money is a good place to live in a nice and safe area, with heating that turns on in the winter, money is a car that starts when you turn the key, with a tank full of gas. Money is fucking important.
There are financial instruments which allow you to sell a dividend stream outright.
Apple claims 12.5% longer life (from 8 to 9 hours) with only a 4.7% larger battery (95 Wh to 99.5 Wh), and without moving to Broadwell processors like in the 13" rMBP which we know are a big part of its battery life improvement.

So is this 15" rMBP battery life improvement software-driven or new hardware throttling or just wishful thinking? The video card and SSD have changed, but doesn't a full hour of battery life improvement seem optimistic? I guess reviews will expose the truth soon enough...
Stunt Hacking
This invention is awesome.

I can't believe all the negativity in this thread for something created by a 17-year-old. So what if the technical complexity of this project isn't the super high? It's a novel approach to a real problem, he did the research to show that in theory it can be effective, and it seems reasonable practical.

Beyond serious diseases, it seems very common to get a cold/cough/flu after flying. This is just anecdotal experience, but it sure seems like 100 people sharing the same 5000 cubic feet of air for 4 hours is the perfect storm for airborne contagions.

CDC, please build on Raymond's work and get it rolled into production.
Hotterkeys: A Game for Learning Keyboard Shortcuts
It is a kid's club. Within the last two years: I discovered my cto, who used to supervise hundreds at google, and therefore absolutely positively had sexual harassment training, was sending candidate engineers a code test that ended up printing a naked woman in ascii art. The answer to the code test was the number between her legs. I realized this when a prospective female engineer emailed basically asking WTF?

Another workplace had 2 female engineers, out of 8 or so. A candidate commented we had, "a lot of secretaries" and was stunned when I pointed out that 2 of the secretaries were engineering peers.

An engineering peer spent lunch speculating about whether the ceo was fucking his secretary until I stopped being subtle and flatly told him to fucking shut up.

I have more stories, but let's stop there for now. Or quietly ask female peers -- most of them will have similar stories.

Further -- like any other industry, the startup / tech world has received enormous dividends from America. From massive investments in early tech, to R&D subsidies, to R&D tax breaks, to the education of the vast majority of the employees at the companies. Demanding diversity is part of fulfilling their social compact with America, and most of the whining is the companies attempting to duck it.
Bop.fm (YC S13) launches customizable music player to automatically find tracks
You gave it away for free by playing it without an agreed upon contract. Had there been a contract, then yes, you could've taken them to court to enforce their side of it.
Maybe I am getting lost in your comment but, are you trying to suggest that Meteor is a proprietary stack?
Probably, but who cares? If you want the job just say that you are planning to stick around, then you can always change your plans once a better job turns up.
This is great! I didn't doubt that Firebase will roll out features to paginate and sort data. I also don't doubt that Firebase will implement filtering in the future. Great work.
You guys are missing the point.

You know that many practices, like price dumping (having preditorially low prices of things) is illegal for the obvious reasons? In a price-dumping kind of way, do you see how what Facebook is doing could be very bad?
An interesting thing about this is that it appears to just use window.performance.timing, which is filled in by the browser automatically. They're just grabbing data that the browser is generating anyway and forwarding it along to themselves.

On my machine, calling `JSON.stringify(window.performance.timing).length` generates 623 bytes of text. Pretty much 0 overhead here.
Why is this complex? There are so many ways for pub/sub implementations.

However I always ended up using Playframework for WS, since it's really really easy to set this up in a scalable way.
I've lately been pondering how to handle the passwords piece of this. I use 1Password, which is convenient because I have a handy-dandy database of passwords, but makes it unrealistic that I'll write them all down on paper. So the problem becomes passing along that database and the master password for it. I also want to avoid giving that to anybody before I'm dead, for obvious reasons.

My best plan so far is to put the database on a hidden (but public) shared location, and use IfIDie.org to send the link to my inheritors. I would then physically meet with them and give them the password (but not the link). It's kind of awkward, and I don't love it, but seems like it could work even for my relatives of modest technical literacy.

I'd be really curious if anyone has a better approach for securely passing important data after you're dead.
Regarding your first point, the people at https://letsencrypt.org/ are working to address that.
They have painted themselves into a corner, because they have sold exclusive rights to so much of their content - e.g friends can only ever be on netflix - so they can't make what people want: spotify for movies (which is what netflix isn't).
Maybe it works as the opposite. On SO there are ~800,000 questions about Java, Javascript, and C#, each.
What do you guys use to collect / aggregate / store / analyze your users' data? Do you do any kind of aggregate analysis to get insights into patterns / behaviours?
Wow. I've experienced exactly this process twice already, and I've only seen the inside of about six large companies. I didn't know it was such a common way of things unfolding.
CoPilot from Twilio
That's not what "security through obscurity" is about. The admonishment against "security through obscurity" in cryptographic circles is about not relying on your adversary's ignorance of your systems to protect your secrets.

So, for instance, if you are using cryptography to secure a transmission, you don't rely on eavesdroppers not knowing what algorithms and protocols you are using. You rely on them not knowing your keys.