skysight-inc/HackerNews huggingface dataset:
I've been working with microservices recently so I needed an easily implementable circuit breaker. Nothing I saw really did what I wanted so I created this.

Thought I'd share.
A reason why websites are so hard to take down is that they're so easy to set up. For example, the video streaming link hosting website primewire.org/ag/com was letmewatchthis.se/com/org/de and they all just reroute traffic. The point is that they are exactly the same website. As long as the Internet is around they can keep taking them down, but they'll just start again under a different name, and word eventually gets around via reddit/4CHAN, word of mouth and the cycle starts all over again. But recently I think link sharing websites are not illegal but Google can't put them on the top of their search results or something.

What's even better are the websites that they host their streams on are constantly changing names since they keep getting taken down, or throttled but the templates the websites use are exactly the same: the type of embedded video players, the font, format, etc. The only thing they change is the color and the name.

But yes banning a domain name is possible, or ICE can take it down but that only applies to American websites.

It's impossible for websites to be taken down but it is possible to limit their exposure and that is to have an American version of the great firewall, but that'll never happen, hopefully...
No. I've written it off as a blackmail* or concern-troll: the information or claim of such a listing has never surfaced since, no one has claimed to have the dox though the main use would be to leak to a journalist or something (since it's unlikely he'd pay blackmail for such flimsy evidence), such dox would be almost impossible to verify (except maybe the passwords), a Satoshi IP arguably already has been found with minimal notice paid by anyone, and the mechanism is odd - he did have Tor configured correctly for everything else, and some of his mail services specifically scrub IPs from mail headers so an incorrect configuration wouldn't matter.

* I believe there was at least 1 P2P foundation post which included addresses for payment at the time, although those seem to have been deleted now.
How about an IP address of a user posting something criminal?
I, for one, immediately checked for Treehouse's open positions. In a world where retention and recruiting are huge challenges for tech, a strong work-life balance policy is very powerful.

Too bad they don't have a need for a front-end engineer right now. I would be all over that.

Keep up the good work, guys!
Tips Wanted on Journey – Learning to Program a Photo App
I've just started to learn how to program (ruby on rails), because I wanted to create a photo app with 1 feature I had in mind.

My question is, are programming photo apps any harder to learn/code than normal apps?

Does it take more time to program photo apps than any other normal apps?

I'm new to all of this, so I try to guess how hard it will be (or guess how much time it may take) to learn all of this, to program a photo app. (I'm a heavy right brain person too, I know you guys hate me)

Anyhow, I would love to hear your thoughts, and suggestions/tips you would have on my journey to learning how to program a photo app.
What sort of joint effort do you have in mind? Force works of course; that's an option (as in China) is it?

Curbing consumption? Same again. Love to know what you have in mind to stop the buyers and how to re-employ the producers?

Finally, 'all' debates? You're that positive?
Please post it, I'd love to see what you come up with!
When you think about it, Germany is like the hot girl in a small town high school. She doesn't care if she's pretty (rich) in the absolute sense, she only cares that she's prettier (richer) than all the other girls in the small town (Europe).

Instead of focusing on optimizing Europe's collective wealth, they are trying to maximize their wealth relative to the rest. There is certainly concerns about things like corruption in the periphery, and Spain and Greece certainly had their inefficiencies, but Germany is going about fixing it in a completely wrong way.
This is how we operate as well. There's no penalty for someone coming in via an external recruiter in terms of their salary.

I don't necessarily believe this but the other argument about making less money is that recruiters are incentivized for you to take the job and not to push the envelope on your behalf knowing that the company might balk and back out.
His first video doesn't seem to exploit any glitches. His second video is clearly exploiting game glitches.
Not sure if OP is author, but this seems like a decent start at a useful compilation. It's obviously highly focused on data structures and algorithms, so the title is a bit misleading.

Strange - not a single citation/reference?
Will this cause improvements that were reported by the Google Inbox devs (reported here, not sure if reported on Bugzilla)?
Neil Armstrong's purse: First moonwalker had hidden bag of Apollo 11 artifacts
That's because Laravel is a website framework and Symfony2 is an application framework.
A couple thoughts:

1. The comment you're talking about is from, essentially, someone who doesn't know what they're talking about. This isn't really meaningfully a "game changer" in terms of "Should I buy an iPhone?"

2. Computers are already used to analyze many of these types of diagnostic tests. It may have been easier to port those systems to a smart phone than to develop a new, bespoke microcontroller. Expertise is a cost.

3. There are massive benefits to having this hooked up to a smart phone, and as you have mentioned, much of it goes to extra functionality. During the Ebola outbreak, case reports often had to be dealt with in paper forms processed by hand, which slowed both reporting and contact tracing. From a public health perspective, being able to link test results (deidentified or not) with a central repository at a ministry of health is a big deal.

