#social 2018-12-19

2018-12-19 UTC
#
@PG_Kelly_v2 @davewiner Mastadon support OStatus and ActivityPub https://en.wikipedia.org/wiki/OStatus https://en.wikipedia.org/wiki/ActivityPub The official W3 orig ActivityPub spec https://www.w3.org/TR/activitypub/ A more useable writeup https://raw.githubusercontent.com/w3c/activitypub/gh-pages/activitypub-tutorial.txt (twitter.com/_/status/1075252592601489408)
xmpp-social joined the channel
#
Cult hello social people !
#
heluecht[m] Moin!
jdormit and jdormit_m joined the channel
#
jdormit So I've been looking through the ActivityPub/ActivityStreams specs, and I can't find anywhere where it says a plain URL (as a string) is valid where an Object/Link is expected
#
jdormit Yet that's what all the existing implementations do, e.g. { "attributedTo": "https://example.com/myactor" }
#
jdormit Which adds a pretty heavy burden on implementors, because then every field with range Link|Object needs to be parsed to see if it's a URL, and if so then it needs to be dereferenced to the actual Object
#
jdormit What's up with that?
#
rialtate[m] jdormit: ldjson specifies it. It's definitely a good thing too because otherwise you end up with nothing but 100k objects with actors embedded 3-4 times in the same message like hubzilla does
#
nightpool[m] as far as I know, there's no type that could either be a plaintext string or a uri
#
nightpool[m] so I don't think there's any ambiguity there
#
jdormit rialtate[m]: so is any property with @type:@id a valid target for being just a URL?
#
rialtate[m] jdormit: yep
#
jdormit huh okay
#
jdormit guess that makes sense
#
heluecht[m] jdormit (IRC): I'm using a function to compact the JSON-LD, this automatically unifies this. This means that I don't have a problem with this.
#
heluecht[m] Means, the {"attributedTo": "https://example.com/myactor"} is converted to something like {"as:attributedTo": {"@id":"https://example.com/myactor"}}
tantek and jdormit_m joined the channel
#
vasilakisfil do I have to have my h-card in the index/root page of my domain or can it be in a separate page like /about? Or can I have it hidden or would that make a search engine not take it into account ?
#
vasilakisfil ah found something: http://microformats.org/wiki/faq#Hidden_Content
#
vasilakisfil hmm that is not optimal though, because microformats claches with the design of the website
#
vasilakisfil on the other hand we could just add h-card on the body and let the other fields wherever they need to be inside the body