Gli ultimi otto messaggi ricevuti dalla Federazione
-
@julian@fietkau.social @julian@activitypub.space @smallcircles I like Accept and Reject but @trwnh is pretty insistent on Add and Remove so I defer to them.
-
@evan @julian@activitypub.space @smallcircles Mind if I butt in here with a question about management of the `replies` collection? I'm looking at this for the interaction controls FEP draft.
GoToSocial currently broadcasts an `Accept(Note)` to let followers know a reply has been accepted (see https://docs.gotosocial.org/en/latest/federation/interaction_controls/#broadcasting-accepts-for-the-benefit-of-third-servers). We'd want to add an inverse for revocation, which would be `Undo(Accept(Note))` imo.
I feel `Add` and `Remove` on the `replies` collection may be more idiomatic and, in a sense, easier. Opinions?
-
Move Slowly and Build Bridges: Mastodon, the Fediverse, and the Struggle for Democratic Social Media by @rwg
ActivityPub: Programming for the Social Web by @evan
Governable Spaces: Democratic Design for Online Life by @ntnsndr
Is that a good start already or is there something I am missing?
-
I could use help composing an essential Fediverse (as a topic) book reading list. I'm planning on talking to people with a variety of technical backgrounds (range and expertise) so variety is good. I haven't read any of this yet but I would read it first and either (verbally) summarise points or point people to them for more info.
So far I have on my list:
(continued)
-
@smallcircles@social.coop I feel personally called out for this 😛
-
#ActivityPub builds on top of #ActivityStreams in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?
A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.
I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.
-
I haven't seen anyone use Add and Remove activities to notify updates to the `outbox`. I don't think it would work; it's too recursive.
I've done it for other feeds, like `replies` or `followers`, and it works pretty well.
-
I might not understand what we're talking about.
@smallcircles said that AP doesn't mention "timelines" or "feeds". We use a different term, collections. They are ordered in reverse chronological order, like what most people expect a "feed" to look like.
