fahrni
fahrni

@johnbrayton @manton Fellas, should we define a standard set of APIs for feed readers?

RSS and JSON Feed are anxiously at the center for adding feeds but if someone wants to hatch a server side component like what y’all have done with Unread and Inkwell wouldn’t it be nice for the basics to be the same?

|
Embed
Progress spinner
JohnPhilpin
JohnPhilpin

paging @dave who I’m sure will have an opinion ..

// @johnbrayton @manton @brentsimmons @fahrni

(#BeyondMyPaygrade … but observing how many cool readers have appeared this year .. that all seem to have a slightly different take)

|
Embed
Progress spinner
fahrni
fahrni

@JohnPhilpin I’m sure he will, John. I’ve had some requests to support feed services like Feedbin, Feedly, and NewsBlur which, of course, made me think having everyone implement something the same would be nice.

The weird thing about it is having a decentralized thing become centralized. But, how else do you keep everything in sync across multiple devices without a service? Be it your own or a third-party? The only thing that comes to mind is standardizing at an API level.

I am 100% open to alternative solutions.

As it stands I will be implementing multiple feed service APIs to support my users.

|
Embed
Progress spinner
johnbrayton
johnbrayton

@fahrni @manton Manton based the Inkwell API on Feedbin’s. That made syncing with Inkwell easier.

But I agree. The Google Reader API serves as a standard, but it is dated and was not intended to be a public API.

I am game for working on a modern standard API with you and/or other folks.

|
Embed
Progress spinner
manton
manton

@johnbrayton @fahrni I’m also happy to work on this! The closest standard I can think of is Microsub. Micro.blog has limited support for it but not in Inkwell yet. I’d probably want to start with that and see where the holes are first.

|
Embed
Progress spinner
prealpinux
prealpinux

@manton really interesting. Let me tag also @tg

|
Embed
Progress spinner