Caropc6 commented on Caropc6's post: @Kaffie: there and who wrote this text there was not me, it was @ssdifnskdjfnsdjk
==========
original PT-BR
há e quem escreveu este texto ali não fui eu, foi o @ssdifnskdjfnsdjk

Caropc6 commented on Caropc6's post: @Kaffie: yes, thank you for your job :D
A big hug for you, thank you

Caropc6 commented on Caropc6's post: @caryoscelus: yes I understood, and yes the translation was good, is that translating this my text translated by google translator, must bugar, but taking your original text and translating to portuguese in google translator, is easy to understand

Caropc6 commented on Caropc6's post: @Blurhy: "Ah, not unique.
That's ok to be decentralized, because id is just a name binding to the public key"
the name or id, i know it is not unique, because there is no way to be unique if it is decentralized unless you use the namecoin network, but i prefer it this way, which uses ALL directly within the zeronet network, i think more safe like that without relying on anything outside the zeronet network: D

Caropc6 commented on Caropc6's post: @Blurhy: KaffieID not only uses zeronet, does it use any servers at clearnet?
I didn't understand your answer: /

Caropc6 commented on Caropc6's post: @Blurhy: ok, but what's wrong with the KaffieId id system, from what I read, seems to be totally decentralized, I prefer any system that uses things from zeronet itself to work, which seems to me to be the case with the system made by zeronet. DEV Kaffie (http://127.0.0.1:43110/Me.ZeroNetwork.bit/?Profile/12h51ug6CcntU2aiBjhP8Ns2e5VypbWWtv/1NWh3WAty57FH8at1WtrZigMrdhrDkuPzh/), the KaffieId

Caropc6 commented on Caropc6's post: @Blurhy: no, but that's what I read so far, is there any information contrary to it?
If you know, please speak, thanks: D
Because I want to use EVERYTHING as DECENTRALIZED POSSIBLE

Sites:
[Syncronite](/15CEFKBRHFfAP9rmL6hhLmHoXrrgmw4B5o/)
[Mother Of All Blocklists](/1LgqZfbtr6dukbjHdjWBEmmthq1shEv3y1/)
[Kave](/4Kave.bit/)
[App 0](/1E7wdLyfWBZAJoPtk7t7dxBAdVFDkWpKrX/)
With App 0, you have to return before adding a shortcut. Possibly Android only.
Contact:
I'm on Wire. Search for @styromaniac or visit https://get.wire.com

Sites:
[Syncronite](/15CEFKBRHFfAP9rmL6hhLmHoXrrgmw4B5o/)
[Mother Of All Blocklists](/1LgqZfbtr6dukbjHdjWBEmmthq1shEv3y1/)
[Kave](/4Kave.bit/)
[App 0](/1E7wdLyfWBZAJoPtk7t7dxBAdVFDkWpKrX/)
With App 0, you have to return before adding a shortcut. Possibly Android only.
Contact:
I'm on Wire. Search for @styromaniac or visit https://get.wire.com

From decentralization and distributed point of view it appear to me like it is better NOT to use .bit name and promote site with internal address like 127.0.0.1:43110/15psKMf7iWZNdos5iKNQRTwu31hXEM9gFi ?

I personally prefer the simplest and most practical solution, although it seems a bit ugly to leave with bitcoin addresses, I prefer it, just as I prefer your ID system, because I try to use the most decentralized thing possible and that is practical and fast at the same time. time.

Of course always remembering Zooko's triangle, that so far, we can't have all three things at once.

Yes. Like all blockchains, namecoin is prone to a centralization of invested wealthy parties, and a reliance on centralized internet infrastructure. Any system that guarantees name uniqueness suffers from this problem. For example if we turned zeroids into domains (which is actually a thing that has been done in the past). There's still a centralized manner of guaranteeing names are unique. Non-legible names (the raw addresses) are unique but lack legibility. This is a known problem of decentralization. The .bit fetching of names is done on your local machine, as it fetches it from the zeroname website (which has a centralized backend that updates from namecoin). You can configure zeronet to use a local instance of namecoin, if you prefer it.

if i promote my site by mentioning its .bit address and then will not renew the .bit name, people will fail to access my site and many will NOT even find the zite "internal"/real address

ZN is currently configured so that if the namecoin domain expires, the registry still maintains the entry until someone else purchases the name and uses it for a new ZN site. This is happened to my network of sites. My domains expired and were immediately bought by others, but not ZN users, so the names still point to my site, but without my control.

From decentralization and distributed point of view it appear to me like it is better NOT to use .bit name and promote site with internal address like 127.0.0.1:43110/15psKMf7iWZNdos5iKNQRTwu31hXEM9gFi ?

Yes, that's the ideal, though it's a bit inelegant. If someone visits your site through the .bit, its stored via the actual raw address. So if your name is compromised, you can just instruct your site to not rely on it, and users will still have your site accessible via the raw address.

If there are any work arounds? I appreaciate if you explain it. Thank You

No. There's a plugin for ZN that allow you to use zeroid names as domain names. Since your zeroid is unique and tied to a particular address, you can make a DNS registry on that address to get subdomains. This avoids a centralized blockchain, but relies on a uniqueness-guaranteed ID provider (which in tern requires a centralized backend).

Zooko's triangle. Look it up.

This page is a snapshot of ZeroNet.
Start your own ZeroNet for complete experience.
Learn More