Re: [pinboard-dev] read later bookmarklet doesn't mark existing bookmarks as unread

[sheila miguez]

If the functionality changes, consider retweets and favorites. I am not sure I'd like an automatic bookmark to overwrite a manual one.

On Fri, May 24, 2013 at 4:45 AM, <isz...@o2.pl> wrote:

Read later bookmarklet does nothing for a site that's already bookmarked. I think it should mark existing bookmark as unread. Of course, all existing tags should be kept. Also, one should be able to choose whether read later keeps original date or updates it.

cheers ;)

--
You received this message because you are subscribed to the Google Groups "Pinboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pinboard-dev...@googlegroups.com.
To post to this group, send email to pinboa...@googlegroups.com.
Visit this group at http://groups.google.com/group/pinboard-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
sheila

[maciej]

The current behavior is the intended behavior. I want people to feel
safe clicking 'read later' on stuff they're not sure whether they've
bookmarked, knowing that it will be a no-op if the bookmark exists.

[junkyar...@yepmail.net]

But... what if "feel safe" means, for someone, "feeling confident that this bookmark will be put in front of them again the next time they look at their unread list"? If the function of "read later" is mnemonic, then it seems like marking an existing bookmark as unread is a reasonable and safe behavior.

[Dan Loewenherz]

In what situation would you have marked a bookmark as read when you didn't in fact read it?

[maciej]

I think you can make a good case for either behavior. But you have to
pick one, and I picked the one I happen to prefer.

[junkyar...@yepmail.net]

On 2013-06-04 d...@dlo.me wrote:
> In what situation would you have marked a bookmark as read when you didn't
> in fact read it?

If, say, you have bookmarks saved that are for reference on a subject that, at various times, you need to refer to, and during one of those times wish to bring it back to the forefront of your attention. I'm not claiming this is the "correct" way to do things, and don't feel too strongly about how saving an existing bookmark as "read later" should behave. Just pointing out that for some use cases, it could be awkward if the user is unaware that it's a no-op. In particular, for the absent-minded among us who use "read later" to remind themselves to take another look at something. :)

[Adrian Howard]

On 4 June 2013 22:30, maciej <mcegl...@gmail.com> wrote:

The current behavior is the intended behavior.  I want people to feel
safe clicking 'read later' on stuff they're not sure whether they've
bookmarked, knowing that it will be a no-op if the bookmark exists.

 

Ah. This explains some confusing things that have happened to me in the past with read later.

(My use case - content changes on bookmarked site so I hit "read later" expecting it to re-mark it. Later on when I realise I never re-read it I thought I'd made a mistake with the book marking...)

This behaviour + the auto-private behaviour of "read later" could be usefully make clearer in the docs I think...

Adrian

--

adr...@quietstars.com / +44 (0)7752 419080 / @adrianh / quietstars.com

http://bit.ly/Effective_Customer_Interviewing_Workshop-7pm-June_6-London