1. 34
  1.  

  2. 6

    Personal website owners – what do you think about collecting all of the feeds you are producing in one way or the other on a /feeds page?

    I think that WWW browsers should rather be repaired and this regression (missing RSS/Atom icon) should be fixed.

    The page already contains machine-readable metadata (URLs of the feeds) and there is no need to provide them in any other way. This is not advancement, this is not improvement, it is just part of the decay of the web technology.

    1. 5

      What’s missing is a place that aggregates all these page patterns in the style of well-known URLs.

      1. 3

        These things should start becoming a standard.

        1. 2

          Just a heads up that the document you linked has been updated by RFC 8615.

        2. 1

          how bout a /urls page

        3. 4

          I implemented this on my website in this commit.

          1. 4

            The feed aggregator I use (Feedly) usually finds a feed if I just add the top-level URL to it.

            1. 7

              The trick is an HTML header like this one:

              <link rel="alternate" type="application/rss+xml" title="Feed Title" href="Feed Location" /> 
              

              That is nice but it does not give readers any call to action.

            2. 4

              At my company we added an icon next to the ‘connect with us’ social icons with the RSS link. Wouldn’t work with multiple feeds, but is pretty clear and there’s a great font awesome icon.

              1. 4

                I had published a half written manifesto (recently took it down) on slashreading.org which suggested /reading and /publishing being OPML feeds of what you read, and what you publish. The idea here being that you could subscribe to all of a persons content if you so choose to, and could discover things through the reading feed. I still think it’s a good idea, but I didn’t push on it.

                Needless to say, I like where the article is going.

                1. 3

                  Additionally, along with RSS feeds, I love when bloggers have a page where they list friends and interesting resources. Some of them do, and that leads to what the web is really about, a wormhole, going from one link to another, a discovery rush instead of a bunch of aggregation silos.

                  1. 3

                    Please note that this article is not suggesting to publish your feed at /feeds, but to create a page at that URL where you list which other feeds you like or you are subscribed to. In other words, the feed version of your blogroll.

                    There is a de-facto standard format for list of web feeds: OPML from UserLand: https://en.wikipedia.org/wiki/OPML. OPML is supported by most feed aggregators.

                    Edit: Fixed comment after reading the post again. Thanks @danburzo.

                    1. 3

                      The article suggests publishing a list of your various feeds, not the ones you’re subscribed to.

                      That being said, OPML is pretty nice for sharing collections of feeds, and I’ve bounced around the idea of using OPML (or another, more appropriate format) to generate a bundle of external links for each blog post

                    2. 2

                      I’ve added this to my site now. I think this is different from /reading and /publishing as it increases the awareness of RSS in the modern internet age. And that matters as it stops the centralisation of web one step at the time.

                      1. 2

                        Love it! Here’s mine: https://sivers.org/feeds

                        And yeah @danburzo I agree, someone should make a meta “Your site should have these URLs”.

                        Thanks to @bcongdon for posting this. I hadn’t heard of it until now.

                        1. 2

                          Wordpress already uses /feed, therefore it’d probably make more sense to use /feed over /feeds given the relative popularity.

                          1. 2

                            Not sure this will change anything.

                            Either people will just try pasting the url into their feed reader and it is autodiscovered, or they might use “show source”. I don’t think anyone will stumble upon a /feeds page. I’d be more inclined to steal wordpress’ /feed url and redirect.

                            1. 1

                              This seems a nice idea. I will try to do something similar this weekend.

                              1. 1

                                I like the idea, but it won’t work easily for multilingual websites. It will need something like /en/feeds, /de/feeds then, probably.

                                1. 4

                                  Or you use the Accept-Language header which is tailor-made for this purpose. The advantage is that you’d only have to configure your client once and it should work for all sites, an added advantage is that it allows for a hierarchy of preference for languages. If, say, Swedish is not available it can take German as a second option, is that not available it can take English, etc.