asonix
re-using the same client between requests potentially helps this problem: https://github.com/durch/rust-s3/issues/212
Was this intended to be closed or was that a result of deleting the target branch
Yeah, those don't do any JSON-LDing yet. I'm really not excited to implement that myself, and the other implementations don't look very complete.
Hey! so for information regarding my http-signatures crate, for encoding, it needs a Ring 13.5 RSAKeyPair type, and for decoding it needs a PKCS1 DER encoded `Input` type (from the...
That's a `PKCS1 DER` encoded set of bytes. I probably should have just taken a `Vec` or `&[u8]` to make it easier for callers.
You can get that from an `openssl::rsa::Rsa` type with [public_key_to_der_pkcs1](https://docs.rs/openssl/0.10.16/openssl/rsa/struct.Rsa.html#method.public_key_to_der_pkcs1)
ACTUALLY I should have created a trait like ```rust pub trait IntoVerifyType { type Error: Fail; fn into_verify_type(&self) -> Result; } impl IntoVerifyType for Rsa { type Error = ErrorStack;...
Alright, with the `openssl` feature, it enables the following helpful methods ```rust CreateKey::from_openssl_rsa(Rsa, ShaSize) AsVerifyKey::as_verify_key(&self) // for Rsa and Rsa ```
Feel free to let me know what sorts of things you'd like to see from the activitypub crate. Right now, it's basically just a few types and traits related to...
@stevenroose the [activitypub](https://docs.rs/activitypub) and [activitystreams](https://docs.rs/activitystreams) crates that I've built already do that.