skysight-inc/HackerNews huggingface dataset:
How do you get an accountant? I've asked friends, and they don't have them, don't know good local ones, or when I did find someone who had one and was happy with theirs, I called the accountant and he doesn't return calls.
Tesla_Europe: Announcing our 50th Supercharger
Stefano here, CEO of CloudAcademy.com, thank you for your comment!

Yes, similar to the concept of Codecademy, but totally focused on cloud computing technologies. Actually in CloudAcademy.com you can test your skills on cloud computing platforms and technologies (AWS, Google etc.) and learn with courses and learning explanations.

Our system is designed around our CloudRank: if you try our quizzes (https://cloudacademy.com/cloud-computing-learning-quizzes/) you will see that we are testing you with a question and right after we show a small learning explanation. Every time you answer you increase or decrease your CloudRank.

We are transitioning to a freemium model, right now all the courses and questions are free and you'll always have a free account to get access to a good number of them.

Stefano
Design Communicates the Solution to a Problem
No, it's an example from the readme: https://github.com/docker/docker-registry#quick-start
In fact, it comes from the Docker GitHub page
https://github.com/docker/docker-registry/tree/master
>What's wrong with setting up kvm "gold" images for your various server types (db server, redis instance, ha proxy server etc.) and then just dd'ing those images to host machines and using ansible/puppet/chef to do any final role configuration on first boot?

You're leaving out the other attractive aspects of Docker/containers: performance, lower cpu utilization, instant spin up, less disk space, etc. Those factors lead to higher density of images on servers. Puppet/Chef + hypervisors can't compete with those particular factors.

In summary:

Containers have less isolation, but can be more densely packed.
VMs have more isolation, but less densely packed.

The 2 technologies have different tradeoffs and economics.
>> In option 2, you praise the 3k.

And shorten your life by 12 months from the initial shock :)
Lastpass is down right now
Over time, sure, but the outliers could be worse. Per Dunning Kruger, people who are bad at something often don't know that they're bad. If you take a bad driver who's desperate for extra cash and set them up with Uber, they might drive a lot of risky miles before their bad driving catches up with them in the form of a suspended license.
This is post-industrialization where England tore ahead of the pack pretty quickly and managed to push a relatively tiny country not just ahead of their European competitors, but also ahead of giants like India and China.

As China industrializes, and they'll have to, they'll push ahead of everyone. Their domestic market is too huge.
Docker certainly has its pain points but I've actually really enjoyed working it into our build and deployment process.

The command syntax is sometimes a bit clunky but they are making regular improvements.

Not to repeat lgbr, but the registry is pretty easy to get running. I had some problems initially, but it was mostly because I didn't really understand how to use a container all that well. That sounds somewhat silly, but it ultimately was true.

Finally, the hype is ultimately a good thing. There's a lot of focus on the project right now, which (hopefully) means we can expect a good deal of improvement and stability in the near future.
Yo wants to connect the Internet of things
You make a rational case for it, while for many going through suffering every day, it doesn't seem to be an option. Think of slaves, (and all the modern more subtle forms of slavery). A far as I am aware the majority still wanted / want to live despite suffering every day.

I guess the idea (for most western people) is that it is a phase that will pass / things will improve.
It almost certainly is cheaper, but it's more than some are willing to learn to do, I guess.
And actually, even the ones that sgdesign liked ended up being copies of existing logos: https://news.layervault.com/stories/25882-the-5-logo

There's a lot of danger and unnecessary pain in it for a founder having a logo that's a liability. Not uncorrectable after the fact, but why do it in the first place?
All of those have simple REST APIs to setup/teardown instances. Libraries exists for popular languages like node, ruby, java, etc.
> To run unit tests which rely on certain hosts to resolve to 127.0.0.1.

If you are unit testing DNS infrastructure, shouldn't you mock DNS things?
LOI's are generally more interesting to investors. As someone who is bootstrapping or working with limited time or money, there's no better validator than money.
Thank you for the comment. Yes, we do talk about CloudWatch, let me check why it's not cited in the index.

Stefano
What's wrong with that is that now your application--and, by extension, your developers--has (have) to care about a lot more stuff and needs to have its testing surface expanded appropriately. The potential interactions and therefore potential failures between, say, ops's cron jobs, the wire-up of stuff like logstash, changes to your chef configs, etc.means there's a ton more testing to be done. In a Docker world, the amount of stuff running in a context that the application can see is minimal and it's all related directly to the application in question. Your inputs and outputs can be clearly defined and this lets you present a stable API to the outside world (via volumes and links) while, as or even more importantly, providing a known-good, stripped-down environment for the application to run on. (chroot jails are a fine solution too, but I do prefer the relative handholding and easier application independence of Docker and AuFS.)

