Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / solid/notifications issues and pull requests

#132 - Update requirmentSubjects

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: protocol

#131 - Update notification-channel-conformance

Pull Request - State: closed - Opened by csarven almost 2 years ago - 5 comments
Labels: model

#130 - Update subscription data model

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: model

#129 - Update classes-of-products interoperability

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: protocol

#128 - adjust terminology to match product classes

Pull Request - State: closed - Opened by elf-pavlik almost 2 years ago - 1 comment

#127 - Add relationship between object and topic resources

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: model, protocol

#127 - Add relationship between object and topic resources

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: model, protocol

#126 - Align WebSocket diagram to Notification Protocol diagram

Pull Request - State: closed - Opened by acoburn almost 2 years ago

#126 - Align WebSocket diagram to Notification Protocol diagram

Pull Request - State: closed - Opened by acoburn almost 2 years ago

#125 - Tag WebhookSubscription2021 as Version 0.1

Pull Request - State: closed - Opened by elf-pavlik almost 2 years ago

#125 - Tag WebhookSubscription2021 as Version 0.1

Pull Request - State: closed - Opened by elf-pavlik almost 2 years ago

#124 - Update notification-data-model

Pull Request - State: closed - Opened by csarven almost 2 years ago
Labels: model

#123 - Use activitystreams-vocabulary instead of activitystreams-core for notification-data-model

Issue - State: closed - Opened by csarven almost 2 years ago
Labels: model, bug

#122 - Remove specific constraint of JSON-LD compacted-document-form

Pull Request - State: closed - Opened by csarven almost 2 years ago - 2 comments
Labels: protocol

#122 - Remove specific constraint of JSON-LD compacted-document-form

Pull Request - State: closed - Opened by csarven almost 2 years ago - 2 comments
Labels: protocol

#120 - Update conformance model

Pull Request - State: closed - Opened by csarven almost 2 years ago - 2 comments
Labels: protocol

#119 - Complete Self-Review Questionnaire: Security and Privacy

Issue - State: closed - Opened by csarven about 2 years ago
Labels: security-review, protocol

#114 - Several questions after implementing

Issue - State: open - Opened by joachimvh about 2 years ago - 3 comments
Labels: status: Commenter Satisfied

#114 - Several questions after implementing

Issue - State: open - Opened by joachimvh about 2 years ago - 3 comments
Labels: status: Commenter Satisfied

#113 - removed custom webhooks authn

Pull Request - State: closed - Opened by elf-pavlik about 2 years ago - 2 comments

#113 - removed custom webhooks authn

Pull Request - State: closed - Opened by elf-pavlik about 2 years ago - 2 comments

#111 - Clarify subscription start and end times

Issue - State: closed - Opened by csarven about 2 years ago - 9 comments
Labels: protocol

#111 - Clarify subscription start and end times

Issue - State: closed - Opened by csarven about 2 years ago - 9 comments
Labels: protocol

#110 - Too Slow: Please provide Updates-Via shortcut to secure web socket address

Issue - State: open - Opened by timbl about 2 years ago - 29 comments
Labels: protocol

#106 - Notifications Protocol Conformance Classes

Issue - State: closed - Opened by csarven about 2 years ago - 1 comment
Labels: protocol

#106 - Notifications Protocol Conformance Classes

Issue - State: closed - Opened by csarven about 2 years ago - 1 comment
Labels: protocol

#105 - JSON-LD structural requirements have issues

Issue - State: closed - Opened by RubenVerborgh about 2 years ago - 7 comments
Labels: protocol

#103 - Cases where Client might want to update Subscriptions/Connections

Issue - State: open - Opened by CxRes about 2 years ago - 1 comment

#103 - Cases where Client might want to update Subscriptions/Connections

Issue - State: open - Opened by CxRes about 2 years ago - 1 comment

#74 - Reconsider `notify:source`

Issue - State: closed - Opened by csarven over 2 years ago - 2 comments
Labels: protocol

#71 - Interchangeable use of notification channel type and subscription type

Issue - State: closed - Opened by csarven over 2 years ago - 3 comments
Labels: protocol

#71 - Interchangeable use of notification channel type and subscription type

