Hello @cosmin :) The question is not whether there are real, honest use cases for blockchain, but rather whether we want our privacy and personal data to be collected, held, sold and used, as is the case in the main business model of most communication platforms.
Jami is free software for universal communication that respects the freedom and
privacy of its users. At its core, Jami aims to be a complete decentralized,
secure, and robust way of communication for the people.
Hello @lascapi @cosmin It's because Jami was designed with openness, privacy, and freedom in mind. Thanks to encryption, no databases and P2P, you can share and chat with family, friends, or colleagues without your data being tracked, collected or sold.
@xdej @p4bl0 @lascapi More or less, Jami's distributed nature is similar to the blockchain technology.
Except for username management, which uses an Ethereum blockchain smart contract, there are some major differences: — Jami uses no centralized storage of messages or user data, with blockchain, the data is stored across all nodes in the network — Jami uses P2P and encryption, while blockchain uses cryptography and consensus mechanisms
@xdej As usual, the answer is no. The fact is that you can't expect (and you shouldn't want to have) every users of a messaging app to run a blockchain node, so in practice you still have third-party on which end users will depend to consult the directory, and even to register their name I guess. So what was to point of imposing the use of a blockchain to users? @cosmin @lascapi @Jami
@xdej So I just went to have a look at the source code (https://git.jami.net/savoirfairelinux/jami-nameservice) out of curiosity and it is exactly what happens. In practice the blockchain is only used as a backend. So either the goal is actually not to decentralize the name service but only to distribute the archival of the directory, or the implementation is broken. The service itself still uses intermediaries, and end users maintain their local nicklist (just like in I2P hidden services for example). @cosmin @lascapi @Jami
@xdej The distribution of an immutable (but is that even a desirable property?) archive of the directory could have been done using a simple merkle tree structure (e.g., a public Git repository). Actually now that I think of it, it would even have been way easier in that case to offer the possibility to each end user of Jami to get a local copy of the the directory archive and to maintain it up to date. @cosmin @lascapi @Jami
I'm sorry for the confusion, and thank you @p4bl0 for actually looking at the source code.
Here are some clarifications. Nothing is imposed: — The nameserver is optional — The nameserver can run on a database (e.g. JAMS) or any backend https://docs.jami.net/en_US/developer/name-server-protocol.html#name-server-protocol — Users don't roll nameservers locally. Just Jami (which does not roll any blockchain nodes). — The Ethereum blockchain is just one of the possible ns.jami.net backends.
Jami is free software for universal communication that respects the freedom and
privacy of its users. At its core, Jami aims to be a complete decentralized,
secure, and robust way of communication for the people.
Elias
in reply to Cosmin • • •> They say there is no honest,
> real world, use case for blockchain
Whoever says that have not understood the value of having a permissionless system.
I think that anyone who understands why someone might want a permissionless system, will see that there are in fact honest, real world, use cases.
Jami
in reply to Cosmin • • •The question is not whether there are real, honest use cases for blockchain, but rather whether we want our privacy and personal data to be collected, held, sold and used, as is the case in the main business model of most communication platforms.
🌈 Lascapi
in reply to Cosmin • • •Updates on the Jami Name Service - Part 1: Byzantine faults
jami (Jami)🌈 Lascapi
in reply to 🌈 Lascapi • • •Jami
in reply to 🌈 Lascapi • • •It's because Jami was designed with openness, privacy, and freedom in mind.
Thanks to encryption, no databases and P2P, you can share and chat with family, friends, or colleagues without your data being tracked, collected or sold.
Cosmin
in reply to 🌈 Lascapi • • •My understanding is it can't use a database because it needs to be distributed and not hosted on any particular server.
@Jami
Xdej
in reply to Cosmin • • •@lascapi @Jami
Jami
in reply to Xdej • • •@xdej @p4bl0 @lascapi
More or less, Jami's distributed nature is similar to the blockchain technology.
Except for username management, which uses an Ethereum blockchain smart contract, there are some major differences:
— Jami uses no centralized storage of messages or user data, with blockchain, the data is stored across all nodes in the network
— Jami uses P2P and encryption, while blockchain uses cryptography and consensus mechanisms
🏴☠️ MC Pablo ∴
in reply to Xdej • • •🏴☠️ MC Pablo ∴
in reply to 🏴☠️ MC Pablo ∴ • • •@cosmin @lascapi @Jami
savoirfairelinux / jami-nameservice · GitLab
GitLab🏴☠️ MC Pablo ∴
in reply to 🏴☠️ MC Pablo ∴ • • •Jami
in reply to 🏴☠️ MC Pablo ∴ • • •Hello 🙂 @p4bl0 @xdej @cosmin @lascapi
@uriel
I'm sorry for the confusion, and thank you @p4bl0 for actually looking at the source code.
Here are some clarifications.
Nothing is imposed:
— The nameserver is optional
— The nameserver can run on a database (e.g. JAMS) or any backend https://docs.jami.net/en_US/developer/name-server-protocol.html#name-server-protocol
— Users don't roll nameservers locally. Just Jami (which does not roll any blockchain nodes).
— The Ethereum blockchain is just one of the possible ns.jami.net backends.
Name Server protocol — Jami documentation
docs.jami.netJami
in reply to Jami • • •@p4bl0 @xdej @lascapi @uriel
For more info:
https://jami.net/updates-on-the-jami-name-service-part-1-byzantine-faults/
Updates on the Jami Name Service - Part 1: Byzantine faults
jami (Jami)🏴☠️ MC Pablo ∴
in reply to Jami • • •