owned this note changed 10 months ago
Published Linked with GitHub

SWICG Issue Triage - 2024-04-17

Present:

ActivityPub issues

Document Authorized Fetch

https://github.com/w3c/activitypub/issues/402

Decision:

  • Defer to HTTP Signatures report

Document handling replies

https://github.com/w3c/activitypub/issues/400

Resolution: EP to write Primer page

Published vs Publicized

https://github.com/w3c/activitypub/issues/399

  • TÇ: Strava has a feature to publish publicly but keep (mute) from feeds/broadcast.
  • a: some precedent in mastodon's "unlisted" and youtube "unlisted" as well, but the core of the issue is that sharedInbox isn't attached to any actor and therefore you can't as a user/client "address" an actor that doesn't exist. you would need to define clearer semantics for "to"/"cc" and to:Public vs cc:Public especially as it relates to "deliver to all sharedInbox" behavior.
    • a: another tangential issue is that there isn't a way to express visibility as separate from delivery.
    • a: another another tangential issue: there is no explicit construct of a "feed" or "profile" for expressing all posts a user has made. there is just an implicit feed based on all received Create activities. it might make sense to consider explicitly managing a feed with Add/Remove instead, have it be a Collection and check that instead of outbox or your local cache
  • TÇ: Also use-case of wanting to publish publicly, NOT broadcast to followers, however DO publish to tag aggregations so someone looking up a hashtag in your post will find your post there. Example: you want to post something on an obscure topic to participate in that topic but do not want to spam your followers with it.

Resolution: Assigned to evanp

Inbox forwarding inconsistent behavior

https://github.com/w3c/activitypub/issues/366

Resolution: assigned to evanp

Other Discussion

Select a repo