It is worth noting that multiple vaults on one LAN is often needed to get a small network such as this started. I only have one LAN, and one cloud server. So a customized binary just for striking that initial spark, and maybe for making available to other hard-coded contacts in the community1 config, is definitely to be expected, because the older binaries (that don’t have the LAN restriction) won’t work with the newer versions.
hi,
surely given that this is a non maidsafe official network used for test and learning purposes only and makes no promise to any other effect, then as long as any tweaks or changes that are made are noted, documented and available to those with an interest there should never be an issue.
to be honest i can’t see any reason why those involved in any way with this project in an official or non official capacity would have any reason to have an issue with the running of a purely volunteer network that provides a network over an above the official one. that allows app designers to test if appropriate, vault famers to optimise and play, introduces a wider audience to the technologies etc etc.
i have followed the project since i first stumbled across it on the udt (UDT: Breaking the Data Transfer Bottleneck) site some 5 years ago and have been waiting patiently for the chance to play a part however small in getting this fantastic resource up and running and in use.
if i can do this in a hopefully constructive, friendly manner, mankind can benefit from a more open, more secure, cheaper, shared network and i can feel good about putting something back, whats not to like?
i’ve probably gone of target a bit, but hey…
rup ![]()
Absolutely right and my mistake born from a misunderstanding of what the switch issue was about and what you guys are about here.
Am I allowed to call myself a moron
yep apology is warranted.
Happy to… but don’t expect anything long and complicated… cause it’s quite easy. ![]()