#dev 2023-04-20
2023-04-20 UTC
[pfefferle], [aciccarello] and [dave] joined the channel
# 
[tantek] ok, test one complete and suspicion confirmed. by changing the slug on my post and reping BridgyFed, I was able to trick BridgyFed into thinking it is seeing a new post, thereby posting a "create" activity from scratch (rather than an update) which then caused that post to show-up in all the hashtags tag pages on all the instances it was federated to
# [tantek] interestingly enough, Mastodon is de-duplicating all these! i.e. my initial reply post, my "update" to that post to remove the "in-reply-to", and then my "create" of that post via a new slug (old permalinks redirect). Only the latest version is showing up here: https://xoxo.zone/@tantek.com@tantek.com/with_replies
# [tantek] so now the Mastodon-hashtag-hack truly is, if you add hashtags to a post, be sure to change the slug before you ping Bridgy Fed, so Bridgy Fed will send a "create" activity, which Mastodon will index the new hashtags in, AND de-dupe with any previous post that redirects from the same permalink!
# 
[schmarty] I don't know what you are saying and I am never doing this lol
# [schmarty] Haha, sorry, I'm reacting a little badly to the activitypub interop alchemy
# [schmarty] Just don't die of mercury poisoning
[keithjgrant], IWSlackGateway and [tantek] joined the channel
# [tantek] interesting, my mention of https://aaronparecki.com/2013/04/19/3/indieweb didn't show up there! and I sent it a few different ways including the form input on that permalink
[keithjgrant] and [snarfed] joined the channel
geoffo, sivoais, gRegor, epoch, [jeremycherfas], notdave, [capjamesg], [KevinMarks], sebbu, [chrisbergr] and [campegg] joined the channel
# 
[campegg] I have a favor to ask of all the ActivityPub-fluent people here: I'm muddling my way through implementing AP on my site, and have started documenting(-ish) some of my thoughts and assumptions here: https://campegg.com/about/activitypub/ — would really appreciate it if someone who knows more than I do could take a look and letting me know if I'm going off in the wrong direction. Thanks in advance!
# [campegg] Thanks, [snarfed]!
# [campegg] Definitely going to go with a library for the sigs… don't want to mess with that stuff
# [campegg] So the way publishing works is by sending the individual activities to the inboxes of each of my followers? I've implemented json views for my notes, so that there's a (hopefully) an AP-compatible version (e.g. https://campegg.com/notes/20230419073932 and https://campegg.com/notes/20230419073932/json/)… what it sounds like is that when I save/update/delete, I need to send that object (with the correct activity type) to each follow
# [campegg] individually
# [campegg] [snarfed] ++
# [campegg] Thank you! that's super helpful!
# [campegg] One more (for now 🙂): I've been looking at httpsig (https://pypi.org/project/httpsig/) as a potential solution for signing; are there any others you might recommend I check out?
# [campegg] Brilliant, thanks!
# [campegg] `requests-http-message-signatures` looks like it might be the way to go
# IWDiscordRelay <capjamesg#4492> My new site rewrite has traversed four programming languages.
# IWDiscordRelay <capjamesg#4492> Lisp, Ruby, Perl, and JavaScript (via 11ty).
# 
aaronpk more background: https://oauth.net/http-signatures/
# [snarfed] yup. specifically, cavage v12 at most, _not_ httpbis, and include specific headers. https://github.com/snarfed/bridgy-fed/issues/430#issuecomment-1510537265
# 
Loqi [preview] [snarfed] conclusion seems to be that the fediverse is still generally on cavage v12 at most, and hasn't migrated to httpbis yet.
- https://socialhub.activitypub.rocks/t/state-of-http-signatures/754/22
- https://socialhub.activitypub.rocks/t/http-signatures-...
# [campegg] 🤔
# [snarfed] [campegg] you may be interested in https://github.com/snarfed/bridgy-fed/blob/main/activitypub.py#L246-L266
[jacky] and pharonix71 joined the channel
# [campegg] [snarfed] Thanks! I've been taking a look into the BF code to see how you've been solving for various bits and pieces 🙂
gRegor, CourtneyR_Dev, [pfefferle], [schmarty], [tw2113_Slack_] and [manton] joined the channel
# [snarfed] they're easy to find in your timeline, but sure. #1/2: https://staging.bsky.app/profile/jay.bsky.team/post/3jtp4gvn6s52f , #3: https://staging.bsky.app/profile/rockinhawke.bsky.social/post/3jtr6gxkn6q2a
geoffo joined the channel
CourtneyR_Dev joined the channel
# [tantek] [snarfed] wrote "[tantek] nice sleuthing, and definitely an awkward workaround for logic that ideally BF would just handle itself automatically" — thanks and I think I have one more iterative test to try before writing it up. And I'm leaning towards recommending Bridgy do the thing that produces better results in Mastodon, even if it is not completely protocol compliant, once the bug is filed on Mastodon to fix "update" handling.
gRegor joined the channel
geoffo joined the channel
# [tantek] well, that was a bust kinda. Bridgy Fed happily delivered an "update", to exactly one instance (that of the in-reply-to URL's server) https://fed.brid.gy/log?start_time=1682034184&key=https://tantek.com/2023/109/t1/btconf-personal-url-fediverse-feed#bridgy-fed-update-2023-04-20T23:43:03.812421+00:00&module= and Mastodon did not display it.
# [tantek] see thread here: https://mastodon.social/@john_fisherman/110224246899618915
# [tantek] thanks [snarfed] for capturing that initial bug in an issue: https://github.com/snarfed/bridgy-fed/issues/487