Aaron Parecki

Excellent. I think the "unread counts" property is useful based on common reader approaches. So I think that is definitely valuable, I can see a lot of people wanting to use that. For my use-case, my unread status will likely be based on if the updated property has been "updated".

I'm gonna have to think about this further because there are three options I could do. Regardless of the option I use, Indigenous' default will always be based on if new posts have come in. However, there are some additional features I might implement:

• I could provide an account-wide setting that changes all Channel Unread indicators to be based on if there are any unread posts in the channel. This would be helpful for people that are completionists.
• One potentially interesting idea is instead of the above option, I could provide a per-channel setting of the "Unread Status" of the channel. This would be helpful because some channels I might want to read completely (more article based channels), whereas other channels I might want to be able to just scroll to the top and only have it be marked as unread when a new post comes in.

I think I'm leaning towards that last approach:

• All channels default to showing as read when the user has scrolled to the top and showing as unread when the channel has been updated with at least one new post.
• Each channel can be edited to have it's read/unread indicator be based on if there are any unread posts in the channel.

Tomorrow I’m sending out a special edition of my newsletter, The Monthly Review. This one will collect personal annual reviews for 2017. There’s still time to sign up for the newsletter (Or hit me up if you want to share your review!)

@aaronpk WebSub stoked my curiousity, so I tried both Wordpress plugins for it but neither seem to support discovery per the websub.rocks publisher test. Wondering if that's typical (i.e. we have to manually edit templates to include discovery links) or it's just my set-up?

@aaronpk Hey, any plans on updating Overland in App Store with the new 'current' location property?

That is VERY strange!! 😕

@aaronpk maybe PowerNap™ was active and the MacBook wasn’t in standby?

My trick to make my 2017 annual review blog post easier to write was to create the draft immediately on publishing my 2016 review. I added little bits to it all year and just polished it off in Dec. I’ve already done the same for 2018.

@canion This looks really interesting! Thanks for sharing.

@aaronpk A starred article is a private favorite — generally it means something you want to come back to later for some reason. It’s common to have a special pseudo-feed that shows just starred articles, so a user can find them all easily.

I haven’t worked with current syncing system APIs much yet: my experience is mainly with NewsGator and Google Reader APIs, both now defunct. I vastly preferred NewsGator’s API, because it was designed as a syncing system, where Google Reader’s API was designed for Google, and was never publicly documented or supported, and didn’t work very well for apps like Evergreen (there were lots of ambiguous cases).

@aaronpk Thanks!

Let me see if I understand it. I’ll try putting it into my own words:

Microsub is a spec for a syncing system.

The server crawls feeds, handles feed parsing, and keeps the true copy of the subscriptions list (folders and feeds).

A client app can add/remove folders and feeds and can download the parsed feed data.

(There are additional features, but I think those are the basics. True?)

The two things I think an Evergreen user would still want are: 1) per-article read/unread status syncing, and 2) per-article starred status syncing.