Social Web Working Group - Activity
No matches.
Past meetings
GitHub
w3c/socialwg
-
1 issue opened.
-
[agenda] 2026-11-13 WG AP Suite Call Series A w3c/socialwg#34, by @dariusk.
-
-
4 issues closed.
-
[agenda] 2026-11-06 Joint WG/CG Series A w3c/socialwg#30.
-
[agenda] 2026-09-24 WG AP Suite Call Series B w3c/socialwg#25.
-
[agenda] 2026-10-15 Joint WG/CG Series B w3c/socialwg#28.
-
[agenda] 2026-10-22 WG AP Suite Call Series B w3c/socialwg#29.
-
-
6 issues received 7 new comments.
-
1 pull request merged.
-
Meeting notes 2026-10-15 w3c/socialwg#31.
-
w3c/activitypub
-
14 issues opened.
-
Shorten the contents of Alyssa's reply to Ben so it doesn't make the page scroll w3c/activitypub#669, by @evanp.
-
Section 6: say that activities are used for interacting? w3c/activitypub#665, by @trwnh.
-
Giving clients some control on whether they want to Tombstone or not on Delete? w3c/activitypub#664, by @trwnh.
-
Mention `updated` property in 6.3 Update activity w3c/activitypub#663, by @trwnh.
-
Describe server's responsibiltiies for managing "created" objects w3c/activitypub#662, by @trwnh.
-
Recommend browsing authoritative collections to respect potential blocks w3c/activitypub#661, by @trwnh.
-
Define Ignore activity? w3c/activitypub#660, by @trwnh.
-
Define "interact" -- what does a Block activity prevent, and how? w3c/activitypub#659, by @trwnh.
-
Non-normatively pointing out that people federate Block activities despite saying they SHOULD NOT? w3c/activitypub#658, by @trwnh.
-
Note discrepancy on Remove.target in AP vs Remove.origin in AS2 w3c/activitypub#657, by @trwnh.
-
Refer to side effects of Accept Follow and Reject Follow from C2S Follow w3c/activitypub#655, by @trwnh.
-
Dedicated section detailing a subscription model w3c/activitypub#654, by @trwnh.
-
"Objects are the core concept" (but not activities?) w3c/activitypub#653, by @trwnh.
-
-
8 issues received 13 new comments.
-
Clarification on HTTPS URIs with fragment in section 3.1 w3c/activitypub#642 (3 comments by @dariusk, @trwnh)
-
Recommend browsing authoritative collections to respect potential blocks w3c/activitypub#661 (2 comments by @tesaguri, @trwnh)
-
Document using `Add` to rather than inbox forwarding w3c/activitypub#644 (2 comments by @evanp, @trwnh)
-
Explicitly disallow non-deferenceable IDs in Object ID section w3c/activitypub#454 (1 comment by @trwnh)
-
Describe server's responsibiltiies for managing "created" objects w3c/activitypub#662 (1 comment by @trwnh)
-
Section 6: say that activities are used for interacting? w3c/activitypub#665 (1 comment by @dariusk)
-
endpoints should be more fully defined and have associated protocol fully specified w3c/activitypub#615 (1 comment by @trwnh)
-
-
6 pull requests opened.
-
Test, please ignore! w3c/activitypub#671, by @dariusk.
-
Test PR, please ignore w3c/activitypub#670, by @dariusk.
-
Fix line breaks in the inbox JSON example w3c/activitypub#668, by @JinDX.
-
Update HTTP caching RFC reference from 7234 to 9111 w3c/activitypub#667, by @dariusk.
-
Fix low-hanging typos, grammar, and word choice w3c/activitypub#666, by @trwnh.
-
Remove reference to AP context and replace it with AS2 context w3c/activitypub#652, by @trwnh.
-
-
1 pull request merged.
-
Update HTTP caching RFC reference from 7234 to 9111 w3c/activitypub#667, by @evanp.
-
-
4 pull requests closed.
-
Test, please ignore! w3c/activitypub#671.
-
Test PR, please ignore w3c/activitypub#670, by @dariusk.
-
Fixed json syntax error in index.html w3c/activitypub#458.
-
Remove references to test suite w3c/activitypub#363.
-
-
9 pull requests received 31 new comments.
-
expand on using non-HTTP ids in 3.1 Object identifiers w3c/activitypub#637 (11 comments by @dariusk, @evanp, @trwnh)
-
Fix low-hanging typos, grammar, and word choice w3c/activitypub#666 (7 comments by @dariusk, @evanp, @trwnh)
-
Remove reference to AP context and replace it with AS2 context w3c/activitypub#652 (2 comments by @dariusk, @evanp)
-
Update HTTP caching RFC reference from 7234 to 9111 w3c/activitypub#667 (2 comments by @evanp, @trwnh)
-
w3c/activitystreams
-
1 issue closed.
-
"core types include" -> "core types are" w3c/activitystreams#704.
-
-
2 pull requests merged.
-
"Core types include" -> "Core types are" w3c/activitystreams#769.
-
Fix 'properties fom' typo in index.html w3c/activitystreams#607.
-
Past meetings
Participants
-
2 participants joined.
-
Juan Caballero (Decentralized Identity Foundation (DIF)) joined.
-
Johannes Ernst (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Decentralized Identity Foundation (DIF) joined.
-
GitHub
w3c/activitypub
-
12 issues opened.
-
Mark ActivityPub context document as archived w3c/activitypub#651, by @evanp.
-
Addressable collections w3c/activitypub#649, by @evanp.
-
Inverse properties for collections w3c/activitypub#648, by @evanp.
-
Consider creating a Threat Model w3c/activitypub#647, by @csarven.
-
Human Rights review w3c/activitypub#646, by @evanp.
-
Document using `Add` to rather than inbox forwarding w3c/activitypub#644, by @evanp.
-
Clarification on HTTPS URIs with fragment in section 3.1 w3c/activitypub#642, by @evanp.
-
Define "non-federated" server w3c/activitypub#641, by @evanp.
-
Reference HTTP in Collections w3c/activitypub#640, by @evanp.
-
Define inbox in section 5.2 w3c/activitypub#639, by @evanp.
-
Revert commit 7c3134342cb3e14e4b3883173a1f745aa9f99910 -- all mentions of "profile" broken w3c/activitypub#638, by @trwnh.
-
-
1 issue closed.
-
12 issues received 28 new comments.
-
Extrapolate the pattern for Retrieving objects to other non-HTTP identifiers w3c/activitypub#608 (6 comments by @bumblefudge, @evanp)
-
Clarification on HTTPS URIs with fragment in section 3.1 w3c/activitypub#642 (3 comments by @csarven, @evanp)
-
Add section in "Object identifiers" about how to specify secondary identifiers for an object w3c/activitypub#601 (2 comments by @TallTed, @tesaguri)
-
Examples for optional properties in section 4.1 Actor objects w3c/activitypub#536 (1 comment by @evanp)
-
Revert commit 7c3134342cb3e14e4b3883173a1f745aa9f99910 -- all mentions of "profile" broken w3c/activitypub#638 (1 comment by @evanp)
-
-
2 pull requests opened.
-
[WIP] Examples w3c/activitypub#645, by @evanp.
-
Remove a duplicated word from the likes collection note w3c/activitypub#643, by @JinDX.
-
-
4 pull requests merged.
-
Remove a duplicated word from the likes collection note w3c/activitypub#643.
-
Fix typos raised in WG readthrough w3c/activitypub#612.
-
Clarify delivery to additional inboxes for public activities w3c/activitypub#621.
-
-
2 pull requests received 8 new comments.
-
Clarify delivery to additional inboxes for public activities w3c/activitypub#621 (6 comments by @bumblefudge, @dariusk, @TallTed)
-
expand on using non-HTTP ids in 3.1 Object identifiers w3c/activitypub#637 (2 comments by @jernst, @TallTed)
-
w3c/socialwg
-
7 issues opened.
-
Does AP spec issue/PR tracker need a "needs-test" tag? w3c/socialwg#33, by @bumblefudge.
-
`@Context` and vocab files fit into change process how? w3c/socialwg#32, by @bumblefudge.
-
[agenda] 2026-11-06 Joint WG/CG Series A w3c/socialwg#30, by @dariusk.
-
[agenda] 2026-10-22 WG AP Suite Call Series B w3c/socialwg#29, by @dariusk.
-
[agenda] 2026-10-15 Joint WG/CG Series B w3c/socialwg#28, by @dariusk.
-
[agenda] 2026-10-09 WG AP Suite Call Series A w3c/socialwg#27, by @dariusk.
-
[agenda] 2026-10-02 Joint CG-WG Call w3c/socialwg#26, by @dariusk.
-
-
4 issues closed.
-
[agenda] 2026-10-09 WG AP Suite Call Series A w3c/socialwg#27.
-
[agenda] 2026-09-11 WG AP Suite Call Series A w3c/socialwg#21.
-
[agenda] 2026-09-17 Joint WG/CG Series B w3c/socialwg#22.
-
[agenda] 2026-10-02 Joint CG-WG Call w3c/socialwg#26.
-
-
5 issues received 7 new comments.
-
1 pull request opened.
-
Meeting notes 2026-10-15 w3c/socialwg#31, by @jernst.
-
-
1 pull request merged.
-
Meeting today w3c/socialwg#24.
-
w3c/activitystreams
-
1 issue closed.
-
Simple Misspelling in Announce Description w3c/activitystreams#528.
-
-
1 pull request opened.
-
Fix: "attention the" → "attention to the" w3c/activitystreams#793, by @emilymdubois.
-
-
1 pull request merged.
-
Fix: "attention the" → "attention to the" w3c/activitystreams#793.
-
w3c/webmention
-
1 issue opened.
-
implementation-reports/TEMPLATE.md omits Discovery Tests #22 and #23 w3c/webmention#123, by @palol.
-
-
2 pull requests opened.
-
Add Discovery Tests #22 and #23 to the implementation report template w3c/webmention#124, by @palol.
-
Add Webmention implementation report: paologabriel.com w3c/webmention#122, by @palol.
-
Past meetings
GitHub
w3c/activitypub
-
19 issues opened.
-
Find a better way to refer to client authentication w3c/activitypub#636, by @evanp.
-
next/prev -> older/newer w3c/activitypub#635, by @evanp.
-
Future-dated publishing w3c/activitypub#634, by @evanp.
-
Revise note on reverse chronological order w3c/activitypub#633, by @evanp.
-
Link to AS2 Collections discussion from AP Collections section w3c/activitypub#632, by @evanp.
-
endpoints registry w3c/activitypub#631, by @evanp.
-
Fuller definition of `proxyUrl` endpoint w3c/activitypub#630, by @evanp.
-
Connect two MAY paragraphs in Actor objects w3c/activitypub#629, by @evanp.
-
"json object which maps" -> "JSON object which maps" w3c/activitypub#628, by @evanp.
-
Add full definitions of new terms defined in ActivityPub w3c/activitypub#627, by @evanp.
-
More logical reactions (order) w3c/activitypub#625, by @Mulder42.
-
Add `manuallyApprovesFollowers` w3c/activitypub#623, by @evanp.
-
Add `movedTo` w3c/activitypub#622, by @evanp.
-
Unclear guidelines for delivery of public content w3c/activitypub#620, by @rochebit.
-
"Actor objects" -> "Actor properties" w3c/activitypub#619, by @evanp.
-
Provide better differentiation between ActivityPub actor and Activity Streams actor types w3c/activitypub#618, by @evanp.
-
Define "ActivityPub actor" w3c/activitypub#617, by @evanp.
-
Amend section on id normalization w3c/activitypub#616, by @evanp.
-
-
3 issues closed.
-
Connect two MAY paragraphs in Actor objects w3c/activitypub#629.
-
"json object which maps" -> "JSON object which maps" w3c/activitypub#628.
-
Move activity example in data portability report is badly formatted w3c/activitypub#390.
-
-
16 issues received 53 new comments.
-
Move discussion of `source` property to Client-to-Server Interactions? w3c/activitypub#610 (10 comments by @evanp, @snarfed, @trwnh)
-
Note about authoritative/complete object in Retrieving objects w3c/activitypub#605 (8 comments by @snarfed, @trwnh)
-
Why is there an actor's `liked` collection but no actor's `shared` collection? w3c/activitypub#611 (7 comments by @evanp, @snarfed, @tesaguri, @trwnh)
-
Add section in "Object identifiers" about how to specify secondary identifiers for an object w3c/activitypub#601 (6 comments by @bumblefudge, @evanp, @snarfed, @tesaguri)
-
Unclear guidelines for delivery of public content w3c/activitypub#620 (5 comments by @bumblefudge, @chrishtr, @evanp, @TallTed, @trwnh)
-
How are Actor Endpoints provideClientKey and signClientKey supposed to work? w3c/activitypub#382 (3 comments by @evanp)
-
endpoints should be more fully defined and have associated protocol fully specified w3c/activitypub#615 (2 comments by @evanp)
-
Spec allows conflation of public and publicized without informing users w3c/activitypub#399 (1 comment by @evanp)
-
-
3 pull requests opened.
-
expand on using non-HTTP ids in 3.1 Object identifiers w3c/activitypub#637, by @snarfed.
-
shared inbox delivery: servers MAY deliver to "all known" => "additional" shared inboxes w3c/activitypub#626, by @snarfed.
-
Clarify delivery to additional inboxes for public activities w3c/activitypub#621, by @rochebit.
-
-
1 pull request received 1 new comment.
-
shared inbox delivery: servers MAY deliver to "all known" => "additional" shared inboxes w3c/activitypub#626 (1 comment by @snarfed)
-
w3c/socialwg
-
3 issues opened.
-
[agenda] 2026-09-24 WG AP Suite Call Series B w3c/socialwg#25, by @dariusk.
-
[agenda] 2026-09-17 Joint WG/CG Series B w3c/socialwg#22, by @dariusk.
-
[agenda] 2026-09-11 WG AP Suite Call Series A w3c/socialwg#21, by @dariusk.
-
-
2 issues closed.
-
[agenda] 2026-09-04 Joint WG/CG Series A w3c/socialwg#19.
-
[agenda] 2026-08-27 WG AP Suite Call Series B w3c/socialwg#20.
-
-
3 issues received 4 new comments.
-
2 pull requests opened.
-
Meeting today w3c/socialwg#24, by @jernst.
-
Added 9-11 meeting minutes w3c/socialwg#23, by @jernst.
-
-
1 pull request merged.
-
Added 9-11 meeting minutes w3c/socialwg#23.
-
w3c/activitystreams
-
5 issues opened.
-
Add `Hashtag` w3c/activitystreams#792, by @evanp.
-
Add `sensitive` w3c/activitystreams#791, by @evanp.
-
Define a filename extension for application/activity+json w3c/activitystreams#790, by @evanp.
-
https://github.com/w3c/activitystreams/issues/720 w3c/activitystreams#789, by @juanao645-dotcom.
-
https://github.com/w3c/activitystreams/issues/720 w3c/activitystreams#788, by @juanao645-dotcom.
-
-
2 issues closed.
-
https://github.com/w3c/activitystreams/issues/720 w3c/activitystreams#788.
-
https://github.com/w3c/activitystreams/issues/720 w3c/activitystreams#789.
-
-
2 issues received 5 new comments.
-
Define a filename extension for application/activity+json w3c/activitystreams#790 (3 comments by @cristianolongoodhl, @evanp, @TallTed)
-
Reconsider SocialCG's relationship to AS2 extensions w3c/activitystreams#723 (2 comments by @evanp, @trwnh)
-