So, got the system to sign the Accept, only to have Mastodon (which I'm using to test) punt it because it didn't have the date in the signature.
So I added the date. Now it's saying that the encoding isn't legit.
FFS system, why is this so flargin hard.
So thanks to @arcanicanis I've gotten past the signature roadblock and have run right into the next problem. Sending an Accept message when I get a follow/unfollow/etc.
This should be straight forward, and I'll start poking at this over the weekend, as of right now I'm tired and $WORK is being a total beetch.
Still beating my head against the ActivityPub signature verification. I'm now up to 5 code approaches, but they're pretty much all the same approach with minor changes. Of those 5 I've re-written 3 of them to better understand things, and still no idea why it isn't working.
I was thinking it was my data, but tbh, the data is being generated from a Masto instance, and not my test rig (Postman). Same result, and to be honest, same data.
I'm still stumped, but this is such an important piece to AP code, it can't be skipped.
I'm gonna take apart pixelfed and see what they did, maybe there's an answer there.
HA. Okay, figured it out. So, ActivityPub docs say that there will be an header called Accept for application/activity+json. But mastodon does not use this.
So when sending the request in via Masto for the inbox, I'm not getting the condition met, thus it's not triggering...
So fixed.
Now... Just need to figure out what the hell is up with the validation rules.
OKAY, so testing shows that my problems are not confined to a single server when looking at my local #ClickthuluFed
I think... Honestly, I think it might be the multiple proxies and such I'm using.
So right now, https on my ngrok address is pointing to 8087 on docker which is pointing to 80 on nginx...
in theory... I think. The issue may just be the fact that the localhost is port 80, and not 443. Now all I need to do is figure out how to make nginx do 443 on localhost in docker.
Welp, time to research. #fun
So one of the things I'm fighting with in #ClickthuluFed is @landrok 's activity-pub library, trying to get the validation for a request.
This is a problem right now because I can spoof the call from my local postman, but when I do that, I get a failure. (Don't know why)
However, when I do it from a mastodon instance, I get that weird https being converted to http (which may be specific to my local instance and cached)
Frustrating, no?
So, working on #ClickthuluFed and have run into something curious. I'm using my Masto account to try and send a Follow Request. I have it all set up for https but the system keeps seeing http come in. I don't quite understand why? (This is understandably throwing an error - not found - because I've got the system set up for https)
It might be a cached artifact from before when I got my shit together, but it might not? It's been a few weeks since I made that switch.
Any masto experts who can tell me if mastodon strips https to http on inbox requests? I mean, I want to make sure everything is working properly and it's not my setup that's fucked up.
Ugh, Okay, I'm working on #ClickthuluFed again, and trying to manage an inbox. And...
Let's be honest. I have no fucking clue what I'm doing here. I kind of deciphered some of the things I need to do, specifically, about a half dozen actions. But I'm no closer to figuring out how this all works together.
Anyone got a "Developing #ActivityPub for ADHD" book handy? I can translate between languages, so Ruby, C#, PHP or Python can all work for me, as long as the examples are relatively clear and, this is important, no steps are skipped.
Could use a hand or three, or even a smack upside the head. Thanks.
Made more (small) progress on #ClickthuluFed, mostly I'm working on getting some of the more central ActivityPub endpoints working.
However, I did get #ngrok set up and was able to mess with it to hook my docker instance through to it's very silly named private endpoints.
Also got Postman set up to test the AP endpoints without having to do weird stuff with chrome extensions. So yay. (I've been using it for years, but haven't had a reason to put it on my non-$WORK computer till today.)
Daemionfox