A client talking to a server is standard form of communication. It uses https/TCP.
Server talking to clients without them initiating the talk is very different and new technologies need to be used
To solve this websocket and push notifications are a thing.
How I understand stuff from reading github issues.
Push Notifications - exclusive to mobile devices - android and apple mobile devices. I assume that means that when something make change to a server. Server sends push notification to all clients about the changed?
Websocket Notifications - for just desktop browsers extensions and desktop application. When a change happen on a server by one of the clients, it is used to tell other clients about the change?
assuming I got it right. The current status is that push notifications dont work and likely wont work, as it would require distributing own version of the apps.
Websocket notifications do work.
What are the benefits of these? What is the danger of not having it?
Benefit is that at any point I am sure that the most up to date version is what I am working in.
Is therea danger that two people might edit or try to create identical entry or something?
To mitigate I should always do sync right before editing on mobile?
How do I test if websocket works?
https://vault.example.net/notifications/hub/ takes me to a site showing some info.
Worth noting that if I dont include the last
/ behind hub I am taken to a page saying
WebSocket Protocol Error: Unable to parse WebSocket key. Intersting that caddy config copied from the reverse proxy setup does not have that trailing slash.
Anyway, I am directly on the servers web, logged in, add new entry and it live immediately show up in the desktop app. Does that mean web sockets are working? As I wrote this, I tested it by commenting out the websocket port line from caddy, reloading config… it still worked strangely… until I closed the desktop app and launch it again. Then new entries appeared only after manual sync.