Discuss mailing list

[kevin <krattai AT gmail.com>]

Hey Jonah,

Yeah, obviously I was also part of that project early on but
unfortunately ran out of available time and had to bail completely.  I
retained those records in case I ever joined back up.  I've pulled the
slaves from my DNS server from the ones that aren't open any longer.

Not intended to be dn42, either.  It's just a reference for BGP and
IPv6, something I think I brought up when I was still part of that
project.  As the public facing FRX page states (limitedly) that DNS
also is a big part, but in no way the only part, so it's not just an
independent openNIC.  Most of the more in-depth description and
discussion is happening inside the network.  The public facing part is
intended to also interest the non-tech adopter, as well and perhaps
especially.

The key part is automated for distributed (mesh).  So the network needs
to be set up, the dns needs to be set up, the routing has to be set up,
and the distributed services need to be set up (think fidonet, cloud,
cluster, etc).  And of course, it has to be simple, so automagic
scripting and SDN and distributed iaas and paas is just as important as
saas.

And part of what I'm also working on is a blockchain-esk methodology so
that people can be compensated for their resources they contribute to
the network as well as being a common currency that is also easily
exchangable and liquid, allowing people to conduct frictionless
transactions.  This has been a side project I've been actively working
on for about 4 years, from a seed of many decades old revolving around
local currencies, barter, and scrip.

Most of it all is close to production with only a couple things that
are just proof of concept.  Just a matter of putting it all together
and making sure that it is seamless, redundant, self healing,
extensible, and efficiently scalable.

Anyhow, that would be great if you are willing and able to provide some
resources.  Those of us here are able to connect together directly with
public IPs, and I'm working with tinc and n2n to start setting up
supernodes to extend the network and mesh for those who don't have
public facing devices.  I already have openVPN running, but I do find
that there's some hesitation on the network from time to time so
looking at other, lighter toolkits to potentially resolve these issues.

Cheers,

Kevin

