In the case of voice chat in servers used for gaming, my experience has been that the persistent channels for voice are actually kind of important, it removes any friction from dropping in and out of voice chat, and allows others to easily see 'hey, there is someone in this voice channel, maybe i should join'
But that can be easily faked in client UI. Something like, clicking an empty channel internally hosts a call, hosting/joining the call causes the client to post a hidden "@user is in #call" message, etc.
Based on some (admittedly very surface level) research, one spot where Zulip will still struggle to replace Discord is Voice/Video chats and Screensharing - the little I could find about voice chatting in zulip is that it has to be configured to use an external service (jitsi, zoom, etc)
I think the main purpose, atleast in this case, is to enable very high resolution satellite imagery (whether or not that being a good thing in and of itself is another matter).
Actually, the name definitely came after noticing RAM prices. Though the idea where the graph-in-memory only for ephemeral RAG sessions came first, we won't pretend the naming wasn't influenced by RAM being in the spotlight.
I think (granted, this is from a quick bit of research so I could be wildly wrong) - the message you see in your credit card app with a transaction is usually mainly the merchant name and location which is part of ISO 8583, so it may be a bit hard to extend it to include an arbitrary message in a way that works without merchants having to replace card reader/POS systems en-masse.
reply