Imagine the use case of this not as one person and a smart phone testing themselves. Imagine it as one person and a smart phone testing 4 villages over the course of the week, in conjunction with actually getting people treatment.
I don't think that that is a good fit for this case.

Remember - he's using only ~11 bodies. The problem remains mainly sequential for that number of bodies.
> You are always at more risk from employees because they have multiple ways to hose you. Labor disputes, billing issues, intellectual property ownership agreements, etc.

That reasoning smells fallacious to me. Just because there are more kinds of risks, doesn't necessarily mean you're at more risk.
Being an Intern at Our Startup Would Be Just Awful
I’m Autistic, and Believe Me, It’s a Lot Better Than Measles
Google trades technicality for brevity with new SSL warning
Get rid of all the abstraction, local state, dependency injection, symbol management and so on. Take HTML/HTTP seriously

You can't just say "remove local state and use HTTP instead" - people didn't invent local state from nowhere, it has a lot of advantages to relying on an HTTP call for everything you do. Particularly when you're scaling out widely or when you're dealing with mobile devices.
I could use a resource along these lines, especially with all the programming tests I'm facing during my job hunt. Thanks.
I've never cared for that and have negotiated with my cats to not do this (generally carried out with a spray bottle). My most recent cat recognized the concept well enough that when I moved to new places (which happened with some regularity) he recognized the concept of "kitchen counter" as "place I'm not allowed". Similarly dining room table, though he was allowed on my desk.
You can use Blockscore (YC S14) for this. When you verify a user's identity, the result tells whether the address has a history of high risk activity
Those sound like ways to hose your employees and make them dependent on you.
Crazy Cat Lady – a game written in Lua in which you throw cats in people's faces
> Yeah, the service will essentially be a man in the middle on the account, and I believe it will be very important to communicate that with users.

No, it will be very important not to do it, because you are knowingly busting security open on Apple IDs with your service and think that educating users is the best way to mitigate that. We all know most of your users won't know any better. The better way to mitigate it is to not accept Apple IDs in the first place.

If you launch that service, I would feel obligated to tip off the iCloud folks that you're knowingly compromising Apple IDs. That isn't because I want to see you fail, but because you are compromising Apple IDs and your users are caught in the middle.

This is an idea you should let go. I know that sucks to hear.
RK4 is not a good choice for periodic systems.

It may be better to use a symplectic integrator.
TL;DR The machines are taking our jobs. 45%+ of current jobs will be done by machines by the year 2050. We need to look into solutions like tax breaks for utilizing human workers or basic income.
The irony of suggesting a framework that abuses html attributes in templates to wire up massively abstracted behaviour as a response to someone tearing into the obsession of JavaScript devs with over-abstraction.

You do appear to be overly keen on pimping it, but it looks kinda unnecessary.
Yup. Pidgin + SIPE http://sourceforge.net/projects/sipe/ + Finch http://linuxers.org/article/finch-command-line-alternative-p...
Hopefully GnuPG developer[s] will also address Mailpile complaints[1]. And JSON-friendly interface as a part of it.

[1] https://www.mailpile.is/blog/2014-10-07_Some_Thoughts_on_Gnu...
I retract my statement. Let's pretend I said "Turning off your brain is hard" instead?
Lots of great advice, and featured here at least five times previously. This submission has the most comments, I think: https://news.ycombinator.com/item?id=3170766
A/B Testing for Restaurants
> So are people expected to work 40 hours/week or not?

Folks are expected to work 32 hours per week, although if you get technical and throw in PTO and holidays they're actually expected to work 28.9 hours per week.
I consider DRM a slight net positive - not because it prevents copying, but because it makes it somewhat inconvenient, and thus provides an economic incentive to use a commercial service, where the DRM is implemented transparently.

No, I'm not afraid about the OS thing to be honest. In ~30 years of using computers the trend has continually been in favor of openness, and I think anxiety over DRM taking over OSes and CPUs is wildly overblown, and largely a psychological projection of sociopolitical anxiety.

I'm talking App-Store like distribution, where they get 30% and handle everything for you, even what you're allowed to say.

Well it's not like the existence of DRM means you lose the ability to give it away in another format if nobody wants to publish it on a commercial platform. This, too, is continually getting better in historical terms, and it's an issue I care very much about personally.
What business do you run? I'd like to avoid ending up there by accident, because it sounds like a place unfriendly to Labor.
You lost me at "That's intercooler.js"
Let's review Docker
Feedback and constructive criticism welcome
Tesla model S is so safe it broke the crash-testing gear
[2011] would be appropriate in the title.
Responds to Selector
I love reading about work style experiments like this and think they're great in some situations. But they make more sense for serial founders who have cashed out before or established cash cows like Google/Apple/Facebook. New founders who are all in on a business can't afford to work 4 days a week because the clock is ticking.
I'm not talking about cdr-coding, but simply the placement of regular 2-element cons cells and/or their contents next to each other in memory. This is often a "happy accident" side-effect when copying collectors fill their destination space based on the traversal order of heap objects.

