I thought it was important to abstract away the complexities of the SafeNet - at its core it’s difficult for a lay-person to understand, but if we (app developers) can make it work in as few inputs as possible from the user’s perspective, it won’t seem quite so daunting. Breeding familiarity was really my goal with the user experience.
I hope it’ll serve as a decent, simple entry point for new users to try out publishing on the safe net before they move on to tools with more depth.
Again, wow just wow! The rate of progress is amazing!
To this end I think it essential to provide additional explanatory pop ups for those that might be confused by the service field and it’s orientation on the left of the URL as opposed to the right. From my understanding subdomains traditionally fall the right. The “post domain” field imo could either use further explanation or rewording to something like “Post this to which domain?”. Finally The “post URL” field might be the most confusing of all for new users. Where the need to specify an HTML and the index at that isn’t obvious.
With your goal in mind I’m sure making this grandma easy will naturally happen
I’m not sure of the reasons, but MaidSafe use the terms profile and public-name, as in safe://profile.public-name and you can support different services (www, LDP, etc) on each public-name by associating each service with a profile.
In the absence of any other convention, I’m using the term host in my SAFE Web API
to refer to the whole profile.public-name.
Is there a reason we can’t have PROTOCOL://DOMAIN.SUBDOMAIN/PATH on Safenet? It would just feel more intuitive to me. Is the GTLD even needed? E.g. safe://google.search/scholar, safe://google.search/images, safe://google.company/contact.
Yes, but I think it’s fair to argue that the traditional route is NOT the best. Given an un-official set of standards, the safe dns can be self-organizing through typical conventions. For example, if I want to add my take on a search system, no one can stop me from simply using “safe://search.with-jlpell”, but people will soon find out that “safe://search.with-google” works better, and “safe://search.by-shane” works way better still. If you are a cat photographer, just post your best CC-SA 4.0 to “safe://cats.by-shane”.
After I thought about the analogous “subdomain.domain.gtld” structure on SAFE from a user interface perspective a little bit, I like it way better than the current web. Seems more intuitive and natural. There are a lot of ways for it to self organize around a simple “style-guide” without forcing people to do anything.
I also think that instead of the WWW codes, we should change the moniker to something else like SSS or SOS and come up with something more creative than “Secure SAFE Site” or “Sites On SAFE”. (Unless a consensus of people think those are decent enough alternatives.)
The only things stuck in a web are victims and vampires.
Hello! If anyone is interested in beta-testing the app, I could really use the following:
Someone using Windows (7 or 8.1 preferred - I do support 10 fully, it’s just what I use for development so it has already been tested to death), someone using OSX (10.9 to 10.12 - again, 10.13 is supported but has been tested to death) and Linux (“Ubuntu 12.04 or above”, “Fedora 21 or above” or “Debian 8 or above”). At the moment, ARM support is spotty at best.
I won’t be needing you for another week and a half (or so), but I just wanted to build up a small list. I’m not looking for a lot of beta-testers, just one per platform if possible - if you post here and aren’t chosen, it’s not for any particular reason.
Those testing will be required to have at least 100 puts available on their SafeNet account (as such you’ll need to have the Safe-Browser installed and a valid Safe-Authenticator account) and will be uploading content to the Alpha2 (the current live) network. You must have a keen interest in posting to the network and writing some content privately before the test would give you a great advantage.
In return, you’ll gain first access to the CMS platform (though I do recommend you upgrade to the 1.0.0 stable version at the end of the month), but you will encounter bugs, usability issues, etc. All testers will be credited in the contributors.md file in the Github repository once it’s released.
Perfect - I’ll just sign you up for Debian / Fedora if that’s okay? I want the test group to be small but it’s also important to have some variety (both of environments and technical capabilities of the users)
I’ll put you down for Ubuntu, which version are you running?
With regards to Centos / RHEL, at the moment there are compatibility issues between Electron and the versions of GLIBC distributed with the most recent versions of Centos/RHEL by default, so I’m not considering it a distribution target for the V1.0.0 release. It’s not a massive loss, since not a particularly large amount of people are using desktop RedHat / Centos in the real world, but if there’s a lot of demand, I’m happy to look at aiming for compatibility with V2.0.0.
I go through different distros like candy via VirtualBox. Just tell me which one you would like and I will install it and test out the CMS. It’s been a little while since I installed an Ubuntu box, but I use debian daily and they are pretty similar. If you would prefer someone to test things with a native host os of Ubuntu, then perhaps someone else might be better equipped. Just let me know what you prefer… I’m happy to help out if I can.
A lot of times the particular desktop environment has an effect on how well things run. So it’s more of a KDE,Gnome, XFCE thing vs. the actual linux distro itself.
I actually don’t know if it (the SafeNetwork libraries) will work within virtualbox by default, this is a little out of my scope of knowledge, perhaps @hunterlester could comment.
Will the NAT traversal techniques, etc, all work from a network perspective from within a virtualised environment? I know that some tools have issues using the virtual PCI networking adapters Virtualbox exports. From my experience, an easy way to resolve any issues is using the bridged networking configuration of Virtualbox, but I’m not an expert in Virtualized networking.
I use Ubuntu to regularly test our libraries and apps via VirtualBox on Windows 10, for both mock-routing and connecting to the live network.
However, I’m running Home edition, which doesn’t use Hyper-V like Professional Edition.
Not sure if that’ll make a difference.
I use virtual machines regularly too for all kinds of stuff (virtualbox and VMware, windows and Ubuntu) - didn’t have networking problems yet with reasonable networking settings
I would be surprised if you ran into trouble but in case there is something going on I do have Ubuntu (16.xx) natively on the machines I mostly work with - so you can just shout out to me in telegram/IRC @jlpell and I will try and be of help