jimmycuadra

I do remember running into this when trying out Riot (Vector at the time) against an early version of Ruma. I'm just trying to see what the best way to...

Pinging @ara4n and @richvdh again. I really don't want unspecified behavior to end up in Ruma. Advice on how to move forward on this? What's the plan for the next...

I'd be interested to see how rate limiting might work at the Nginx layer. At first thought, it doesn't seem like the right choice, since rate limiting is part of...

Here's the section on rate limiting from the current version of the spec: https://matrix.org/docs/spec/client_server/r0.2.0.html#rate-limiting. You'll notice that various API endpoints are marked as rate limited also.

Probably also worth mentioning that the rate limiting in the spec is there to prevent the Matrix event graph from getting spammed, e.g. a malicious bot trying to flood a...

As long as Diesel supports SystemTime (which it looks like it does) this sounds good to me!

chrono would be fine if the stdlib time APIs don't cut it.

Yes, because it's also used for the [room previews](https://matrix.org/docs/spec/client_server/r0.2.0.html#room-previews) API. I mentioned to the Matrix team that it was odd that one section of the spec says it's deprecated without...

These will all be separate binaries/repositories. [ruma-federation](https://github.com/ruma/ruma-federation) is the only one that exists so far. Not much to do while the client-server API is still in flux and the specs...

They're all separate APIs, none of which are necessary to run the core client-server API. This allows people to only run the components they need. Looking forward to a deployment...