This of course applies to any connected chain of objects which can freely coexist in a GC space, not just cons cells.
Welcome to Our New Share-the-Scraps Economy
Please don't call yourself an engineer unless you've got the ring.
I wasn't given a ring because my school doesn't do the ceremony :(

Actually, I had this conversation with someone in Italy, who said I couldn't put "engineer" on my business card because of some certification or another that was missing. What I did was give him a quick lab tour, with emphasis on the battlebots. It worked.
How about using Web Components? They seem to solve most of the problems that JavaScript frameworks try to solve.
I have the impression that many OpenSSH users are unaware of its OpenBSD relationship, and so perhaps less likely to take note of the fundraisers. If it hadn't been for the extra publicity last year, I'd probably still not know.

So for anyone like me: These are the guys behind OpenSSH too, get your wallet out ;)
We've had a significant 3rd party (Lib dems) since the 90s. Sure, FPTP sucks, but British politics has had more than 2 parties (that actually win seats) for quite a while
> In order to reduce costs, plastic parts were incorporated into the Proprinter design.

This article pushes the pros of these decisions and not the cons.

As a result of similar decisions, you end up with devices being throw away because the case had a single little plastic tab break.

As always, it is a tradeoff.
Interweaving Touch and In-Air Gestures (2014) [pdf]
Well, neither ww1 nor ww2 was as damaging for the US as it was for Europe... but then again, we started them ;-)
Software engineering-the only
Engineering field I know of where people professionally represent themselves as such without a four year degree with the word "engineering" in the title-hacking Linux and PHP since you were 15 seems to suffice.
There was a reason I included the second paragraph. There are type systems that can handle intrusive data structures. However, they aren't used in any mainstream language (affine types in Rust is already a major achievement).
It's a legitimate question. I have mixed feelings about it myself, but not to the point that I've bothered to train the cats to stay off the counters. Mostly I just avoid putting food directly on the surfaces the cats touch. It's not that hard, really.
While I understand the sentiment, this is pretty insulting to a lot of people who bear the title "engineer" without having completed an engineering degree. You're not going to be able to win this, it's like being upset that the definition of "literally" has changed. Many people without degrees are employed by companies like Google and Microsoft with the title "engineer."

Some of my friends don't have college degrees at all, and they demonstrably understand computer science fundamentals, algorithm design and software development better than many or even most college graduates.
The '7t/sec' limit isn't that relevant at this point. Currently, average tx/second is closer to ~1. [1]

Additionally, this limit isn't static. [2]

It is pretty naive to think that the community isn't aware of this (non) issue. [3],[4]

[1] https://blockchain.info/charts/n-transactions

[2] https://en.bitcoin.it/wiki/Scalability

[3] https://bitcointalk.org/index.php?topic=608561.0

[4] http://blog.bitcoinfoundation.org/a-scalability-roadmap/
It's a thought-provoking article, but I would also like to see something about React in it. It seems to me that React is a very pragmatic way to get around the global complexity-driven performance issues with DOM manipulation.

When we're coding, we're optimizing for a couple of different things, really. First is real-world performance (represented by slowpoke DOM manipulation). Second is programmer performance (represented by inappropriate abstractions). A lot of things we can do in Javascript to make programming less difficult and complex result in poor real-world performance, and vice versa.

But what do I know? I'm not by any stretch of the imagination a Javascript expert.
> The German government, in collusion with the German business establishment, has wrecked Europe, first through its irresponsible lending...

I do agree that this sanctimonious moralizing of the virtues of the German over the Greek is risible. However, with common assumptions in place, what Germans did makes sense. Businesses had high productivity, lots of capital investment, and nowhere to send the excess of the commodities it could produce, the domestic market was satiated. So they lent money to the Greeks etc. and had a place to send these excess commodities for a few years. They kicked the can down the road so that they could figure out what to do with this overproduction and - today is the result.

I see a worldwide self-reinforcing cycle for slow growth, unemployment, recession and depression. Companies have it over employees so money goes to profit more than wages. This happens eveywhere so money goes to capital, not consumption. But the more impoverished workers have no money to buy commodities. So a temporary solution is found - debt. Things go along again and then one day the game of musical chairs ends and you have a situation like now.

Greek youth is not going to put up with a 65% unemployment rate forever, and the election of Syriza points to that. So does the rising number of votes going to Golden Dawn and the KKE. I see news commentators calling Syriza "far left" - they are not far left, they are just socialists. People are so used to soi disant socialist and labour parties performing neoliberal cuts when elected to government, the idea that a socialist politician wants a floor to living standards is a shock to them.
> Abstraction is dangerous

