We started with this implementation, however there are 2 issues with this approach. 1) NOTIFY has a limit of 8000 bytes, so large rows are silently dropped. 2) you need to attach the notify trigger to every table (vs a Publication, which can listen to an entire database in a single line of code).
> why WS was used
The Server is Elixir (Erlang) so it's very good at WS. Over time we will add other multiplayer useful features (like presence)