Great - until that one gets acquired or acqui-hired by Facebook|MS|Google...
I wish there were some open source resource sharing protocol a bit more high-level than HTTP.
I wish there were some open source resource sharing protocol a bit more high-level than HTTP.
You can migrate your data to another server and change your entity (global user identifier) as part of the protocol, so there's no messy "please update your address books" (that part happens automatically.
Data is stored as posts and post types are developer extensible (posts are JSON and binary attachments), so if your favorite app is discontinued, another developer can make a great app that interacts with the same post types.
We're working on a Tent app that imports Posterous posts right now.
Vigilance is going to be required whichever solution you choose, but having said that, a properly set up, locked down server based on a stable server-oriented OS distro, is going to require very little maintenance, if you subscribe to the old ways. Don't fix it if it isn't broken, and keep installed software to the absolute bare minimum required. Analyze upgrades to see if they're actually necessary (the answer is usually "no"). Pick your blog software carefully, from projects with proven track records for stability and security, and apply the same practices of keeping modules and add-ons down to the bare minimum, and you'll find there really is not much you have to keep up with.
Self-hosting is great and I don't think we'll ever replace it. But for the vast majority of personal content out there, you want a caretaker. I hope you'll think of us when you do.
And you absolutely do have to hope.
Until then, that pledge is just words which can be rescinded any given time.
To be very clear: I am not insinuating you would break your pledge, but as a user, I'd be unwise to trust a non-binding statement on a web page.
Our pledge to you...
We'll never be acquired.
We'll always keep your URL's online.
We'll always keep it the best place to post.
I've talked to Garry and Brett about Post Haven and they are genuinely committed to making this work as they pledge on the website.
Just look at the examples.
WebFaction works just fine for me and so does Jekyll.
- Open source the code
- Allow users to supply their own domain
- An API (not "coming soon...")
If all those are in place then great :)
[edit] Looks like the site doesn't support any of the 3 - facepalm
Brett and I have discussed #1 and it's an option we want to keep on the table. First priority is to build and create a great hosted experience, however.
By custom domains I mean user supplied top level domains. Definitely have a read on how we view URL permanence [1]. I wish more sites thought about it and glad you already are.
[1] http://blog.theopenphotoproject.org/post/10537443380/namespa...
>And they charge $5 per month, so >the sustainability is more clear.
In 1996, Geocities began offering a deal: pay $4.95 a month and no ads will be shown on your site, and you get to use your own domain for your website. I signed up immediately. 3 year later, Geocities was acquired by Yahoo. 10 years later, Geocities was closed:
http://geocities.yahoo.com/index.php
There is nothing really permanent about any of these services. Ma Bell may have offered a reliable phone service for almost 100 years, but in the era of the Internet the half-life of consumer sites tends to be much shorter.
There are many others besides that did stuff like this so check out the archive team, archive.org and so on.