HNHacker News
TopNewBestAskShowJobs

danielsiders

4,059 karma · joined September 3, 2010

submissionscomments
danielsiders··on Flynn Beta (YC S14)
In the simplest sense it's an open source Paas (think Heroku), but with much more flexible technology. It's designed for ops teams who can run a single platform instead of doing custom deployment work for each application and database
danielsiders··on Flynn Beta (YC S14)
We're currently raising a VC round (we're in the current YC batch).

We've already done paid support contracts on the enterprise side and are developing the management service into a SaaS offering.

danielsiders··on Flynn Beta (YC S14)
Yep, tons more, soon. For now, start here https://github.com/flynn/flynn/tree/master/demo. We're moving this and more like it to the docs.
danielsiders··on Flynn Beta (YC S14)
Flynn cofounder here, happy to answer any questions
danielsiders··on Soviet Armored Military Vehicles for Sale
$500 for a tour of 25 people. Are there 25 people on HN who'd want to visit as a group?
danielsiders··on CoreOS Stable Release
The best option right now is to check out https://github.com/flynn/flynn-demo however we'll have some much better tools in a couple of weeks.
danielsiders··on CoreOS Stable Release
Beta's coming soon and we're still on target to ship a production-grade stable version of the major features in a few months.
danielsiders··on CoreOS Stable Release
Flynn co-founder here. Flynn is free open source software and always will be.

Our managed service is for users who want to outsource the management of the cluster to us. There's no secret extra technology (it's just Flynn underneath), what you pay for is a professional ops team to manage your cluster. The service is also freemium (and free for the vast majority of users).

danielsiders··on A SWAT team blew a hole in my 2-year-old son
Also in general the severity of the charge is directly proportional to the quantity of drugs. So if the quantity is instantly flushable, how serious of a charge can it have been, and thus how much accidental damage is acceptable in the arrest?
danielsiders··on Xanadu: we have a working deliverable
Ted spoke at a Super Happy Dev House at the Tech Museum a few years back and gave a short(ish) explanation of Xanadu

https://www.youtube.com/watch?v=ePOWsePB8zY (part 1) https://www.youtube.com/watch?v=u5D83SpbTXM (part 2) https://www.youtube.com/watch?v=EcgV-lsQUwo (part 3)

danielsiders··on Canada's Pitch to Tech Entrepreneur: We'll Pay 80% of Your Salaries
I believe the company also needs to be majority owned by resident Canadian citizens. There are a number of accounting firms that specialize in SRED claims, but most take a cut of your return in exchange for their services.
danielsiders··on App.net State of the Union
Absolutely correct. We'll also release a protocol validator for 0.4 prior to the server refactor to help other folks implementing other servers.
danielsiders··on App.net State of the Union
Hi, Steve. Most of the github issues you opened (in the week after Tent 0.1 was announced) weren't "problems" with the protocol, just differences of opinion with our architectural choices. For a variety of reasons that we discussed extensively we felt (and still feel) that hypermedia, microformats, and other preexisting attempts to solve "decentralized social" aren't good solutions to the problems we're trying to solve. A few of the other issues you raised were actual implementation errors (we shipped the initial proof of concept very quickly), and to my knowledge they've all been fixed.

In the first few days after we released the first Tent proof of concept we were swamped with user feedback and a variety of discussions. We addressed many architectural questions in detail from "why not use a custom binary protocol" to "consider using ostatus, microformats" and "Consider not making claims about REST". If you're still interested in any of these topics I'd be happy to explain in greater detail the reasons for our choices.

Tent has evolved a great deal since the initial release. We've discussed most of the reasons behind the choices we made in great detail on Tent, IRC, and during monthly office hours, recording of all are available online.

danielsiders··on App.net State of the Union
One of the Tent architects here.

We're actively working on 0.4. The big challenge right now is that a number of organizations are considering using Tent is very large scale deployments for sensitive data, so we're making the transition from move fast and break things to enterprise grade reliability.

This includes everything from a solid protocol validator (future versions of the protocol will have complete validation coverage before we release a reference implementation) and a highly scalable multi-tenant server that large service providers can easily deploy. We're refactoring the server we use for hosting Cupcake users and releasing it under a permissive license in the next few months to make that transition easier.

So it's an exciting time for the core team but there isn't a ton happening on the surface just yet.

Our goal has always been to get Tent to a solid 1.0 after which the APIs could remain unmodified for several years at least (similar to HTTP and SMTP). The tradeoff is that we then need the freedom to break things between versions of the pre-1.0 versions. It's frustrating for early app developers (one of the reasons we don't encourage adoption) but will pay off once we hit 1.0

danielsiders··on Flynn: first preview release
Flynn is the product ops should provide to developers.

Flynn is a single platform that runs all your services from databases to applications to individual Linux processes. With Flynn ops teams can stop being consultants and start providing a single product to their internal "customers". Basically you can deploy and scale whatever you want all in one place on any infrastructure without having to think about individual hosts.

danielsiders··on Flynn: first preview release
Flynn definitely isn't "ready" yet. This is a preview release, production grade stability is still a few months away.

I haven't looked closely at Deis in several months, but Flynn doesn't use Chef (or anything similar) anywhere and don't plan to.

danielsiders··on Flynn: first preview release
Flynn is designed to run on any modern Linux kernel. We haven't tested CoreOS yet, but once we put out a few fires we'll explore more fully.