On Mon, 2018-12-24 at 17:04 -0600, Jonah Aragon wrote:
> Hello!
> 
> Looks like the records you have there were from the FreeNIC network
> that Angelica, vvande, and I were running. I can’t speak for gris and
> quoque, but smart is offline, as is the entire overall FreeNIC
> network for the time being. Feel free to remove smart from your
> servers.
> 
> I’d love to work with you on this project, but I took a look at your
> website and it was very difficult to determine what exactly it is
> that you’re doing. You say it’s similar to dn42 but it looks more
> like just a less restrictive OpenNIC, much like FreeNIC was/is trying
> to accomplish. Unless you plan on extending to other technologies
> besides DNS in the future. I know dn42 is kind of making their own
> virtual internet with VPN tunnels, which is a lot more complex than
> simply peering DNS servers.
> 
> All that being said, shoot me an email if you’d like to discuss this
> further, looks like an interesting project! I’m in the process of
> moving my servers from DigitalOcean to an OVH dedicated server and as
> a result I have a lot more server space I could cheaply dedicate to
> stuff like this.
> 
> Merry Christmas! All the best,
> Jonah
> 
> > 
> > On Dec 24, 2018, at 3:22 PM, kevin <krattai AT gmail.com> wrote:
> > 
> > FRX update:
> > 
> > OK, FRX is running two servers now:
> > 
> > 199.101.56.46
> > 24.76.93.80
> > 
> > They are functioning as openNIC T2 servers, as well.  Not fully
> > resolving IPv6 right now.  My radvd is malfunctioning for some
> > reason.
> > 
> > And, they are now slaving the following tlds from a previous
> > agreement
> > with some members.  The IPs are live and two of them resolve
> > identifiers so I'm assuming they are still functioning.
> > 
> > NB:  For those who operate these tlds, let me know if I shouldn't
> > be
> > slaving them.
> > 
> > zone "gris" {
> >         type slave;
> >         masters { x.x.x.x; };
> >         file "/etc/bind/gris.zone";
> > };
> > 
> > zone "quoque" {
> >         type slave;
> >         masters { x.x.x.x; };
> >         file "/etc/bind/quoque.zone";
> > };
> > 
> > zone "smart" {
> >         type slave;
> >         masters { x.x.x.x; };
> >         file "/etc/bind/smart.zone";
> > };
> > 
> > I've updated the frxdns.html page to reflect the new server.
> > 
> > I will likely be putting bind info onto my github page soon to
> > reflect
> > and to expedite and support the automation of collaboration and
> > peering.
> > 
> > Cheers,
> > 
> > Kevin
> > 
> > On Mon, 2018-12-24 at 10:57 -0600, kevin wrote:
> > > 
> > > That's awesome!  Thanks Sebastian and the others who have
> > > responded
> > > to
> > > the call.
> > > 
> > > I will also be working to get back in touch with those who were
> > > playing
> > > around with a dns peer project a while back.  Hopefully those who
> > > were
> > > part of that will also be able and willing to continue that good
> > > work.
> > > 
> > > I will ashamedly admit that the FRX site is somewhat inaccurate
> > > about
> > > how long I've been toying with the idea.  It originally started
> > > in
> > > proof of concept not 15ish years ago, but rather 20 years ago
> > > during
> > > the Terra Vista VRML project era.  :D  I just didn't quite want
> > > to
> > > admit my age.  lol
> > > 
> > > Anyhow, good things take time.  B)
> > > 
> > > Cheers,
> > > 
> > > Kevin
> > > 
> > > On Mon, 2018-12-24 at 13:54 +0100, Sebastian Makowiecki wrote:
> > > > 
> > > > 
> > > > Hey Kev, hey all :)
> > > > 
> > > > Good stuff. I have (some) time, attention and resources to
> > > > spare so
> > > > keep us updated.
> > > > 
> > > > Wishing you all happy holiday season. Take care :)
> > > > 
> > > > ~
> > > > Sebastian MakowieckiOn 24 Dec 2018 6:34 am, kevin <krattai@gmai
> > > > l.co
> > > > m>
> > > > wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Hey folks, 
> > > > > 
> > > > > Merry (almost) christmas eve to those of you who are reading
> > > > > this
> > > > > on 
> > > > > the (23rd) 24th.  8) 
> > > > > 
> > > > > I'm working on a project called FRX (FReedom eXchange) and I
> > > > > am
> > > > > looking 
> > > > > for people who are willing to peer DNS servers.  The goal is
> > > > > also
> > > > > to do 
> > > > > something similar to dn42 (https://dn42.net/home) if not to
> > > > > connect
> > > > > to 
> > > > > it directly, as well as other technology frameworks.  FRX is
> > > > > being 
> > > > > built out as a distributed infrastructure for distributed
> > > > > applications 
> > > > > and discourse. 
> > > > > 
> > > > > The social community discussion is located on the
> > > > > distributed, 
> > > > > blockchain social community (U.Community), here -> https://u.
> > > > > comm
> > > > > un
> > > > > ity/ 
> > > > > posts/2976 
> > > > > 
> > > > > The project page for non-network connected people is here: 
> > > > > http://aebl.asuscomm.com/frx/ 
> > > > > 
> > > > > If connected to the network, it can be visited here: 
> > > > > http://home.frx/ 
> > > > > 
> > > > > And to speak directly to any questions as to why I don't
> > > > > apply to
> > > > > have 
> > > > > the tlds incorporated into opennic.  Let's just say that it
> > > > > is
> > > > > my 
> > > > > opinion that, even though I really love opennic and what it
> > > > > stood
> > > > > for, 
> > > > > it is far too polluted and exclusive to have a tld on the
> > > > > network
> > > > > after 
> > > > > the recent changes, as opposed to how it once was.  But, I
> > > > > will
> > > > > keep 
> > > > > moving forward with what I'm doing. 
> > > > > 
> > > > > Thanks in advance for your considerations. 
> > > > > 
> > > > > Cheers, 
> > > > > 
> > > > > Kevin
> > > > > 
> > > > > 
> > > > > 
> > > > > -------- 
> > > > > You are a member of the OpenNIC Discuss list. 
> > > > > You may unsubscribe by emailing discuss-unsubscribe AT lists.ope
> > > > > nnic
> > > > > pr
> > > > > oject.org 
> > 
> > --------
> > You are a member of the OpenNIC Discuss list. 
> > You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicpr
> > oject.org
> 
> --------
> You are a member of the OpenNIC Discuss list. 
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproj
> ect.org