Items not staying marked as read

  • 95
  • Problem
  • Updated 5 years ago
This may be a problem related to too many new users, etc, etc, but some of my feeds that are more active than others have had their items marked as un-read many times. For example, I'm currently looking at a feed where the oldest "new" item is from yesterday at 4:39am. I've marked this feed as read MANY times since then, but they keep coming back!
Photo of crazydog115

crazydog115

  • 3 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 95
Photo of Ed Hagopian

Ed Hagopian

  • 1 Post
  • 0 Reply Likes
Same thing happens here. Regardless of reading to the end of a feed, marking the feed as read or the whole folder with multiple feeds as read, some come back with the same amount of unread as when I marked it read.
Photo of tedder42

tedder42

  • 149 Posts
  • 11 Reply Likes
Yeah, this seems to happen. It was really bad during The Announcement, but I still get some repeated unread items at the oldest end of my feed.
Photo of Tara Calishain

Tara Calishain

  • 2 Posts
  • 0 Reply Likes
Is this just related to the scaling issue Newsblur is having? Because it's a pretty severe problem -- I'll see the same story presented as new eight or nine times.
Photo of Cody Williams

Cody Williams

  • 23 Posts
  • 10 Reply Likes
Make sure your using the dev server (until it goes live):

http://dev.newsblur.com/

Much less problems here!

This is a temporary problem due to the sudden influx of Reader refugees.

The sole developer was just as surprised as all of us at Reader's closing, and really has done a fantastic job as a one man team scaling up incredibly quick. I went from getting this problem often on day 1 to very rarely now.

It's likely that the command to the server to mark as read is not received for an item because the server is overloaded. As Newsblur continues to scale this problem will completely disappear.
Photo of Jeremy Cherfas

Jeremy Cherfas

  • 14 Posts
  • 1 Reply Like
Someone on app.net told me that Dev was just a different skin on the front end and that using dev made no difference to speed or other things. I doubt that, myself, but he seemed sure.

Is it a different server with different functionalities?
Photo of lockhead883

lockhead883

  • 2 Posts
  • 0 Reply Likes
It looks like that there differences, normal site uses gunicorn dev site uses nginx. Perhaps this hole thing could be speeded up without the simpsons quotes on every response.
Photo of toekneebullard

toekneebullard

  • 13 Posts
  • 1 Reply Like
I still have this issue on dev though...
Photo of Rob W

Rob W

  • 9 Posts
  • 0 Reply Likes
just to note, i am having this issue on the standard and dev site.. its happening on some, but not all of my feeds
Photo of Alan Isherwood

Alan Isherwood

  • 5 Posts
  • 1 Reply Like
Also having the same problem on the dev site.
Photo of Tara Calishain

Tara Calishain

  • 2 Posts
  • 0 Reply Likes
Thanks Cody, I'll try that. And I agree, I think he's doing an excellent job considering what he's fighting against -- which is why I'll give him both the benefit of the doubt and my money!

I just wanted to make sure that the issue we were talking about was a result of the recent server load problems, and not a "feature" -
Photo of uk

uk

  • 49 Posts
  • 6 Reply Likes
Same problem here, seems to happen a lot on xkcd and Explosm:
http://www.xkcd.com/rss.xml
http://feeds.feedburner.com/Explosm

Both sites showed me the same articles over and over again, especially on the Android app.
Photo of lailoken

lailoken

  • 9 Posts
  • 1 Reply Like
Happened to me as well...

And sometimes it shows those read items as well again... even though I've specified only unread and they display as read... yet they show up.

Perhaps it is because of a item too far back to display, yet keeps the feed "current"?
Photo of tedder42

tedder42

  • 149 Posts
  • 11 Reply Likes
Happening more. "the official google blog" is the latest. Is it more common with the most popular blogs, perhaps?
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
The reason this is happening is because the marking as read times out. Do me a favor and tell me the status code you get when this happens. If it's a 502, then it's timing out. If it's a 500, I can look it up.
Photo of tedder42

tedder42

  • 149 Posts
  • 11 Reply Likes
Just tried, all the /mark_story_as_read posts were 200 codes but it pops up the next time. Here's an example of the post and misc info you might enjoy:

