tag:blogger.com,1999:blog-2139369089307571102011-04-21T19:14:49.941-07:00Flenserhttp://www.blogger.com/profile/02832729379722634503noreply@blogger.comBlogger21100tag:blogger.com,1999:blog-213936908930757110.post-24000238589193432812009-05-13T11:01:00.000-07:002009-05-13T13:31:56.835-07:00<div>I just noticed today that Bloglines Classic has a new search and select feature:</div><div><br /></div><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_kSOZFSqGsEA/SgsqfK4hMBI/AAAAAAAAAFI/f79WCrdyXec/s1600-h/Select+%26+Search.png"><img style="cursor:pointer; cursor:hand;width: 320px; height: 270px;" src="http://3.bp.blogspot.com/_kSOZFSqGsEA/SgsqfK4hMBI/AAAAAAAAAFI/f79WCrdyXec/s320/Select+%26+Search.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5335404898536206354" /><br /></a><br /><div>I assume it was added today as I've only noticed one tweet about it so far. Frnnr's Tweet sums up my feelings:<div><br /></div><div><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_kSOZFSqGsEA/SgsqfK4hMBI/AAAAAAAAAFI/f79WCrdyXec/s1600-h/Select+%26+Search.png"></a><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_kSOZFSqGsEA/SgsqfCnii9I/AAAAAAAAAFQ/qpd_zR0hjZo/s1600-h/Select+%26+Search-tweet.png"><img src="http://4.bp.blogspot.com/_kSOZFSqGsEA/SgsqfCnii9I/AAAAAAAAAFQ/qpd_zR0hjZo/s320/Select+%26+Search-tweet.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5335404896317508562" style="cursor: pointer; width: 320px; height: 154px; " /></a><br /><div><br /></div><div>I've never liked the similar feature on the NY Times website. For those of us that select as we read to mark our place it's a distraction. Still, since I use the Beta interface it doesn't concern me much, although it's easy enough to block.</div><div><br /></div><div>I suppose this is a good sign, in that it shows that Ask.com are still trying to monitize Bloglines by sending traffic to their search business. However I wish they'd found something that didn't have the potential to alienate their users.</div></div></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/213936908930757110-2400023858919343281?l=bloglines-beta.blogspot.com' alt='' /></div>Flenserhttp://www.blogger.com/profile/02832729379722634503noreply@blogger.com0tag:blogger.com,1999:blog-213936908930757110.post-77801248497616667882009-02-09T14:12:00.000-08:002009-02-09T14:17:13.383-08:00I noticed the other night that setting a feed to ignore updated items was not remembered when I reloaded the page. However, there's an easy workaround:<br /><ol> <li>Edit the Feed</li> <li>Change Updated Items setting to "Ignore"</li> <li>Click Update button</li> <li>Edit the Feed</li> <li>Change Updated Items setting to "Display as New"</li> <li>Click Update button<br /> </li> </ol>It appears that the messages are being interpreted incorrectly by the server. So the first update, the server thinks you're setting it to Display as New, and the second update, it actually sets the feed to Ignore.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/213936908930757110-7780124849761666788?l=bloglines-beta.blogspot.com' alt='' /></div>Flenserhttp://www.blogger.com/profile/02832729379722634503noreply@blogger.com0