FEP-1a11: Send Announces Containing Many Activities
-
temporary placeholder
-
temporary placeholder
- I think this can be generalized to all kinds of fediverse applications using the mechanism described in FEP-0499. Is there a reason for using a domain-specific solution (FEP-1b12
Announce)?
- Whyobjectis a collection? An array of activities would be more concise.
- The second example is named "New and improved fep-4248-style POST". Did you mean fep-1a11? -
- I think this can be generalized to all kinds of fediverse applications using the mechanism described in FEP-0499. Is there a reason for using a domain-specific solution (FEP-1b12
Announce)?
- Whyobjectis a collection? An array of activities would be more concise.
- The second example is named "New and improved fep-4248-style POST". Did you mean fep-1a11?This FEP documents something that PieFed already does and as such it is a bit limited in scope and intended to optimize the kind of federation that FEP-1b12 involves - many frequent votes sent from a community using an Announce. FEP-0499 is great for Mastodon-style federation where a note can go to multiple inboxes but that very rarely happens in 1b12 land.
objectis a collection because it’s not allowed to be an array, according to the spec. Initially it was an array (and PieFed still accepts that) but discussion with other 1b12-using devs convinced me to switch to a collection.fep-4248 is an older name, I’ll fix that!
-
This FEP documents something that PieFed already does and as such it is a bit limited in scope and intended to optimize the kind of federation that FEP-1b12 involves - many frequent votes sent from a community using an Announce. FEP-0499 is great for Mastodon-style federation where a note can go to multiple inboxes but that very rarely happens in 1b12 land.
objectis a collection because it’s not allowed to be an array, according to the spec. Initially it was an array (and PieFed still accepts that) but discussion with other 1b12-using devs convinced me to switch to a collection.fep-4248 is an older name, I’ll fix that!
rimu1:it’s not allowed to be an array, according to the spec
Where are you getting this information? Common fediverse softwares might not handle it correctly, but the spec makes no requirements like what you say. In general, anything not marked "functional" is theoretically always an array, even if it is serialized as a single value or object/reference when the array contains exactly 1 item.
rimu1:Mastodon-style federation where a note can go to multiple inboxes but that very rarely happens in 1b12 land.
What is "Mastodon-style" about this, and what problems does it pose for 1b12? Are you saying that in FEP-1b12 implementations, activities are only delivered to a single recipient? That doesn't sound right.
-
rimu1:
it’s not allowed to be an array, according to the spec
Where are you getting this information? Common fediverse softwares might not handle it correctly, but the spec makes no requirements like what you say. In general, anything not marked "functional" is theoretically always an array, even if it is serialized as a single value or object/reference when the array contains exactly 1 item.
rimu1:Mastodon-style federation where a note can go to multiple inboxes but that very rarely happens in 1b12 land.
What is "Mastodon-style" about this, and what problems does it pose for 1b12? Are you saying that in FEP-1b12 implementations, activities are only delivered to a single recipient? That doesn't sound right.
> Are you saying that in FEP-1b12 implementations, activities are only delivered to a single recipient? That doesn't sound right.
Traditionally, yes. If I like something it goes to the distributor server only, and that server takes care of relaying the activity.
Implementors that straddle threadiverse and microblog send it to all followers and the distributor server.
-
julian2:
If I like something it goes to the distributor server only, and that server takes care of relaying the activity.
That's only half of the equation, though. You send an activity to the distributor, okay, that's one recipient. But then the distributor ostensibly distributes it to more than 1 recipient, right?
-
julian2:
If I like something it goes to the distributor server only, and that server takes care of relaying the activity.
That's only half of the equation, though. You send an activity to the distributor, okay, that's one recipient. But then the distributor ostensibly distributes it to more than 1 recipient, right?
Yes that's correct, the distributor relays it to all community followers.
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