pads your actor keys

Amber

Amber

this may seem innocent but https://activitypub.software/TransFem-org/Sharkey/-/issues/806

:neobot_book: *neptunyl⁷-hydroxide :neptune:

@[email protected] honestly the fact it isn't sanitizing the signature is kinda worrying

Amber

@[email protected] I'm ignoring that too for mental health reasons.

Amber

@[email protected] Also ignoring the fact that it somehow cascaded into the drive service because that doesn't make sense to me

Ivy [_gay] Mae :fire_trans:

@puppygirlhornypost2 @ada what, how do you have cascading failures and why would you need to sanitize it? /gen (I never use js/ts and this seems cursed asf to me)

:neobot_book: *neptunyl⁷-hydroxide :neptune:

@[email protected] @[email protected] you can store multiple keys in a key, that might have differing authorities.

and i have no clue how it cascaded into the drive service, i'm just assuming misskey moment

Ivy [_gay] Mae :fire_trans:

@ada @puppygirlhornypost2 wait multiple keys?? in a key??? mastodon never documented that :neofox_melt_sob:

Ivy [_gay] Mae :fire_trans:

@ada @puppygirlhornypost2 just when I think my signing and verification is good theres more crap I didn't know existed

:neobot_book: *neptunyl⁷-hydroxide :neptune:

@[email protected] @[email protected] basically just extract the signing subkey from the key, if it exists. certify, codesign, encrypt are not needed (atm, who knows what happens in the future.)

Ivy [_gay] Mae :fire_trans:

@ada @puppygirlhornypost2 is there actually documentation on this or is it just magical you figure it out in production

Amber

@[email protected] @[email protected] this entire network is built of magic you figure out in production when your instance explodes receiving a certain Activity