[pfefferle]I think it goes to the fragment and interpret only this part and if the author informations are outside of the fragment they will be ignored
[pfefferle][snarfed] I still think it should be decoded, but I agree, that it is problematic... perhaps we should always strip the hash-part or we should disable fragment parsing in the mf2 lib (if possible)
[snarfed][pfefferle] understood! the parts that make me think twice are that the Python requests library I'm using doesn't URL-encode the % characters in a form-encoded POST, and that other webmention receivers like www.jvt.me are handling these source URLs fine
[snarfed][pfefferle] you're right, form-encoded POST body do get URL-encoded. I checked and confirmed that in this webmention I'm sending, the # char is getting *double*-URL-encoded to %2523 in the POST body
[pfefferle]GWG what do you mean by "I'm still trying to figure out the upgrade trigger..it isn't working in testing"??? does the code not work or the trigger?
[pfefferle]> Use with caution: When you use the `upgrader_process_complete` action hook in your plugin and your plugin is the one which under upgrade, then this action will run the old version of your plugin.
[chrisbergr]Maybe you can provide a minor update of the previous version. In that update you register the action hook to redirect to a plugin file. If you do your major update, you may access the hook from previous version but the redirect goes to the new file. There you can handle all the stuff you have trouble with. - Sounds plausible in theory
[James_Van_Dyne] and RasAlGhoul joined the channel