#social 2018-07-31
2018-07-31 UTC
# donpdonp its probably disguising some other error
# donpdonp heads outside for now (i'll be back later)
# puckipedia it may not be able to get the actor still
# puckipedia or ehm, hm, does it like the public key having a newline at the end
# up201705417 I don't think that's the problem
# up201705417 but it seems dansup got a track on the issue
# up201705417 will cleanup the code while he instigates it
# up201705417 what the...
# up201705417 mastodon accepted this time '-'
# up201705417 although, theoretically I didn't change the code much, just refactored it...
# up201705417 oh
# up201705417 yet
# up201705417 it accepted but the post isn't on the other side
# up201705417 so, it had the same behaviour of pleroma
# up201705417 2018-07-31 01:02:30 LOG_DEBUG: [www.hackthis.space:22076.3a2d8a18 POST /social/index.php/notice/new] ActivityPub Explorer: Found a local Aprofile for https://mastodon.social/users/dansup
# up201705417 .php\/notice\/49","type":"Note","inReplyTo":null,"published":"2018-07-31 01:02:23","url":"https:\/\/www.hackthis.space\/social\/index.php\/notice\/49","atributedTo":"https:\/\/www.hackthis.space\/social\/index.php\/user\/1","to":["https:\/\/mastodon.social\/users\/dansup"],"atomUri":"https:\/\/www.hackthis.space\/social\/index.php\/notice\/49","inReplyToAtomUri":null,"conversation":"https:\/\/www.hackthis.space\/social\/index.php\/conversation\/49#
# up201705417 2018-07-31 01:02:30 LOG_DEBUG: [www.hackthis.space:22076.3a2d8a18 POST /social/index.php/notice/new] ActivityPub Postman: Delivering {"@context":"https:\/\/www.w3.org\/ns\/activitystreams","id":"https:\/\/www.hackthis.space\/social\/index.php\/notice\/49","type":"Create","actor":"https:\/\/www.hackthis.space\/social\/index.php\/user\/1","object":{"context":"https:\/\/www.w3.org\/ns\/activitystreams","id":"https:\/\/www.hackthis.space\/social\/index
# up201705417 notice-49","content":"@dansup test","is_local":true,"attachment":[],"tag":[],"cc":"https:\/\/www.hackthis.space\/social\/index.php\/user\/1\/followers.json"}} to https://mastodon.social/users/dansup/inbox
# up201705417 2018-07-31 01:02:34 LOG_DEBUG: [www.hackthis.space:22076.3a2d8a18 POST /social/index.php/notice/new] ActivityPub Postman: Delivery result: {}
# up201705417 that delivery result
# up201705417 I don't know if it was mastodon answer or if it is a buggy debug result
# up201705417 ---
# up201705417 GNU Social delivering a notice to Gargron: https://www.hackthis.space/social/errors.txt
xmpp-social, vasilakisfil, KevinMarks_, KevinMarks and cdchapman joined the channel
# up201705417 tested and debug result seems to be correct
# up201705417 so, mastodon isn't saying anything apparently
# up201705417 tested again with pleroma and got this:
# up201705417 ActivityPub Postman: Delivery result: "ok"
# nightpool[m] the result of the POST http request only indicates whether the http signature was validated
# nightpool[m] because all other processing is done asynchronously.
# nightpool[m] also, caching should never affect http signature validation because if we fail validation with the key we have, we re-fetch the profile to look for a new key
# up201705417 pleroma requires follow requests acceptation?
# nightpool[m] what?
# nightpool[m] I don't know what you mean by acception
# up201705417 well, this probably isn't a good way of checking this: https://git.gnu.io/dansup/ActivityPub/blob/fun1/utils/postman.php#L121
# up201705417 mainly given asynchronous processing
# up201705417 dansup said we had to handle pending follow requests as some instances could require approval
# nightpool[m] it's part of the spec......
# up201705417 yeah, so:
# up201705417 The side effect of receiving this in an inbox is that the server SHOULD generate either an Accept or Reject activity with the Follow as the object and deliver it to the actor of the Follow.
# up201705417 as pleroma answered with "ok"
# up201705417 it entered in that case and added the follow request to pending list
# up201705417 and if an accept is now sent back to this GS instance it will be processed...
# nightpool[m] you weren't delivering a follow though?
# up201705417 well, now I was
# nightpool[m] oh, okay
# up201705417 since I wasn't making much progress with notice creation decide to try other requests now xd
# up201705417 (it seems pleroma answers everything with an happy "ok")
# JasonRobinson[m] if they do async processing, that is the only thing they can answer
# nightpool[m] like I said, they're processing stuff asynchronously
# nightpool[m] yeah
# up201705417 sigh... fair enough :/
# up201705417 okay, created a dummy account on mastodon for test purposes
# up201705417 and seems that the follow requests I sent were successful :)
# up201705417 diogo@www.hackthis.space is following both gargron and dansup
# nightpool[m] maybe you missed the Accept mastodon sent you?
# up201705417 following from mastodon also works
# up201705417 like from gnu social on a mastodon notice works! ^^
# up201705417 yet, replies don't
# up201705417 nightpool: is there something wrong on this notice/reply format: https://git.gnu.io/dansup/ActivityPub/blob/fun1/classes/Activitypub_notice.php ?
# nightpool[m] can you send me a rendered version?
# up201705417 GS announce works with mastodon
# nightpool[m] using a gist or something?
# up201705417 nightpool sure
# up201705417 https://git.gnu.io/snippets/444
# nightpool[m] `"inReplyTo": null,`
# nightpool[m] can't show it as a reply unless you tell us what it's a reply to :P
# up201705417 okay, that's easy, a sec
# aaronpk Hey congrats! https://i.imgur.com/fEGsldI.jpg
# up201705417 :)
# up201705417 nightpool: the rendered notice now looks like this:
# up201705417 https://git.gnu.io/snippets/444
# up201705417 wait
# up201705417 I think I know what the problem is
# up201705417 those IDs can not be grabbed in a json format as the spec requires them to
# nightpool[m] up201705417: we don't require resolution for notices, because not everybody may implement authentication
# nightpool[m] I still don't see a inReplyTo there though?
# up201705417 that notice is not a reply
# nightpool[m] oh, but it's still not showing up
# up201705417 no :/
# up201705417 do you have any idea of what the problem could be?
# up201705417 it is not the signatures otherwise likes and follows wouldn't work
# up201705417 "published": "2018-07-31T07:15:54Z",
KevinMarks_ joined the channel
# up201705417 that's not the problem :/
# up201705417 now I can not see anything different from mastodon's notices (https://git.gnu.io/snippets/444)
# nightpool[m] isn't the question just whether the status is showing up at all?
# up201705417 and maybe I have to specify the To and Cc on the Create object
# up201705417 currently it is only specified on the Note object
# up201705417 I thought the public thing was used only for notes being published without anyone specified
# nightpool[m] so is it showing up on the user profile or not????
# nightpool[m] if you want to check if mastodon is receiving the status, check the profile in the web ui
# up201705417 it is not showing up on user profile
# up201705417 https://mastodon.social/web/accounts/400865
# nightpool[m] i'm at work right now, so I can't really help debug any further
# nightpool[m] if you're still around tonight I can maybe help
# up201705417 nightpool: no worries, thanks for the support! :)
# up201705417 all you said aaronpk is 100% correct :)
# up201705417 I have the mentions to implement yet
# up201705417 but it will be easy
cwebber2 joined the channel
# up201705417 https://git.gnu.io/snippets/444
# up201705417 what about now? :)
# up201705417 mastodon adds the hostname
# up201705417 but it isn't working
# up201705417 the notice shows up on my profile
# up201705417 but is not linking to dansup
# up201705417 but maybe that's how it is supposed to work?
# up201705417 clickable link
# up201705417 but maybe I should send html for that?
# up201705417 all right, GNU Social isn't handling html under AP right now
# up201705417 so that's okay
# up201705417 well, since I did the mention tag and it is in the To shouldn't it show up somewhere on dansup profile?
# up201705417 (or it did and I didn't noticed it?)
# up201705417 will try with my dummy account :)
# up201705417 it notified me on mastodon
# up201705417 so cool *-*
# up201705417 yeah :)
# up201705417 there are some edges that I have to work on yet, but it's progress!
up201705417 joined the channel
# donpdonp up201705417: im looking at your logpost from yesterday and i see the bit about Could not find a valid profile for "acct:don@donpark.org". but i dont see just what its looking for and not finding
cwebber2 joined the channel
# up201705417 donpdonp: I'll take a look at that
# donpdonp up201705417: i found a problem in my webfinger profile anyways
# donpdonp ive got a local mastodon install limping along enough to try a remote follow
# donpdonp and i can finally look into the ruby and see whats going on
# donpdonp woot. just got a good lookup from local mastodon. the 'self' section of the webfinger response was missing a type:""
# donpdonp 1 day is the mastodon webfinger cache
# donpdonp im not sure about the activitypub profile though.
# up201705417 ooops, awesome catch, thanks!!
cwebber2 joined the channel
# up201705417 e.e
# up201705417 sorry about that
cwebber2, kaniini and KevinMarks joined the channel
# up201705417 when mastodon sends a follow request to GS I am returning an accept object containing the follow request with status code 202
# up201705417 but mastodon says that the request is pending approval...
# up201705417 but mastodon isn't doing that with me...
# up201705417 when I send a follow request to mastodon I don't receive anything back
# up201705417 (on my inbox)
# up201705417 dummy1 at mastodon.social
# up201705417 I get the empty 202 response, but the Accept is not showing up on the logs here :s
# up201705417 hm, which is the typo this time? xD
# up201705417 let me grab the rendered activity
# up201705417 id...
# up201705417 my follow request has no id
# up201705417 mine has @context, type, actor and object
# up201705417 the id can be a dummy URL right?
# up201705417 all right
# dansup for the ID
fr33domlover joined the channel
# dansup pixelfed and GS activitypub support in the same week? 😉
# puckipedia dansup: please make the Follow and Like IDs unique though
# dansup they are
# dansup likes and follows are handled differently in the db than Notes and Announce, they will all contain unique ids per the spec though
# puckipedia attachment code bad
# puckipedia :P
# dansup the type?
# puckipedia no, the fact that it always contains the item
# puckipedia also attributedTo must basically equal the actor
fr33domlover1 joined the channel
# puckipedia and should be activitypub-proper IDs (aka you acn do accept: application/activity+json), just to be sure
# dansup every post has an attachment, except comments
# puckipedia oh right pixelfed I thought it was the other thing
# dansup yeah, actor should use the permalink() instead of url()
# puckipedia based on like, the code style
# dansup it shares the same language but pixelfed adopts PSR coding style guide. Much cleaner than GS
fr33domlover2 joined the channel
# up201705417 all right with id mastodon likes my follow request
# up201705417 and now I received back the Accept activity :)
fr33domlover3 joined the channel
# dansup up201705417: Nice!
# puckipedia amusingly, I don't think I have any special handling for follows in Kroeg
# puckipedia well, I should have
# dansup up201705417: did we discuss the Approve/Reject UI for GS ?
# up201705417 well, it already had two amazing UIs
# up201705417 the first one would tell you that your request was pending approval and that was it
# up201705417 the current UI just says everything is really top and that's it xD
# up201705417 the Subscribe button was designed for two states only and I'm unsure how we will add a third state...
# up201705417 but in the backend it is processing the third state properly
# dansup yeah...
# up201705417 so, when you press Subscribe the button changes to Subscribed (and the request is added in the pending table until receive an accept from remote instance)
# up201705417 if you unsubscribe it doesn't matter whether your request has been accepted or not the entry from the pending table is removed
# up201705417 but even if your request wasn't accepted it will show up on your profile as it has
# up201705417 I don't think this is a serious issue but we can improve this later
# up201705417 (if a reject is received we are simply discarding it)
# dansup yeah
# dansup sounds good!
# dansup i like "ignoring" reject because someone can keep sending a follow request to the same person and continue getting rejected otherwise
KevinMarks, KevinMarks_ and Guest84 joined the channel