-
-
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
PR? #2847
Comments
Yeah |
Take a look at https://github.com/ZeroNetX/ZeroNet, it's actively being developed. |
there was only one maintainer (i.e. person with write access) on ZeroNet and they disappeared. this eventually lead to a few forks being developed; i'm working on https://github.com/zeronet-conservancy/zeronet-conservancy (and back around time of forking i've gone through PRs here and merged some). development has been stagnating, but it's not completely dead |
ok thanks guys |
Is "last commit was 10 month ago" called "actively developed" these days or am I looking in a wrong place? |
@mx5kevin thanks but so which fork is the right one to follow up the repo? |
There isn't one. Anyone who waits for such a thing is wasting their precious time. I followed the work of all the current developers, nothing can be expected from them. If someone wants working visited content, he is forced to use the open Internet, or perhaps torrent, which still works relatively well. The very last developer who did something was 0NetDWF, he also said that there is only problem with the whole thing, with video file sharing services, blogs, multilingual forums and the 0NetDWF binaries he deleted everything in one day because he was tired of it all. He did more in a few months than the other developers in three years. He said he also started that project because it was worthless what other forks developers are doing. Before him, all the major content owners left the project. The remaining pages are all useless, childish, rudimentary crap on this network. |
i was gonna ignore this, but
is just ridiculous misinformation. all the changes in 0NetDWF were either copy from other forks or simple numeric changes and seeing how the developer openly admitted to not being programmer i don't see how that could have changed in the time since i last checked @ROBERT-MCDOWELL just see which fork is more active for yourself ^_^ there are currently more people spreading (often hostile) misinformation than actual users around this repo on github |
Your project does not even know a quarter of that services. The same with ZeroNetX. All the updates from other forks are integrated in the DWF project, and a lot of custom fixes. Including that the video sharing and file sharing services worked on it and did not get stuck at 10MB limits, and other dumb site limits. The DWF source code, and his binaries at the moment it is probably the most worthwhile to develop further. Several of the users have already indicated that you are lying to your users in the zeronet-conservancy project where you can. Its developer was not a programmer, but the two of you together over the years did not achieve such results as him. Both of the ZeroNetX, and Conservancy project are a big scam joke behind of the original Hungarian developer Kocsis Tamás, both you are living off the reputation of the original project. I have been following the project since 2015 with his forks, I know for sure that you are both unfit for the meaningful development of such a project. |
ah yeah, thanks for reminding that you are one of the regular trolls |
the obvious question among this awful ridiculous fight from fork guys is, where are the authors of this repo to answer what's happening? my research on zeronet found very weird result, like rothschild corp financed it and maybe stopped it. is anyone can confirm? |
@ROBERT-MCDOWELL there are enough donations to keep developing for a long time: https://www.blockchain.com/explorer/addresses/btc/1QDhxQ6PraUZa21ET5fYUCPgdrwBomnFgX (source), but it doesn't seem like anyone has access to the wallet anymore. neither you could reasonably expect we'll ever get response from Tamas |
The original developer is dead, imprisoned or threatened by the authorities. I am Hungarian like the original developer and I live there like the original developer. He stopped the project unexpectedly and not voluntarily, and he will not return, he has disappeared from everywhere permanently. The writings before her disappearance reveal that she had serious plans for the project, and clearly something so unexpected happened that she didn't even leave any message anywhere. He became a well-known person and was financed by the Internet community. However, he has not been able to take anything out of the collected BTC donations since then, and this is a very significant amount. Anyone can verify this by examining public BTC transactions. He was an individual developer who was not commissioned by anyone, but the authorities could force him to install back doors, and several people wrote about signs of this.. |
@mx5kevin my research are correct so.... this kind of project brings often dark business or networks, most of them criminal unfortunately |
The problem is that if you upload a content to the network, it should be available. This system is so flawed that it is unable to perform a simple download. I have seeded a lot of content on this network, and most of it is not downloadable by users. It cannot do what it promises that you can host websites with files. If this content are uploaded as torrent, to a file sharing service, to a web hosting service in the open internet, free blogging platform, video sharing platform in open internet it works with much less effort and is achieved by a hundred times more people. The problem here is not that fewer people access a piece of content, but that if you, or another user want to use it, the whole system are failing. And developers who are currently forking this project all they all posers in the hype train, and are completely unfit to solve such problems. |
why 0net maintainers don't integrate the 53 PR since 2 years?
is the project dead?
The text was updated successfully, but these errors were encountered: