There's never been a better time to
abandon Discord and start using Matrix with Element for your communities 💚
#Discord #AgeVerification #Censorship #MassSurveillance #Privacy #E2EE #Matrix
There's never been a better time to
abandon Discord and start using Matrix with Element for your communities 💚
#Discord #AgeVerification #Censorship #MassSurveillance #Privacy #E2EE #Matrix
I want to be part of a flat collective/network of folks / orgs working together to provide resilient e2ee data storage using free software.
Like a file backup / object storage federation of sorts.
I want it to be scalable, i.e. folks and orgs who have spare storage capacity can contribute this capacity to the collective, effectively increasing the collective's total storage capacity. The collective should gracefully handle nodes dropping off or quitting the collective, and re-joining.
The API should be well-known, preferably something like S3, so the collective/network easily integrates as a backend for existing software.
I think there should be some way to 'balance the books' so to speak, to avoid selfish behavior like a participant providing 3GiB of storage and using 3TiB.
The balancing can be in-software, e.g. each participant gets an identity which the software uses to identify how much the participant contributes and utilizes across all their nodes.
The balancing can also be out-of software, through a member system or similar.
Would be nice with a social aspect.
Is there already something like this?
What software would be good for building something like this?
@deuxfleurs would #garage fit this use case?
If I understand correctly, Garage can scale to many nodes in many locations/zones, but 3-4 zones (one of which can be a hot spare) is recommended. If a garage cluster consists of 50 zones with 150 nodes total, will chunks be spread across zones in a way that isn't limited by low-capacity zones? Does the total storage capacity of the cluster depend on whichever location has the least capacity?
Another option I found earlier is @peergos, but I'm fairly lacking in knowledge about the project. Being p2p, would that fit this use case better?
#techCollective #democracy #privacy #digitalIndependence #e2ee #anarchism #p2p
I want to be part of a flat collective/network of folks / orgs working together to provide resilient e2ee data storage using free software.
Like a file backup / object storage federation of sorts.
I want it to be scalable, i.e. folks and orgs who have spare storage capacity can contribute this capacity to the collective, effectively increasing the collective's total storage capacity. The collective should gracefully handle nodes dropping off or quitting the collective, and re-joining.
The API should be well-known, preferably something like S3, so the collective/network easily integrates as a backend for existing software.
I think there should be some way to 'balance the books' so to speak, to avoid selfish behavior like a participant providing 3GiB of storage and using 3TiB.
The balancing can be in-software, e.g. each participant gets an identity which the software uses to identify how much the participant contributes and utilizes across all their nodes.
The balancing can also be out-of software, through a member system or similar.
Would be nice with a social aspect.
Is there already something like this?
What software would be good for building something like this?
@deuxfleurs would #garage fit this use case?
If I understand correctly, Garage can scale to many nodes in many locations/zones, but 3-4 zones (one of which can be a hot spare) is recommended. If a garage cluster consists of 50 zones with 150 nodes total, will chunks be spread across zones in a way that isn't limited by low-capacity zones? Does the total storage capacity of the cluster depend on whichever location has the least capacity?
Another option I found earlier is @peergos, but I'm fairly lacking in knowledge about the project. Being p2p, would that fit this use case better?
#techCollective #democracy #privacy #digitalIndependence #e2ee #anarchism #p2p
RE: https://mastodon.social/@HolosSocial/116007730441888134
We have published a new version of #Holos app (rc-1) that supports #E2EE DMs over ActivityPub.
We wrote a page that explains our E2EE implementation: https://holos.social/e2ee
If you want to discover how Holos app and relay work together: https://holos.social/how-it-works
We are entering a new step in the development of #Holos and we need more people to test.
We have reopened subscriptions through the app: https://holos.social/signup
We wrote a page explaining how we implemented #E2EE DMs over #ActivityPub: https://holos.social/e2ee
Don't hesitate to contribute and share your feedback with us. Thank you.
I'm glad to hear that I will have to take a closer look. Classical encryption is still a deal breaker though because of Store Now Decrypt Later attacks, SimpleX uses the double ratchet algorithm developed by signal, maybe DeltaChat could too idk if that's helpful.
#FLOSS #E2EE #PSA #Privacy #Anonymity #SimpleX #Signal #DeltaChat #QuantumResistantEncryption
A lot of messaging systems try to reinvent the email system but many (signal, matrix, xmpp) took over one key traditional design which we actually dropped while retaining SMTP/IMAP compatibility: server-controlled identities.
With #chatmail user identities are cryptographic and reside on end user devices only. Servers are only message relays and have no control over identities or chats, only perform fast message routing. See this fosdem talk by one of our lead developers https://mirror.cyberbits.eu/fosdem/2026/ud2218a/3F9VTU-deltachat-chatmail-relays-multi-transport.av1.webm
@delta Reminds me of SimpleX, if you can add quantum-resistant encryption and easy multi profile management and throwaway (incognito) profiles like simplex then the privacy and anonymity features would probably be on par and I'd consider switching to get away from the far right dev team.
#FLOSS #E2EE #PSA #Privacy #Anonymity #SimpleX #DeltaChat #QuantumResistantEncryption #FarRight
We are entering a new step in the development of #Holos and we need more people to test.
We have reopened subscriptions through the app: https://holos.social/signup
We wrote a page explaining how we implemented #E2EE DMs over #ActivityPub: https://holos.social/e2ee
Don't hesitate to contribute and share your feedback with us. Thank you.
RE: https://mastodon.social/@HolosSocial/116007730441888134
We have published a new version of #Holos app (rc-1) that supports #E2EE DMs over ActivityPub.
We wrote a page that explains our E2EE implementation: https://holos.social/e2ee
If you want to discover how Holos app and relay work together: https://holos.social/how-it-works
@rzeta0 @analogfusion What there is not however is a single unified platform 'workspace', that people have grown accustomed to like, integrating auth flow with devices & application layer & across the platform space.
Nextcloud, to some degree, have made headway in this regard, at least so far as the sync, drive, calendar, docs, conferencing needs cluster.
Implementing high-reputation & sovereign mail transport with secure webmail atop is especially tricky, which is why I teach it. 2/2
@JulianOliver @rzeta0 @analogfusion #Proton will be there when Proton Meet comes out of beta. It is full suite (well, only dice and sheets ATM but mail, calendar, drive, password manager, authenticator, VPN) and all #e2ee. And easy import from Google.
Only catch is that it is freemium and most people think technology should be free.
@protonprivacy
This is just one reason why I use SimpleX over Signal:
I can maintain several SimpleX profiles each with different static contact addresses and switch between them easily in the official client, and if I need more anonymity than that I can send someone a dm with a 1-time invite. Either way after someone connects to you every dm you are part of uses a different internal pair of addresses for sending and recieving messages which is why its like having a burner phone for every contact
http://isdb4l77sjqoy2qq7ipum6x3at6hyn3jmxfx4zdhc72ufbmuq4ilwkqd.onion/
#deltachat does
- no bindings to public handles/numbers
- no address-book upload
- not do public contact or group discovery
- not have critical persistent server state (!)
Social identification is private, between people though ephemeral #P2P #E2EE messages.
Servers see messages with random sender and recipient addresses, but those can not be mapped to a phone number or public handle. Servers see IP addresses. But you can use Tor, or a VPN, if you want to hide that.
It' not all bad :)
Talk:
#UnifiedPush - #Push notifications. Decentralized and Open Source - Daniel Gultsch, s1m
Sat, 16:00, UB4.132
Visit the XMPP Realtime Lounge in #ULB, AW Building, Level 1!
#jabber #chat #opensource #messaging #federation #Brussels, #Belgium #opensource #rtc #e2ee