story_id=tag%3Ablogger.com%2C1999%3Ablog-10861780.post-3498969730356539289&feed_id=766

X-server:app23
Photo of George Licursi

George Licursi

  • 3 Posts
  • 0 Reply Likes
Happens to me as well. I just upgraded to premium to get the continuous stream. Eventually it will say newsblur is down right now, try again later, and when I refresh I'm back to where I started or maybe a few less. I've tried manually marking as read and automatic but still same problem.

Great site. Had no idea it was a "labor of love" since it looks so professional, etc. Hope things will get better once the number of new users levels off...
Photo of George Licursi

George Licursi

  • 3 Posts
  • 0 Reply Likes
Also just noticed if I purposely stop, quit my browser and relaunch, it doesn't keep the items marked as read. Gonna go back to google reader and try again in a few days.
Photo of Maulkin

Maulkin

  • 3 Posts
  • 0 Reply Likes
Hia,

I've had a quick look, and I'm getting 200's back from mark_story_as_read, but with response times of 8.03, 9.55, 6.21 11.93 seconds etc.

Response content seems fine too:
{"code": 0, "authenticated": true, "payload": ["http://www.explosm.net/#20130312"], "result": "ok"}

Interestingly, replying the post seems to also return a 200... not sure if that'e meant to happen or not.

Hop ethis helps!
Photo of lockhead883

lockhead883

  • 2 Posts
  • 0 Reply Likes
The Problem is that if you rush through your Headlines and have such "mark_story_as_read" requests that takes too long, it seems that the front-end forgets to post the mark_as_read requests to the server.

Simple test: open up a feed with 10 unread story's and go fast with the next unread button and after that count the amount of post requests. You will be missing a couple of them especially if one of the first needs a very long time to finish.

So the not updated unread count looks like a front-end problem that only occurs if the back-end is not fast enough to handle the request.
Photo of tedder42

tedder42

  • 149 Posts
  • 11 Reply Likes
I don't think this is entirely accurate. I've seen all the requests go through (return successfully), yet if I come back to Newsblur 15 minutes later those stories will be marked as unread.

I'm wondering if it's the /everything collection that is the problem.
Photo of moontear

moontear

  • 13 Posts
  • 1 Reply Like
I have the same problem on different feeds, so it is not the /everything collection. I think lockhead883 hits the nail on its head: The backend simply isn't fast enough to handle all the requests, hence there should be some kind of queue of some sort. Google must handle it in some way as well, never had that problem there that items I read pop back up at a later time.
Photo of Bryn Hughes

Bryn Hughes

  • 8 Posts
  • 1 Reply Like
For me what seems to happen is I eventually get a message saying "Newsblur is down, try again later" on the bottom pane. The last however many stories that were already loaded in the browser don't get marked as read on the backend even though the unread count does decrease on the frontend.
Photo of Buddha Buck

Buddha Buck

  • 5 Posts
  • 0 Reply Likes
My experience (using LifeHacker as an example) is that when I have unread items in the feed, it will show me all items in the feed (read or unread). When I have no unread items, the feed does not show up on my unread feeds list.

However, when a new unread item arrives on LifeHacker, all the unread items come back. They are treated as read (rereading them does not decrease my unread count), and I don't have to reread the read ones to clear out the unread ones.

Feedblur only loads about 10 stories at a time when I look at a feed, so when I go to the LifeHacker feed it insists on loading the scores of already-read stories, in batches of 10, until it gets all the stories read. At which point, the new, unread stories, are at the bottom of the list. I haven't tried Insta-Fetching to get around the batchiness. I'll try that next time LifeHacker (or Ars, xkcd, etc) updates.

If I look at all my unread items, the old items gum up the works horribly. The working solution I have is to go specifically to the feeds with this problem, like LifeHacker, and clear them out first, then look at my unread items. Sometimes, of course, one of them updates while I'm trying to clear out the mess, and I've got to start all over again.

