Re: [w3c/push-api] A javascript api for sending push notifications to others (#303)

Yeah, Push would make a terrible messaging system for a lot of reasons. 

Push's main concept was to provide a way for sites (which tend to have addresses that are fairly static) to send messages back to users (which tend to have addresses that vary), in a way that's controllable by the client. There are a LOT of better protocols for doing messages (e.g. WebRTC, Message Layer Security (MLS), etc.)

That said, I've seen some configurations do some fairly clever things with push. Including encoding a subscription info block into a QR code so that two devices could share info. Say, connecting up a mobile device with a desktop device. In that case, both "users" are the same person, just different user agents. Could that have been done another way? Absolutely. Still, I can understand the trade-offs that come with all of the solutions.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/303#issuecomment-998280445
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/303/998280445@github.com>