True statement. Of course, it's more or less true, depending on how much the abstraction you're using leaks. Few (if any) abstractions completely encapsulate complexity, almost all will leak. But there's a range. Some abstractions elegantly cover a modular portion of your problem space and do it so well you only rarely have to think about what's going on under the hood (and will even produce effective clues as to what's going wrong when something does go wrong). Some abstractions awkwardly cover only part of a modular portion of your problem space, require a high intellectual down payment to even start to use, have gotcha cases that chew up performance or even break things, and require continual attention to what's going on just to keep development going.

Most are probably in between.

I think this is what JWZ is talking about in his famous "now you have two problems" assessment of regular expressions. I don't read him as saying "regular expressions suck," I read him as saying anything but tools from the high end of the abstraction quality spectrum means now you have two problems: (1) the problem you started with (2) the problem of keeping the model/details of how the tool works in your head. Regular expressions are arguably in the (maybe high) middle of the spectrum -- they may not cover your case well (ahem, markup) and they can send your program's performance to hell or even halt it if you don't know what you're doing.

Now, they're also broadly useful enough in all kinds of development that the benefits go up with the costs and so they're probably worth investing in anyway, as part of a suite of other parsing tools/techniques. So I'm not bringing the topic up to bash them.

But to take us back to the topic, I might be bringing it up to question the ROI of popular JS frameworks, which, as far as I can tell, are generally not at the the high end of the abstraction quality spectrum, don't have the broad usefulness of regular expressions to recommend them, and may not even survive longer than a handful of years.
> I wish there were some sort of joint efforts underway to curb populations, in countries like India, and at the same time curb consumption in the Western world.

The best way to curb a population is to accelerate a Third World country into the First World consumption you so denigrate.

Suddenly, female fertility drops below replacement when being a female doesn't suck.
$10 makes you an engineer. Please.

http://www.order-of-the-engineer.org/?page_id=237
wasn't it posted 4 years ago ?
Or, you know, don't play their game. You don't need to babble in politics, work in adversarial environments where 'someone is looking to get you fired', and deal with all the bullshit in OP. Find a small (10-20 people) software shop/consultancy, work on interesting problems, write good code, be free of all that shit.
"Criminal" is definitely the word to use when it comes to applescript, though maybe not in quite that way.
Why? Do you think there's something exceptional about being an "Engineer"?
I dislike the use of engineer for the IT industry. It was a title that was picked because it made you seem like more than you are, riding on the actual engineering disciplines that have to work for that title.
Another JavaScript NES emulator
I call myself a certified web ninja.
What do you suggest someone be called if her job title is "Software Engineer", she fairly received the job offer because she was qualified and she has no formal education?

Should we segregate people like because they don't have a formal education? What if she develops an algorithm superior to every other one in the field for a specific use case? Is she not an engineer, despite using the same skills as anyone else?
Look, what you are saying just doesn't work. What happens when the pointers are in registers? What happens when the loop is occurring in a thread running on another core?

Yes, you can make GC work in these situations, but you are going to pay for it. In perf.

I have to say frankly I do not believe any of the words in your last paragraph at all.
Maybe it's like that in the USA, but it isn't like that in most of the world. 'Engineer' means something.
Duplication is only one half of the economic picture. You don't need to explain to me how the costs of duplication have fallen to zero, but I would like you to address the fact that the fixed costs of creating something people want to duplicate are very far from zero.

Humans have been creating art, with or without economic recompense, for thousands of years, they're not going to stop now.

And for the longest time art was the preserve of the wealthiest segment of society that used it as means of keeping the population in line. The idea that people who work in the arts should not be allowed to use technology to monetize the product of their labor is a bunch of self-serving bullshit. Nobody is entitled to have an artwork they produce become successful, but if it does become successful (in terms of people wanting to watch/listen/read) then they're entitled to something in return for the utility their product has provided to the consumer.
Do you have any public examples? I have a use-case where I think this might make a lot of sense, so I've been toying with the idea.
But, but, but... Optimizely?
As long as your javascript framework is a micro framework and not a monolithic one, the abstraction does not make the project foggy.

Building the core and then using micro frameworks or components like react, jquery, etc leads to less walls as swapping is easier as time progresses.

You don't want to be caught high and dry stuck in years of monolithic to cleanup when the fad dies and at that point having abstracted away everything you need to know.

Outside of javascript, .NET WebForms and Drupal are classic examples of too much abstraction in monolithic fashion (those poor bastards stuck there - dead man walking), Angular might be another. The whole time you spent building addendums and machinations to a framework, not building the core of what needs to be known.

If the framework changes everything you do and abstracts core logic or the systems you are building doing things without you being aware, it might be easy to start 90% but there are gonna be problems and eventually walls and walls against you.

The only thing that should be monolithic and the base is programming languages and platforms. Everything else should be micro components or messaging.