You can add any route to any app in Flynn, so different subdomains, domains, and TCP ports are pretty easy.

danielsiders··on Flynn: first preview release
Right now Flynn Layer 0 is very immature compared to Mesos, but yes they're trying to solve similar problems. After Flynn reaches production stability and builds out more features, we expect Layer 0 to be a valid (and much lighter weight) alternative to Mesos that we hope will be a superior solution for a broad class of users.

I feel like the projects have very different prospective user bases and communities (Mesos is an Apache project, hundreds of thousands of lines of C++; Flynn Layer 0 is run by a startup and only a few thousand lines of Go) and will likely develop in very different directions to service those communities.

That being said, we've explored creating a version of Flynn layer 1 components that run on Mesos instead of Flynn Layer 0 for users who are already deeply invested in the Mesos ecosystem.

danielsiders··on Flynn: first preview release
Cupcake (Apollic Software) has been the company behind Flynn (and Tent) since day 0 (we tend to downplay the branding because we think both projects can stand on their own).

Most of the development on Flynn (nearly all of the 2014 work) was done by Jonathan Rudenberg (@titanous), one of the founders of Cupcake. We brought in Jeff as a contractor and paid him out of the crowdfunding campaign. He contributed to the initial architecture and prototypes but stepped back in December.

I don't want to speak for Jeff (@progrium) but my understanding is that he'll keep evangelizing the project at conferences and may be working on a proprietary version/components at Digital Ocean.

The Cupcake team (especially Jonathan) will keep developing Flynn (of course with open source contributions) full time in the future.

danielsiders··on Flynn: first preview release
Built-in database appliances are a big part of what Flynn will offer in the next few months (right now it's only Postgres).
danielsiders··on Flynn: first preview release
Running it on your own server: We're currently only providing step by step instructions for vagrant, but you should be able to use the script in the vagrant file on your own host with some modifications on your own hardware. Happy to help in IRC (#flynn on freenode)

Flynn Dashboard: At least some part of this will end up as open source in the not distant future, we're trying to figure out the best strategy for additional tools like the dashboard and what parts should be packaged.

danielsiders··on Flynn: first preview release
We actually did a crowdfunding campaign[1] last summer to pay for the development time.

[1] https://news.ycombinator.com/item?id=6058662

danielsiders··on Flynn: first preview release
Thanks! Let us know if you have any questions!
danielsiders··on Japanese railway operator to license maglev tech to US for free
Or even the Taiheiyo belt in Japan https://en.wikipedia.org/wiki/Taiheiy%C5%8D_Belt
danielsiders··on Cover is joining Twitter
Is anyone aware of a standard promise or "contract" startups can sign with their users that says if we close or get bought and the product is shut down we promise we'll open source it within X days under Y license?

This happens so often it would be great to have a standard and clear expectations.

danielsiders··on Coming Soon to Hacker News: Pending Comments
I agree in principle but not in practice.

Social systems can be broken in a way that won't manifest until a certain type of discussion comes up. So while I trust HN/YC to do their best to protect and promote discourse, I don't know that the types of conversation that come up during the evaluation period will be representative of all future conversation on HN

danielsiders··on Amtrak Residency
There are apparently serious strings attached[1]

[1]http://dduane.tumblr.com/post/79161065289/the-amtrak-residen...

danielsiders··on ONO sells for $9.5 billion and nobody cares
People in general don't care about telco acquisitions unless there's a major strategic consequence. The example the author gives “Google buys Spanish Ono for $9.5bn to start Google Fiber throughout Europe” would have huge consequences for everyone from consumers to device manufacturers to content providers throughout Europe. Normal telco consolidation is rarely anything other than the slow march of monopoly.

A 16 year old cable company is barely a startup, and highly unrelatable to the startup community at large. The same story about a US company wouldn't get coverage here unless there was a major strategic element. Kudos to the founders and funders, but it's not a particularly inspirational story for other entrepreneurs. The kinds of companies that get the most coverage here are very young and generally have a global reach. A regional company (which most telcos are) in say New England wouldn't get much coverage in the pacific northwest. This isn't a regional or even a cultural issue, just a significance issue.

danielsiders··on Transitioning Persona to Community Ownership
Mozilla does a great job promoting open web standards and Firefox is the one of the best footholds the community and industry have against hegemony and stagnation online.

However other organizations can and do work towards the same goals. I'm one of the creators of Tent[1] which shares a lot in common with Persona (including some community members) but is more ambitious in many ways.

In the Persona AAR Mozilla identified several reasons for Persona's failure to gain adoption[2] including that Persona " can't offer the same [as Facebook Connect] incentives (access to user data)". Tent's primary purpose is as a user data store and also supports features like address changes automatically (which Persona never did).

We were fans of and friendly with the Persona team, but I believe the best solutions to these problems will come from teams that aren't afraid to think bigger than Mozilla's strategy at the time allowed.

The work of federated identity solutions will continue on Tent and other projects, many of which are probably better suited for a wide variety of users and products than Persona would have been. Of course none of us have (or are likely to gain) the level of institutional (or financial) support that Persona had.

[1] https://tent.io

[2] https://wiki.mozilla.org/Identity/Persona_AAR

danielsiders··on [dead]
This is how many days after the Female Founders conference? I know it's a portfolio company, not a YC corporate decision, but this is really poor message planning.

edit: Valleywag's already got it http://valleywag.gawker.com/startup-flying-dateable-women-to...

← PreviousPage 2 of 7Next →