The other problem with your suggestion -- dd'ing and then running Chef or whatever -- is boot time. I can spin up an AMI ready to deploy Docker apps in under sixty seconds. We work in AWS, so I can't speak to the actual time of deploying a physical server, but I can download and deploy a Docker image from an AWS-hosted private registry in ten seconds. Chef won't even get its act together in thirty seconds, let alone do your stuff; between downloading a full VM disk image, the startup time for that virtual machine, and the time to run chef, you've wasted so much time.

Here at Localytics, we're trying to transition to an environment that is very comfortable with automatic scaling and can do so fast--seconds, rather than minutes--and Docker is a big part of that effort. Right now we deploy to AWS autoscaling groups (with AMIs defined via Packer). I'm pushing hard for us to use a clusterization system like Mesos/Deimos because it'll let us save money by introducing safe, sane multi-tenancy--and it'll let us react to changes in system load in mere seconds.

(obligatory: we're hiring. we work on fun stuff. eropple@localytics.com)
Those ideas about community aren't just sentimental, they're reflections of real human needs. Humans value community to a tremendous degree, shaped by evolutionary pressures evolving from our tribal roots. We want to feel part of a larger group, whether it is our family, neighborhood, city, company or country. This isn't a relationship born out of "creating solutions," it independently nourishes an innate emotional need.
Sounds great, thanks for the info!
How much did your lawyer's hug cost you?
The problem with the landing-page-and-email-addresses method is that it's impersonal. It's also a low-commitment activity. It's so easy to sign up for something, and it requires so little conscious thought. You will get a lot of false positives because of that.

It's counterintuitive to some extent, but consider a two-phase signup process: a landing page plus an email validation of some kind, or perhaps a two-step signup process on the landing page. There will be a noticeable drop-off between Step 1 and Step 2, and that's good. Those are probably people who would have washed out anyway, and you no longer have to waste time catering to them as false positives. [1]

I'm not saying this was necessarily your issue, but a lot of people run into problems with hypothesis testing by conflating it with marketing or growth hacking. It's not. You're not trying to optimize a hypothesis test for pure signup volume. You're trying to use a hypothesis test as a filter: for the right audience, for your problem/solution statement, and for the value proposition you've chosen to test.

You don't want signup to be a total pain in the ass, but at the same time, you don't want it to be so easy that it loses meaning as a signal of intent.

[1] Caveat being that you still want to probe, and perhaps ask people who've bounced between 1 and 2 why they did so. Sometimes it really is just a UX issue. But in my experience, if someone really has the problem you're addressing, he or she will stick through a two-step signup or validation process.
You don't need a government-sanctioned monopoly to get a taxi service. You need government regulations of existing taxi services to avoid the many problems that have been observed with unregulated taxi services, including but not limited to:

-- drivers that jack tourists around
-- drivers that don't know where they're going
-- drivers that don't make enough to live on
-- excessive numbers of empty taxis idling/cruising the streets, creating unnecessary congestion and pollution
-- drivers that red-line particular areas of the city
-- drivers that red-line particular ethnicities of passenger
-- taxis as a public service: making sure everyone has access

If your only analysis is the typical Hacker News mouth-breathing of "government BAD huh-huh", then I can't help you. But if you're actually trying to understand the problem, you should maybe consider why every city in the world has some sort of taxi regulation system.
Browser Face-Off: Battery Life Explored 2014
My understanding is that dumbwaiters and laundry chutes fall under a fire code which boils down to "Nah, dude. Don't do that" just about everywhere. Vertical passages are great for fires, and bad for people who like not being on fire.
Centralised Logging with Rsyslog
The big thing was just that the Saturn was supposed to be a badass 2D platform, with insanely powerful hardware sprite management. When Sega belatedly realized that 3D was the next big thing, they stapled on an extra CPU to give it enough power to handle 3D...but neglected to up the RAM or the CPU bandwidth. IIRC, it wasn't even theoretically possible to fully utilize both CPUs.

Very different situation than the Emotion Engine or Cell.
New iPads to have anti-reflective screen
Umm, so, how do you deal with Docker when you have more than one physical machine? It seems half the stuff it does just doesn't work then, and you have to pile on further abstractions anyway, using Docker just as a simple container management system (of which we have working ones already) and container build system (of which there are far better systems available).
I'm interested to hear what's everybody's take on how Docker compare/compete/integrates with virtualization (e.g. VMware, KVM, HyperV).
> it's all JavaScript so performance is rather moot point

If that was the case, http://asmjs.org/ wouldn't be a thing.
At Localytics, we wouldn't need to lease a dedicated server. We'd need to lease dozens. And we'd need to have the ability to spin up new hardware to accomodate more load in a minute or two.

You don't get that with physical hardware unless you want to overpay. We could overpay for depreciating plant assets or we could overpay for variable costs that we can more directly control. The latter makes sense to us.
I setup docker for our server deployments here at lever.co. We deploy our application multiple times a day. We test our changes in our staging environment first, and its important that we deploy the exact same code to production that we tested. Its also important that we can rollback any changes we make.

An application-image is the right way to do that. (With compiled dependancies and whatnot). And we could make an OS image every time we deploy code, but making a 600MB Ubuntu image to deploy a few lines of code change is ridiculous.

There's certainly lots of things that docker could do better, but I haven't seen any tools that let me deploy so conveniently, easily & reliably.
Yes, as I said, it's only /some/ Greeks that feel this way. I hope I haven't misrepresented the situation too much? (Please correct me if I'm wrong!)
A bit offtopic: Great idea :) . It's really hard to find customized birthday presents (it was actually a startup idea that was floating around at several startup meetings I attended).
Just wanted to add some other links to the current status.

https://twitter.com/LastPass/

I've never seen this site but it seems to be pretty accurate about when I just couldn't access Lastpass any more.
http://www.isitdownrightnow.com/lastpass.com.html
then just use environment variables (ENV keyword in Dockerfile or --env param in docker run command)
I'm trying an idea for a small project that I am sure I stole from Hacker News.

I run a football pool at my office, and I was manually creating each week's list of games. So I scratched my own itch and automated this as much as possible (some manual work). I've made the results available on footballpickempool.net. It simply offers weekly pool sheets for the full season, and results will also be posted. I know many people could find this useful, but not necessarily a paying audience for such a simple offering.

The validation idea I'd seen before was to offer a link to a "feature," and see how many people click on it. So I have a "Start a League" link. The page let's them know that this feature is not available yet. And I also have a Google form on the page asking if anyone would pay a small amount for this feature.

Hopefully I see some results as the upcoming season starts.
It would be interesting if people here on HN have tried the course, to hear what they think about it.

My understanding is that users are required to pay; why don't you offer a limited access for free, say for the next 24 hours?

I'm sure that you would benefit from such feedback.
Other business owners in your market & locality are a great source of referrals. And there's nothing wrong with searching the Internet, if you're willing to check references of the firms you consider.
More Tips for a Software Résumé
It was supposed to run Steam Machine but Steam has delayed SteamOS until 2015. Still a very heathly piece of hardware though for its size.

http://steamcommunity.com/groups/steamuniverse#announcements...
Kinda. You need H.264 codec support in Gstreamer. Try installing the Gstreamer libav (an FFMPEG fork) plugin: https://www.archlinux.org/packages/?name=gst-libav

That should give your Gstreamer support for all formats libav supports.
Then you should be (ideally) using a service discovery solution or (less ideally) wiring up with environment variables. This is (one reason) why CoreOS uses etcd.
I'm not unit testing DNS infrastructure. I'm unit testing an Apache module. I send requests to different virtual hosts on 127.0.0.1:80, and checking whether the responses are what I expect.
Are you familiar with a Chrome extension called rather? It's a great way to block out posts you don't want, like those containing buzzfeed links. The replacement content is so-so in my experience.
http://www.getrather.com/
The 8th set ends in an elliptic curve attack that (a) is useful in the real world and (b) only one person I know has been able to implement. It is amazing.
The word 'bicycle' is mentioned only two times. 'bicyclists' once, 'bike' none. Why are we officially overlooking a fantastic and common form of transport?
Nice one, sounds like a great resource. Anybody knows if they will add more content about AWS stuff in the future?
Taking The Shape Out of GoPro
I've been playing around with docker, so I will lend my two cents. If kvm gold images work for you, then by all means use them!

What I like about docker: The layered filesystem [0] is easy to work with and seems pretty smart. I can easily tweak an image, push it to docker hub and pull it back down. Only the delta is being pushed and pulled, not the whole filesystem. This seems like a pretty big win to me! Your db server and redis instance can share the same base system image. This makes updates and redeploying the images much faster!

Also the containers are much lighter weight to run than a vm. You don't need a beefy machine to run a few containers. I'm under the impression that one can run 20-30 containers on a modern laptop, but haven't verified this for myself.

[0] http://docs.docker.com/terms/layer/
I personally would say "It's just you."

Docker has been huge for us. We can run the same containers locally that we run in production. Dockerfiles are SIMPLE and easy for people to create and understand.

Fig has really made using docker for local dev rather pleasant.

Are there some hiccups here and there? Yes. The project is young and they are actively trying to smooth over a lot of issues and pain points.

I feel like most people who dislike docker have not actually tried it or used it. That could just be a wrong opinion though.
Ask HN: Anyone Building Something Geared Towards Senior Care Market?
I'm working in the senior care space but rarely see much innovation or exciting start-ups focused on this market. My gut is most young, entrepreneurial types don't have this market on their radar even though it's growing rapidly and in my experience deeply undeserved. Would love to hear from other innovators in the space!
We should not be too harsh with people who inadvertently post their secret key. They may be very nice, well-meaning, smart people who, you know, make a mistake and post their key. Maybe it is in an environment file, and they post it to their public github. Could happen. Maybe they forgot and went to sleep, and found out their key got jacked. Maybe -- hypothetical here -- someone ran up $1000s of dollars producing bitcoins on this innocent person's account who made one mistake. One tiny mistake. You never know.
That's not true, it was meant to be a 3D console from the get-go.

However after they found out how powerful the Playstation was they quickly added extra power to make the console more comparable and that was where the complexity came from.
I have actually implemented a TCP stack in python, unfortunately I can't share it publicly just yet.

The authors problems are because she is not using RAW_IP_SOCKETS.

Making TCP packets using pythons struct module is a breeze. I can post specific examples in code if anyone is interested.

Finally you can write a proper TCP stack in python, there is no reason not to. Your user-space interpreted stack won't be as fast as a compiled kernel-space one - but it won't be feature short.

PS: I guess, Google is probably sending him a SSL/TLS handshake which he isn't handling.

Edit: Corrected author's gender as mentioned by kind poster.
“How to make a pop song in a minute”
Multiple clouds is the killer app - that's a key thing that nobody offers at the moment.
Why no :)?
The tcomb library seems to do quite a lot, some of which might be sort of useful, but the example supplied here doesn't really seem to support why you might use it. The code in fact just seems weird to me: if you're having to use a try/catch to do some really basic form validation, then obviously that's horribly wrong... but the example below, under "Further Reading", which is (I think?) proposed as the better solution, doesn't really seem any different from how you might go about solving this problem were you not to use any library at all, except you wouldn't have the struct stuff. Very unconvincing, if you ask me.

