skysight-inc/HackerNews huggingface dataset:
I was on the autoimmune protocol for about a year and slowly introduced things after that. The first month on the diet sucked. I felt worse. After that though, things really started to turn around. I was also on vit supplements due to a lot of my levels being extremely low (Vit D & Iron) and am still supplementing because my body has a hard time holding onto these things.

I also take a 20 min fast walk each morning when I wake up and do my best to eliminate stress (I know easier said than done).

I had very high antibodies and now have none. I wasn't able to make it past 1pm without crashing and now have no problems making it through the day.

3 years later I am still on a strict diet but not nearly as strict as it once was. There are certain foods that still make me crash (sugar, beer, etc) but overall I got my life back :)

I am not saying this will work for everyone but it has worked for me and others like me.
They've also lost COMPLEXITY, and this always pays off, even if in roundabout ways that you cannot measure, and even if it's only for the positive effects on the mental-health of the engineers working on this!

Really... modern WordPress is a very complicated beast and keeping all sorts of details about how you need to optimize it, server, caching, db in you head is just no worth it. Yeah, "changing two lines in the nginx configuration" could have worked, but imho simply the cost of keeping in your head the information about what two lines to change is just too large. As it grows, it simply drives you insane by how many technical trivialities you need to keep in your head to keep it working smoothly, when you could instead use that brainpower so solve the really interesting problems.

An the fact that "their marketing team has to use the Github interface and learn Markdown" is also a hidden benefit, if you think about all the subtle frontend bugs that happen when somebody uses the WYSIWYG editor of WP and they end up with a combination of styles that breaks the layout. For any project above a certain size, the "dumb WIM" (What I Mean) interface of Markdown always trumps the WYSIWYG.

Also, the benefit of mostly NOT HAVING TO THINK ABOUT SECURITY AT ALL is freaking HUGE! Developers can simply say "it's the server guys' problem" now. Forget about having to manually audit the code of 3rd party plugins if you really care about security. And forget about updating and realizing something breaks and you have to fix it.

For any fast growing company, keep this in mind: REDUCE COMPLEXITY. ALWAYS. NO MATTER HOW LARGE THE SHORT TERM COST.
PolarSSL said it wasn't affected by Heartbleed. There's quite a few non-OpenSSL libraries out there to use which might or might not be affected by any given bug in OpenSSL. I just remember PolarSSL because I stumbled on that claim while reading on users of Frama-C tool for finding bugs. They use it apparently.

The LibreSSL people showed one commit at a time that OpenSSL was just poor coding through and through. I'd expect any implementation that paid more attention to code quality to do better. That's just one part of getting a crypto library done right, though.

http://www.openbsd.org/papers/bsdcan14-libressl/mgp00001.htm...
Were they holding on to a /48 per week? If they were, I'd have to imagine that at some point a single company that's not in the ISP or hosting business would be effectively holding on to a /32 and some questions would be raised.
This only seems to work for the country where such company is headquartered. The technological advantage, meanwhile, spreads to pretty much any country (e.g. countries that had little with invention of television or automobiles have TV sets and roads), so what's the solution for them?
See my comment above. I would love to hear about what you have done too.
How gravity kills Schrodinger's cat
Ask HN: What sort of database would be a fast backing store for git?
In this thread, mhodgson explains why Postgres would not be a fast data store for git. https://news.ycombinator.com/item?id=9833548

mhodgson says: "Once you understand how git works under the hood it's actually fairly easy to predict that performance will be poor. A simple checkout involves accessing 100s if not 1000s of objects. Also, you can't fetch these all at once because the objects you need to fetch are determined based on a nested tree. So you have to query the tree all the way down, getting each nested tree or blob based on the previous tree's contents. So ultimately you're doing 100s-1000s of queries for any given git command. Each query is fast, but even at 1-2 ms per query it adds up quickly."

So the question is, what sort of data store would be extremely fast and scalable for storing git? A graph database? A key/value store? Seems a little odd that the plain old file system is the fastest option.
One might also hypothesize that survivors tend to be more careful, conscious of their health, etc. I don't know if it's a great hypothesis, but it seems plausible.
I see where you are coming from, but I wonder if Apple will play it's "luxury brand" card and cater not so much to the masses but to the wealthy. Privately owned self driving cars will definitely be preferred among those with wealth in the future. Sort of like owning the latest iPhone, it will be a status symbol that will also attract those for whom the cost is illogical beyond status.

Also China.
I would also add that unikernels make sense from the architectural point of view. Instead of running the monolithic behemoth of modern operating system, you can run something very basic, like a hypervisor and have everything else in optionally-linked libraries.
I don’t disagree that making something is hard, but really good ideas are actually very rare and valuable. The problem is most people’s ideas are not very good and hence worthless.
> Also, a nit: the butterfly effect has nothing to do with this discussion. It's an effect [...]

