#social 2018-11-01
2018-11-01 UTC
Guest84_, Guest84, xmpp-social, Angle, timbl, jdormit and jdormit_mobile joined the channel
# 
jdormit Can someone give me a sanity check on this theory? I accidentally sent an Update to Mastodon which set the publicKey field of my Actor to a non-resolvable value
# jdormit I think that mastodon accepted that update and stored the invalid publicKey
# jdormit And now it is rejecting all further updates I send it because it can't verify the signatures of my requests
# jdormit Does that sound plausible? And if so, is there anything I can do?
# heluecht[m] AFAIK Mastodon is caching the stuff for some time until reloading.
# rialtate[m] jdormit: I don't think that's plausible. I can't even figure out what makes mastodon accept an actor update (as with all objects it's super picky)
Angle joined the channel
# nightpool[m] jdormit: yes, and mastodon caches the webfinger result for 1 day.
# nightpool[m] after a day had passed though stuff should start working again (assuming your actor json is fixed)
# jdormit oh good, that's a relief
# jdormit rialtate[m]: in what circumstances have you seen mastodon reject actor updates?
# jdormit the main problems I've had were with signature verification, but that you can sort out on your end
Angle, dmitriz and jdormit_mobile joined the channel
# rialtate[m] jdormit: all :-) I've sent it every possible way I could think, tried immitating how pleroma does it, and it never seems to take. All I was changing was the name and followers endpoint... Not even anything complicated like key or anything. It fetches... But then ignores...
jdormit_mobile and Angle joined the channel
# jdormit_mobile Hmm, and you're getting a 200 back from Mastodon when you post the update activity?
Angle joined the channel
# rialtate[m] jdormit_mobile: yep
# jdormit_mobile That's frustrating
# rialtate[m] Very :)
Angle, timbl, jdormit_mobile, vasilakisfil and dmitriz joined the channel