Today I discovered an interesting inconsistency in Activity Streams specs while investigating [a Fedify issue].
-
Today I discovered an interesting inconsistency in Activity Streams specs while investigating a Fedify issue.
The question: How should we interpret URLs like
"icon": "https://example.com/avatar.png"?JSON-LD context (https://www.w3.org/ns/activitystreams
@type: "@id"→ “This is an IRI reference, dereference it to fetch an ActivityStreams object.”Activity Streams Primer: “assume that a bare string is the
hrefof aLinkobject, not anid” (no dereferencing)Result: JSON-LD processor-based implementations try to parse PNG files as JSON and fail.
Turns out w3c/activitystreams#595 already discusses the same issue for
hrefproperties. I added a note thaticon,image, etc. have the same problem.Once again reminded of how tricky spec work can be…
#ActivityPub #Fedify #ActivityStreams #fedidev #specifications
-
Today I discovered an interesting inconsistency in Activity Streams specs while investigating a Fedify issue.
The question: How should we interpret URLs like
"icon": "https://example.com/avatar.png"?JSON-LD context (https://www.w3.org/ns/activitystreams
@type: "@id"→ “This is an IRI reference, dereference it to fetch an ActivityStreams object.”Activity Streams Primer: “assume that a bare string is the
hrefof aLinkobject, not anid” (no dereferencing)Result: JSON-LD processor-based implementations try to parse PNG files as JSON and fail.
Turns out w3c/activitystreams#595 already discusses the same issue for
hrefproperties. I added a note thaticon,image, etc. have the same problem.Once again reminded of how tricky spec work can be…
#ActivityPub #Fedify #ActivityStreams #fedidev #specifications
@hongminhee It's a place where our loosey goosey style goes into nondeterminism. We should tighten it up in the next version. My main answer would be: publishers, don't do that.
-
undefined Piero Bosio ha condiviso questa discussione
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@piero @notizie E per via di "centralizzato / decentralizzato" non avrei idea di come si possa fare a far capire ai profani. A parte il solito esempio del numero telefonico e la mail.
Tu non dovresti preoccuparti di quale istanza segue la persona con cui dialoghi. Le grandi aziende sono riuscite a far diventare inconsueto quello che è normale (vedi telefono e mail)
-
@piero @notizie La faccenda della verifica dell'età e il controllo chat, sempre adducendo la solita scusa dei bambini, è un modo per SCHEDARE le persone. Oggi ti dicono "sei anonimo se guardi i siti porno" ma i dati loro ce li hanno. Poi passano a mandarti pubblicità, poi a crearti problemi (di qualsiasi tipo) se non rispetti i canoni voluti dal politico. Che per carità potrebbe essere destra o sinistra, a quel livello là il colore importa il giusto.
-
@bkardell how so?
-
@evan seems like this particular poll might be just slightly biased
-
They call options related to this "feature" "get a room", which somehow makes it more annoying.
-
OK, Discourse (the forum software, not "the discourse" about any current news) made me mad today, and that's not something that ever happens. I love Discourse, but this one is crazy.
I get mad when someone PMs me, and this damned forum software is telling people to do it behind my back. This is a support forum for an Open Source project, people are not allowed to ask for private help without paying for it. It is bonkers to recommend taking public conversations private.
-
julian Oh, you're right. I never did it manually and they must have defederated for some reason.
Sorry, but I absolutely hadn't noticed this, so I'd say the problem with NodeBB is solved then
-
@hongminhee It's a place where our loosey goosey style goes into nondeterminism. We should tighten it up in the next version. My main answer would be: publishers, don't do that.
