anotherjesse

Not only do they not provide enough information, the information they do provide is contradictory...

The homepage says:

    We believe our customers should use Cherry 100% 
    worry-free. So, we’re introducing the Cherry Guarantee:

    Accidents happen. But when you use Cherry, we’re
    accountable for those accidents, not you. We cover 
    any scratch or ding and replace anything broken in 
    or stolen from your car.

But the terms say:

    THE COMPANY OFFERS INFORMATION AND A METHOD TO OBTAIN 
    SUCH THIRD PARTY CARWASH SERVICES, BUT DOES NOT AND 
    DOES NOT INTEND TO PROVIDE CARWASH SERVICES OR ACT 
    IN ANY WAY AS A CARWASH PROVIDER, AND HAS NO 
    RESPONSIBILITY OR LIABILITY FOR ANY CARWASH 
    SERVICES PROVIDED TO YOU BY SUCH THIRD PARTIES.

I was just thinking of inviting jeff to give this talk at a openstack hacking event and I see slide 10 he references us :)

it is still around. just using it today to prototype webhooks with openstack

I use this method - except I use a fork called nvalt - http://brettterpstra.com/project/nvalt/ - since text files via dropbox & simplenote. The fork has better markdown support (and a few other things I forget)

I map (cmd)(enter) as the global hotkey to bring nvalt to the foreground.

No proprietary code. 100% open source

It is very easy to fat finger the "flag" link as a user when browsing from a phone.

Any thoughts on a mobile skin to HN that removes flag?

Any thoughts / recommendations on pushing small projects to app store?

I have a few I was debating pushing but I don't know if the time/learning cost is worth it for fun projects vs a download link on a webpage

Sadly this is common for twitter to do without contracting the party.

For over a year I ran a bot called @amazon which when messaged would look up the price of a book using the amazon api and respond to the user.

When amazon decided to join twitter, they contacted twitter who simply deleted my account and gave it to them without contacting me. After contacting amazon as I would have gladly given them the bot, they informed me they didn't ask for it to be deleted but to contact me.

At the time twitter made some excuse about how it is against their TOS to give my email to another party (yet acceptable to delete with even contacting me)...

Seems like things haven't changed at le twit

Congrats!

Please don't stop blogging your technical deep dives! Your passion is an inspiration.

Source and docs at https://github.com/ha/doozerd and https://github.com/ha/doozer

By policing and issuing a dmca notice dropbox seems to be risking their status from "carrier/hoster"?

IANAL but the dmca provides hosting sites protection against users who infringe. By actively checking for infringement of users having dropship could they be openning themselves to legal complications if they lose "hoster" status?

Understandable except the assertion of filing a dmca because he thinks that the reposts of code are "geek rage". The DMCA provides that you may be liable for damages (including costs and attorneys fees) if you falsely claim that an item is infringing your copyrights.

Using this powerful law as a scare tactic isn't acceptable. If you wish to claim that the code was infact infringing, then the conversation is different.

This seems to be:

* illegal use of dmca by dropbox * dropbox says dropship using reverse engineered sync protocol broke anti-circumvention techniques or contains their copyright

Either of which are bold statments

It was fun working on flock. I still work with many of the guys I met there.

"Wanted to destroy something beautiful" - http://factoryjoe.com/blog/2005/12/29/wanted-to-destroy-some...

Why I joined Rackspace: to make OpenStack awesome!

The folks I met at Rackspace share our (Anso Labs) vision of making OpenStack the best cloud platform for themselves and others.

The "marketing" team at Rackspace were the folks who understood the importance of OpenStack and worked to convince the rest of the company to open source their cloud.

Sure there are growing pains. And one could point out technical areas that the community has struggled with (automated testing against real clusters)... The point is that everyone I've talked to from developers to the CEO understand that OpenStack needs to be its own project. We (individually and as a company) are trying to shepherd the project.

Geoffrey went to do safetyweb.com after dancejam.

