Hiromi Ogawa

Maybe it is ISO8601 instead of RFC3339, but in any case, the problem is not parsing but conversion to SystemTime, which may lead us to depend on time-rs anyway...

having distinct date-time type (which does not convert to SystemTime) for ISO8601-encoded date-time field in -api and provide conversion to time::OffsetDateTime in -util would be nice

This is no longer such a serious problem as `chrono` has been back in maintenance since 0.4.20.

Thank you for the feedback. You can use `FromStr` implementation of `Id` to get `Id` from string. In other words, you can use `parse`: ``` let note = client.get_note("8s27fg0gok".parse()?).await?; println!("{}",...

- `misskey` 0.3.0-rc.1 https://crates.io/crates/misskey/0.3.0-rc.1 - `misskey-api` 0.3.0-rc.1 https://crates.io/crates/misskey-api/0.3.0-rc.1 - `misskey-core` 0.3.0-rc.1 https://crates.io/crates/misskey-core/0.3.0-rc.1 - `misskey-http` 0.3.0-rc.1 https://crates.io/crates/misskey-http/0.3.0-rc.1 - `misskey-websocket` 0.3.0-rc.1 https://crates.io/crates/misskey-websocket/0.3.0-rc.1 - `misskey-util` 0.2.0-rc.1 https://crates.io/crates/misskey-util/0.2.0-rc.1

Thank you for your contribution, I'll have a look within this week along with #65 #64

@poppingmoon I cannot review this all at once because of the huge amount of changes. Can you do me a favor to split this PR into some parts? For example,...

edit: "there should be no operations allowed by the v1 policy that aren't allowed by the v1beta policy, and Karpenter v1 should work with the v1beta policy" was not correct....

> LimitExceeded: Maximum policy size of 10240 bytes exceeded for role Karpenter-terraform-aws-eks-testing-3n8AYX Including both v1 and v1beta policies inline in the role seems to exceed the IAM role's policy size...

thank you!