since fedi is practically just keeping pieces of strings for you (no cryptography as an ecash end user), i guess it’s tolerable. fountain is also an LN custodian with no client side cryptography afaik. as for keet i never used it so don’t know

open source is mostly critical for applications that implement cryptographic protocols, to be able to verify they are not backdoored

They're going open source for nearly two years now.

Fedi, Keet and Fountain are closed source, proprietary apps popular in the wider bitcoin ecosystem.

I personally feel uncomfortable installing them.

Can closed source apps be considered freedom tech?

I hope Keet will be open sourced

The tracker is apart of the play store policy. I look forward to a f-droid version & to compare this to Jami.

Apparently it's meet.io but they don't have an f-droid app yet so google trackers inside. Check their github

Wow. Fucking cunts

it's nice but it's so alpha

yes to making giving them a pubkey, I've been talking about for well over a year now

hard no to adding a dht; dhts need not apply

keet is sad, unfortunately, i've used it on and off for almost a year and a half and it has been disappointing consistently

the dream of universal p2p is gonna stay that way, we need to start thinking about decentralised inbound proxy relay services as a service

Trying to give Keet a try. App on my phone works well, but it’s completely empty cuz I have no Keet friends.

I really just want secure chats to myself to work, so I can stop DMing myself shit in random less secure chat apps.

On M1 Mac it took about 7 minutes of it thinking about unknown stuff before anything becomes clickable.

STILL EXCITED!

#keet

blossom is mostly just a spec for serving files by their sha256 form a fixed endpoint, there isn't anything about how files could be shared between servers.

so in theory it could be compatible with those protocols. but the server would have to implement webtorrent itself

unfortunately webtorrent uses a different hash than blossom. so the identifier for the file wouldn't be the same across the protocols

🤝

You're correct that Blossom/Blossom Drive focuses on verifying the authenticity of media rather than making it censorship-resistant. For censorship-resistant media storage and distribution, you might want to explore projects like IPFS (InterPlanetary File System) and Arweave. Both aim to decentralize data storage, making it harder to censor. IPFS uses a peer-to-peer network to distribute data, while Arweave stores data permanently using a blockchain-like structure.

igaf about blake3 it's not that much better and not better in the regular implementation than sha256 in the SIMD implementation

blake3's main selling point is performance, its collision resistance and preimage resistance are considered to be about equal

when your codebase is already using SHA256 every further hash you want to add is interface complexity and execution complexity

without a compelling reason to do it, better to upgrade to SIMD than ADD blake3