Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.
One thing I find challenging with the #ActivityPub spec is that the terminology is very loose.
-
One thing I find challenging with the #ActivityPub spec is that the terminology is very loose. Some examples are the way (API) "endpoint", "collection", and "stream" are used. Posting to an inbox endpoint is not the same as adding an activity to an (optional) inbox collection. A reverse-chronological collection of events is a history of an event stream, not the stream itself. I think conflating these concepts leads to much confusion. See the AP "streams" property, for example.
-
One thing I find challenging with the #ActivityPub spec is that the terminology is very loose. Some examples are the way (API) "endpoint", "collection", and "stream" are used. Posting to an inbox endpoint is not the same as adding an activity to an (optional) inbox collection. A reverse-chronological collection of events is a history of an event stream, not the stream itself. I think conflating these concepts leads to much confusion. See the AP "streams" property, for example.
I think an interesting statement from Chapter 3 of the #ActivityPub spec is "Objects are often wrapped in Activities and are contained in streams of Collections" (different than the collection/stream conflation). However, the meaning of "streams of Collections" is defined nowhere. It's also interesting to me that "stream" has no normative definition in the Activity Streams 2.0 spec although it's in the name! The pre-W3C 1.0 version did define an Activity Stream as a collection, so ...
️ -
I think an interesting statement from Chapter 3 of the #ActivityPub spec is "Objects are often wrapped in Activities and are contained in streams of Collections" (different than the collection/stream conflation). However, the meaning of "streams of Collections" is defined nowhere. It's also interesting to me that "stream" has no normative definition in the Activity Streams 2.0 spec although it's in the name! The pre-W3C 1.0 version did define an Activity Stream as a collection, so ...
️There's a long-standing issue and recognition that streams is underspecified..
-
One thing I find challenging with the #ActivityPub spec is that the terminology is very loose. Some examples are the way (API) "endpoint", "collection", and "stream" are used. Posting to an inbox endpoint is not the same as adding an activity to an (optional) inbox collection. A reverse-chronological collection of events is a history of an event stream, not the stream itself. I think conflating these concepts leads to much confusion. See the AP "streams" property, for example.
What? Inserting into a database table isn't the same as POSTing to an API endpoint that does this anywhere else either.
-
There's a long-standing issue and recognition that streams is underspecified..
@smallcircles Yes, that 2018 issue is a great example of what appears to be conceptual confusion between collections and streams. Calling a collection of contacts (the use case described in the issue) a "stream" is strange. The problem is that streams can't be specified well until we decide what they are. I see this issue recurring in the AP C2S discussions. https://github.com/swicg/activitypub-api/issues/37
-
What? Inserting into a database table isn't the same as POSTing to an API endpoint that does this anywhere else either.
@nik Yes, that's why I think it's confusing that the AP spec loosely communicates them as if they are the same.
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi
Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy