I gave Flock another try, and I still find it quite cool, but not ready for prime time.
Its blog editor ate my blog post about the blog editor, which sucks, recursively.
The other features are all a great idea but just don’t work as well as expected. Maybe in another year or two I’ll try it again and it will blow my mind.
[Update: Ive found the post, it's here! When it was edited in Flock, it was saved without a publishing date. I considered it lost, but it was only tucked away on ...January 1st, 1970.]
2 responses so far ↓
1 Evan Hamilton // Apr 24, 2008 at 17:43
Sorry to hear that our blog editor ate your post…we almost never hear reports of that, so I’d be interested in trying to hunt that bug down. What were you doing at the time that it ate your post?
Evan Hamilton
Flock Community Ambassador
evan at flock dot com
2 admin // Apr 28, 2008 at 10:46
Hi Evan,
IIRC, the problems I ran were caused by Flock not knowing how to properly *edit* a post, instead of starting from scratch with the previous content (and no previous metadata) and replacing a previous post. My steps were:
1. Create a new post, set to two categories.
2. Edit a previous post.
3. Save post.
Expected: Flock should remember all the previous’ post settings, like category, comment access, etc. Saving should replace the previous post.
Result: Flock re-asks for post metadata, and ask the user to choose a post to be *replaced*.
4. Choose the previous post from the list control.
Expected: Saving should replace the selected post.
Result: The previous and new posts both disappear.
Leave a Comment