Ably

Documentation

We will shortly be correcting an incongruency in our capabilities definitions. Currently, a capability for a resource such as ns:* also permits operations on the bare channel ns. While this behaviour matches how channel rules work (a channel rule for "ns" will apply to both the literal channel "ns" and all channels that start with "ns:"), and can be a useful shortcut, it's not remotely intuitive, and does just violate the natural interpretation of the wildcard matcher. So we are planning to remove this inconsistency, and the supported way going forward will be that if you want a capability that matches both (say) channel and channel:xxx for all xxx, you will have to explicitly specify both resources, e.g. {"channel": ["*"], "channel:*": ["*"]}.

Managing complex, fast-changing state for AI agents, live configs and collaborative apps just got much cleaner with new LiveObjects path based API. Here's what it unlocks:

This release fixes clients failing to connect on networks whose proxies reject WebSockets, and moves connection continuity decisions from the client to Ably. For the full changelog, please visit the GitHub release page.