Social Web Working Group - Activity in 2025
No matches.
GitHub
w3c/activitypub
-
1 issue opened.
-
Broken link in README w3c/activitypub#526, by @jernst.
-
-
6 issues closed.
-
"The actor's namespace" w3c/activitypub#443.
-
[Meta] Can we open GitHub Discussions "forum" on this repo ? w3c/activitypub#426.
-
Application actor purpose and limitations w3c/activitypub#524.
-
Broken link in README w3c/activitypub#526.
-
8 issues received 28 new comments.
-
Application actor purpose and limitations w3c/activitypub#524 (9 comments by @daenney, @evanp, @trwnh)
-
Conflicts with JSON-LD specification regarding object identifiers for anonymous objects w3c/activitypub#476 (7 comments by @evanp, @silverpill, @ThisIsMissEm, @trwnh)
-
Cannot create transient activities in ActivityPub API w3c/activitypub#525 (5 comments by @evanp, @TallTed, @trwnh)
-
Relevance check for inbox forwarding mistakenly refers to "object being forwarded" instead of "activity being forwarded" w3c/activitypub#441 (1 comment by @evanp)
-
[Meta] Can we open GitHub Discussions "forum" on this repo ? w3c/activitypub#426 (1 comment by @evanp)
-
-
1 pull request received 1 new comment.
w3c/activitystreams
-
1 issue opened.
-
Normative requirement "MUST omit empty arrays" is unsound and contradictory w3c/activitystreams#658, by @trwnh.
-
-
1 issue closed.
-
The property definition links to `object` and `image` are incorrectly linked w3c/activitystreams#497.
-
-
2 issues received 5 new comments.
-
Normative requirement "MUST omit empty arrays" is unsound and contradictory w3c/activitystreams#658 (4 comments by @evanp, @nightpool, @TallTed, @trwnh)
-
The property definition links to `object` and `image` are incorrectly linked w3c/activitystreams#497 (1 comment by @evanp)
-
-
1 pull request merged.
-
fix: correct links to image, object, relationship w3c/activitystreams#548.
-
w3c/webmention
-
1 pull request closed.
-
WordPress with capital "P" w3c/webmention#112.
-
GitHub
w3c/activitypub
-
2 issues opened.
-
Cannot create transient activities in ActivityPub API w3c/activitypub#525, by @evanp.
-
Application actor purpose and limitations w3c/activitypub#524, by @daenney.
-
-
2 issues closed.
-
OAuth 2.0 profile for ActivityPub report w3c/activitypub#434.
-
Error in described results of dereferencing an object id w3c/activitypub#523.
-
-
11 issues received 22 new comments.
-
Cannot create transient activities in ActivityPub API w3c/activitypub#525 (5 comments by @evanp, @silverpill, @ThisIsMissEm, @trwnh)
-
Relevance check for inbox forwarding mistakenly refers to "object being forwarded" instead of "activity being forwarded" w3c/activitypub#441 (2 comments by @evanp, @snarfed)
-
Conflicts with JSON-LD specification regarding object identifiers for anonymous objects w3c/activitypub#476 (2 comments by @evanp)
-
Revisit the `https://www.w3.org/ns/activitystreams#Public` == `as:Public` == `Public` equivalence and guidance w3c/activitypub#404 (2 comments by @evanp, @trwnh)
-
clarify/extend security consideration B.2 "verification" for attached files w3c/activitypub#432 (1 comment by @trwnh)
-
[Meta] Can we open GitHub Discussions "forum" on this repo ? w3c/activitypub#426 (1 comment by @evanp)
-
Documentation/best practices on rejecting inbound activities w3c/activitypub#424 (1 comment by @evanp)
-
w3c/activitystreams
-
1 issue closed.
-
Remove example for `@vocab` w3c/activitystreams#657.
-
-
4 issues received 8 new comments.
-
Example 2.1.2 "Context with an object" is both wrong and misleading w3c/activitystreams#524 (3 comments by @evanp, @trwnh)
-
The property definition links to `object` and `image` are incorrectly linked w3c/activitystreams#497 (1 comment by @evanp)
-
GitHub
w3c/activitypub
-
1 issue opened.
-
Error in described results of dereferencing an object id w3c/activitypub#523, by @evanp.
-
-
1 issue closed.
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320.
-
-
2 issues received 7 new comments.
-
Error in described results of dereferencing an object id w3c/activitypub#523 (6 comments by @evanp, @snarfed, @trwnh)
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (1 comment by @evanp)
-
w3c/activitystreams
-
4 issues opened.
-
Remove example for `@vocab` w3c/activitystreams#657, by @evanp.
-
null values w3c/activitystreams#656, by @evanp.
-
Range of `type` property w3c/activitystreams#655, by @evanp.
-
as:Profile used as an Actor? w3c/activitystreams#653, by @christophediprima.
-
-
8 issues closed.
-
Incorrect JSON-LD: Missing '#' from the end of @vocab param in Core Example 2 w3c/activitystreams#510.
-
Compact URI speaks about "type" and "id" (not "@type" or "@id" as in JSON-LD documentation) w3c/activitystreams#505.
-
Image properties width and height w3c/activitystreams#598.
-
Example 75, 77 and 87 use property summary on a Link w3c/activitystreams#496.
-
ABNF as2-partial-time accept time-secfrac without time-second w3c/activitystreams#488.
-
Mention explicitly that Link#name can also be a nameMap w3c/activitystreams#486.
-
Tombstone "formerType" Property Range Needs Clarification w3c/activitystreams#440.
-
as:Profile used as an Actor? w3c/activitystreams#653.
-
-
1 issue reopened.
-
reverse link relations (inverse properties) w3c/activitystreams#20, by @evanp.
-
-
10 issues received 30 new comments.
-
Incorrect JSON-LD: Missing '#' from the end of @vocab param in Core Example 2 w3c/activitystreams#510 (4 comments by @evanp, @tesaguri)
-
Compact URI speaks about "type" and "id" (not "@type" or "@id" as in JSON-LD documentation) w3c/activitystreams#505 (3 comments by @evanp, @TallTed)
-
Tombstone "formerType" Property Range Needs Clarification w3c/activitystreams#440 (3 comments by @evanp)
-
ABNF as2-partial-time accept time-secfrac without time-second w3c/activitystreams#488 (2 comments by @evanp)
-
1 pull request opened.
-
Add errata for issue #496 to ERRATA.md w3c/activitystreams#654, by @evanp.
-
-
4 pull requests merged.
-
Update ERRATA.md to add a # to end of namespace in @vocab example w3c/activitystreams#545.
-
Update ERRATA.md to note lack of aliases for @type and @id w3c/activitystreams#546.
-
Erratum for Example 79 to correct `width` and `height` properties w3c/activitystreams#630.
-
Add errata for issue #496 to ERRATA.md w3c/activitystreams#654.
-
-
4 pull requests closed.
-
fix: Erratum for as2-partial-time w3c/activitystreams#652.
-
Update ERRATA.md to add full list of properties for Link type w3c/activitystreams#553.
-
Issue 496 w3c/activitystreams#549.
-
Issue #440 w3c/activitystreams#647.
-
-
4 pull requests received 8 new comments.
-
Erratum for Example 79 to correct `width` and `height` properties w3c/activitystreams#630 (2 comments by @evanp, @trwnh)
-
Update ERRATA.md to add full list of properties for Link type w3c/activitystreams#553 (1 comment by @evanp)
GitHub
w3c/activitystreams
-
2 issues opened.
-
how to suppress previews for links in HTML `content`/`summary`? w3c/activitystreams#650, by @snarfed.
-
Section 2.2 on IRIs and URLs in activitystreams-core incorrectly references URLs in JSON being a problem w3c/activitystreams#648, by @ThisIsMissEm.
-
-
3 issues closed.
-
Unclear descriptions of 'to', 'bto', 'cc' and 'bcc' w3c/activitystreams#482.
-
Grammatical error in description of "audience" property w3c/activitystreams#600.
-
Example 157 is not valid JSON w3c/activitystreams#448.
-
-
7 issues received 26 new comments.
-
how to suppress previews for links in HTML `content`/`summary`? w3c/activitystreams#650 (9 comments by @evanp, @ThisIsMissEm, @trwnh)
-
Section 2.2 on IRIs and URLs in activitystreams-core incorrectly references URLs in JSON being a problem w3c/activitystreams#648 (9 comments by @evanp, @nightpool, @ThisIsMissEm, @trwnh)
-
Tombstone "formerType" Property Range Needs Clarification w3c/activitystreams#440 (3 comments by @cristianolongoodhl, @evanp, @tesaguri)
-
Grammatical error in description of "audience" property w3c/activitystreams#600 (2 comments by @evanp)
-
ABNF as2-partial-time accept time-secfrac without time-second w3c/activitystreams#488 (1 comment by @evanp)
-
Mention explicitly that Link#name can also be a nameMap w3c/activitystreams#486 (1 comment by @trwnh)
-
`href` has inconsistent typing in the term definition (AS2-Vocab vs jsonld context) w3c/activitystreams#595 (1 comment by @dahlia)
-
-
2 pull requests opened.
-
fix: Erratum for as2-partial-time w3c/activitystreams#652, by @evanp.
-
Issue #648: overly specific reason for not using relative URLs w3c/activitystreams#651, by @evanp.
-
-
3 pull requests merged.
-
Update ERRATA.md w3c/activitystreams#555.
-
Update ERRATA.md w3c/activitystreams#601.
-
Add erratum for example 157 w3c/activitystreams#587.
-
-
1 pull request closed.
-
fix: Erratum for time format with secfrac but not sec w3c/activitystreams#550.
-
-
1 pull request received 2 new comments.
-
Issue #648: overly specific reason for not using relative URLs w3c/activitystreams#651 (2 comments by @ThisIsMissEm)
-
w3c/activitypub
-
2 issues opened.
-
How does ActivityPub relate to ActivityStreams exactly? w3c/activitypub#522, by @aschrijver.
-
Are activities without actors allowed? w3c/activitypub#521, by @snarfed.
-
-
5 issues received 17 new comments.
-
Move errata from wiki to repository w3c/activitypub#519 (6 comments by @evanp, @TallTed, @ThisIsMissEm)
-
How does ActivityPub relate to ActivityStreams exactly? w3c/activitypub#522 (3 comments by @aschrijver, @evanp, @samsethi)
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (2 comments by @evanp)
-
Safety consideration: Collections with exposed items can facilitate spam w3c/activitypub#520 (1 comment by @evanp)
-
GitHub
w3c/activitystreams
-
2 issues closed.
-
Example 146: Missing `Z` in startTime w3c/activitystreams#445.
-
Example 60 Missing `@context` Property w3c/activitystreams#441.
-
-
7 issues received 13 new comments.
-
Tombstone "formerType" Property Range Needs Clarification w3c/activitystreams#440 (6 comments by @cristianolongoodhl, @evanp, @snarfed, @tesaguri)
-
Spec does not clarify non-functional natural language values when mapped w3c/activitystreams#443 (1 comment by @sebilasse)
-
-
1 pull request opened.
-
Issue #440 w3c/activitystreams#647, by @evanp.
-
-
1 pull request merged.
-
Add AS2 context to Example 60 w3c/activitystreams#643.
-
-
2 pull requests received 4 new comments.
-
Update ERRATA.md to add full list of properties for Link type w3c/activitystreams#553 (3 comments by @dariusk, @TallTed)
-
w3c/activitypub
-
5 issues opened.
-
Safety consideration: Collections with exposed items can facilitate spam w3c/activitypub#520, by @trwnh.
-
Move errata from wiki to repository w3c/activitypub#519, by @ThisIsMissEm.
-
Non-addressable collections? w3c/activitypub#518, by @ThisIsMissEm.
-
Changelog HTML is incorrect w3c/activitypub#517, by @ThisIsMissEm.
-
Consider a section on cache management for ActivityPub spec w3c/activitypub#516, by @evanp.
-
-
2 issues closed.
-
Use of "reference" with `inbox` and `outbox` w3c/activitypub#289.
-
Changelog HTML is incorrect w3c/activitypub#517.
-
-
9 issues received 19 new comments.
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (2 comments by @cristianolongoodhl, @evanp)
-
Use of "reference" with `inbox` and `outbox` w3c/activitypub#289 (2 comments by @evanp, @silverpill)
-
C2S Like Activity description does not specify updating the likes collection w3c/activitypub#515 (2 comments by @evanp, @trwnh)
-
Safety consideration: Collections with exposed items can facilitate spam w3c/activitypub#520 (1 comment by @tesaguri)
GitHub
w3c/activitystreams
-
1 issue opened.
-
Restore `Actor` type. w3c/activitystreams#646, by @steve-bate.
-
-
4 issues received 7 new comments.
-
Spec does not clarify non-functional natural language values when mapped w3c/activitystreams#443 (2 comments by @evanp, @sebilasse)
-
1 pull request opened.
-
Small grammatical correction in Announcement notes. w3c/activitystreams#645, by @KristofferStrube.
-
-
1 pull request received 2 new comments.
w3c/activitypub
-
4 issues opened.
-
C2S Like Activity description does not specify updating the likes collection w3c/activitypub#515, by @evanp.
-
Define the relationship between a "server" and an object w3c/activitypub#514, by @evanp.
-
Clarify whether ActivityPub object IDs can be non-URI IRIs w3c/activitypub#513, by @evanp.
-
No C2S `Announce` w3c/activitypub#512, by @steve-bate.
-
-
7 issues received 45 new comments.
-
No C2S `Announce` w3c/activitypub#512 (27 comments by @csarven, @evanp, @nightpool, @steve-bate, @tesaguri, @trwnh)
-
Use of "reference" with `inbox` and `outbox` w3c/activitypub#289 (7 comments by @cjslep, @evanp, @silverpill, @trwnh)
-
C2S Like Activity description does not specify updating the likes collection w3c/activitypub#515 (3 comments by @evanp, @nightpool)
-
Clarify whether ActivityPub object IDs can be non-URI IRIs w3c/activitypub#513 (2 comments by @evanp)
-
Example 9 uses an array for `icon` despite having only a single value w3c/activitypub#507 (1 comment by @evanp)
-
w3c/Micropub
-
1 pull request opened.
-
add 3. pronoun to person in " Implementation" definition w3c/Micropub#125, by @Jak2k.
-
GitHub
w3c/activitypub
-
7 issues opened.
-
Dating App w3c/activitypub#511, by @Schism86.
-
Negotiating protocols and constraints between actors or clients w3c/activitypub#510, by @trwnh.
-
Export definitions for reSpec w3c/activitypub#509, by @evanp.
-
HTTP is...not required? w3c/activitypub#508, by @snarfed.
-
Example 9 uses an array for `icon` despite having only a single value w3c/activitypub#507, by @trwnh.
-
Clarify that JSON-LD allows ActivityPub object properties to be either references or embedded w3c/activitypub#506, by @trwnh.
-
Use of "A link to..." with `followers`, `following`, `liked` w3c/activitypub#505, by @trwnh.
-
-
2 issues closed.
-
Timeouts & Retries w3c/activitypub#365.
-
HTTP is...not required? w3c/activitypub#508.
-
-
16 issues received 93 new comments.
-
Use of "reference" with `inbox` and `outbox` w3c/activitypub#289 (16 comments by @csarven, @evanp, @gobengo, @nightpool, @silverpill, @trwnh)
-
Revisit the `https://www.w3.org/ns/activitystreams#Public` == `as:Public` == `Public` equivalence and guidance w3c/activitypub#404 (15 comments by @nightpool, @silverpill, @TallTed, @trwnh)
-
Clarify that JSON-LD allows ActivityPub object properties to be either references or embedded w3c/activitypub#506 (12 comments by @csarven, @evanp, @gobengo, @nightpool, @steve-bate, @trwnh)
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (12 comments by @evanp, @gobengo, @trwnh)
-
Add RFC-3986 to Normative references w3c/activitypub#504 (8 comments by @evanp, @nightpool, @silverpill)
-
Use of "A link to..." with `followers`, `following`, `liked` w3c/activitypub#505 (7 comments by @evanp, @gobengo, @nightpool, @trwnh)
-
Negotiating protocols and constraints between actors or clients w3c/activitypub#510 (5 comments by @evanp, @silverpill, @trwnh)
-
Example 9 uses an array for `icon` despite having only a single value w3c/activitypub#507 (4 comments by @evanp, @gobengo, @trwnh)
-
Clarify permissibility of additional Accept media types during content negotiation w3c/activitypub#502 (2 comments by @gobengo, @trwnh)
-
Update references to RFC 7231 and 7234 to RFC 9110 and 9111 w3c/activitypub#503 (2 comments by @gobengo, @trwnh)
-
Move activity example in data portability report is badly formatted w3c/activitypub#390 (1 comment by @trwnh)
-
w3c/activitystreams
-
1 issue opened.
-
Export definitions for reSpec w3c/activitystreams#644, by @evanp.
-
-
1 issue closed.
-
Example 102: `url` property missing `type: "Link"` w3c/activitystreams#444.
-
-
2 issues received 3 new comments.
-
Example 102: `url` property missing `type: "Link"` w3c/activitystreams#444 (2 comments by @evanp, @TallTed)
-
-
1 pull request merged.
-
Update ERRATA.md w3c/activitystreams#585.
-
GitHub
w3c/activitypub
-
3 issues opened.
-
Add RFC-3986 to Normative references w3c/activitypub#504, by @silverpill.
-
Update references to RFC 7231 and 7234 to RFC 9110 and 9111 w3c/activitypub#503, by @trwnh.
-
Clarify permissibility of additional Accept media types during content negotiation w3c/activitypub#502, by @trwnh.
-
-
4 issues closed.
-
Standardize discovery using link rel on user-visible URLs w3c/activitypub#310.
-
6.11 Delivery Ambiguity w3c/activitypub#297.
-
Clarify use of context w3c/activitypub#362.
-
-
14 issues received 20 new comments.
-
Distribute posts to instances based on followed hashtags in addition to followed users w3c/activitypub#360 (3 comments by @evanp, @silverpill, @trwnh)
-
Clarify permissibility of additional Accept media types during content negotiation w3c/activitypub#502 (2 comments by @evanp)
-
Revisit the `https://www.w3.org/ns/activitystreams#Public` == `as:Public` == `Public` equivalence and guidance w3c/activitypub#404 (1 comment by @silverpill)
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (1 comment by @evanp)
-
Update references to RFC 7231 and 7234 to RFC 9110 and 9111 w3c/activitypub#503 (1 comment by @evanp)
-
Resolved errata makes it possible to be fully compliant with "Federated Server" profile by doing nothing w3c/activitypub#482 (1 comment by @gobengo)
-
Add a reference to AS2 Core's requirement that documents must be compacted w3c/activitypub#359 (1 comment by @evanp)
-
w3c/activitystreams
-
3 issues received 5 new comments.
-
Spec does not clarify non-functional natural language values when mapped w3c/activitystreams#443 (2 comments by @evanp)
-
-
1 pull request opened.
-
Add AS2 context to Example 60 w3c/activitystreams#643, by @evanp.
-
GitHub
w3c/activitypub
-
3 issues opened.
-
Link to Editors Draft is invalid -- 404 error w3c/activitypub#500, by @bobwyman.
-
Federated mutual Blocks can lead to irreconcilable state desyncs w3c/activitypub#498, by @trwnh.
-
3 issues closed.
-
Discussion threads with Tombstones w3c/activitypub#352.
-
Link to Editors Draft is invalid -- 404 error w3c/activitypub#500.
-
6 issues received 16 new comments.
-
clarify/extend security consideration B.2 "verification" for attached files w3c/activitypub#432 (7 comments by @evanp, @nightpool, @silverpill, @trwnh)
-
Change the required content-type returned by servers from `application/activity+json` to `application/activity+ld+json` w3c/activitypub#501 (3 comments by @csarven, @jeswr, @TallTed)
-
Federated mutual Blocks can lead to irreconcilable state desyncs w3c/activitypub#498 (3 comments by @evanp, @nightpool, @trwnh)
-
w3c/activitystreams
-
3 issues closed.
-
Clarify the definitions of Application and Service types w3c/activitystreams#563.
-
Timezone independent events/events that lasts the whole day? w3c/activitystreams#615.
-
Feature similar to ostatus:conversation w3c/activitystreams#476.
-
-
6 issues received 8 new comments.
-
`url` is defined as `@type: @id` in the context document which precludes use of xsd:anyURI values w3c/activitystreams#596 (2 comments by @evanp, @trwnh)
-
Timezone independent events/events that lasts the whole day? w3c/activitystreams#615 (2 comments by @evanp)
-
`relationship` in JSON-LD context document should use `@type: @vocab` w3c/activitystreams#593 (1 comment by @evanp)
-
Clarify the definitions of Application and Service types w3c/activitystreams#563 (1 comment by @evanp)
-
w3c/websub
-
1 issue opened.
-
Subscription should still be possible later even if denied at some point? w3c/websub#183, by @trwnh.
-
w3c/webmention
-
3 pull requests opened.
-
Move implementation report to correct folder w3c/webmention#120, by @capjamesg.
-
SVNmentions v1.0 implementation report w3c/webmention#119, by @carrvo.
-
Create README.md w3c/webmention#118, by @tantek.
-
-
1 pull request merged.
-
Create README.md w3c/webmention#118.
-
-
1 pull request received 6 new comments.
w3c/ldn
-
1 issue received 1 new comment.
GitHub
w3c/activitystreams
-
2 issues opened.
-
`formerType` should be `@type: @vocab` in context document w3c/activitystreams#642, by @trwnh.
-
Disjointness of Activity Streams types w3c/activitystreams#641, by @silverpill.
-
-
1 issue closed.
-
Improvements to the Place type w3c/activitystreams#582.
-
-
8 issues received 11 new comments.
-
Disjointness of Activity Streams types w3c/activitystreams#641 (4 comments by @evanp, @nightpool, @silverpill)
-
Appropriately defined properties for Content Warnings and Content Labels w3c/activitystreams#583 (1 comment by @evanp)
-
How to indicate that a message is a translation of another message w3c/activitystreams#463 (1 comment by @evanp)
-
`formerType` should be `@type: @vocab` in context document w3c/activitystreams#642 (1 comment by @evanp)
-
-
1 pull request received 1 new comment.
w3c/activitypub
-
1 issue opened.
-
Du bist leider nicht berechtigt, Kommentare zu diesem Beitrag zu bearbeiten. w3c/activitypub#497, by @ThomasKujawa.
-
-
2 issues closed.
-
Follow on a non-Actor object w3c/activitypub#343.
-
Du bist leider nicht berechtigt, Kommentare zu diesem Beitrag zu bearbeiten. w3c/activitypub#497.
-
-
5 issues received 18 new comments.
-
Discussion threads with Tombstones w3c/activitypub#352 (6 comments by @bobwyman, @evanp, @TallTed, @trwnh)
-
clarify/extend security consideration B.2 "verification" for attached files w3c/activitypub#432 (1 comment by @evanp)
-
Du bist leider nicht berechtigt, Kommentare zu diesem Beitrag zu bearbeiten. w3c/activitypub#497 (1 comment by @nightpool)
w3c/ldn
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Fix typo s/complimentary/complementary w3c/ldn#69, by @csarven.
-
-
2 pull requests merged.
-
Fix typo s/complimentary/complementary w3c/ldn#69.
-
GitHub
w3c/activitypub
-
4 issues opened.
-
Section 5.1 "Outbox" describes returning "objects" or "posts" instead of "activities" w3c/activitypub#494, by @trwnh.
-
Guidance on "how to interact" / "where to send activities" could be extended w3c/activitypub#493, by @trwnh.
-
Potential issue with private delivery when an `inbox` is associated with more than one resource w3c/activitypub#492, by @trwnh.
-
1 issue reopened.
-
Section 6 on C2S does not describe side effects of Accept or Reject w3c/activitypub#489, by @evanp.
-
-
10 issues received 24 new comments.
-
Section 5.1 "Outbox" describes returning "objects" or "posts" instead of "activities" w3c/activitypub#494 (7 comments by @evanp, @silverpill, @TallTed, @trwnh)
-
Loosen restrictions on `bto` and `bcc` to allow including them on POST to the inbox of the recipient w3c/activitypub#495 (4 comments by @evanp, @nightpool, @ThisIsMissEm)
-
Potential issue with private delivery when an `inbox` is associated with more than one resource w3c/activitypub#492 (2 comments by @evanp, @nightpool)
-
clarify/extend security consideration B.2 "verification" for attached files w3c/activitypub#432 (2 comments by @evanp, @nightpool)
-
Guidance on "how to interact" / "where to send activities" could be extended w3c/activitypub#493 (2 comments by @evanp)
-
Section 6 on C2S does not describe side effects of Accept or Reject w3c/activitypub#489 (2 comments by @evanp)
-
Section 6.3.1 C2S Partial Update property deletion behavior is impossible and should be deprecated w3c/activitypub#477 (1 comment by @trwnh)
-
Section 7.1: relax requirement not to deliver to yourself? w3c/activitypub#480 (1 comment by @trwnh)
-
-
1 pull request opened.
-
Fix incorrect URLs in links w3c/activitypub#496, by @per1234.
-
w3c/activitystreams
-
3 issues opened.
-
Split `mediaType` into two properties; one for Link, one for Object? (`contentType`?) w3c/activitystreams#638, by @trwnh.
-
Section 4 "Model" uses a non-robust Link detection algorithm which does not consider properties w3c/activitystreams#637, by @trwnh.
-
Paged and unpaged collections ought to be distinct and disjoint w3c/activitystreams#636, by @trwnh.
-
-
5 issues received 30 new comments.
-
Paged and unpaged collections ought to be distinct and disjoint w3c/activitystreams#636 (11 comments by @evanp, @nightpool, @TallTed, @Tamschi, @trwnh)
-
Split `mediaType` into two properties; one for Link, one for Object? (`contentType`?) w3c/activitystreams#638 (6 comments by @evanp, @nightpool, @trwnh)
-
Section 4 "Model" uses a non-robust Link detection algorithm which does not consider properties w3c/activitystreams#637 (2 comments by @evanp)
-
-
3 pull requests opened.
-
Fix links to extensions page w3c/activitystreams#640, by @silverbucket.
-
Replaced "MIME media type" with the recommended terminology: "media type" w3c/activitystreams#639, by @csarven.
-
fix: erratum for "core object types" language in section 4 "Model" w3c/activitystreams#635, by @evanp.
-
-
1 pull request received 8 new comments.
-
Replaced "MIME media type" with the recommended terminology: "media type" w3c/activitystreams#639 (8 comments by @csarven, @nightpool)
-
GitHub
w3c/activitystreams
-
2 issues opened.
-
"core object types and properties" is confusing w3c/activitystreams#634, by @evanp.
-
Is Actor a core type? w3c/activitystreams#633, by @silverpill.
-
-
6 issues received 12 new comments.
-
Is Actor a core type? w3c/activitystreams#633 (7 comments by @evanp, @nightpool, @silverpill, @strugee, @TallTed)
-
change name of activitystreams2.owl to activitystreams2.ttl w3c/activitystreams#606 (1 comment by @plehegar)
-
w3c/activitypub
-
5 issues opened.
-
Multiple inbox feeds with different sorting and filtering algorithms w3c/activitypub#490, by @evanp.
-
Section 6 on C2S does not describe side effects of Accept or Reject w3c/activitypub#489, by @trwnh.
-
Issues re. Primer - here /HTML w3c/activitypub#488, by @sebilasse.
-
ActivityStreams -> Activity Streams w3c/activitypub#487, by @evanp.
-
Delivering to Collections can be ambiguous w3c/activitypub#486, by @trwnh.
-
-
1 issue closed.
-
Issues re. Primer - here /HTML w3c/activitypub#488.
-
-
12 issues received 39 new comments.
-
Delivering to Collections can be ambiguous w3c/activitypub#486 (17 comments by @evanp, @nightpool, @silverpill, @ThisIsMissEm, @trwnh)
-
Section 7 S2S describes delivering activities to non-addressed actors? w3c/activitypub#478 (6 comments by @evanp, @trwnh)
-
Multiple inbox feeds with different sorting and filtering algorithms w3c/activitypub#490 (4 comments by @evanp, @nightpool, @ThisIsMissEm)
-
Section 6 on C2S does not describe side effects of Accept or Reject w3c/activitypub#489 (2 comments by @evanp)
-
Conflicts with JSON-LD specification regarding object identifiers for anonymous objects w3c/activitypub#476 (2 comments by @sebilasse, @zotanmew)
-
Give recommendation on how to identify an "actor" in the spec w3c/activitypub#470 (1 comment by @silverpill)
-
Inconsistency on the side effect of receiving a Follow activity w3c/activitypub#320 (1 comment by @evanp)
-
Section 7.1 refers to nonexistent `item` property (should be `items` or not wrapped in code tag) w3c/activitypub#481 (1 comment by @evanp)
-
Sections 6.1 and 7 neglect to mention whether Announce activity requires `object` w3c/activitypub#479 (1 comment by @evanp)
-
w3c/webmention
-
1 pull request opened.
-
Add Denizen implementation report w3c/webmention#117, by @dz4k.
-