FoF 0.1.9 is debugged
Feed on Feeds 0.1.9: That problem is fixed, this stuff is included. <stevejobs>Oh, by the way… this release is also about 10 times faster.</stevejobs>
See, I’m just now figuring out this whole “database index” thing. If you’re upgrading from a previous version, re-run the installer (install.php). It will add some indexes to the items table that really should have been there from the beginning. If you’ve already created indexes yourself, and run the installer, it may create duplicate indexes. Would that be bad? Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light. Or if that is too scary you could just go in with phpMyAdmin or whatever you used to create your renegade unauthorized indexes in the first place and delete them.
REPLY))
[...] 04
Feed on Feeds 0.1.9
Filed under: inet i_xml — hipslu @ 09:17
Feed on Feeds 0.1.9 ist verfügbar; der bug der durch Magpie 0. [...]
REPLY))
Okay, I’ve got to know… how many of your RSS hits are from FoF installs and how many are from other readers? I don’t know that it relates to FoF at all, but it would be some neat trivia. FWIW, I was using FoF for months before I realized that you even had a blog. I didn’t know until I was looking for an update and realized that you post them here.
REPLY))
I post them here, at sourceforge, and at feedonfeeds.com. I’ll look up that data, I’m interested too, now that you mentioned it.
REPLY))
Wow that’s creepy. I was listening to the Ghostbusters soundtrack on XM the other day and they played the “every molecule in your body exploding at the speed of light” clip.
Nice reference. My hat is off.
Ghostbusters==Best movie ever
Ghostbusters2? Feh….
REPLY))
fof is just great i was waiting for something like this :)
just waiting for categories :)
REPLY))
Phelps: Yes, most of my RSS and Atom hits are from people with FoF. Looking at those logs is funny because I can see that just about every version of FoF I’ve ever released is still in use out there. Even 0.1 is still in use, from two different IPs! The next greatest number of subscribers is from Bloglines. Then NetNewsWire, then NewsFire, then SharpReader, then noise. There’s also lots of hits that come from what look at first glance to be browsers… but it seems that some of them are actually from robots are now announcing themselves as “Mozilla/5.0 (compatible; actually robot blah blah)”.
REPLY))
Mozilla/5.0 (compatible;…
I know that Mozilla and Firefox authenticate as Mozilla 5.0. BTW, Firefox has build-in rss handling…
REPLY))
I just found your script, I think you’re on the right track with it, if you can make it multi-user and also allow users to create their own RSS content streams, you could have a great product! Keep in touch.
REPLY))
I’ll be upgrading soon. Good to see you set up some indices! I was investigating a bunch of slow queries I was seeing, and ended up with the following:
mysql> show index from px_feeds;
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Comment |
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
| px_feeds | 0 | PRIMARY | 1 | id | A | 89 | NULL | NULL | |
| px_feeds | 1 | title_idx | 1 | title | A | 89 | NULL | NULL | |
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
2 rows in set (0.00 sec)
mysql> show index from px_items;
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
| Table | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Comment |
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
| px_items | 0 | PRIMARY | 1 | id | A | 10154 | NULL | NULL | |
| px_items | 1 | link_idx | 1 | link | A | 1692 | 20 | NULL | |
| px_items | 1 | title_idx | 1 | title | A | 10154 | NULL | NULL | |
| px_items | 1 | ts_idx | 1 | timestamp | A | 5077 | NULL | NULL | |
+———-+————+———–+————–+————-+———–+————-+———-+——–+———+
REPLY))
The indexes that really made a difference in my testing were on the ‘feed_id’ and ‘read’ columns in px_feeds. I’ll try adding some of the others you listed, and see if I get even more speedup.
REPLY))
I’m wondering how to actually use the digest auth to read an lj feed?
I try passing http://user:password@www.livejournal.com/users/username/data/atom, but it’s not seeing friends-only posts – although when I go to that url in a browser, I can see the friends-only posts in the feed..
REPLY))
Oh, and, FoF is refusing to parse the RSS feed for comments on this post..
MagpieRSS: Failed to parse RSS file. (not well-formed (invalid token) at line 20, column 33)
:(
(btw, I love FoF, it’s fantastic, lots of thanks.. I hate the fact that the first time I talk to you is when I find a problem)
REPLY))
Actually, when I go to that url in another browser, it doesn’t actually work – it looks like I thought it was working because I was already logged in to livejournal..
So… getting back to my original question.. how do I use the digest auth in FoF, your most wonderful excellent rss aggregator?
REPLY))
Zhasper: The feed URL I use to get friends-only posts at an LJ is like this:
http://USER:PASS@www.livejournal.com/users/JOURNAL/data/rss?auth=digest
Maybe your URL will also work if you put ?auth=digest on the end?
And the feed for comments on this post isn’t working because of that screwy pingback from konfabulieren. It has some characters that got mis-encoded somewhere along the way. feedvalidator.org shows the problem.
REPLY))
hi,
as you maybe already know i love feed on feeds, so i’ve developed a small wordpress plugin to use it for a blogroll; you can find it here if you are interested: http://www.konfabulieren.com/wordpress-plugins/
REPLY))
Thanks Steve, that worked :)
I had a fairly large brainfart and had tried using “?authby=digest”, which didn’t work. I’d also read (somewhere, on a page I can’t find any more :( ) that the “?auth=digest” wasn’t needed any more..
So.. it works now. Now I just have 60+feeds that I need to change append “?auth=digest” to. whee!