Hi @zayac,
If you want to implement a custom network provider, you don’t necessarily need to interpret the yjs content. It is just important that all clients end up with all document updates. This is explained in more detail here: GitHub - yjs/yjs: Shared data types for building collaborative software
There is no yjs implementation in go yet. Please also have a look at this thread: Y-websocket server vs ydb for long-term persistent store of documents - #2 by dmonad
The y-websocket protocol requires you to understand the sync-protocol that is implemented in y-protocols and requires you to understand the Yjs document updates. You can implement your custom sync protocol purely on synchronizing document updates.
As long as your custom server implementation syncs document updates with all clients, you can use Yjs with any editor binding. You can even use multiple network providers at the same time.