I have an extra one of these if anyone would like it. email me (info in profile).

One of our guys wrote http://github.com/termie/git-bzr-ng to try to make it easier to work with OpenStack from git/github. There are mirrors at http://github.com/openstack

the "sponsors" is buysellads.com - which brings in ~400 a month. That said it used to make $100+ a day on adsense but I didn't like the ads. (funnily after I removed adsense google offered their custom packages/...)

I'm purposely minimizing revenue since:

1) if the site made money those who don't like what greasemonkey does might seek damages for the money 2) it sends the wrong message to the community if I'm just making money and not giving it the attention it needs

Before Nebula I had planned to work on userscripts and make it pay for itself and my time. I tried to spend some time on it each day, but working on Nebula is really 2 jobs - working for NASA (the client) and working on my company (ansolabs) - and I rarely get any time for the company, let alone my non-nebula open source work.

Status quo would take an hour or so once I have procedures in place for how to deal with DMCA issues. But I think it needs a lot of community features (moderation, groups, directories of good scripts, ...)

The technologist in me loved being able to write and deploy software accessed by over a hundred of thousands users a day.

I've learned so much about running a (relatively) large website from userscripts.

I used to have time to watch munin, new relic, ... every day - it has been a month since I've checked http://munin.userscripts.org :(

I don't really want to get rid of it, but my life is too hectic to give it the time it needs. The site went down for half a day last week due to a DMCA takedown request that occurred while I was traveling for work. It needs someone who can pay attention.

Maybe I can find a product / hacker / designer who can run it with me - but I don't want to make myself the bottleneck, so if someone comes around who can do a better job, I should probably step down :(

We already host usaspending.gov and a few other sites for non-NASA users - but our focus is on NASA scientists, researchers and engineers.

That said our work is open source, so others inside and out of government can adopt our work. For instance Rackspace has started OpenStack and it adopted Nova (our python powered compute framework).

"I am a little shocked that you're ready to turn it over to someone else."

I am very conflicted about it. I have spent thousands of hours developing and operating it - but I don't even have time to sleep right now with the work going into Nebula/Nova.

I don't want to turn it over to someone who would destroy the community. Any transition would require them understanding the community and a solid plan for how to improve it.

looking forward to the combined efforts.

we really want to make the cloud that hacker news users would want to deploy on their own infrastructure.

I recently started consulting for us govt. Such an odd world. Things like #2 are illegal.

Does anyone know why apple only included 256MB memory?

The lack of ram means that in-memory cache for the browser is limited (to zero?), which limits performance.

The cost of ram seems so small (a few dollars per GB in bulk) to a software developer - is the cost energy consumption or ???

This is REALLY useful when you are bundling AMI images.

When we changed NASA Nebula from XEN to KVM we had to tweak a few files in every image, this sped up the conversion by minutes per image.

I thought the coverage was pretty weak. Not due to unicorn but because there are many options (including passenger (aka mod_rails) for apache) that allow queueing to occur at the proxy instead of at the individual workers.

I wish they had discussed why unicorn instead of mongrel and why didn't solutions like haproxy or passenger or ... didn't work?

This discussion was: our apache configuration didn't work so we switched the load proxy mechanics and our app server at the same time.

I've had great success with mongrels with HAProxy (with maxconns=1 so only 1 request per mongrel at a time) for years. I've also had great success at Passenger with apache.

I think it is a great step forward for twitter's servers, I just wish the article had some meat. Isn't this the twitter engineer blog, not blog for the general audience about how twitter works?

Ha! Funny as always.

Too bad there is no way of verifying you are really lloyd.

Seems like we could come up with something - even if it only works for techies.

What I find surprising is how unpolished it is.

UI Redraw is slow, small feature set, UI is very crude.

The triangle of: scope, quality, time to release - it seems like this app went with: none of them.

Anyone have this frame?

It looks like a good solution

I also wildcard *.localhacks.com to 127.0.0.1