-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZeroNet Censorship! .bit domains not working with ZeroNet! #2361
Comments
You need to wait some time so that domains are updated. |
It is updated for about 18 hours now! |
Is it listed here? |
No. |
For that matter another domain I registered and configured more than 2 week ago also not in this list you linked! |
Then you need to wait until it will be. Sometimes this is quick, but sometimes it takes a few days (or more)... |
WTF is this list anyways? Who manages it? Is this not some kind of censorship? Basically saying hey if I don't add your .bit domain to this list managed by me than your .bit domain will not work with ZeroNet! For me sounds like censorship! |
Suprise, @HelloZeroNet manages it... The reason why this list is used is that there isn't any other good option for interacting with blockchain without downloading it. I don't think users will want to download 6GB of blockahain data just to view domain. But if you want using local Namecoin blockchain, use ZeronameLocal plugin. |
This is ABSURD! If @HelloZeroNet manages this list than he can also remove any domain from it which IS CENSORPSHIP! |
Who said that you need to use Namecoin? And how would you interact with it without list? |
This goes to Reddit! Don't you claim that ZeroNet is censorship resistant when one guy can add or remove .bit domains from a list at his own will! And with this blocking zeronet sites! This is how censorship works! |
We've already seen that Reddit really likes you. |
Again, how would you interact with it without list? And who said that you need to use Namecoin? |
Hardcoding it and run a cluster where can access Namecoin blockchain on a few servers. That is absolutely bullshit if he can add or remove domains at his own will! This is exactly how censorship works! |
What do you mean with this? It would still run in centralized servers so there won't be any benefit. |
These are just servers with let's say .onion addresses where ZeroNet connects to check the blockchain. Leaving ZeroNet to open for censorship is absurd and unacceptable! |
And of course that servers can't be compromised or censored. Who runs that servers can still manage all domains. |
I can run the server, I'm not afraid to pay $5 for a server with 20 Gb space... There should be a plugin or something to point ZeroNet to a server with the Namecoin blockchain. Better put this directly into the Config of ZeroNet! But to have one list what one guy manages and he decide what .bit domains will resolve is absurd! |
Yes, but then you can still manage that server.
Domain plugins should be plugins included in core, but not directly in core.
And if you run your server and everyone uses it, you can also manage domains. That is also absurd! |
But the question comes up how others can resolve the domain if they don't have this in the Config of ZeroNet.. Maybe the best would be to have an option to add "bitresolve" field in content.json and there everyone can state the server where the blockchain can be accessible for ZeroNet. |
One thing is for sure this can't stay how it is now! He don't update the list anyway so no matter if you register a .bit domain or not it will not work with ZeroNet without begging mr holly @HelloZeroNet to include those domains in the list. This is absurd! How can someone claim censorship resistance when he himself able to censor any site on ZeroNet???? |
Nobody said that you must use Namecoin. |
Tell this to @JeremyRand who even advertise ZeroNet on Namecoin.org! |
/ban @ezdr You can run a local ZeroName instance or use another DNS like Name.YO. |
The local ZeroName instance will not solve anything because other people unable to visit the mydomain.bit domain anyway! |
Sure, when someone comes and exposes how @HelloZeroNet censoring ZeroNet than he is already attacked, blamed and subject to ban! What kind of person are you? Don't you claim that ZeroNet is censorship resistant when one guy can censor the whole thing! |
Again, in any case, you will have to rely on centralized provider. And just that you know, most programs (browser extensions) that use Namecoin also rely on centralized servers.
Or ENS. Or classic DNS. Or just Bitcoin address.
@HelloZeroNet runs some script that fetches data from blockchain and puts them to Zeroname site. Maybe that script stopped for some reason, but it can be restartzed so your domain will work. And if you rely on another centralized server, that server can also crash and all domains will stopped working. ZeroNet initially used centralized server (DNSChain), but it was discontinued so all domains would stopped wotrking if ZeroNet wouldn't be updated to use Zeroname site.
And relying on your centralized clearnet Namecoin proxy would solve this? |
Doesn't change the fact that ZeroNet can be censored by one guy! |
Again, who said that you have to rely on Namecoin to use ZeroNet??? |
@JeremyRand we need to block in namecoin the possibility to configure .bit domains with ZeroNet! |
? |
@JeremyRand we can check the JSON field data and if "zeronet" is in it than we can block the domain registration or nameupdate. |
Or just block you. |
Again, most programs that use Namecoin (and any other decentralized name system) use it with centralized clearnet servers! Will you block all of them?? |
Just making sure that .bit domains can't be configured for ZeroNet! ZeroNet censoring .bit domains and one guy has the availability to remove any .bit tld from the entire ZeroNet network!!!! |
Every program that uses Namecoin relys on centralized servers!!! |
@JeremyRand @imachug ZeroNet censoring .bit domains and one guy has the availability to remove any .bit tld from the entire ZeroNet network!!!! |
Every program that uses Namecoin relys on centralized servers!!! |
@JeremyRand @imachug ZeroNet censoring .bit domains and one guy has the availability to remove any .bit tld from the entire ZeroNet network!!!! |
@HelloZeroNet Close this issue please. |
And update Zeroname list 😀 |
Beside the usually spamming antifa (or what you are called now) is a little right. |
How do you define majority in a system where there is no verified identities? |
@krzysztof113 I partly agree with you. However, as I previously said, it is hard to design and use system that is efficient, safe, user-friendly and decentralized at same time.
|
I totally mean the infrastructure behind, not the Zeronet. For ZN current status with signers etc is pretty great and will work by itself. |
Pardon my ignorance, but can't this data be stored in a similar way Bitcoin"s blockchain data is stored? I mean, its blockchain is huge and yet people don't have to download tons of gigabytes to use it. How's Zeronet data different and why can't be it stored in the same way as BTC transactions data? |
If they want to use it in completely decentralized way, they have to download tons of gigabytes. But they can also simply use some online wallets, which are centralized, and something like this is currently used by ZeroNet.
And how are BTC transactions data stored? Isn't the only way of accessing them to download blockchain - either locally or using some online service? |
Thanks for reporting, I think I found the problem, re-synced the namecoin client and it should work now. I agree that the current operation method is not the best, and if it's possible, then we should find a more decentralized way to resolve the domains. |
So obviously this issue is a trolling attempt, not a serious bug report. That said, I'll comment on my position here. (I'll use singular first-person here because in practice, for the last couple years, liasoning with ZeroNet is my job at Namecoin, but I don't have any reason to think that any other Namecoin devs disagree with my take). Am I unhappy that ZeroNet uses unnecessarily centralized resolution by default? Yes, without a doubt. However, I am not in the business of shitting on projects, or refusing to work with them, just because they have shortcomings. In order for me to shit on a project over something like this, the project would need to demonstrate that they don't care about those shortcomings and have no intention of fixing them. That is not the case for ZeroNet; I've spoken with both Tamas and Lola extensively, and it is clear to me that they want to fix those issues. Work is ongoing to fix the situation (and this is a collaboration between me and Tamas and Lola), so I'm satisfied and have no intention of removing mentions of ZeroNet from Namecoin.org. Why is it taking a while to get the situation fixed? Because it's hard for me to get funding for ZeroNet-related Namecoin work, so I usually need to find a way to justify that work as relevant to another use case, and find a way to implement those deliverables so that they meet the requirements of the other use case but happen to also make things better for ZeroNet. This will hopefully change in early 2020. I was hoping to meet up with Tamas and/or Lola at 36C3 to discuss our next steps in this department, but unfortunately it looks like neither of them will be there this year. I'll probably spend some time talking with them in January to coordinate things. Anyway, yes, everyone involved knows that the current situation is not great, and everyone involved is trying to get the situation fixed. Shitposting about it is not going to get it fixed any faster (but obviously getting the situation fixed was not ever the goal of our Antifa troll). Cheers. |
Unfortunately, that centralized resolution is not really "unnecessary". Currently, this is the only efficient way to query blockchain without downloading it. Because in any case, you will either have to download whole blockchain or rely on centralized resolution. |
@filips123 I'm not going to dignify this issue (which was started by a troll and should just die) by getting into further serious discussion, but your statement is not completely accurate. There are a variety of approaches to authenticating name lookups that are substantially less centralized than what ZeroNet uses now [1]; I've already discussed this in significant detail with both Tamas and Lola. This month is not a good time to rehash those discussions on GitHub (I'm busy getting ready for 36C3), but at this point most of the work remaining is an engineering/implementation effort, not design/research. If you're curious, feel free to contact me via some channel that isn't a GitHub issue started by a troll, but don't expect me to be around until January at the earliest. Cheers. :) /me will not be replying further in this issue. Let the shitpost die. [1] EDIT: And no, I'm not talking about multisig-signed centralized resolution. That's generally the kind of "solution" proposed by clowns who have no solution. |
@JeremyRand When you will have time, could you continue discussiong that alternative solutions for domain queryng? And yes, use new new normal GitHub issue for that, not this one... |
This issue sounds quite funny. Lol |
Since I feel I can solve any type of problem I will come with solution for this in few days, I had already solution in my mind but I want to do some research on that. |
I have registered a domain with the
.bit
tld and configured the name accordingly, also included in thecontent.json
file thedomain
field but can't get it work!Ping: @HelloZeroNet @JeremyRand @imachug
The text was updated successfully, but these errors were encountered: