Simon Woolf

We do document this: https://ably.com/docs/best-practice-guide#use-existing-presence-set . I know because I wrote most of that entry. The problem is that it's in the best practice guide, which is hard to discover...

@matthew.oriordan `for channel in channels.all` is the way it was designed to work, at least. We can discuss changing it, but I suspect any way of making `for channel in...

AFAICS, https://github.com/ably/docs/issues/251 is about the active channel enumeration REST api that's in beta. That's not really anything to do with this issue, which is about RST2 iteration of the local...

yep, sounds good. My motivation for adding that bit to RSN3c was pretty much that I dislike `channels#get(name, options)` because it _feels_ like a functional API, but it doesn't work...

when documenting this, pls note that `headers` must be a flat object, `map` or equivalent - no further nesting. (also we recommend that if using unenveloped reactor rules, header names...

@QuintinWillison this is an issue to document it, so probably docs rather than spec repo? (the spec already says extras is an untyped object that sdks should treat opaquely, TM2i)

> Having said that, I don't remember seeing it in PHP or Python. It's a realtime client lib feature, php and python are currently rest-only

> Confirm that the metrics I have listed are correct - `channels.maxRate` should be `channel.maxRate` (as within a single channel) - For acct-wide limits, currently the message you get when...

> Would it be possible to please get that list of the most common error codes so that we can create appropriate solution articles? what list of most common error...

...So now I'm looking at this, they're not very consistent. Per-connection publish rate limit is 42911 (or 42921 if fatal), and acct-wide rate limits are also 42911, but most other...