@delta so yeah, #deltaChat does proper #E2EE with #SelfCustody in a #decentralozed, #SelfHosting capable fashion.

  • Whilst one may argue that #IMAP & #SMTP as well as #PGP/MIME were never "designed" for that, they do work reliably, don't require much cooperation (cuz even the strictest #CGNAT allows #eMail!) and can be transparently shoved through #VPN|s & @torproject / #Tor without much fuss.

Plus the "store & forward" architecture of #eMail lends itself to #AsynchronousCommunication, making it a good option when people need to "keep it brief"...

  • Add to that existing technologies like "#DataMule" style units to provide almost-#airgapped communities with "high bandwith, high lantency" connections as well as #SATCOM, I'd not be surprised if delta chat would work excellent everywhere on the planet - regardless if using #Iridum in #Antarctica, 10GBit/s FTTH in Sweden or uucp in Western Sahara.
In Sync, Yet Apart: Understanding the Dynamics of Asynchronous Communication - wpWax

Unlock productivity & collaboration with asynchronous communication. Embrace flexibility & efficiency in the digital age.

wpWax

Zulip is absolutely underrated as a chat platform for teams. Its automatic threading makes it so much easier to catch up on previous conversations than with Slack, Teams or Discord. In my opinion, Zulip is ideal for distributed teams who prefer to work and communicate asynchronously -- like my team, for example.

And it's 100% #OpenSource!

Check it out at https://zulip.com/!

#Teamwork #Chat #Collaboration #AsynchronousCommunication #RemoteWork #RemoteCulture

Zulip — organized team chat

Zulip is an organized team chat app for distributed teams of all sizes.

Zulip
@wakame @gilest File transfer could be done with something like magic-wormhole, there really just needs to be a user-friendly UI (problem is that it's a synchronous-use program).

Something like NNCP + syncthing for uninteractive multiple-retry would also be an option (based #AsynchronousCommunication).

(Supporting Veilid would be useful for all of those, since it takes care of the TURN-style & relay shenanigans necessary for NAT traversal and other similar annoyances.)

The homepage/blog can just be content-addressed, but it'd need to be in the Freenet/dat way rather than IPFS: not just addressing the content but incorporating an encryption key so that various caches along the path that do not have the capability/link for the decrypted file can't decrypt it. (Yes, all of those support mutable/updatable documents.)

(I'm working off the notion private = restricted access, otherwise encrypting the document is completely unnecessary.)

Calendar/Email can also be handled with NNCP over Veilid. Calendar more specifically could also be handled with a mutation capability for an encrypted content-addressed document (which I suppose makes it more a reference to another document then but whatever, precedents already exist as I mentioned prior).
@dalias @_L1vY_ @lauren Correct, I do not foresee a way for them to really destroy NetNews and other highly-asynchronous communication networks.

"The (Use)net interprets censorship as damage and routes around it" line, essentially.

They would most likely manage to kill ActivityPub, because most of its implementations have little to no tolerance for disruption, have garbage support for transport-diverse networking and do not properly support #AsynchronousCommunication... but a lot of other options, some newer and some a lot older, do have very good support for those things.
@normjess @david I'd say ultimately anything that is server-centric is priming itself for abuse.

Anything that makes no provisions for #P2P and/or #AsynchronousCommunication (for basically anything that isn't expected to have a live real-time operator) also ensures it is unusable in adverse conditions such as those of emergency situations which affect infrastructure reliability.

Basically every time there is some big storm, snow, a power outtage or anything similar here, the mobile phones stop working within 8 hours at most if they didn't drop entirely from the very start. I would be surprised if no one has died as a consequence of this by now.

(In theory mobile infrastructure is supposed to have adequate backup power, though I'm not sure if there's anything legally binding about that here, but the Canadian telecom cartel isn't famous for its willingness to properly maintain its infrastructure.)

Meanwhile CB and HAM radios just keep on working like they always do. That's an example of resilient P2P technology.
What’s New in HelpGent 2.0? [Latest Edition]

HelpGent 2.0 has finally arrived, and as promised, it upgraded the features that can transform how we communicate and engage with our audience.

wpWax

@qwazix @ajroach42 It is thankfully achievable to have something similar with Tor/I2P/Veilid, which I think also solve various issues of the clearnet notably the easily corruptible centralized authorities involved in cryptographic identity verification and attestation.

And also ISPs opposing certain types of traffic on their networks (like MTAs). They simply shouldn't have the insight into said traffic to make that decision in the first place. Their role is to be routing infrastructure, nothing more and so they shouldn't have any more knowledge than necessary to accomplish that task.

I actually have a full Linux computer as my router and no CGNAT (addresses are dynamically reused though, so dynamic DNS is necessary), so I can do the direct end-to-end connection stuff unlike many. It is quite nice.

Of course all of these don't solve the low-latency networking problem and fail to provide resilient #AsynchronousCommunication.

The Tor Project | Privacy & Freedom Online

Defend yourself against tracking and surveillance. Circumvent censorship.

Unfortunate observations as far as #AsynchronousCommunication facilitation goes.

There appears to be no user-friendly way to use #NNCP on #Android.

This seems unfortunate, as mobile phones are essentially purpose-designed mobile nodes capable of bridging networks and being easily carried around.

I don't really have the kind of UI sense that NTs tend to like though, so I'm probably not the best person to rectify this lack (at least in any way conducive to the kind of mass adoption I think Asynchronous Communication should be seeing).

I have complicated feelings regarding #Usenet and #NNTP due to some server-centric aspects.

Granted due to message #gossip the death of any given instance isn't catastrophic and moving is largely unnoticeable, but it still puts some hurdles on usability in adverse conditions.

It still fulfills most of the #AsynchronousCommunication characteristics handily, but that's still a nagging thought, since /most/ instances demand fairly high-uptime to peer and don't allow such instability from peers.