Your irregular reminder that domain blocking is not a feature of #ActivityPub
-
Your irregular reminder that domain blocking is not a feature of #ActivityPub
-
Jesse 🇫🇷 :versia:replied to Hrefna (DHC) last edited by
@[email protected] Do you mean that it breaks federation if you try to do it naively, or it's just not in the spec and “left up to implementations”
-
Nor are, incidentally, "content warnings."
-
Hrefna (DHC)replied to Jesse 🇫🇷 :versia: last edited by
@jessew It's entirely absent from the spec. It isn't even left up to the implementations per se, it's simply not defined or even considered.
The existing block semantics are about actors, not domains.
-
smallcircles (Humanity Now 🕊)replied to Hrefna (DHC) last edited by [email protected]
You can Simsalabim it into existence by handwaving the extensibility wand, and then just as easily anyone can magically become aware of it through your codebase.
It is super easy.. just read: https://socialhub.activitypub.rocks/t/desired-changes-for-a-future-revision-of-activitypub-and-activitystreams/4534
Update: Kidding. Without the sarcasm, there's not much help in the spec for creating interoperable extensions.
-
smallcircles (Humanity Now 🕊)replied to Jesse 🇫🇷 :versia: last edited by
-
Hrefna (DHC)replied to smallcircles (Humanity Now 🕊) last edited by
-
@hrefna @smallcircles @jessew wow that was… rough. But I like SorteKanin’s summary of the underlying issue with JSON-LD:
I appreciate your enthusiasm about JSON-LD and the extensability it provides but I think that JSON-LD is a technical solution to a theoretical problem that is so far removed from actual user needs that it achieves nothing more than make the whole system more complicated. It seems to build for the 1% of power users and esoteric use cases rather than the 99% of normal users.