Contracts.js is quite a different approach, maybe even to an orthogonal problem, but perhaps is more interesting: https://github.com/disnet/contracts.js
I haven't suggested that general anarchy has erupted. I've suggested that "breaking the rules is part of being human" is a crappy justification for breaking rules.
Mmph, have done this with XenServer (can just self-built OSS) and just standard RDP clients for the short while I had access to a machine about that powerful. That worked beautifully and gave me (yes, just me :P) a bunch of very practical isolated environments on which I concurrently ran various heavy workloads (and one as my 'standard desktop' on which I watched YouTube videos whilst waiting for things :P).

I only use Linux/OSX for local machines, but RDP was substantially more responsive than any VNC server I could get my hands on (including RealVNC Enterprise).

Layering Guacamole shouldn't cause any real trouble beyond that - the dashboard needs to run on a separate Unix machine and so can be pointed at all those desktops just fine once you set up the network interfaces.
I thought at one point it would be fun to gather all the titles of this nature I could to create a hype/buzz title generator maybe using a markov model or something. No time though.
All the other alternatives pain in the ass to use?

Pardon me, but like op I found docker to be quite unusable, and LXC a breeze to use.

Why go with the bad abstraction when you can have the real thing? Lxc has everything you want, with zero obscuring "magic" which you don't need anyway.

LXC is definitely recommended. For max benefits you probably want to couple it with a fancy filesystem like btrfs, bit it's by no means required.
I've had great experiences with voice-over services etc, but I'm a bit hesitant with creative work like logos (most just run through online logo creators). I do earn some[0] though creating small AngularJS directives and services, pays for my Digital Ocean dev box

[0] http://www.fiverr.com/ihatehandles/help-you-with-angularjs-c...