rykov

Gemfury supports Python, so OK for now.

Michael from Gemfury here. We've been using Golang for a couple of years with a dependency manager that we've built internally and will shortly release to the public. If you'd like to try it, check it out here: https://melody.sh/docs

Rather than creating new methods for a class, YAML.load can be used to call one of a few specific methods ([]=, init_with, or yaml_initialize) for the specified class. This exploit found a class where string arguments to the []= method are inserted into an eval() block, thus becoming code.

A few more details here: http://blog.gemfury.com/post/42259456238/rubygems-vulnerabil...

Gemfury also supports private Python packages

For a long time Amazon fulfilled only their own products (and some large partners) from their warehouses. Now, it's offered to everyone as Fulfillment by Amazon service. No doubt Amazon will offer the locker service, if the market is there.

http://answers.google.com/answers/threadview/id/758002.html#...

It offers all the advantages of a cloud service - on demand, pay as you go, no maintenance. Very similar to Artifactory Online (cloud version)

Every language has a separate way of doing packages, explaining the individual benefit based on your preference is a more clear message to get across. The other benefit is it helps us choose where to focus.

And, funny story: the word "weapon" is A/B tested with the word "repository" because I had the same doubts. Guess which one converts better? Hint: It's not "repository"

That's because we started the site before Bootstrap was released, but as we iterated, we ported much of the site over.

And you're spot-on about Gemfury's purpose

I cringe too, but the reason it's used is because it works - great way to explain something new based on something you already know in a few words.

Thank you and Twitter - Bootstrap makes things so much easier.

The service currently services RubyGems customers from the root domain. We figured Hacker News is a wider audience than just Ruby and would be of great help to decide which direction we should go next.

Sorry for the confusion - we figured it'd be easier to explain the service for each individual platform separately, rather than all at once. Hence the up-front selection.

Dropbox stores files in the cloud which are then easily accessible by authorized computers - Gemfury does that for code packages.

Great idea. Thanks for the suggestion

Thank you for the "more info" suggestion. Which language and package repository are you interested in?

Maybe one day :)

Not sure what you mean about packaging process. Are you talking about combining "gem build" and "fury push" into one command?

As far as pricing, unlike Github, our $9 pricing is for unlimited Gems. Can you suggest a plan that would work for you (# of Gems, collaborators, price, etc)?

Thanks for your help with beta testing the service. Glad you're not letting this little bit of fun affect your opinion.

Thanks for the support. Judging by other comments, the pitchforks are never fully put away on literal-net :)

Thank you. It beats writing a dry "Introducing Gemfury" blog post.

Thank you for the suggestion. We've fixed the "See Plans and Pricing" link to give a more appropriate response.

Thank you. This has been a lot of fun. It took about 2 hours from inception to the first iteration. You're right, I was worried that Curebit will capitulate before we're done and would take much humor out of it. Luckily, it still did pretty well with the crowd, even though we published this after their apology.

http://www.gemfury.com for hosting private Ruby Gems. I wanted a unified way to deploy software for another project and decided to use gems. First built it for myself, then figured it would benefit others.

GetGlue apparently stores much of their data in SDB. CEO (Alex Iskold) talked about it in TWiST #78: http://thisweekin.com/thisweekin-startups/this-week-in-start...

Netflix is also migrating to SimpleDB from Oracle: http://highscalability.com/blog/2010/10/22/paper-netflixs-tr...

Pros/cons to consider in a few contexts:

* Custom domains - if you ever want to allow custom domains (ala Tumblr, Posterous, etc), it's probably easier to go w/ subdomains. The URL recognition will be much easier.

* Security - if you ever want to allow custom HTML/Javascript, I would say that custom domains are a must for security reasons. However, passing login credentials across multiple domains might be trickier than using a single domain.

* SEO - I'm not completely sure, but very curious to know. Can someone chime in on SEO tradeoffs of these two options?

If you want to skip the drawn out intro, Jeff's speech starts around 6:00 mark

"..failed enhancement of a new approach to timeline caching"

I hope this is not a testament to scalability of Cassandra or Redis.

Ref: http://engineering.twitter.com/2010/02/link-cassandra-at-twi... http://github.com/twitter/haplocheirus

The speed and subtlety of nose-picking is also fantastic (at 0:09 mark)

From the beginning, I thought Brian's and Gizmodo's best defense would be to say "We collaborated to try to find the owner through a large platform." How well that will work with "$5k for exclusive access" is questionable.