#social 2018-06-23
2018-06-23 UTC
cwebber2, tantek, pantherse and xmpp-social joined the channel
#
dansup Hello ActivityPub. https://mastodon.social/@dansup/100253003190305470
#
dansup I started this because I want to help make it easier to understand using real world examples, and have both visual and code representations so that its easily explained for both users and developers alike.
#
dansup and also this, lol. https://mastodon.social/@dansup/100253075924652260
#
dansup I
#
dansup I am getting feedback from her tomorrow :)
#
jaywink[m] dansup: extremely cool 👍 and needed. Would be great to especially have examples on auth and signing from the current implementations

#
dansup yes, HTTP signatures first, then LD
#
jaywink[m] ooh didn't realize funkwhale was django

#
dansup funkwhale is pretty cool, I am working with the dev to support audio on pixelfed
#
jaywink[m] I might need to steal... I mean learn from some of the AP related code for socialhome :P

#
dansup yabir is also working with python on an AP IG replacement! https://github.com/yabirgb/zinat
#
dansup we are working together so UX is similar, lmk if you have any questions about our implementation
#
jaywink[m] cool thanks, seen heard of zinat before but didn't realize it was python. nice to have some reference implementations when creating the AP stuff

timbl and cwebber2 joined the channel
#
nightpool[m] gargron wrote a great intro post about AP if anyone wanted to check it out https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
#
nightpool[m] I know there were a couple people in here who were looking into AP but weren't sure where to get started
#
technomancy oooh
#
technomancy <3 static files
#
jaywink[m] was just reading it and about to link here. nice :)

#
dansup that is awesome :D
#
dansup I'm working on something like that too
#
jaywink[m] nice 👍

#
Gargron could you drop some upvotes on HN if you liked the blog post?
vasilakisfil joined the channel
#
puckipedia been building kroeg with a thought of easy decentralized trust, which should allow for any user to delegate signing the object to e.g. another server, or even to your local machine
cwebber2 joined the channel
#
nightpool[m] hey puckipedia!! great to see you around again
#
nightpool[m] also lol @ cwebber2 joining right as you mentioned decentralized trust
#
nightpool[m] i'm definitely really pro that kind of stuff
#
nightpool[m] signing delegation would be really useful for e.g. the gitpub stuff yookoala is doing
#
puckipedia primary use is signing in on server A, then posting messages on server B
#
puckipedia ajordan: ah, this is mostly a flow used when the server doesn't actually have the private key
#
puckipedia yes and no
#
puckipedia It'd probably be a "to_sign" claim inside the authorization token, which is a url. send the objects and requests to sign there, the server/client signs it, returns the objects
#
puckipedia the only thing is
#
puckipedia if we implement this, we need to probably throw out the current LD signing technique
#
puckipedia ajordan: yes, but only after the user accepts
#
puckipedia the current LD signing is just for an entire document
#
puckipedia yeah
#
puckipedia it'd probably be like a draft view
#
puckipedia so you'd see the result, accept/reject it
#
puckipedia for the LD signatures: I have an untangling thingy that works for everything but completely tangled documents
#
puckipedia no idea, as, y'know, I haven't thought this out further than "this would be nice for allowing e.g. ipfs-stored actors"
#
puckipedia fun fact: I can have kroeg-rs create the most cursed activity ever
cwebber2 joined the channel
#
puckipedia curl -H 'Authorization: ...' --data '
{"id": "_:b0", "type": ["Create", "Person", "Note"], "object": "_:b0", "content": "hi", "attributedTo": "user", "actor": "user", "name": "Cursed Post-user-thing", "preferredUsername": "idk-even"}
' http://127.0.0.1:3000/~puckipedia/outbox#
puckipedia I am slightly proud that this works at least
#
puckipedia output is approx https://gist.github.com/puckipedia/bedf18b1c87d3c2a6bd318e41b723468
#
puckipedia anyways i gotta sleep
#
puckipedia kroeg-rs is like way better already
#
puckipedia and written in rust :P
#
puckipedia turns out not giving up and just building infrastructure on top of json-ld node maps works
#
puckipedia took a little work to make it work
#
puckipedia but. I never touch the raw JSON unless it is to translate it into expanded JSON-LD, and even then I just flatten it
#
puckipedia also I ehm. I kinda dropped the divide between Create and just using it immediately, because of code reasons
#
puckipedia so now,
{"type": "Announce", "object": {"type": "Note"}}
is valid#
puckipedia TIME FOR BED