ActivityPub update: Signatures

• 
  
• implement LD signatures
  
• implement HTTP signatures
  
• implement signatures that actually work and will still validate a year from now
  
• break the requirement for ActivityPub signatures to require external/centralised resources to validate
  
• break the reliance on "intermittent signatures" that could fail at any time and have a shelf life
  
• decentralise the schema and allow it to change without breaking signatures - past or present or future
  
• make it all legal JSON-LD and ActivityPub
  
• have a #homebrew
  

We'll generate LD Signatures for those who think they require them, and will consume them if they can't provide anything else that actually works, but if you actually depend on LD Signatures, you're basically f*cked.