Like Bryn Hughes, the "load 10 stories at a time" bit sometimes times out, with a "Newsblur is down" message (this afternoon, of course, was "Newsblur is in maintenance mode", but that's a different issue). Once that happens, I have to start all over again.
Photo of Thomas Carpenter

Thomas Carpenter

  • 1 Post
  • 0 Reply Likes
I'm having this problem, as well. I have to wade through things that have either been read, or marked as read, many, many times. I tend to scroll through items quickly, so perhaps that's it.

But it's supremely annoying. In the meantime, I'm "untraining" everything until it evens out. I'd rather not have filters gumming up my experience right now.
Photo of Alex

Alex

  • 5 Posts
  • 0 Reply Likes
The problem only arises for me when I view the stories in Oldest order. If I switch to Newest then I just have to push through once and then on the next refresh I only have the latest updates. I prefer to read Oldest first but I'll adapt until a fix comes out.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
This should have eased up by now. If it continues I'll have to implement some sort of queue that re-sends read stories.
Photo of Melinda Johnson

Melinda Johnson

  • 1 Post
  • 0 Reply Likes
I have been having this issue as well, but only on my Android phone app. The old stories keep showing up and then, once I scan through them again to "read" the stories and go back to the main page, my new stories count shows a negative number. It's really irritating...but I also understand you are swamped and I hope things get resolved in the next few weeks or so once you've had a chance to breathe :)
Photo of Alex

Alex

  • 5 Posts
  • 0 Reply Likes
I still have the same issue (right now it's with engadget) on the www and dev sites.
Photo of Alex Lomas

Alex Lomas

  • 3 Posts
  • 0 Reply Likes
Similar problems still right now - engadget items I read from yesterday keep popping up and a feed of 20 items a marked as read (by double-clicking the unread count) still keeps popping up like a zombie.
Photo of jeff

jeff

  • 2 Posts
  • 0 Reply Likes
I just noticed this thread and wanted to contribute my two cents. I am a premium user who has been using only the 'dev' site since I signed up for premium early this week. I also have the issue with items not staying marked as read. Items coming back into the feed list from as old as 4-5 days ago.

I pulled up the dev console as I flipped through a bunch of items fairly quickly (I have mark-as-read set to immediately, but I was seeing the same behavior when I had it set to 1 second)

While most stories were coming back with 200 responses in <500ms, there were outliers:

13:08:59.217] POST https://dev.newsblur.com/reader/mark_... [HTTP/1.1 200 OK 4243ms]

[13:10:59.494] POST https://dev.newsblur.com/reader/mark_... [HTTP/1.1 200 OK 4185ms]

My problem is that I am seeing 200 responses, but still items come back unread even while previously considered read.
Photo of jamuraa

jamuraa

  • 1 Post
  • 0 Reply Likes
I've been having this problem before, during and after the Google Reader-pocalypse announcement. It seems to happen a lot more with feeds that are busier.

I see multiple symptoms:

- In the "All Site Stories" feed, I get lots of unread items, that I have read before. If I go to a particular site which is showing up with old items in the "All Site" feed, I get served the old items, but they are marked as read when looking only at the specific feed.
- Double clicking to mark all stories as read seems to have no effect at all beyond the current page load. My current thorn in my side is The Verge, which is extremely high traffic. I've marked it as all read multiple times, with 200 OK responses from the /mark_all_as_read endpoint, and upon refresh of the page, there are the same stories marked unread again.
- Occasionally a feed which was marked as read comes back from the grave, and all of it's items are unread again. This has happened with XKCD a couple times in the last few days.

I'm willing to help out any way that I can, let me know what information you need from my browser requests, what the server sends back, what I need to do. This reader was something I switched to from Reader before the whole thing because it is better! Let me help out if I can.
Photo of jeff

jeff

  • 2 Posts
  • 0 Reply Likes
For me it's been Ars Technica and Eater National that I've had this issue, mostly. I have tried deleting the feeds from my list, and then re-adding them. So far so good, but it's only been ~60 minutes since I did this.
Photo of Nicholas Piasecki

Nicholas Piasecki

  • 6 Posts
  • 0 Reply Likes
I've been using the "Mark Everything As Read" feature in the gear menu after I'm done reading to prevent the zombies from popping up. It seems to happen the most on the biggies like Ars Technica and Boing Boing. I prefer to read from oldest to newest so am not sure if that sequence is related. Maybe the mark as read request is taking too long, and the feeds refresh before the read request finishes?