dat / ready-to-use

[callil]

Initial thoughts on how this tool might develop

dat-ready-to-use would be a no-config rpi setup that would drastically simplify the UX of being a part of the dat network.

For instance:

1. plug in pi
2. navigate to dat.local on any computer
3. add dat url to configure and turn on mirroring services (content and peers)

Some sort of front-end gets you the ability to add custom urls - fine tune peering settings etc.

This tool could be especially useful when connected to mesh networks or small local networks to instantly peer and support access to content and services within the network.

It can also act as a proxy for a regular users beaker browser pinning habits. Maybe beaker can build in a small utility to turn on peer mirroring so this node would automatically add any pinned sites in beaker to the list.

It may also be interesting to eventually think of this tool as less of a mirroring tool, but actually the permanent peer through which services like social networks on dat run. With multi-writer people would get the ability to edit permissions and their own information from any computer provided they can authenticate the private key (like google authenticator)

[callil]

a figma napkin sketch to get this idea out there.
the site is just a dat with a gui for entering configs - behind the scenes there would need to be a small node app restarting the swarms and speaking to dathttpd when things changed along with some simple logging.

There are some other interesting ideas that popped up when I was thinking about this. Communities could seed dat sneakernets like this proposal https://github.com/m-onz/hyperdat-paper that are one click ways of joining a mass swarm for your neighborhood or learning-group

One route might be to essentially fork hashbase - or make a similar service with a focus on self hosting and management.

[neauoire]

I have a rasp pi image which does something very similar.
It automatically streams all sites found in /pi/beaker and makes them available to all connected devices. I would be happy to help with this project.

[callil]

@neauoire this would be a big help. Does your tool have a front end for adding sites yet?

[neauoire]

No, as I think that would be more cumbersome than not. Managing RPi through SSH seems like the way to do it. I could build a blessed based front-end with instructions, but it works so well headlessly, and is so simple that it might not be necessary.

To monitor traffic I use the dat tools to see the number of peers, but could be added to the blessed front-end, made to look similar to your preview image up on top here :) Let me give this a try.

[louiscenter]

I'm seeing the value in building a GUI that's accessible via dat.local in the browser. ssh, blessed, and /pi/beaker won't mean a lot to those who don't come from a background in writing code, and it would be nice to aim projects like this at a broad audience.

if @neauoire is happy to provide his code, I'd be happy writing a choo front-end for it that writes and updates things inside of pi/beaker.

[louiscenter]

likewise, this could tie into the hypercored related front. a choo app for hypercored would be fire.

[neauoire]

That sounds good, you can control the backend tools easily, as everything I'm doing for this is npm based, and enabling/disabling sites would be a text file.

So, just to make sure I'm understanding correctly. The end game is:

• To distribute an .img file that people can burn on their SD card.(I can make, it will be Raspbian)
• That automatically starts to serve content upon being powered.(That's what I have already)
• Reachable to through dat.local (the url of the front-end control panel)
• With control tools that allows to manage dat sites and content existing on the SD card.(A list of available sites, with enable site / disable site front-end options)
• For the non-programmerkin.

[urcades]

I'm seeing the value in building a GUI that's accessible via dat.local in the browser. ssh, blessed, and /pi/beaker won't mean a lot to those who don't come from a background in writing code, and it would be nice to aim projects like this at a broad audience.

yeah, everything here resonates strongly — something you can literally plug into a wall and browse to on a phone or laptop nearby would be incredible

[louiscenter]

@edouerd @neauoire @callil if anyone wants to whip up a design, I'll start the choo repo. I could also just start with cal's above?

[urcades]

yeah, you can def start off with what cal has defined above! in general, a lot of our works are longer-term/form in nature (and will likely evolve over time) but there's nothing stopping us from getting something out there now

[callil]

I think you can start with the above - it was a super quick sketch though. @louiscenter I can also write the front-end with you.

Here is the working document. I will look at this a bit more seriously tonight and maybe we can work through comments on the figma.

I think we should aim for what @neauoire has outlined above. Can we also add the ability to confiugure custom domain names to the tool the way dathttd does? Also eventually being able to get this on a droplet via docker may be a really valuable step too.

Also, how should we align the pieces of this project? We may want to start a team/project repo to align a bit more so there is a single source and open some of these ideas as single issues. Are you all ok with doing it in newcomputers org?

[neauoire]

Assign me a repo and I will use it to assemble the parts for the backend.
I think that providing a linux image with everything installed and ready to be connected to the wall is a better option to the non-programmerkin than having to run a shell script through SSH. So I will focus on that.

[louiscenter]

@callil spin up any repos within newcomputers and lets give it a go! I'm happy to setup the skeleton for the front-end if you give me a repo to work from

[callil]

Actually - let's keep this repo for this project I'll move the rest to a guides repo unless someone has major objections.