http://benjamingolub.disqus.com/enTue, 13 May 2008 22:23:27 -0000http://benjamingolub.com/2008/05/13/ophthalmologists-and-divers-love-rssmeme/#comment-460051<p>Paging works fine for me: <a href="http://www.rssmeme.com/api/?output=atom&amp;order_by=-feed_count&amp;page=1" rel="nofollow noopener" target="_blank" title="http://www.rssmeme.com/api/?output=atom&amp;order_by=-feed_count&amp;page=1">http://www.rssmeme.com/api/...</a> compared to <a href="http://www.rssmeme.com/api/?output=atom&amp;order_by=-feed_count&amp;page=2" rel="nofollow noopener" target="_blank" title="http://www.rssmeme.com/api/?output=atom&amp;order_by=-feed_count&amp;page=2">http://www.rssmeme.com/api/...</a>.</p><p>As far as HTML output; no the "next page" links don't reflect your API filters. The API is mainly meant to be used for JSON/ATOM generation and not HTML.</p>Benjamin GolubTue, 13 May 2008 22:23:27 -0000http://benjamingolub.com/2008/05/13/ophthalmologists-and-divers-love-rssmeme/#comment-459701<p>Just a small FYI, I've been playing with the page= part of the API and it doesn't seem to work. No matter what I tell it I just get the first page. On a related note, for the HTML output, the 'next page' links all loose the other values (i.e. to cut and paste from above /api/?output=html&amp;feeds_gte=3&amp;search=ophthalmologist the page 2 link will just be /api/?page=2</p>Sam GrovesTue, 13 May 2008 21:13:22 -0000