As the intranode grows, it will start to develop districts, the first will be the login district at 0,0 as people profiles grow, this own little clusters of nodes will sprout off, this will generate a need for hubnodes.
each district will have a hubnode which will be connected to all other hubnodes (within reason, maybe within 10000 pixels or something) hubnodes have their own styles that nodes directly surrounding them (1000px or something) can inheret to give the district a distinctive look and feel. hub nodes are user generated or spawned when a neigbouring hubnode has too many nodelinks. See concepts->connector nodes
also there needs to be a facility to change a node into a junction manually – see node creation
hrm.. im not sure about that. shouldnt that be handled by the node-to-connector ratio watcher?
usually yes, but sometimes you are going to want a certain node ie an image to be a hub for.. oh wait, i guess it will on its own if enough ppl connect to it
A user can right click + back to parent junction at any time – this solves the 2 way linking navigation problem where users travel down a branch, reach a dead end and are stuck (portal nodes notwithstanding of course)