bro, project xanadu says we will have royalties on steem/hive. We WILL have a system for residual rewards built into hive once hive engine tokens like @leofinance work with @aggroed to create some sort of system for STAKING REWARDS based on POSTS or POST 7 day upvotes ..... where you can upvote with LEO ... which, like any HE token, can, thanks to @eonwarped and @beggars ... be set to have scotbot settings with a SUPER long reward payout even a year 365 days or more ... even 2 5 or 10 year residual times, where you dont get paid for years lol thats the problem hmm maybe have the reward pool retroactively blah blah blah its fun to figure out well figure it out with scotbot tHEN hard code it into Hive main net proper hahahaha
PROJECT XANADUUUUUU! @ned scott
https://en.wikipedia.org/wiki/Project_Xanadu#Original_17_rules
Original 17 rules
Every Xanadu server is uniquely and securely identified.
Every Xanadu server can be operated independently or in a network.
Every user is uniquely and securely identified.
Every user can search, retrieve, create and store documents.
Every document can consist of any number of parts each of which may be of any data type.
Every document can contain links of any type including virtual copies ("transclusions") to any other document in the system accessible to its owner.
Links are visible and can be followed from all endpoints.
Permission to link to a document is explicitly granted by the act of publication.
Every document can contain a royalty mechanism at any desired degree of granularity to ensure payment on any portion accessed, including virtual copies ("transclusions") of all or part of the document.
(BINGO ted nelson scott! THATS our royalty mechanism using hive engine or some sort of royalty upvote staking reward of a % of a users LONG TERM curation reward voting power or something with delegation )
Every document is uniquely and securely identified.
Every document can have secure access controls.
Every document can be rapidly searched, stored and retrieved without user knowledge of where it is physically stored.
Every document is automatically moved to physical storage appropriate to its frequency of access from any given location.
Every document is automatically stored redundantly to maintain availability even in case of a disaster.
Every Xanadu service provider can charge their users at any rate they choose for the storage, retrieval and publishing of documents.
Every transaction is secure and auditable only by the parties to that transaction.
The Xanadu client–server communication protocol is an openly published standard. Third-party software development and integration is encouraged.[13]
See also
Enfilade (Xanadu)
Hypermedia
ENQUIRE
Interpedia
American Information Exchange
Tent (protocol)
In addition to the Web, the Project Xanadu FAQ suggests other hypermedia systems which are similar, including HyperWave (or Hyper-G) and:
Microcosm (hypermedia system)
IBM Notes (descendant of Notes on PLATO (computer system), featured in Nelson's Computer Lib)
Wiki
Memex
ipfs