Issue - State: closed - Opened by csarven over 2 years ago - 3 comments
Labels: protocol

#63 - Rename `subscription resource`

Issue - State: closed - Opened by uvdsl over 2 years ago - 8 comments
Labels: protocol

#63 - Rename `subscription resource`

Issue - State: closed - Opened by uvdsl over 2 years ago - 8 comments
Labels: protocol

#62 - :bike: shed: Use `object` (closely aligned with AS) instead of `topic` to receive notifications about a resource

Issue - State: closed - Opened by csarven over 2 years ago - 2 comments
Labels: model, protocol

#62 - :bike: shed: Use `object` (closely aligned with AS) instead of `topic` to receive notifications about a resource

Issue - State: closed - Opened by csarven over 2 years ago - 2 comments
Labels: model, protocol

#61 - Update Delta Feature

Pull Request - State: open - Opened by jaxoncreed over 2 years ago - 4 comments

#60 - Define Notification Content

Pull Request - State: closed - Opened by jaxoncreed over 2 years ago - 2 comments
Labels: model

#60 - Define Notification Content

Pull Request - State: closed - Opened by jaxoncreed over 2 years ago - 2 comments
Labels: model

#52 - (Re)Naming of "Solid Notifications Protocol" specification

Issue - State: closed - Opened by csarven over 2 years ago - 2 comments
Labels: editorial, question, protocol, status: Commenter Satisfied

#49 - Relation between storage and notifications source (or agent delivering notification to target)

Issue - State: closed - Opened by elf-pavlik over 2 years ago - 2 comments
Labels: protocol

#49 - Relation between storage and notifications source (or agent delivering notification to target)

Issue - State: closed - Opened by elf-pavlik over 2 years ago - 2 comments
Labels: protocol

#48 - Include webid in subscription response to use standard AuthN

Issue - State: closed - Opened by elf-pavlik over 2 years ago - 6 comments
Labels: webhooks

#48 - Include webid in subscription response to use standard AuthN

Issue - State: closed - Opened by elf-pavlik over 2 years ago - 6 comments
Labels: webhooks

#46 - Specify that each chunk must include one full notification.

Issue - State: open - Opened by elf-pavlik over 2 years ago - 6 comments
Labels: streaming-http

#46 - Specify that each chunk must include one full notification.

Issue - State: open - Opened by elf-pavlik over 2 years ago - 6 comments
Labels: streaming-http

#36 - Subscription service as a container

Issue - State: open - Opened by csarven almost 3 years ago - 4 comments
Labels: protocol

#36 - Subscription service as a container

Issue - State: open - Opened by csarven almost 3 years ago - 4 comments
Labels: protocol

#34 - A consistent naming scheme for Channel Types

Issue - State: open - Opened by CxRes almost 3 years ago - 6 comments
Labels: status: Waiting for Commenter

#21 - Is the proposed notification endpoint negotiation tied to OIDC?

Issue - State: closed - Opened by RubenVerborgh over 3 years ago - 1 comment
Labels: protocol, status: Waiting for Commenter

#17 - Universal Notifications Layer

Issue - State: closed - Opened by brownhoward about 3 years ago - 1 comment
Labels: protocol

#16 - Client can trust notifications are not forged.

Issue - State: closed - Opened by brownhoward about 3 years ago - 2 comments
Labels: postpone, protocol, use case

#15 - List types in preferred order in request

Issue - State: closed - Opened by brownhoward about 3 years ago - 2 comments
Labels: protocol, status: Commenter Timeout

#12 - Why do notifications use JSON-LD?

Issue - State: closed - Opened by RubenVerborgh over 3 years ago - 4 comments
Labels: status: Commenter Satisfied

#10 - How can we version the notifications mechanism?

Issue - State: closed - Opened by RubenVerborgh over 3 years ago - 2 comments
Labels: protocol

#8 - How does the proposed notification mechanism work?

Issue - State: closed - Opened by RubenVerborgh over 3 years ago - 2 comments

#6 - Solid WebSockets API: Missing Unsubscribe!

Issue - State: open - Opened by CxRes over 4 years ago - 13 comments