#social 2020-11-14
2020-11-14 UTC
sl007, ilmu and ilmu2 joined the channel; CogaJett left the channel
# trwnh question: am i wasting my time trying to implement support for type arrays in AS2 documents? i think all current ap implementations only support a single type, but i kinda don't wanna abandon extensibility...
sl007, ilmu1, ilmu3 and paul joined the channel
# sl007 will be 5 minutes late https://socialhub.activitypub.rocks/t/2020-11-14-meeting/1128
cwebber2 joined the channel
# sl007 confirmative https://mastodon.social/@sl007/105209766819734820
# nightpool[m] FTR my position on the rel question is that I'm not against it, but it's solving a problem that's already solved in the spec through Content-Type negotiation
# nightpool[m] sl007: I don't see any difference (and in fact, more complication) between using a rel link and using Accept: application/activity+json
# sl007 Again the first is to specify and combine relations like rel="me activitypub" "It is me and this is my activitypub profile" or "this is chris, a friend and this is his profile" or whatever semantically in html (like in e.g. the indieweb) not only "Hey, accepting AP" … Am also at indiewebcamp - session up next is hamish, tomorrow is hackday
# sl007 It's just sad if we schedule meetings and nobody of the people scheduled it attend …
# nightpool[m] couldn't you just do that with <link rel="me" type="application/activity+json"> though?
# nightpool[m] how are the two different?
# sl007 well, I personally could but not the communities (aka my users) not familiar like indieweb (see rel="micropub"). And a question would type="application/activity+json" always refer to an AP Actor?
# sl007 yes, thanks for claryfing, rhiaro, sometimes hard for me to explain short in english and photos about digital subjects are hard as well ;)