#ActivityPub is getting its first formal update path since 2018.
-
@julian There are several dozens of actively maintained ActivityPub implementations, I think it is not difficult to find two implementers among them, especially if they will be paid to implement a proposed change / extension (as we have seen with the E2EE proposal).
@slyborg @evan @connected-places @fediversereport @ArneBab @alexchapman
@silverpill In a hilarious twist of fate, this gives (streams) and Forte an unfair advantage. They're nearly identical, they have the same maintainer, but they're two separate implementations, also seeing as Forte uses ActivityPub for nomadic identity, and (streams) doesn't and still uses its own Nomad protocol for it.
Since Mitra appears to implement (streams)/Forte features one by one and cast them into FEPs, that's three implementations already. Two if nomadic identity via ActivityPub is involved. And if Hubzilla happens to have it, too, we've got up to four implementations.
Yes, ActivityPub is only an optional add-on on Hubzilla and (streams), but an implementation is an implementation. And whatever they do on Nomad that federates has to get out through ActivityPub one way or another.
It'd be even more hilariously skewed, hadn't Mike discontinued the five apps between Hubzilla and (streams) on New Year's Eve 2022.
CC: @slyborg @Evan Prodromou @Connected Places @ArneBab @Alex Chapman
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Hubzilla #Streams #(streams) #Forte #Mitra -
@julian @silverpill @slyborg I will fight pretty hard against breaking changes in ActivityPub. We have an active network with tens of millions of people and tens of thousands of servers. It's too late for breaking changes and it has been for a really long time. Expect changes like: describing required properties of activities better. How `replies` (and maybe `context`) work. References to OAuth, Webfinger and HTTP Signature.
-
@julian @silverpill @slyborg I will fight pretty hard against breaking changes in ActivityPub. We have an active network with tens of millions of people and tens of thousands of servers. It's too late for breaking changes and it has been for a really long time. Expect changes like: describing required properties of activities better. How `replies` (and maybe `context`) work. References to OAuth, Webfinger and HTTP Signature.
@julian @silverpill @slyborg it's also worth noting that all discussions of the WG will be on a public mailing list. People can join the meetings, comment on drafts on GitHub. People interested in making more substantive contributions can become invited experts, even if they're not from a member organization.
-
@julian @silverpill @slyborg it's also worth noting that all discussions of the WG will be on a public mailing list. People can join the meetings, comment on drafts on GitHub. People interested in making more substantive contributions can become invited experts, even if they're not from a member organization.
@julian @silverpill @slyborg most importantly: no protocol is mandatory. No protocol revision is mandatory. If the work the WG does isn't useful, nobody has to implement it.
-
@julian @silverpill @slyborg most importantly: no protocol is mandatory. No protocol revision is mandatory. If the work the WG does isn't useful, nobody has to implement it.
@julian @silverpill @slyborg the changes I have marked for the next version are here.
https://github.com/w3c/activitypub/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Next%20version%22
I know there are some on there that Silverpill won't like, such as supporting IRIs for object IDs. I think it's worth having that conversation.
-
@julian @silverpill @slyborg the changes I have marked for the next version are here.
https://github.com/w3c/activitypub/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Next%20version%22
I know there are some on there that Silverpill won't like, such as supporting IRIs for object IDs. I think it's worth having that conversation.
@julian @silverpill @slyborg I wonder, though: what would be some changes that would worry you, though? I'm having a hard time imagining what they would be.
The best I can come up with are features that are too complex for small development teams (e.g. oodles of mandatory APIs), or too resource intensive for small instances to support (e.g. required to handle terabytes of big data).
-
@julian @silverpill @slyborg I wonder, though: what would be some changes that would worry you, though? I'm having a hard time imagining what they would be.
The best I can come up with are features that are too complex for small development teams (e.g. oodles of mandatory APIs), or too resource intensive for small instances to support (e.g. required to handle terabytes of big data).
The only other thing I can think of are forced anti-features, like mandatory advertising, mandatory algorithmic feeds, or forced participation in LLM training.
Are there other things I'm missing?
-
The only other thing I can think of are forced anti-features, like mandatory advertising, mandatory algorithmic feeds, or forced participation in LLM training.
Are there other things I'm missing?
@julian @silverpill for you two especially, I wonder if you think there could be Trojans inserted into the ActivityPub 1.1 spec -- something that seems innocuous on the surface, but would actually EEE the Fediverse? I just don't think the standard is complex enough that anyone could hide anti-features in it that you and I couldn't find. Maybe, I dunno.
-
@julian @silverpill for you two especially, I wonder if you think there could be Trojans inserted into the ActivityPub 1.1 spec -- something that seems innocuous on the surface, but would actually EEE the Fediverse? I just don't think the standard is complex enough that anyone could hide anti-features in it that you and I couldn't find. Maybe, I dunno.
@julian @silverpill I think a heaping dose of skepticism is healthy for this effort, though. I'm glad to know you're keeping your eyes open.
-
@julian @silverpill @slyborg I will fight pretty hard against breaking changes in ActivityPub. We have an active network with tens of millions of people and tens of thousands of servers. It's too late for breaking changes and it has been for a really long time. Expect changes like: describing required properties of activities better. How `replies` (and maybe `context`) work. References to OAuth, Webfinger and HTTP Signature.
@evan @julian @silverpill @slyborg What about "breaking" bug fixes in the spec? Many parts of spec are used by ~0 people on ~0 servers so the impact is only positive to do those fixes. Required properties is an interesting topic. Adding a required property beyond `id` (conditionally), `type`, and `input`/`outbox` for actor types *would* be breaking and potentially have a large negative impact (unless they are only associated with optional new features).
-
undefined filobus@sociale.network shared this topic