News for hackers. Stuff that matters.
Re:What should follow the web? by xj9 on Tuesday September 26, 2017 @11:41PM (#15344750)
make me a p2p app that runs in a browser that has acceptable performance on mobile. I want soft real-time sync between n users with no central router or global data structures. I want to share arbitrary blobs up to 1MiB or so and stream larger data in with bit torrent. my traffic should be anonymized. I should also be able to automatically replicate my data across all of my of devices.
Re:What should follow the web? by digikata on Tuesday September 26, 2017 @11:54PM (#15344792)
Perhaps go back to a sandbox VM model where you access an URI that's a program with attached data objects. Maybe have a standard for updatable "peripheral" modules, but provide standard sandboxed storage, display, messaging, & streaming APIs to start.
Re:What should follow the web? by xj9 on Wednesday September 27, 2017 @01:54PM (#15350438)
yes! this is actually something that i'm slowly hacking away at... and you've described the architecture pretty well!

https://www.heropunch.io/roadmap.html#finally-relax

site still has a few bugs (it isn't officially "out" yet, but its topical so why not).

the sandbox VM is a docker container with a standard interface for storage (relax/vfs), display (wayland), messaging (relax/pub).

vfs supports torrents and partial replication, so you're pretty much always streaming. we try to cache things to keep it fast, but different systems have different storage limits so we have to assume that we're always going to be fetching from the network.

applications can actually consist of multiple docker containers with different capabilities that can be scheduled on any host that has been paired with your user key. these can be updated individually or in tandem.

docker registries have to be explicitly trusted before you can run anything. we realize that docker isn't a security boundary by default, but we are attacking that problem from a few angles.

we implement a lot of this functionality as docker engine plugins. so you get anon overlay routing and distributed storage transparently from the perspective of the application.

Re:What should follow the web? by digikata on Wednesday September 27, 2017 @04:52PM (#15352221)
That sounds pretty reasonable and interesting for prototyping, but also possibly heavy weight to run as a "browser". But I think it's basically what we seem to be moving towards anyway - if we could securely run it, the simplest model of interaction is to just download a program + data and run it.
Re:What should follow the web? by xj9 on Wednesday September 27, 2017 @11:49PM (#15354408)
for "browsing" you'd have a browser app along the lines of patchwork[0], might even be patchwork actually since we use the same core tech. i don't think they need to be the same thing, personally.

[0]: https://github.com/ssbc/patchwork/releases