Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Better GReader (specifically CTRL-ALT-Y) slow since update
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
tizzo  
View profile   Translate to Translated (View Original)
 More options Nov 17 2011, 9:20 am
From: tizzo <ti...@computer.org>
Date: Thu, 17 Nov 2011 06:20:20 -0800 (PST)
Local: Thurs, Nov 17 2011 9:20 am
Subject: Better GReader (specifically CTRL-ALT-Y) slow since update

Since the new Google Reader rolled out, I've noticed that the whole thing
is dog slow in general.  Same thing with GMail.  But the one feature of
Better GReader in particular that I can't live without, the "Mark until
current as read" keyboard shortcut (CTRL-ALT-Y), is particularly hard hit
by this change.

I suspect that it is because the script visits every item that's being
marked read, and doing so causes Google to do stuff (Google+ related I'm
guessing - I noticed that when I try to view an item manually it takes a
second or two before the "+1" button appears) in the background.  The
bottom line is that CTRL-ALT-Y has become a go-get-another-cup-of-coffee
event, and I can only drink so much coffee...

I don't even really have much hope that the developer could do anything to
fix this even if he or she was still monitoring this and was so inclined.  
This is obviously a Google problem.  However Google's official Reader app
for Android has this functionality implemented natively, and the
responsiveness is such that it's clear to me that not every item is being
visited - so maybe there's some way to do it.  Interesting that they have
not implemented the same feature directly in the web app - but that's
another discussion.

Anyhow, this is 10% bug report (or more accurately, enhancement request),
and 90% rant.  I'll wrap it up before that ratio gets any more out of
balance.  Anything that could be done would be appreciated.  Thanks.

Tony


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.