Sorry, I had assumed it as an idiom without establishing a shared lexicon. I mean, an effect so small as to only possibly be significant via an appeal to the butterfly effect. As in, ultimately we can't rule out that assassinating Hitler when he was a teen would have caused the sun to go supernova, because X, but it's vanishingly unlikely.

> I'm arguing that it's not crazy to think a small perturbation in policy (an x% decrease in the total cost of having sex) would likely lead to a small and proportionate response in behavior [...]

Sure, this can always happen. We always need to have our eye on the metric (the 21st century "ball").

But unless you've actually got a good argument for why it's likely that this program will go wrong, you're more likely to cause harm by kvetching than by letting change happen.

> [...] as an example of such a study, look at this one [0]. It's about how certain abstinence-only programs [...]

Sure, if the alternative is emulating reality shows then anything, including _Catholic Hour in the Nursery_ would probably be better. Thankfully we don't live in a black and white world.

And of course any classes should include a huge dose of self-esteem and other training supporting the right/desire to say "No", but when a couple want to have sex do we really want to punish their offspring? Sins of the father? Srs?

Or do you really deny the plight of the unwanted/required (high death-rate) child?

TL;DR What I'm saying is that we know people will have sex despite it being wise. (Do you really require a cite? If so, list the keywords you've searched and I'll help you use the internet.) So when they do, though we may wish/help to delay that a while, lets help them do so safely when they inevitable do.
The question you should have asked is "how is it that [idiomatic] python is less amenable to functional programming?", which you basically answer yourself. Otherwise, I can't see how amatsukawa implied Python itself was less amenable.

