I've been thinking about graue's criticism of Tent's immutability of posts, and I share his concern. People make mistakes. Imagine storing a nude photo of yourself and by accident making it public. Or sharing a sensitive post with the wrong group of people. Tent's subscription magic would immediately push that post to your subscribers, and there's nothing you can do about it.
Allow servers to be configured with functionality like Gmail's Undo Send feature for non-private posts (per post type), allowing users to undo a post within a specified amount of time. The post would only be pushed to subscribers after time runs out, and not if the user hits undo (in time).
Maybe this is something that's better left to app developers to implement? I'm guessing that would be DJJ's reply. The protocol should be as lean and generic as possible, and this feature would only be useful in some situations. It's not that hard to implement a "delayed posting with undo" feature in your apps either. Email doesn't have this feature, but Gmail implemented it.
Then again, having it included in the protocol would encourage app developers to implement this feature in their apps, and make it even easier to do so.
I'm leaning towards that Tent shouldn't babysit its users on the protocol level. The problem is real though, and I think we as developers should be aware of it. If it's not Tent's, it is our responsability to babysit our users, and help them avoid making dumb mistakes.
Having human interface guidelines for Tent applications wouldn't be a bad idea, with a section on when and how to inform users about possibly making a dumb move.
Educating users on the dangers of posting your personal thoughts and photos online is needed anyway. Facebook would never encourage you to think twice about doing that. With Tent we have the opportunity to do so.