Thank you for boosting this (important) discussion. People will need the smoothest transition possible. That might first be desktop applications to download, but the web-compatibility should not lag far behind, in my opinion.
A second question I want to raise is about the DNS service on SAFE. I can see how the network would allocate names on a first come, first serve basis. But if we learnt anything from URLs over the past decades, is that in retrospect it’s rather unfortunate system: domain names get bought up and resold at ridiculous prices, on top of that the majority of top-level domain names point to neglected age-old websites, or nothing.
So in respect, what if you have to pay the network in safecoins to host a domain name? (Network reallocates the coins for farming) - could this work? remarks?
Secondly, can we brainstorm something new, something beyond URLs (and Google search)
COPIED FROM MAILING LIST: On 03 May 2014, at 19:31, Dan Jasek wrote:
Frameworks like Angular.js are commonly used in this type of design.
I do not believe there is any timeline or immediate plans for implementing this, and some of it may come from the community. This is what I expect will be built eventually:
You will sign in to the browser plugin and all SAFE sites will just know who you are. You will be able to have multiple aliases and be able to set which sites see what identity/data. It will be the ultimate single sign-on.
When the index.html page and other files are pulled, these are coming from the SAFE network directly. You will not have a server running. You will save the files to the network and be done. You won’t have to deal with scaling, server and database maintenance, or other operations issues. The network will handle it all for you automatically. If your site goes from 10 hits a day to 1,000,000 hits overnight, you will not have to change or do anything (except enjoy the popularity).
Tools, frameworks, and tutorials will be built to make this all very easy. You are looking at the absolute cutting edge of web technology, it will take time for the community and infrastructure to built up to support it in the same way you see currently in PHP.
I think allowing “web apps” to be a GUI engine for apps (one of) allows for the most flexibility and cross platform, OS agnostic adoption. Granted some things will need native OS access (like accessing the camera on a phone or tablet) and will need to be device / OS specific. But Apple (Google) could block native apps from their app store that they don’t like if it cuts them out from data gathering / marketing / spying / profit. Web apps cannot be blocked right now.
I think much wider / faster adoption will occur with web technologies being used to get apps out there faster. There are many app builder type tools out there that will help accelerate adoption if they can tap into Maidsafe.
That. Is. Awesome. I think it’ll be interesting to see how data gets handled. It seems like for a given application you might want to store user data in the user’s own MaidSafe data store, and store some other data in more of a “global” MaidSafe data location that’s available to everyone who is using the app. Which begs the question, what type of existing database would best work with MaidSafe, or is new database technology required?
@wolf I think the answer to all of the questions you just asked are going to be yes. Everyone is going to come up with a solution that works “for them best” until a real best solution comes to light.
@physics I think a new solution will eventually come out, but only time will tell. The best part about Maidsafe is that it is a framework - you can build what you need to make a best solution using it.
This might not be the right sub forum, but I wanted to ask, what is to prevent someone or some group from stealing your pin / password with an app designed to steal said information? That pin / password combo is the key to all your encrypted data, correct? (I am not well versed in exactly how bitcoin works, and perhaps my answer lies in understanding it better.) i.e. where is the user pin / password entered (a general maidsafe login, or is it on a per app basis?)
For example, let’s say I as a developer make a web app for an Android phone, using maidsafe on the back end to store the user data. As a user, where is the password and pin entered to authenticate the maidsafe user data as it pertains to that the app? Is it a secure maidsafe login object embedded in the app? What is to prevent a rouge app designer from stealing my pin and password or token generated from the secure object and breaching all my data out on maidsafe? It is just 1 pin and password for all my data, right? And it is only entered and stored on the device where it is entered, and it is not transmitted? But if the app is malicious, is there a security threat to all my data?
What is the methodology that will prevent a government or any entity from creating rogue apps with the express intent to gain access to the encrypted data for the user who falls victim to the rouge app? Or what steps are in place to prevent entities from inserting back doors in the core code base? As we have seen with Windows, hardware level firmware back doors, corrupt cell 2G / 3G / 4G code stacks, etc…
Please move this to the appropriate sub-forum if this is the wrong spot for it. I was expanding upon the web app idea with a security oriented questions as to the security of the web app.
The network is by itself one giant database, or rather a key value store: You give it a key, it passes you back a value. Those are the underlying cogs of the machine :).
So yes, your own data should always be in your own account, so you control it at any point in time. A SAFE application can be stored under a different account and have it’s own storage needed for running the application (binaries, graphics, etc).
To share your private information with friends, on the other hand, you don’t need to release this information to application level (as you would upload a picture to Facebook today). You simply share this data with your friends directly, without the application controlling this shared information.
This would be great, though I suspect that IE, Safari, and Chrome will take a while to get built-in support for the network. Their companies’ operating systems don’t ship with torrent apps even though including them would be easy.
For browsers like Firefox at least, it would be useful to have this core support early on, maybe before the network goes live. This way, they could end up in the system by clicking a safe:// link, and that would be a smooth welcoming.
I’m guessing that viewing public data (such as webpages) on the network wouldn’t require joining the network, and the incentive for joining would be interaction (posting on forums, contributing to video library sites, messaging others, backing up personal data, etc)?
Sorry to sound like propaganda but I think we need a browser model that irrevocably places total control over the end user interfaces in the end users hands.
On this a stake holder model wont work. We are all end users and that is the means and ends to consider things from. Doing a modal ad on the system now or in the distant future should range from being impossible to completely impractacle. Of course, complementary search/trending and culture, community and education would be needed. But clearly no pop ups or modal window or outside control over scrolling, back/forward.
Just a thought, but as we will need a name for the safe browser, I was thinking “Beagle” as it sounds similar to “google” and has lots of relevance to the Maidsafe project -ie Darwin’s voyage of discovery, evolution etc.
It does matter if you care about marketing. If people associate your product with some other product subconsciously then it generates unnecessary confusion.
There was no such word as Mozilla until it was made up. Netscape had no app with that name when they came up with it. Windows described the functionality and look of the GUI but it wasn’t common. Beagle on the other hand is not only a word already in use but in use by one of the primary demographics for SAFE Network.
If you like the name you can use it but it’s risky and could result in people thinking it’s this Beagle