Posterous (YC S08) launches private, password-protected blogs by email
blog.posterous.com
blog.posterous.com
My understanding of how posterous works is to select and implement, cleanly, core functionality in a way that keeps the interface simple. I don't think that posterous out-competes other blog websites (or software) on features.
The general blog semantic of visible/invisible is simple but underpowered: there are a lot of things I want to show to one group of people that would just be noise to another group. This sort of feature lets me segregate my output.
[PS: is it just me, or are there no theme options at all with Posterous?]
and it's a template engine people who aren't computers can actually understand.
Any tips, since you're one of the big Tumblr stylists? (Also, did your Dadaist theme ever get made public or was that a demo?)
Check out http://www.tumblr.com/docs/custom_themes
The only thing that really keeps me from diving in is that my data are owned by someone else. I see I can use it w/ my own domain, which is really cool (http://posterous.com/faq/), but is there any way to import/export data?
My content is precious to me. I don't want to give it to a web startup if I can't get it back.
BUT -- if I post by email, everything I post will be mirrored to my usual email places ...
Leaving only other people's comments on my posts, and submissions to my groups, that I won't be able to archive. (Cue sound of needle scratching across record.)
I can see this might not be a concern for a wide swathe of the potential Posterous user base... but for this prospective user, it matters.
Any plans to implement some data export/migration capabilities, rantfoil?
[edit: maybe there is an option to have other people's comments & posts to my group be forwarded to my email? Don't see it in documentation -- time to make an account & find out if the option is there.]
API's are coming, both for posting and retrieving. It's going to be one of the big tent pole features alongside theming we're excited about in the next few months.
Although there is a difference between exposing API to developers vs. giving users a feature, my "I want to own my data" worries will be greatly assuaged if a good API exists.
There are lots of people in my life who I could give a link and a password to, but who I would not ask to make a LiveJournal account.
Here's an additional use case from my world: I'm in grad school & often want to share data and thoughts with various scientific honchos whose time budgets are very limited.
Now I can cc. a Posterous group called "my advisor might be interested" whenever I send an email. When my advisor gets some downtime, he can check this group out. This lets me communicate in a "non-push" way to him -- I don't clutter his inbox with my email, but I do get to keep him in the loop.
Essentially, this lets me create a "soft" cc. semantic.
I've had this in mind for a while, and made some half-baked efforts to roll my own, but trying out your service will be much easier in the short term.
Keep up the good work!
Though for public blogs, you can autopost from Posterous to your Livejournal.
As for specific friends-only functionality, this is password protected so people without accounts can easily access it.
Best of luck.
Any plans to add webhooks functionality?