What is stopping you from implementing those ideas in Python during a first-semester course in CS is that you will not serve your students, as amatsukawa described.
See also the official CERT Advisory [1] on vulnerabilities in the ID4 Alien/OS, warning of potential denial of service attacks by inferior life forms and recommending various workarounds in the event that planetary takeover is necessary (yes, it's a joke, but having been published within hours of the first screening of the movie this may well have been the fastest CERT vulnerability response in history)

[1] http://users.rcn.com/alderete/humor/comp/id4.html
Can't reply, but the annotations off plugin is called
"YouTube - Disable Annotations" by notsie
See my comment at https://news.ycombinator.com/item?id=9843715
There is also a Dart version: https://github.com/domokit/cassowary
Kind of, but not exactly.. They exchanged many of the short term loans with longer term ones, with conditions that demanded heavy austerity. The private banks took a big haircut after years of negotiation but the private loans were a small total portion compared to the public ones. The IMF readily admits how flawed their troika bailout was;

http://www.washingtonpost.com/blogs/wonkblog/wp/2013/06/05/i...
They're in Venice Beach, they may just be using the palette and style they know.
Huh. I thought many of those surprisingly good. Certainly better that what I see in local art galleries.

https://www.flickr.com/photos/7474079@N02/17227816585/
https://www.flickr.com/photos/7474079@N02/18470207921/
> And the fact that it's cheaper is basically "disruption from below" - a proven strategy in many businesses.

I believe the business model you are referencing is generally known as "race to the bottom"[1]. FWIW, it typically is only a "proven strategy" for the business which can starve out everyone else.

1 - https://en.wikipedia.org/wiki/Race_to_the_bottom
I wonder, is art only about education? I used to be pretty good at sketching in general, But i feel i do not have the imagination to create such wildly out of the world landscapes. Is there a way to learn how to imagine? Or would one say art isnt for everyone?
I don't know why this comment is being downvoted, do we downvote on differences of sentiment now on HN?
Given the OpenSSL trackrecord [1], I recommend switching to LibreSSL [2] if possible. They tore through OpenSSL to pull out all the horrors they found and beat it into shape. OpenSSL's code was so unbelievably bad that there's certainly more problems lurking in there.

[1] http://www.openbsd.org/papers/bsdcan14-libressl/mgp00001.htm...

[2] http://www.libressl.org/releases.html
> First, why does your home office need globally unique identifiers for its devices?

For the same reason that the original plans for the Internet ensured that every connected machine was a peer of every other: a network of peers easily allows for new and novel services on the network.

> Second, how does having the MAC address make routing simpler?

It doesn't.

> Third, wouldn't temporary (privacy) addresses undermine this entire EUI-64 setup's efficiency improvements?

That's not the point. The point of this setup is to provide a way for SLAAC to easily create a stable IPv6 address to make DNS forward and reverse mapping on the LAN easy to manage. There's also an alternative method for stable address creation that doesn't use the system's MAC address.

> Now you're back to randomized data in the low 64-bits, so the router and PC need to have some kind of negotiation to know the IP addresses just like before anyway.

You really need to read how SLAAC works [0]. In particular, pay attention to the Duplicate Address Detection section, and note how DHCPv4 uses a similar method for determining whether or not an IP in a pool is safe to hand out.

After you've read about SLAAC and DAD, read about Neighbor Discovery [1]. This stuff is more well thought out and less complicated than you seem to think that it is.

[0] https://en.wikipedia.org/wiki/IPv6_address#Stateless_address...

[1] https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol
Ah – didn't think about the dependency on Xorg.

I don't think Byzanz requires GNOME though. I've been happily using it with i3.
Our problems actually weren't with Jekyll. Like I mention in the post, much of the functionality came right out of the box. The major pain here was exporting and combing through the data afterwards, and that required some Python to parse comments and convert to markdown. Once we did, that meant less security holes, opening up our content and technology more, among other pluses.
Hey that's pretty cool! I wasn't aware of this.
How to download files hacking team?
Someone else also mentioned prose.io - something I didn't come across when building this. Going to explore.
The humans do seem to drive a little crazy on California St. in Mountain View! I've had a near miss with a negligent driver on that street myself. Nice to see that they're moving the cars away from the quieter (more suburban) southern parts of the city near the hospital.

I have yet to see the new prototypes, which are allegedly making tours as well. Does anyone know what streets they frequent?
Does this or CJDNS have any mechanisms in place to limit metadata exposure?

From what I could gather, both use public DHTs for routing, and AFAIK public DHTs in general can be rather trivially crawled for metadata.

The current generation Internet already offers plenty of methods to protect message contents, but very few can also obfuscate metadata, which can be just as revealing, but almost always much more readily accessible.
I would say that the CEO's key role is more to make sure that key constituencies and stakeholders are addressed as effectively as possible, not necessarily to address them directly themselves. Sometimes it is actually more effective to delegate that job. Having said that, it certainly seems to be the case that the closer a constituency is to the core competency of the business, the more likely it is that they should be addressed directly by the CEO, and I buy the argument that moderators and heavy contributors should be the core competency or reddit.
The problem there, which The Innovator's Dilemma didn't cover, is that seals were a huge problem for hydraulics until the invention of Neoprene synthetic rubber around 1930. Until then, hydraulics always leaked. Somebody built a hydraulic excavator around 1880, but that was a dead end. Success didn't come until 1948 or so.

Pumps, valves, and hydraulic cylinders that don't leak are a post-WWII technology. Natural rubber doesn't tolerate oil. All the alternative to it (cloth packing, oiled leather, etc.) are worse, and hopeless at high pressures. This is an example of something that just doesn't work with natural materials.
Implementing Token-Based Authentication in a Microservices Architecture
Not realy. cjdns seems to need an invite to get onto its network.

Not saying that's necessarily a bad idea; cjdns seems to be useful to the people that use it. But if I want to build an app that communicates P2P over such a network, a manual step to join the network won't fly.
I use these sites as a client to get work done on projects that I don’t have time for. From the hiring side it is rather hit and miss. I have found that price does not correlate with quality or reliability of freelancers. About 2/3rd of all developers flake out before delivery. This is despite me providing technically very detailed proposals and extensively discussing the projects before choosing a freelancer so they know what I expect.

What I have found works best is just hire two people to do the same project at the same time - rarely you will get two delivered projects, but since cost is not such an issue I just chose the best coded one.
Why Do I Code? On Accepting Donations
For python + qt version check enaml - https://github.com/nucleic/enaml - it was posted here from 28 days ago - https://news.ycombinator.com/item?id=9677375
so it is as secure as every other pieces of software out there
https://en.m.wikipedia.org/wiki/Bupkis
Frotz feels to me like a pitch perfect choice for extending TempleOS's ecosystem. A job well done in so many important ways.
Facebook Password Stealer 2015-2016 Download
I think that when the Manhattan Project was started, physicists knew that it was possible, in theory, to build a nuclear bomb. It's just that no one knew how to manufacture it. Going from "we know it's possible" to "built" is more amenable to a systematic process than going from "is this even possible?" to "built". I think the article is talking about the latter. iPhones were firmly in the realm of science fiction fifteen years ago. It would have been very different to systematically try to create one. Whereas in 2007, it was apparently possible, just no one knew it yet.
If someone made a Go compiler for it, I'd switch - today.
You could see a (perhaps incorrect or ultimately misleading) example of it:

1. What would have to be true for us to have reliable transmission of messages over an inherently lossy network?
1a. some kind of method to ensure that a message got to its intended destination

2. what would have to be true to ensure that a message got to its intended destination?

2a. some kind of method of ensuring that failures don't occur, or if that is impossible, some kind of method of making intermittent failures not prevent the system from eventually functioning.

3. what would need to be true to make intermittent failures not prevent the system from functioning

... etc...

Slightly misleading because I'm obviously working back from a familiar example, but I think the technique is applicable in some cases. At the very least your solution is born out of trying to make the impossible just barely possible rather than seeking to build layer by layer to achieve something possible.

However, with TCP/IP you can also see how using traditional methods also work.
Yeah, I'm still not feeling much sympathy for him though. He did 11 months for a premeditated theft for which he tried to cover his tracks. Is that too harsh? Of course they're going to go after him. And you're worried about him getting another job?? I don't get it.
This. London is a shit-show, filled with people that don't want to talk to you, and without wanting to mention the old rat-race cliché, that's precisely what it is; selfish, greedy, and unhealthy.

I lived in London for five years and it was the most miserable five years of my life, rent was £1,000 a month for a shared house in Camden, and with bills on top the majority of my salary was eaten up by living. I moved from London to Liverpool, my salary actually increased, and my rent halved for my own apartment. Now I have savings, my office is walking distance (8 minutes, to be precise), and the city is friendlier, safer, and being smaller it is made much easier for seeing friends and getting out more.

What London doesn't want you to know is that there's a whole country outside of it, with much better living conditions.

If moving is not an option, you can look at reducing and removing your debt using a charity, they arrange monthly payments straight out of your salary so that you're not building arrears, Martin Lewis normally has good advice on this sort of stuff: http://www.moneysavingexpert.com/loans/debt-help-plan – the same website will also help you lower your outgoings.

Most importantly, $50k is not a lifetime of struggling, and you should look at getting a payment plan sorted before it becomes usurious. I've seen debt do horrible things to people and families, it's better to fix the roof whilst the sun is shining. Talk to someone.
The paper is looking at these types of consumers in aggregate, effectively at the proportion of a product's sales that come from each group. These "harbinger" consumers are only harbingers if, collectively, they make up a disproportionately large percentage of sales.

Another way to think about it is that what you really should care about is not the number of sales, but instead the the number of sales to people who have similar purchasing patterns to the typical consumer you hope to reach.

What's interesting is that the authors are arguing that sometimes having a lot of early sales is actually worse than having only a few. It's a problem if that large number of sales includes a disproportionately high percentage of "flop affinity" consumers. It would be better to have a small number of sales, but also with low percentage of high "flop affinity" consumers. The intuition behind this is perhaps that in order to reach so many of a relatively rare consumer type - the harbinger of failure consumer - you must have also reached a lot of the more typical consumers, and they decided your product isn't appealing to them. On the other hand if you have low sales, but only a small percentage of these sales is to harbinger consumers then presumably your product is appealing to mainstream consumers, and your sales problem can be fixed with relatively straightforward marketing and distribution tactics.

Maybe the tl;dr could basically just be: not all early sales are the same, so understand who your buyers are and how representative their purchasing habits actually are of the market you're trying to reach.
Raising capital gains gives a boost of about one year though http://www.adamsmith.org/sites/default/files/resources/capit...

After that the market reprices accordingly.
Looks a lot like Space Fence...

https://youtu.be/7SJdN90vT04
Because they are special snowflakes. They apparently aspire to seen as some sort of ivy league university and don’t want the “stigma” of being mistaken for being in Australia. As an Australian this sort of cultural cringe makes me angry, but it is all too common :(
That’s exactly what I just did for my daily video / podcasting site Rate My App.com.

- Everything in markdown

- Generate the podcasts as an RSS feed

- Generate the list of videos as JSON, filtered inside the AngularJS app

Such an approach is not great for SEO in the short-term, so I won't be surprised if they lose ranking because their posts and comments are missing from the the html until their jQuery code fetches and renders them.

For me, I don't have 700 posts so that's easy to address later once I have content worth indexing, keeping the urls the same of course. :)
Google's latest science camp for kids starts on July 13th
Of course. I'm just saying that from the point of view of Servo, drop-in Gecko isn't really the focus. Making Gecko more HTML-y is a great step for Gecko, but from a purely Servo point of view at the moment it's not really something tangible. Though you're right, it may mean something for Servo a couple of years from now.
The new ones drive on San Antonio quite frequently, making the loop near Central Expressway.
Way close of a name to MIUI.
Taxi companies already have all the raw political power they need.

Hiring software engineers to churn out software apps and maintain highly available servers should be the easy part then.
I think we need to be careful of treating Material as an all encompassing solution. A lot of UI / UX folks I know are full on embracing it without taking a step back and seriously evaluating what problems it will and won't solve. I'm not saying I dislike it, I just think that there are different solutions for different situations. There is no silver bullet in our industry.
Everything dmux said, adding the fact that Forth can be implemented by extremely simple and compact code, think of it as the smalltalk of the embedded world (For instance Apple bios - open firmware - give the user a Forth REPL)