username: indyweek
digest id: S15L3EJZ6T
site feed is on: http://www.indyweek.com/gyrobase/index (bottom left)
the feed for our scan blog doesn't seem to be updating. there's been 3+ posts since the one currently showing on the above site. (the post i'm seeing on the above site is titled "'60s Garage Legends The Night Riders on WXDU Sunday Night" but the most recent post on the blog -- http://www.indyweekblogs.com/scan/ -- is titled "Thou anointeth my head with oil!")
thanks!
Look at the feed:
http://www.indyweekblogs.com/scan/feed/
Even though the site has new entries, the feed that site is putting out does not, so Feed Digest is just copying that.
I am having the same problem with one of my feeds. Digest ID is FXHRGXNYBQ. It is going on 2 hours since the last update and I have confirmed that the source feed (http://del.icio.us/dlmsite/earlier) is in fact updated. The digest just isn't for some reason.
it just updated. Is there any way to speed it up at all. It took about 4 hours.
That feed is on a 2 hour (default), has now been reduced to 1.
Thanks Peter. That Digest (FXHRGXNYBQ) as well as RUOSOXUEBT play a pretty large role on my site. Is there anything we can do to get each of them under an hour or is that the lowest setting?
My feed (C38RTKFB7B) from Google News sometimes takes two weeks to update even though I see there are sometimes 30-40 updates on it in IE. Do I need to do something?
oggie: Bear in mind that digest updates depend on digests being accessed. So if you access a digest VERY rarely, it will only be updated AFTER those requests. This is a big problem on test sites or extremely underused digests, and may be relevant info to you.
fdw2006: The problem with going under an hour is that it's against the generally accepted netiquette and could lead to being blocked (either automatically or manually by site owners). So Feed Digest only tends to turn it lower if it's from an unimportant site (that few users are using), and not a major site whose blockage would inconvenience everyone.
got it, thanks Peter. An hour will be fine then.
Peter - any idea why FXHRGXNYBQ as well as RUOSOXUEBT would not have updated? It's been at least 7 hours at this point from what I can tell.
Are they frequently requested? And/or are the source feeds updated? I say 'source feeds' specifically because some sites, such as del.icio.us, often have lag times between their Web renderings and feed renderings. del.icio.us were once over 24 hours behind!
The source feed is updated 2x per day. Whenever I notice the digest not updated, I visit the delicious feed directly and so far, it always has been so that led me to belief FD is not updating.
Bear in mind that FD could still well be 1 - 2 hours behind del.icio.us in any case. If you look at the del.icio.us feed and it has something and you access the digest at that time, but then FD doesn't have it two hours later, then there's possibly an issue.
I'm having the same problem with my feed (RNFWGHEP47). It's been well over 3 hours since the source delicious feeds have been updated. I've noticed that updates have slowed way down the last several days. Can I get the updates on my feed cranked up to hourly?
Peter - I am seeing FD at least 7 hours behind delicious. It could be more but it's certainly not less than that on my 2 digests.
Any idea why any of my two feeds are not updating at all? FUK8KPNTXO and JB1TCK9YEV
We are ready to use the service and upgrade when available, but cannot get a reliable performance. 1hour update will be fine. How could we get that?!?!
Thanks!
I'll try again, for the last time before moving on somewhere else...
Is anybody reading this?
thx
Mic check. Is this thing on? It's been a week and I'm still having the same slow updates on my feeds. Can I please get RNFWGHEP47 on the one-hour update schedule?
I'm afraid this is over....
Peter posted this a while back on Yahoo and Google news searches...
===try putting .nyud.net:8090 after the hostname. For example.. URL as you've got it, but news.search.yahoo.com.nyud.net:8090 instead of just news.search.yahoo.com.===
You must log in to post.