Friday, March 20, 2009

Bookmarking Dilemmas...

I've been waiting for more comments on the previous posts before I made any more decision just to get some feedback. Got some good comments from Liz (many thanks again).

Some important things of note:

How many different layers of privacy should there be? It makes sense to have personal bookmarks, group bookmarks, and public bookmarks. personal bookmarks are pretty straightforward, and the current sketch of the interface will support that just fine. The group bookmarks are somewhat trickier. I think that if a user selects that, a new selection box or check-boxes should appear of the groups/projects they belong to. Then they can select which project can see that bookmark. Otherwise the public bookmark will be seen by everyone.

How public should public bookmarks be? could unauthenticated users view them? or should that be a separate level altogether? I think that all public bookmarks should be available to everyone, even unauthenticated users. However, they should not be allowed to comment or edit the bookmark. This is similar to a bulletin board where people can see posts, but not reply unless they're logged in.

Speaking of comments, I will be adding more sketches of what the "Bookmarks" page should look like with comments. I think that if we are going the route of giving users updates upon log in, then any new bookmarks that they can view (but not necessarily edit) should also appear in that list. Also, authenticated users should be allowed to comment on any bookmark they can view and only the person who posted the bookmark should be allowed to change it (i.e. if the link was incorrect or note was wrong, then only the creator could go and change that). Again, unauthenticated users could view public bookmarks, but not comment or edit them.

I'm also thinking of changing the "New Bookmark" button to just a text field where users can just type in a site url and hit enter. That would make it much easier to do, but then we get into privacy setting issues. Should the default be private for the user or public? I think in that case, the default should be private to the user, so that they can create bookmarks fairly quickly and if they decide to share it, then they can go through the extra steps to do so. In that case, should the text field be inside or outside the tabs? If we put it inside the tabs, then the default would be context sensitive depending on where it is. if we put it outside, then the default would be private for the user.

I think I need comments on that. There are so many options. Much sketch and show everyone!


Liz said...

Do you anticipate people wanting to save a lot of private bookmarks? If not, I think the default should be public. I don't think people will be saving many things that they would have strong privacy concerns about - but I'm not sure, have you asked people how they might use something like this?

pongers said...

That is a good point. I will ask around. Thanks!

Maia Bittner said...

Interesting questions. You seem to have a good sense of what a good bookmarking service would need to have. Do you mind checking out Archivd for me? I'd really appreciate any thoughts you have on the service. Thanks!

Fox Directory said...

I think there seems to be a flood of private bookmarks in the run up to the election.