314
results for "alternate"
-
whereas the use case I was talking about, having a homepage which has no feed, and a link to a separate feed page, is not an alternate representation of the same content
barnaby
at
2022-02-27 01:55
-
afaik the intended usage is that a page showing an HTML representation of a feed uses rel=alternate to link to an alternative representation of the same content, but serialised using RSS/ATOM
barnaby
at
2022-02-27 01:54
-
A page that has a rel-alternate of text/mf2+html pointing to itself would be as you noted
GWG
at
2022-02-27 01:54
-
barnaby: But isn't that also what rel-alternate for RSS does right now?
GWG
at
2022-02-27 01:53
-
rel alternate seems like a weird choice for cases where you’re linking to a feed from a non-feed profile page, rather than the intended usage of linking to an alternative representation of the same content with a different content type
barnaby
at
2022-02-27 01:53
-
from GWG’s link, linked h-feed discovery should now be done via rel=alternate links with a text/mf2+html media type
barnaby
at
2022-02-27 01:48
-
I searched your domain name. It might pick feed sources in order, grabbing the first rel=alternate with a format it recognizes. You've got them in order: jf2, json, atom
Matt[m]
at
2022-01-29 05:06
-
The RSS Advisory Board declares rel=alternate as a standard for autodiscovery, so you're probably right: https://www.rssboard.org/rss-autodiscovery
Matt[m]
at
2022-01-29 04:46
-
Thanks aaronpk , for the life of me I couldn't find it on your site. I found the JSON feed by looking for you on feedly. I see now that you've got rel=alternate links. Is that a standard? (inside or outside of the IndieWeb community?)
Matt[m]
at
2022-01-29 03:52
-
because the same discovery mechanism is used for h-feed. "when you have rel-alternate"
[tantek]
at
2022-01-16 21:20