Conversation
Notices
-
Discussion of the #ActivityPub Note's "name" property usage and it's processing by Pleroma. Main attention is on the Client to Server interactions that are being implemented in #AndStatus.
I feel that we mixing two different use cases here:
1. An ActivityPub property, to which a Note's Subject/Title is placed, when entered via Pleroma web UI.
I understood about this point.
2. Delivery / sending to other servers a Note, which came from a client application or from another server and which has the "name" property.
I assume that if incoming Note has the "name" property, Pleroma doesn't delete that property, but sends it to recipients with the same value.
?!
https://git.pleroma.social/pleroma/pleroma/issues/635-
@andstatus Pleroma/Mastodon WebUI is using the summary field, name has just no place at all in the REST APIs nor in the current world of the fediverse.
And even in a bit different world: Friendica posts with a title are Articles, without they are Notes.-
@lanodan It's OK for #Mastodon and #Pleroma to use in their UI "summary" property only. Especially taking into account that Mastodon actually doesn't have Title/Subject of a "toot" but "CW" only (Content Warning) that fits into semantics of #ActivityPub's "summary" better than into "name".
Above decision shouldn't influence the "name" property, one of basic properties of #ActivityPub vocabulary.
Regarding current usage: Pump.io uses both "name" and "summary" properties since its creation in 2013, and they live together without problems.
-
-
