** Now in Android and iOS app stores **
No Face, No Name, No Number, No SIM card, No Internet! Berty is a messenger that doesn’t require any of your personal data or network connection (using Bluetooth Low Energy BLE). All conversations are encrypted with end-to-end encryption, in a fully distributed network.
It is a peer-to-peer messenger with no servers, no cloud - your data is only stored on the device where Berty is installed and used. No one would be able to access the data or shut the app down, not even the developers.
Being P2P, it means the IP address needs to be available to route messaging, but their site explains a bit about how they’ve tried to mask this. Whilst Briar is an excellent alternative, it is still Android only. The closest alternative is maybe Jami, but it lacks a non-Internet Bluetooth alternative if I recall correctly. Interestingly, Berty also can use Airdrop (iOS to iOS) and Android’s Nearby as alternative protocols.
You can share your details and add contacts via a QR code, public key, or an invite link. It is currently available on both iOS and Android, with desktop clients to follow.
#technology #messenger #berty #P2P #IPFS #privacy
The only ipfs component it uses is libp2p, right?
So we decided to abandon our custom network to start Berty V2 from scratch based on a full IPFS node […].
Wat, that would be insane battery usage. They would have had this problem anyways, just because they do p2p messaging, a c2s model is way better for battery life. But going with a full ipfs node?? Whyyy, what purpose does it have? Content-addressable storage isn’t really any use to them, right? Do they want to integrate filecoin?
berty uses gomobile-ipfs, which is a version of libp2p adapted to run on mobile, therefore much more efficient, but also less capabilities iirc; gomobile-ipfs is rather efficient in my experience, i run two apps that use it and don’t notice any unusual battery drain
the reason to run a full ipfs node is in order to pin(upload)/download content to ipfs, you have to run one if you want to do that; you can sort of get around it by using the ipfs-http-api, but that defeats the purpose of using ipfs, as utilising the http gateways makes the entire thing censorable and centralised
