@julian, can you add "https://w3id.org/security/v1" to your ActivityPub context?
-
@julian, can you add "https://w3id.org/security/v1" to your ActivityPub context?
e.g. from: "@context": "https://www.w3.org/ns/activitystreams"
to: "@context": [ "https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1" ]
in: https://browser.pub/https://community.nodebb.org/ (json tab)
the 'publicKey' term is not defined in activitystreams
-
æīŠ æ°æ (Hong Minhee)replied to John Spurlock on last edited by
@js Just out of curiosity, does BrowserPub use a proper JSON-LD processor, or treat ActivityPub objects as plain JSON?
-
John Spurlockreplied to æīŠ æ°æ (Hong Minhee) on last edited by
@hongminhee it does json-ld processing under the hood - the idea is to bubble up errors/recommendations to the ui as well, workin on it ð§â
-
John Spurlockreplied to John Spurlock on last edited by [email protected]
@hongminhee for example right now in the "outline" view, you can hover over the property names and see their canonical uris and a bit of documentation
-
æīŠ æ°æ (Hong Minhee)replied to John Spurlock on last edited by
@js That's cool, it's rare for ActivityPub implementations to handle JSON-LD properly.
-
John Spurlockreplied to æīŠ æ°æ (Hong Minhee) on last edited by
@hongminhee yes, I've already prompted a few context fixes for mbin and other server impls
hopefully we can clean this up - will make more standards-based tools developers' lives easier in the future
fortunately context fixes are usually easy changes
-
æīŠ æ°æ (Hong Minhee)replied to John Spurlock on last edited by
@js FYI Fedify also deals with ActivityPub objects using a proper JSON-LD processor, so Fedify-based apps always generate valid JSON-LD documents. ïļ
-
John Spurlockreplied to æīŠ æ°æ (Hong Minhee) on last edited by
@hongminhee nice, we need an ActivityPub version of Postel's Law
'be conservative in what you send, be _extremely_ liberal in what you accept, expect almost nothing' : )
-
@[email protected] sure thing! Nice catch.
-
@julian thanks, also one small thing on AP calls to post urls
e.g. using accept AP request header to
https://community.nodebb.org/topic/180/who-is-using-nodebbI see you have the nice link header in the response but the response content-type header is wrong (it says json, but it's actually html)
-
-
alright just pushed some fixes/workarounds for nodebb
I'll eventually bubble up some warnings in the visual view, but for now at least it renders!
(also kudos for first TABLE tag in content I've come across)