WhyINeedToFillUsername

Thanks for the quick reply. I'm not sure we're talking about the same stuff - permissions for CRUD operations on inbox are alright, AFAIK. I am talking about the WebSockets...

Still the same on Solid 5.6.4.

For details on how does my application subscribe to the WS messages, see the source: https://github.com/WhyINeedToFillUsername/inbox/blob/86c8cd0f40a280e1775e157ede0a25d681c0f18e/src/app/services/monitor-inboxes/monitor-inboxes.service.ts#L81 But basically it does exactly what is presented at the spec (https://github.com/solid/solid-spec/blob/master/api-websockets.md#example).

I think they were about the client-side part of Tailor, which TailorX doesn't support. You can find the missing pages in the Tailor's repo: https://github.com/zalando/tailor/tree/master/docs

> The [former solid-spec](https://github.com/solid/solid-spec/blob/master/api-websockets.md#solid-websockets-api-spec) repository describes using the following subprotocol when connecting to a WebSocket server: `solid/0.1.0-alpha`. For example: > > ``` > const socket = new WebSocket('wss://example.org', ['solid/0.1.0-alpha']); >...