why even get any server in the loop, when messages can be delivered directly between interested parties, as with GNU Jami?
CC: @janvlug
CC: @janvlug
@lxo @janvlug we have to still solve the reliability issue somehow, and also mass adoption.
How does Jami handle messages if the receipient is not online? This likely involves processing more data by peers.
Like I keep repeating, choice of a messaging platform is not just a personal unlike GNU/Linux or Libre Office, we need our contacts using the same platform as well.
So to provide the same usability, we need server and phone book integration.
message gets delivered when sender and receiver can contact each other. that's the only way to go without involving intermediaries.
(in groups, any peer that receives a message can pass it on to others later)
the need for others to share the same platform is somewhat artificial: we'd be better off with protocols that multiple different programs and platforms could use to exchange messages. but the centralizing 'app' mentality pushes us the wrong way. Email, XMPP and the Fediverse, for some examples, have different servers and different clients, and they all interoperate to some degree. now, maybe you consider the protocol as the platform.
anyhow, GNU Jami would likely benefit from different applications, including TUI and CLI. GUIs are often inconvenient and constraining.
we don't need server, so we can't need server integration.
phone book? what phone?!? who needs anachronic phone numbers when we can have mnemonic nicknames (backed by crypto-strong hashes) that are not traceable to a tracking device?
CC: @janvlug
(in groups, any peer that receives a message can pass it on to others later)
the need for others to share the same platform is somewhat artificial: we'd be better off with protocols that multiple different programs and platforms could use to exchange messages. but the centralizing 'app' mentality pushes us the wrong way. Email, XMPP and the Fediverse, for some examples, have different servers and different clients, and they all interoperate to some degree. now, maybe you consider the protocol as the platform.
anyhow, GNU Jami would likely benefit from different applications, including TUI and CLI. GUIs are often inconvenient and constraining.
we don't need server, so we can't need server integration.
phone book? what phone?!? who needs anachronic phone numbers when we can have mnemonic nicknames (backed by crypto-strong hashes) that are not traceable to a tracking device?
CC: @janvlug
@lxo @janvlug I think this approach of a single solution will work for everyone does not help in mass adoption. And unlike GNU/Linux mass adoption is crucial for a messaging platform. If we blindly try the same strategy we use for GNU/Linux, without understanding the network effects and forced usage, we are not going to succeed. The challenges have changed and we can survive only if we adapt. I'm not saying we must use phone numbers, we should interopetate with people who want that.
who's this mythical person who wants phone number integration though?
I don't know of any person who as much as cares about that, it's just a requirement imposed by the (snooping) platform providers as far as I'm concerned, and one that excludes (as in phase out) other computing platforms to force the cattle towards the slaughterhouse
the challenge of interoperation that we're up against walled gardens full of prisoners, not that we don't use phone numbers that enable user tracking
apps that work on phones, but not exclusively on phones, are certainly part of the solution. but they need no integration whatsoever with phone numbers. phones are mobile computers with tracking devices on them. we need to focus on the mobile computers part, and reject the user-tracking aspects with as much strength as possible
CC: @janvlug
I don't know of any person who as much as cares about that, it's just a requirement imposed by the (snooping) platform providers as far as I'm concerned, and one that excludes (as in phase out) other computing platforms to force the cattle towards the slaughterhouse
the challenge of interoperation that we're up against walled gardens full of prisoners, not that we don't use phone numbers that enable user tracking
apps that work on phones, but not exclusively on phones, are certainly part of the solution. but they need no integration whatsoever with phone numbers. phones are mobile computers with tracking devices on them. we need to focus on the mobile computers part, and reject the user-tracking aspects with as much strength as possible
CC: @janvlug