I have to say that Feedbin + @sod’s new experimental feeds are an awesome way to read Micro.blog. Brilliant!

Sign-in workaround worked as well. Enjoying it a lot.

@maique 🥰

@MitchW Hopefully I have now fixed the problem, please try again.

@maique With Feedbin, are you experiencing any lag between where the feed is currently at and where your timeline is actually at? If so, by how much? I'm currently at 25 minutes, though it can be an hour+.

@crossingthethreshold Around 20 mins, as far as I can see. I expect a certain delay, I guess. I have no idea how often Feedbin refreshes the feeds, but I don’t think Feedbin it does that every 5 mins. Trying to find that on their help docs.

@maique I'm currently at an hour and counting. Like you, I expect a certain delay. I have been watching it through the weekend, uninstalled on Sunday night and re-installed this morning. Refreshed...just in case, but no ☹️ Maybe this is not the way for me?

@sod Thanks! Will do

@sod @mitchw I subscribed to your feed in Reeder and somehow also got subscribed to the default feeds.

@sod Works great now. Thanks!

@pratik That shouldn't really be able to happen anymore, but let me know which URL you're trying to subscribe to in Reeder and I will troubleshoot from here.

@crossingthethreshold @maique Knowing a bit about how caching works for my experimental feeds might shed some light on the phenomena and inform your decision if Feedbin is for you or not. Caches are shared among us, but to make it easier to reason about, let's pretend that you (or rather your Feedbin account) is the only person in the whole world fetching my experimental feeds… It goes like this:

1. You make a request to the URL https://micro.blog.via.dahlstrand.net/posts/discover.
2. If it's less than two minutes ago since the last request, you will get the cached version of the feed.
3. If more than two minutes have elapsed since the last request, you will still get the cached version of the feed, but my service will also fetch the latest version in the background and update the cache. The next time you make a request, this newly fetched version will be returned.

So, the maximum age of the feed you get depends on how often you (or Feedbin rather) check the feed for updates. Say, for example, that Feedbin checks the feed every minute, then you will always get a version of the feed that is no older than two minutes. If the feed is checked every 5 minutes, you can get a version of the feed that is up to 10 minutes old. Check it every hour, and you can get a cached version from two hours ago in the worst case. And so on.

As I mentioned earlier, cached versions are shared among all of us. That means, the more people subscribed to a feed, the higher chance that you will get up-to-date content. (Someone else might have already triggered an update of the stale content for you.)

If the freshness of the feed is important to you, you should choose a feed reader service or app with the ability to set the fetch frequency or to manually trigger a refresh. That way, you can make sure to always have the latest possible version of the feed.

@sod That’s a great explanation, thank you for taking the time to write all this, on top of actually making it work 🙂 @crossingthethreshold

@sod Thank you for taking the time to explain this. It helps me in picturing what is going on behind the scenes. Feedbin does not appear to allow the adjusting of feed requests, at least not from what I can see. The feed, as I am seeing it, is currently an hour behind (I saw your reply in Gluon).

I am deciding whether to stick with using it in Feedbin (maybe being a little behind is fine?), use the local accounts on NetNewsWire (though the iPhone & Mac won’t be in sync then), use the NetNewsWire iCloud account for the feed, or simply just use a Micro.blog client.

Oh decisions! 😂

// @maique

@sod If I manually trigger a refresh, I will get a current version of the feed? Or should I refresh again after a couple of minutes to be sure to get the current version?

@MitchW It depends. If someone else fetched the feed right before, you might get a fresh copy. If you're the one triggering the cache bust, you will have to make a new request to get the fresh copy. In the best case, that copy is ready for you in a second or so, but it can take longer.

@sod I am probably the only one using the feed on inoreader, so it seems like I should fetch the feed, wait a few minutes, and then fetch it again, to ensure I’m getting the most current content, if I understand you correctly. 

And thank you for doing this work!

@MitchW In most cases you should just have to wait seconds (not minutes) but yes, that is correct. But doing that refresh dance sounds horrible. 😱 If "real-time" updates are that important to you, go with the official feeds instead. 😊 My experimental feeds will always lag behind a bit.

@sod It doesn't seem bad: Open feed in Inoreader. Optionally, click the refresh button at the top. Read and reply to items. By that time, several minutes will have passed. Click refresh button again. Read and reply to anything new that comes in. Done.