Strangely enough, I don't actually see posts from Flotch in the feed, there are only Scawen's posts so that's fine.
However, I'm using "Feedly Notifier" Firefox extension and I get a notification every time Flotch posts. I'm 100% sure about that, yesterday I got a notification right after he posted this.
I have no idea how these things work but I assume that for the extension to push the notification your website has to trigger it somehow?
Basically, my "scraper" visits the forum, searches for posts by Scawen (as well as Victor and Eric) and adds the content of the posts to a RSS feed.
I wasn't familiar with with Feedly or the Feedly Notifier extension, but after looking at them quickly I gather that it'd work something like this:
The scraper visits the forum and searches for developer posts.
New posts are added to the "original" RSS feed.
In Feedly, you've added the RSS feed as a source, effectively creating a "copy" of the feed.
In Firefox, you've installed Feedly Notifier and logged in with your Feedly account, allowing the extension to monitor Feedly's copy.
So, when a new post is added to the original RSS feed, Feedly adds it to it's own copy, and finally Feedly Notifier displays a notification in Firefox / your desktop.
Since I can't find any posts by Flotch in the original RSS feed (view-source:https://www.liveforspeed.se/lfsdev-rss) or in Feedly (see screenshot) the problem must be with the Feedly Notifier extension -- Though I did not get any notifications from Flotch when setting it up in Firefox.
Since the posts sometimes contain HTML (for example when people are quoting or including links or images) I would not be surprised that certain parsers may interpret the feed incorrectly, but since the feed does in fact validate I can't really think of something I could do differently.
That said, I'll keep the Feedly Notifier extension in Firefox for a while and keep an eye on it.
Edit: Would you too please log in to Feedly and check if any posts by Flotch are showing up there? If not, the problem is most definitely with Feedly Notifier.
Anyway. When I find the time (probably tomorrow) I'll make a little adjustment to the feed to correct a small issue I noticed with Feedly. The item title (as well as the "Visit Website" button that appears when you expand an item) leads nowhere rather than to the post. This happens because Feedly (to me, incorrectly) uses the Feed's <guid> element rather than the <link> element as the reference for the links.
I suspect that this change will cause a large number of duplicate items.
The timing of driftchris posting at the same time Feedly / Feedly Notifier updated is just a coincidence (I can't really make sense of Feedly's update interval).
Again, that's just a coincidence. Neither my feed or Feedly knows when someone posts, so notifications can not be triggered by such an event - The information simply isn't there (unless Feedly has created their own scraper for lfsforum.net and - for some reason - concatenates it with my feed. But that would be some next-level insanity )
That said, once I get around making the fix I mentioned earlier, I'll add an <ttl> element indicating that aggregators such as Feedly should update more regularly.
No, I promise that's not a coincidence because that's like 5th time this happened (that I noticed) and the times always match. Shame I didn't screenshot those, I will from now on
Right now we have a "pending" post by Scawen posted at 18:47. Oops, actually two (another one at 18:51). They have already been added to my feed, but they're not showing up in Feedly yet (the time is 19:01). It'll be interesting to see when they're added to Feedly (I'll see it in the access logs) and when the notification appears.
Note that pressing the refresh button in Feedly won't actually make it refresh the feed. It's just a GUI thing.
Edit: I went ahead and added the <ttl> element. Hopefully it'll make Feedly refresh more regularly.
Feedly just refreshed (after being idle for about 3 hours), and like clockwork the notification(s) appeared in Feedly Notifier. The posts that eclipsed and gu3st created meanwhile did not trigger any notifications.
Also, now that Feedly has refreshed it might have read the ttl setting that I had added since the last visit. if Feedly does in fact adhere to that setting the somewhat arbitrary reresh intervals should be fixed too. We'll see.
Edit: Nope. Looks like Feedly will update whenever it feels like it:
I don't understand any of this man but don't bother with it too much. It's not even a big deal I just initially thought that the feed itself is bugged and clearly it's just a delayed notification. I can live with that. I'm probably the only one using a notifier anyway
Yeah, no. I won't. I stand by my previous conclusion.
Also, I just noticed another Feedly "quirk" It doesn't display post times correctly. Rather than displaying when a post was published (as described in the <pubDate> element), it displays the time the was received (eg: when Feedly refreshed my feed).
Perhaps you've noticed that both entries in your notification appears to have been posted "8 minutes ago" when, in fact, they were posted an hour apart. Perhaps that may add to the confusion.
Edit: For my own piece of mind I'll post each visit by Feedly's "fetcher" bot throughout the day:
It's an active thread with up to 50 posts a day. Sometimes someone will post at the same time Feedly decides to refresh my feed. There's nothing I can do about that.
Thanks for the interest, though. I'm glad people find the feed useful.
It's been done. And as I suspected it did trigger a bunch of "new" items to appear. But not to be worried, it was just a one-off thing to fix the broken links.