@winter #Gnunet (https://www.gnunet.org/en/) also tries to address many of these though it has issues.
Key-based addressing is ultimately the way to deal with collisions and for human-friendly names I consider petnames (https://en.wikipedia.org/wiki/Petname) the best solution to Zooko's triangle (https://en.wikipedia.org/wiki/Zooko%27s_triangle).
#Yggdrassil was sort of a response to #CJDNS' shortcomings (https://yggdrasil-network.github.io/faq.html#why-yggdrasil).
#gnunet #meshnet #Yggdrassil #cjdns
@eater @noracodes There's also #AsynchronousCommunication like #NNCP, which makes no assumption of adequacy & fitness of infrastructure (such assumptions are often wrong).
But also some #meshnet projects like #Gnunet do actually (optionally) handle the lower layers of the networking stack (short of physical itself).
#asynchronouscommunication #NNCP #meshnet #gnunet
Il y a aussi #GnuNet qui mérite un coup d'œil.
Leurs concepts sont assez similaires et le projet est bien vivant.
(J'avais participé à la trad FR. Mon dieu ! Presque 20 ans !!)
@mike805 @jeffcliff @brewsterkahle There's more to it than that. Both #Loopix and #Gnunet Filesharing go into such scenarios as resilience in the face of a malicious majority.
@jeffcliff @mike805 @brewsterkahle Ah, correct. For some reason that very important part about relay membership was completely absent from their main site.
Then I guess it's down to racing with I2P for implementing the additional features to improve on the model's resilience.
For example, their whole Sybil issue has researched countermeasures (and continued research) mentioned in #Loopix and #Gnunet papers (among others) that would be easily applicable to any mixnet.
@lefarfadet @sebsauvage je suis plus intéressé pour ma part, par une nouvelle pile de protocoles telle que #GNUNet
Looked into #GNUNet a little bit today. I like their "throw it all away and rewrite it" approach to the problem of centralization on the internet. Sometimes it's just what you have to do.
https://www.gnunet.org/en/index.html
I didn't know anything about it until @raphadue pointed it out to me. (https://social.tchncs.de/@raphadue@fosstodon.org/109972789844993170)
My search has shown that while not well known, it is a well regarded project. It's been around over twenty years but it still has momentum.
Intro vid: https://youtu.be/qZYI-3Q1INI
I am really starting to get into learning about the #zerotrust security concept. I've also started reading a lot about #gnunet and attempts to create networks that act as an overlay or ride on top of existing infrastructure. The biggest hurdle seems to be metadata. GNUnet is doing some real interesting work on this front.
I am really getting into some of the advanced and experimental aspects of computer networking. A lot of it is well above my my present knowledge level but it is fascinating. My whiskers are twitching. #gnunet
If you zoom out, maybe cloning existing tech was the mistake. Why did #GNU need to clone anything beyond cc, ld and libc? Instead of creating e.g. an Eiffel clone in Sather, they could have doubled down on, say, 1 Lisp (GCL, Emacs Lisp, Guile, whatever) and got to building applications on top.
In this smartphone and webapp age, we still have lots of F/OSS clones of commercial services.
Maybe we need(ed) many more well-thought-out projects like #GNUNet / #GNUTaler.
2/2
Some short-term history: in 2021 we finally mitigated the pitch black attack that had been found by the #GNUnet folks.
With this the friend-to-friend mode that was introduced in 2007 got robust enough that nowadays people can rely on it for hidden #communication.
In the same release (1492) #decentralized streaming of video on demand started to work well enough to share conference talks: https://freenetproject.org/freenet-build-1492-released-video-diagnostics-pitch-black-plugins.html
#communication #decentralized #freenet #hyphanet #gnunet
I believe that this united future can be reached with the help of #technologies that remove central authority that can on a whim lock us out of our lives. #Email, #Matrix, the #Fedivers and other technologies go in the right direction, and the #gnunet once adopted by more people may hopefully move us even closer to a more free future
#technologies #email #matrix #fedivers #gnunet
@strypey a bit into the tech side, maybe the offline-first focus should be at a lower level and work for all apps?
Instead of having to, say, allocate 100MB to cache #Mastodon posts and 5GB to cache #Pixelfed photos, we should be able to allocate all we can spare to, say, #IPFS pinning and all apps should deal with content hashes in their protocol and clients should pull from the local IPFS node rather than a CDN.
https://www.gnunet.org may already be like this #GNUNet
#mastodon #pixelfed #ipfs #gnunet
The worst thing about #gnuNet not having any of it's transports standardized is that I can't read the specs in my spare time. /hj
@1ynx Personally I'm looking forward to #gnuNet reaching a fully usable state and cross-platform compatibility beyond *nix.
And I see it as an easy base for many #p2p programs to use like #filesharing and #communication once it reaches 1.0
#gnunet #p2p #filesharing #communication