When you subscribe to an #RSS #Atom feed, what do you expect to find in your reader?
-
-
@jwildeboer I expect the summary to be in the summary field and the content to be in the content field, which is why I hate RSS that puts either in the description field.
-
@jwildeboer I expect the summary to be in the summary field and the content to be in the content field, which is why I hate RSS that puts either in the description field.
@jwildeboer also mastodon that treats the summary field as a content warning, subverting the entire point of standardising this in Activity Streams in the first place and preserving that in Activity Pub 12 years later
-
@jwildeboer also mastodon that treats the summary field as a content warning, subverting the entire point of standardising this in Activity Streams in the first place and preserving that in Activity Pub 12 years later
@KevinMarks @jwildeboer We are digging ourselves out of that hole, thankfully. For non-Note objects, Mastodon now treats the `summary` like a summary. For Note objects, there's a plan to develop a dedicated content warning property. I think it's fair to say that a summary on a 1-paragraph text is rarely needed, so in practice it should not be blocking progress in AP.
-
@KevinMarks @jwildeboer We are digging ourselves out of that hole, thankfully. For non-Note objects, Mastodon now treats the `summary` like a summary. For Note objects, there's a plan to develop a dedicated content warning property. I think it's fair to say that a summary on a 1-paragraph text is rarely needed, so in practice it should not be blocking progress in AP.
@KevinMarks @jwildeboer I'll be frank: the `summary` property is absolutely essential to having a general-purpose AS2 vocabulary; it's a fallback text representation for objects that don't have a user-assigned title (`name`).