#fledger #danu #decentralized #p2pinbrowser #webrtc
Took up some work on fledger/danu - cleaned up once more the way it connects to other nodes. It's incredible how many things can go wrong when doing decentralized systems :)
I'm also working on creating a simple to use npm library for danu. So you can do something like:
```
node = await DaNode.from_default();
let home = await node.get_page("/");
// home is the content of the landing page now
```
#Danu #Fledger That was quite some cleanup session for Danu/Fledger:
- reduced idle network load by about 95% to 500Bps
- cleanup of all my modules to follow the new templates
- fixed a bug where pointing to a page deleted the private keys (oupsi)
- more regressions - I really need to add some tests there
- nicer logging in the CLI
- more fixing of the WebRTC (Dis)Connection - now it also works in Helium...
Meet #Danu, the new #Fledger! It can finally share data in a Distributed Hash Table (#DHT), and now it can also update this data! At least on the CLI...
The first example here is the actual homepage of the system, which is stored in the DHT. I'm so happy this actually works now!
When you go to:
Your browser connects to the other nodes, synchronizes part of the DHT, and then shows the homepage of Danu.
Coming up: storing your own webpages on Danu!
OK, #fledger is starting to come together nicely. I made some progress with my decentralized sharing app in the browser. It now has a kademlia-based DHT which allows it to store webpages. The chat is still based on a gossip protocol.
Upcoming:
- new name, Fledger is really difficult to spell and describe :)
- store your own webpages on the fledger network, directly in the browser
- add identities to combine multiple nodes
Give it a try at
Leave a message in the chat!
Yay - did some work on the networking part of my pet project, fledger. WebRTC connections between nodes should be much more stable now, including browser.
Crazy take: let nodes run for longer than 20 minutes w/o restarting!
Perhaps one day I'll finally implement something useful with it, besides a web-proxy?
@simon Of course, real nerds build their decentralized network first, before writing their blog post software.
Oups - forgot to write the blog post now... But at least I have a blackboard and a web-proxy :)
Upcoming: blog post for fledger. ETA: 2 years...
I'm very happy to have a new version of #fledger, the #decentralized system in your #browser !
To join the network, all you need to do is to point your browser to the following url:
And off you go, participating in a decentralized network. No need to install any binary, proxies, whatever. Even though you can also run it as a binary on a server.
Currently there is a blackboard where you can post messages, and a simple web-proxy service which allows to use another node to send GET requests.
We have a semester-student project at #C4DT_EPFL together with #DEDIS to add a #mix_network. I'm curious how this will work with the web-proxy.
I never liked CORS. It makes problems, and after years of fighting it, I'm still not sure what problem it tries to solve.
Now I have a new grudge against it: for my https://web.fledg.re decentralized project I wanted to add a "proxy" functionality: it allows the app running in the browser using another browser to make a GET request. Once you throw in a mixer, you have a simple anonymous surfing system.
But: CORS! Of course you cannot connect to any remote website from javascript in your browser. So my marvellous project doesn't work :(
I'm preparing slowly to start investing some time in my #Fledger project. It's a #distributed application running in the browser. The connection between browsers is done using #webrtc .
It is written in #rust, compiled to #wasm for the browser, and a libc-binary for the CLI. I want to add more modules to make a distributed web-hosting system. You can have a look at some proof-of-concept here - please leave a message:
Today I presented a poster at #suriEPFL and had some interesting discussions.
#programming #software
Linus Gasser
ineiti