Many consider that #p2p contradictory to such use cases as organizations, project teams, tasks, wiki, Jira-like or YouTrack-like software, and other use-cases that require restricted access and support of permissions.
But implementing such things would be a fascinating goal per se.
Sadly I don;t have too much time to spend on that, and I am not a pro in P2P development, just a newbie touching this scope with curiosity in this context.
@koteisaev
You don't necessarily need new skills to build #p2p apps these days.
I'm finishing off a demo app which publishes websites to #Autonomi and also acts as a viewer.
I can't really call it a browser because it is very basic, but it does one thing that the current web tooling doesn't support: you can browse every version of any published website, forever. No link rot!
Using #TauriV2 I can build for desktop and mobile, and have done early testing on Windows, Linux and Android.
Having beaten Windows .BAT files and FTP into submission on one laptop (thanks #WinSCP) while getting my #TauriV2 app to build for #Android on another, today I will be figuring out how to debug it with #AndroidStudio.
It almost works. I can call #RustLang from the #Svelte GUI, but my custom protocol handlers aren't being called. 🤔 #Tauri
Today I'm migrating my working but buggy demo from #Tauri v1 to the v2 beta.
So far so good. One area needs work because they've removed the tauri::http crate which I use to build Response structures. I can't see how to do this with tauri::request which is offered as a replacement, so need to find a protocol handler example for #TauriV2.