[harryvederci]

After a quick search I haven't found a good example of a blogroll yet. Was this something that was added as a part of the html on a page?

I think an advantage of an endpoint with just the information (regardless of if that's in JSON, newline-separated plain-text, etc) would be that you could query them witout everyone and their mother having to create custom parsers. Think "consuming an API" instead of "surfing the internet in a browser". I believe webrings also fall into the "surfing" part, which is not what I'm going for here.

[dreamlessfate]

Here's an example of what ZeroGravitas mentioned. This is a blog from the "old" Web2.0 days, when social media was nascent.

This old man still updates his blog almost daily with content that would have him banned on Twitter. He's one of the most insightful and inciteful voices in the world of advertising.

https://adscam.typepad.com/

[harryvederci]

Yeah that definitely falls in the "surfing the internet" category, unless I'm missing a link to a bare list of sources he follows, so I don't have to write a parser.

I understand it can be annoying when people come up with things that have already been implemented, and for which standards exist. But so far I don't see how what I suggested with a "/following" endpoint is exactly like RSS.

[ZeroGravitas]

Atom feeds also had the concept of a "via" link which would be used to give credit to the person you discovered it via.

[harryvederci]

That's more like sharing a post and including its source. In twitter terms: retweeting.

What I intend with the "/following" endpoint example is to say: "Here are some sources that I think publish worthwile content."

Not: "Here is an interesting individual post, which I got from $source."