Items not staying marked as read

  • 95
  • Problem
  • Updated 6 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


  • 3 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 95
Photo of Cody Williams

Cody Williams

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

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 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


  • 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


  • 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.