Discuss mailing list

[Brutalent <brutalent AT email.com>]

The ORK domain prevent the spam like Bitcoin. One id one domain. We prevent all malware protection for single domain. Operative Ring Key prevent fraudolent transaction or scam. 

Il 29/set/2017 02:15, "Christopher" <weblionx AT gmail.com> ha scritto:

First, it's up to you to be a member of OpenNIC and propose the vote.
Note the requires on the wiki for starting a new TLD. Secondly, if a
vote was brought right now I would vote no as I still do not
understand how this is going to integrate. Lastly, a one year old
Twitter account with 200+ followers is not really a great way to
verify anything.

If you could spend maybe an hour making a diagram showing ORK
integrates with DNS and your TLD of .ork and preferably how it would
be used by someone, I would be a lot happier with this proposal.

So, my current understanding is you generate an ORK address/coin/key
and that becomes a domain under the TLD. How are the entries resolved,
is that part of the key? Would all Tier 2 DNS servers have to run an
ORK client or would your T1 provide that information?


On Thu, Sep 28, 2017 at 6:54 PM, Brutalent <brutalent AT email.com> wrote:
> For security ORK tld register is valid for twitter account with minimum 1
> year old and 200 followers. The totally security doesn't exist. OpenNic is
> an alternative dns, but not provide for viruses. The people want new
> projects. Null domain or bbs are strange domains, operative ring key is a
> simply id with support of any technology. Please valuate this project.
> Thanks.
>
> Il 29/set/2017 00:05, "Jeff Taylor" <shdwdrgn AT sourpuss.net> ha scritto:
>>
>> Since the person who wrote that paper saved it as an image, there is no
>> way to search for specific text.  So why don't you just tell me how you plan
>> to use decentralized transactions to create domains that can be connected to
>> a known owner?  The parts of the whitepaper that I did read seem to indicate
>> ORK is exactly as anonymous as .bit.  Can you point to which pages describe
>> how you can identify the owner?
>>
>> I'm especially curious about this "built-in Turing-complete programming
>> language".  If ORK allows scripts to run within the anonymous transactions,
>> how do you identify the true owner of the script if it does something
>> malicious?  More importantly, how do you stop it when someone decides to use
>> that language to write a virus?
>>
>>
>> On 09/28/2017 07:51 AM, Brutalent wrote:
>>
>> This is a WhitePaper link: http://docdro.id/A01DlMP
>>
>> 2017-09-28 1:35 GMT+02:00 Jeff Taylor <shdwdrgn AT sourpuss.net>:
>>>
>>> You didn't answer how you intend to *prevent* scams and malware on
>>> domains if nobody can contact the owners.
>>>
>>>
>>> On 09/27/2017 04:41 PM, Brutalent wrote:
>>>
>>> Ok we want create a ORK Tld register. We host the server and project. Not
>>> want scam or malware, want use ORK Tld for id with redeable webpages.
>>>
>>> Il 27/set/2017 23:53, "Jeff Taylor" <shdwdrgn AT sourpuss.net> ha scritto:
>>>>
>>>> How do you propose to prevent abuse similar to what we are currently
>>>> seeing with .bit domains?  If you are trying to obfuscate the domain
>>>> information, how will individuals be held responsible for damaging botnets
>>>> or distributing malware?  If you cannot identify the owner of a domain, will
>>>> YOU be taking personal responsibility for their content and any damages
>>>> done?
>>>>
>>>> You said you need OpenNIC support to regulate the ID addresses.  I
>>>> assume these ID's will correspond to individual domains?  What role do you
>>>> expect OpenNIC to play in regulating the addresses?  OpenNIC will not host
>>>> servers for you, nor will anyone write software for your project.  OpenNIC
>>>> provides DNS only, the rest is your own responsibility.
>>>>
>>>>
>>>> On 09/27/2017 02:46 PM, Brutalent wrote:
>>>>>
>>>>> Sorry, but not know voting system. This is OpenNIC. Why don't like ORK
>>>>> project? I'm serious and we don't want create a partnership. We make a
>>>>> simply TLD for support it. Thanks.
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --------
>>>> 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
>>>
>>
>>
>>
>>
>> --------
>> 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
>



--------
You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org