You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Raising the question of whether parsers should, if there are multiple h-* elements on a page that do not have a u-url that matches the retrieved page, return an h-feed, even though one is not expressly declared.
There’s no precedent for implying entire mf2 objects (only properties, and those only under very specific conditions to avoid false positives) so I’m strongly against implied h-feed. Implying a feed from a list of h-entries is a job for consuming code, not the parsing spec itself.
Raising the question of whether parsers should, if there are multiple h-* elements on a page that do not have a u-url that matches the retrieved page, return an h-feed, even though one is not expressly declared.
https://indieweb.org/feed#How_To_Consume
There is a suggestion about how to parse this above, but should some variant of it end up in the specification?
The text was updated successfully, but these errors were encountered: