Handling iFrame busters? By using iFrame buster busters, of course!
When I detect an iframe buster, I prevent it from doing its job, but instead of continuing to show the original site, I switch over to the feed view. It complies with the wishes of the parent site, and I don't look like a bozo with such a glaring and awful bug. The feed view is still a great view. (It's the Google Reader view.)
That's awesome. That's perfect tradeoff between the wishes of the parent website and convenience for your users.
I'm assuming you fetch feeds using a queue.
* How do you add jobs to the queue ? Do you run a cron every n minutes to check which feeds need fetching and add them to queue ?
* When you add jobs do you check to see if a previous job for fetching the queue is still in the queue or do you use flags to mark feeds for which the jobs are in queue and eliminate duplicate jobs that way ?
Yes, I use celery/rabbitmq as a queue. But I don't bother checking for duplicates. If the feed is still in the queue by the time it comes back around for processing again, I let it run. That means that the queue is behind enough that it will even out in the wash.
For what it's worth, it's "diggbar"-style garbage that I added that to thwart, and as much as I like your interface, I'm going to be leaving the iframe-buster in place.
Edit: it looks like A List Apart's feed also breaks, likely for a similar reason.
And I'll have to admit, the more I'm using this, the more I'm liking it.
Comments
Handling iFrame busters? By using iFrame buster busters, of course!
When I detect an iframe buster, I prevent it from doing its job, but instead of continuing to show the original site, I switch over to the feed view. It complies with the wishes of the parent site, and I don't look like a bozo with such a glaring and awful bug. The feed view is still a great view. (It's the Google Reader view.)
That's awesome. That's perfect tradeoff between the wishes of the parent website and convenience for your users.
I'm assuming you fetch feeds using a queue.
* How do you add jobs to the queue ? Do you run a cron every n minutes to check which feeds need fetching and add them to queue ?
* When you add jobs do you check to see if a previous job for fetching the queue is still in the queue or do you use flags to mark feeds for which the jobs are in queue and eliminate duplicate jobs that way ?
Yes, I use celery/rabbitmq as a queue. But I don't bother checking for duplicates. If the feed is still in the queue by the time it comes back around for processing again, I let it run. That means that the queue is behind enough that it will even out in the wash.
Just an FYI: my blog (see profile) seems to have busted your iframe. :) The code I'm using (not included in <head>):
if(top.location!=self.location)top.location.replace(self.location);
For what it's worth, it's "diggbar"-style garbage that I added that to thwart, and as much as I like your interface, I'm going to be leaving the iframe-buster in place.
Edit: it looks like A List Apart's feed also breaks, likely for a similar reason.
And I'll have to admit, the more I'm using this, the more I'm liking it.
So far so good. But when I click on a story there, it loads up that story -- and blows away NewsBlur. I can navigate back, but now I've lost my place.
In such cases, maybe you could doctor the links so that they'll open in a separate tab?
I'll make that a preference in the next couple weeks. That feature has been requested more times than I can count.