For example -
Even protocols based on top of UDP use IP addresses. You can not operate on the internet without IP addresses. To say maidensafe doesn't use IP addresses shows you really don't understand what is going on, yet you want people to believe you read their code.
MaidSafe does not have IP addresses. So just saying that UDP uses IP addresses doesn't mean that the MaidSafe platform uses IP addresses. If you can find and show me otherwise I'm open to it.
From my review they are not using IP addresses at all (at least not in a way which can be tracked). It's just like I can say that Tor hidden services don't use URLs, or Freenet does not use URLs, they use some encrypted form of addressing.
You say a lot of little things like this that don't add up.
Responding in particular to the above quote, I have been saying repeatedly that I think maidensafe's bigger application is a better TOR.
It does more than TOR. TOR is at the application layer.
For example lets say you come up with a completely new public key encrypted addressing scheme at the layers below 4 which does not involve IP addresses at all but you can still find what you want to find? You cannot use new schemes if you're on the application layer because you have to depend on the transport and lower layers. If you can innovate at the transport layers and below then all of the stuff you typically associate with an IP address could be encrypted. You need an identifier and a locator but you do not necessarily need an IP address.
In any case, MaidSafe as I currently understand it doesn't allow you to have an IP address on the platform. Of course if you're connecting to MaidSafe from your ISP then you already have an IP address from your ISP but MaidSafe platform itself doesn't seem to use IP addresses.
I suppose what I should have said is that while you may have an IP address, it's impossible to track people by IP address on MaidSafe. MaidSafe as a platform does not allow IP address tracking. This means your ISP cannot see what you're doing and neither can anyone else.
TOR on the other hand, if you use that you can be tracked.
Yet you conflate that into something else to continue arguing. THat is because your objective here is nothing but promotion, so what others say has little effect on your pages and pages of ...... thoughts.
What am I promoting? The only thing you're trying to say is that I'm somehow wrong about something or have made some technical error. Point it out.
Again, you don't listen or read. When I brought up dropbox, I explicitly mentioned truecrypt. Truecrypt has recently had a serious 3rd party independent audit. I use truecrypt to encrypt. Dropbox keeps my files on their cloud service and replicates across any device I own. Mac/Phone/Windows/Linux. All of those. Yes, this has the problem in that an error in dropbox service can propagate across all my devices, but this is the same level of issue you'll have with Maidensafe.
This is true. MaidSafe could have a bug in it and that is a risk. The same could be said about Bitcoin, Bitshares and many others. The risk is also in hardware as well, because your harddrive could be defective.
The code section I posted up was one of the most relevant parts of code for our discussion, the self encryption part, and the RUDP part. If there is a flaw in the self encryption part of the code then all your data could be compromised. From the looks if it they chose the best algorithms available for the self encryption and it's the fact that we can all review it leads me to have confidence that a bug isn't in that portion of the code.
I'm sure there are better C++ programmers than me but I definitely review these things. The RUDP section of the code may have minor bugs but its something which can be tested out and debugged if true. So the most important part I would think for reducing your risk would be to know that your information remains confidential, that data integrity is secure, and you can always back your data up at Dropbox in addition to MaidSafe while you test MaidSafe which spreads your risk.
You made another example about how one's computer can be hacked and they can lose their BTC. Maidensafe doesn't stop this. If you are hacked, a keyboard logger will open up the door to maidensafe unless maidensafe uses one of those visual keyboards that relies on mouse clicks.
You're not being innovative here. App developers can solve this problem. You don't really need to use the password at all. I actually agree this is the main risk with MaidSafe but since anyone can write apps it will be possible to solve this problem. Simply allow for multi factor authentication which specifically does not use "passwords" but instead use SQRL, biometrics, or some other combination such as a one time code sent to your cellphone combined.
Whether or not it's secure I don't know. It seems to look okay but this is one of the more important parts of the code to review along with this whitepaper
https://github.com/maidsafe/MaidSafe/wiki/unpublished_papers/SelfAuthentication.pdfWe demonstrated a working version of such a system for
the first time in April 2008 in our offices in Troon, Scotland,
and as far as we are aware this was the first time in history
a person created their own identity, stored it and managed all
their actions without any server requirement and without any
3rd party control
https://github.com/maidsafe/MaidSafe-Passport/blob/master/src/maidsafe/passport/detail/passport.ccIn the end I'm not really concerned about this problem because I see many ways to move beyond passwords and keyboard based authentication. I think the code is too complicated for anyone to understand what everything is doing so I'd hope we audit it. The design of it looks fantastic and the code isn't so ugly that it looks shady but you never know.
You make tons of assumptions how others use their computing devices to make your point, when you don't understand what the services that people use actually do.
Maidensafe is a great idea. Neat. I'll play with it. I just lol at the thought of it being more disruptive than bitcoin.
Bitcoin is a lot of things but it's not capable of decentralizing the Internet. Consider the effect MaidSafe will have on net neutrality. Consider the effect it will have on the copyright industry and everything associated it. Consider the effect it could have on Silicon Valley.
I think Bitcoin is disruptive and a great innovation but MaidSafe is way more disruptive. Bitcoin allows you to transmit digital property, solves the Byzantine generals problem, is counterfeit proof. So I cannot take anything away from Bitcoin.
At the same time MaidSafe may potentially do something even greater than Bitcoin. If MaidSafe were to catch on then computing resources could be accessible to the whole world, and all the talk we have about building decentralized autonomous corporations, MaidSafe would do more to facilitate that than any technology so far.
If you're an app developer how would you like to not have to worry about computing resources such as storage space, processing power, bandwidth? All you would have to worry about is writing the code and marketing the app on a platform which would scale up with the popularity of the apps running on it.
MaidSafe is in my opinion more disruptive because so many corporations are set up to try and profit from collecting and selling our data. What are those businesses going to do when they face disintermediation?