Getting some streamable data uploaded to our local baby Flemings will be the first challenge. But once thats done and the actual range fetching is tested, my instant take on it is its getting the interface built and the subscription payment model defined. Something that I would not imagine needs much direct input from the core devs.
So get tore in…
3 Likes
I tested this version of SAFE Browser and it connects successfully to a non local vault base on latest Fleming branch. The file to update is:
C:\Users\...\AppData\Roaming\MaidSafe\safe_vault\config\vault_connection_info.config
with content like "ip-address:port".
This works but it allows only one contact node. In the past we could also create another file that allowed several contact nodes:
C:\Users\...\AppData\Roaming\MaidSafe\safe_core\config\safe_core.config
But I don’t succeed in using this method anymore. I tried various contents like:
-
["ip-address:port"] -
{ "hard_coded_contacts": ["ip-address:port"] }
Can anyone @maidsafe indicates the file and the syntax for defining a set of hard coded contacts. The aim would be to set up a non local network.
5 Likes
From memory this was the format of the old hard-coded bootstrap files we used. I have cleaned out a load of old stuff from ~/projects/maidsafe so I can’t check.
Let us know how you get on when you get an proper answer, please 
3 Likes
json format, from here qp2p/config.rs at main · maidsafe/qp2p · GitHub
So what you have is correct, there was a bug that @nbaksalyar recently sorted @tfa and that is in master
8 Likes
Coming back to this.
Can you please either inject the following into the conversation, or get them to look at this post.
In the past there have been a number of suggestions for how to handle private and/or deleting data. Each time there were major issues and out of that came the concept of making private data contain the owner ID within its addressing hash.
The big advantage is that it solved most issues in a KISS way.
So if things change can they discuss it with the community before they get too far down the track so that any issues can be discussed prior to development. Sometimes keeping it simple makes it more powerful a feature.
4 Likes
