discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: Erich Eckner <opennic AT eckner.net>
- To: "discuss AT lists.opennicproject.org" <discuss AT lists.opennicproject.org>
- Subject: Re: [opennic-discuss] Manufacturing Zones inside OpenNIC
- Date: Wed, 14 Oct 2020 07:25:40 +0200 (CEST)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wed, 14 Oct 2020, Nicholson-Goult Hayden wrote:
I hate to butt in, but I too had a TLD idea to replace .neo, Either .code or
.codes, this have many uses like:
[name].codes
php.code
my.code (Possibly like GitHub)
Read.code
Lets.code
Then possibly free code storage at store.code? I can see endless
possibilities for this TLD. I already have a system for how it would work as
I host my own private TLD, and maybe a self signed certificate generator for
the tld. So you install the root ca, and all is trusted.
What do you think?
This sounds nice to me, but why don't you start a new thread about it? ;-)
regards,
Erich
-----BEGIN PGP SIGNATURE-----
11:27 pm, 13 October 2020, Jeff Taylor <shdwdrgn AT sourpuss.net>:
OK but I think you're missing the point. You are trying to
reach out to an industry of generally non-technical people (I.E.
not computer geeks). HOW are they going to view the domains in
your TLD? In most cases of manufacturing equipment that I am
familiar with, the computers are rigidly controlled to ensure
there is no chance of virus infection or unintended software
updates. So not only do you need to convince other
manufacturers that it's worthwhile to change their DNS settings,
but you also need to develop the software for their computers to
keep up with a changing list of DNS servers, and probably be
capable of reliably making the initial updates to their
computers. And you've already stated that you have no interest
in maintaining a TLD server, so I'm not sure who you expect to
write and maintain the code to update multiple operating
systems?
Beyond that, who will these manufacturers call for assistance
when they have trouble reaching the internet because the DNS
updates failed? Who will they call to support them when they
have trouble creating or renewing a domain? This TLD is your
project, so you are ultimately responsible for supporting your
customer's domains. Is that something you are ready to take on,
or are you going to tell them to join this mailing list and wait
a few days for someone to answer their queries?
The reason I keep saying Opennic is not suitable for commercial
applications is because you are asking businesses to change the
very core of the way their computers connect to the internet.
Imagine if a company goes offline for an hour -- how much money
did they lose during that period? How much did they pay someone
to troubleshoot the problem and get them back online? And how
does that compare to the $10/year that it costs to purchase a
domain from ICANN and avoid the potential loss of business?
On 10/13/20 3:47 PM, postmaster wrote:
There are at least a few dozen small shops in the NW
suburbs of Chicago, and that is all I care about. Those
shops cannot afford any Industry 4.0 advancements, but I
can help them to begin with digitizing their production
floor.
You must work in manufacturing to be able to see most the
opportunities - yes, commercial opportunities. For
example, for 3D printing I specialize in movement and
storage, such as dovetails and rails. Some of my
prototypes are printed in PLA, then they are fitted with
shim stock to reach accuracy. The plastic dovetails are
opened to fit and route electrical wiring and mount
sensors such as limit switches, cycle count, temperature
and heat sensors. The PLA later is going to be replaced
with molded nylon, the standard screws with precision
threaded rods, the walls of storage with pierced steel. I
help people design so their printed plastic is as close to
manufacturing capacity as reasonable or practical.
OpenNIC has a purpose, more later. industry 4.0 is a
service stack, mostly edge-computing with proprietary
gateways to the sensors and process - much like the
self-checkout stations you see everywhere. In
manufacturing this is much more complex, and it is still
evolving. The reason i got into MAAS is to free myself
from ICANN, and via VPN like ZeroTier or similar
thechnologies make the NW Chicago Factory 4.0 network -
entirely ICANN independent possible.
The only reason you do not see how this could fit together
is because you, unlike me, is not researching this for
years. Industry 4.0 is way too large and too expensive for
99.99999 percent of factory floors. I have much better
ideas and solutions.
But I am not going to write more until there are a few
people interested. Again, manufacturing is not as exiting
as free software or the theory of anarchy. Its a
repetitive, rigid and unforgiving environment, but not
without room to play.
On 2020-10-13 15:11, Jeff Taylor wrote:
So let me ask you... Who is your target
audience for creating this
TLD? There is no commercial application for
it, but it sounds like
you want to create a domain space for
manufacturers. To me that
appears contradictory, so I'm curious as to
what purpose you think it
would serve?
--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing
discuss-unsubscribe AT lists.opennicproject.org
--------
You are a member of the OpenNIC Discuss list. You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org
--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing
discuss-unsubscribe AT lists.opennicproject.org
Hayden A N Goult
iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl+Gi9UACgkQCu7JB1Xa
e1qL+Q//dCXVej5/UHm8Fgef7C4vzTPKS9SMEvQNYbJdzO7V8ero+uLnRpeqpjJz
zUwjpNkGAaj1jcGuqCt4q4fEY7Sw1nE22y8sz7gyNApHqyixqmDD0pTNtaSexFCQ
seBK5vLpwFFHktjy0AEWuks9DdAvkojgkhqVxtKft5dIGU1gD5A+Ig2Bepe9V0IK
VMwKcoldSIOvUM/6cqOLIUwF9wX+3+FwRJuEy1CwM9S2y4yUZSHHe8YFhNey82tM
YwCfRu1VPQQGlX/xsZVC0Mh787FoF1oa6ccF3BAfQnxyKYBup9cnE5L55WAzn1yu
kIrye259+hzbbvo5TuEqnTvlulJ0EZvgm3XOhpToWODuv7Pfe+BSBBG8yxeceduZ
Il7ULf6ToV4A6wh8wKcDvlsy6qJCywT2ggypqD9Czzec4BOkE3SR1x6CgqjPEhv6
Lbk0e+zegdONjie8mzbcW/XrL0JdWOx+zfdDhQ87SV2DOkqGCQ3waM235ab424p5
2dTxwVBghLNU8OhRVjMt8uHEyZh9S5aAhzYJUiaaOynRzamr3ufTpYlTPuatxtRb
k7yW+6s6BWv1kB3tpgfvoQy3IBawAnglE6pMoKB/gw+kbw1+tX9Op4LqN+NmAImz
QfjM8mLY8BxVCWNB7XtGFqfIfYM8n21zUK0XaJcI7PXxmEMxnLA=
=7Ci/
-----END PGP SIGNATURE-----
-
[opennic-discuss] Manufacturing Zones inside OpenNIC,
postmaster, 10/12/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Charles Wyble, 10/12/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
postmaster, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Jeff Taylor, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
postmaster, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Jeff Taylor, 10/14/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Nicholson-Goult Hayden, 10/14/2020
- Re: [opennic-discuss] Manufacturing Zones inside OpenNIC, Erich Eckner, 10/14/2020
- Re: [opennic-discuss] Manufacturing Zones inside OpenNIC, postmaster, 10/14/2020
- Re: [opennic-discuss] Manufacturing Zones inside OpenNIC, Erich Eckner, 10/14/2020
- Re: [opennic-discuss] Manufacturing Zones inside OpenNIC, postmaster, 10/14/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Nicholson-Goult Hayden, 10/14/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Jeff Taylor, 10/14/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
postmaster, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Jeff Taylor, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
postmaster, 10/13/2020
-
Re: [opennic-discuss] Manufacturing Zones inside OpenNIC,
Charles Wyble, 10/12/2020
Archive powered by MHonArc 2.6.19.