Skip to content

Latest commit

 

History

History
29 lines (18 loc) · 1.79 KB

company.md

File metadata and controls

29 lines (18 loc) · 1.79 KB

Model of economy for company relying on info for living.

  • trust reliability
  • 24/24 server with big bandwidth allowing their database to help convergence.

Yet the possibility for user / applicative rules to distrust those, example :

  • hardcoded in applicative (application are central) : this is dangerous and user should only use opensource to be able to fork application in case of abusive filtering (or privilege) of statement
  • through smart applicative inference rules

Trusted company could intervene in merging and convergence by defining synonym of existing triples that will allow to lower the number of far Striple (orphan by low propagation). For example, on a for of an Striple, the company could issue its fork relation that applicative will check. The company service being an equivalence or inference helper (like a search engine). This could also be achieve by sidechain insertion of hash, which is not incompatible with the company service : being in the side chain is a way to fact check yet it does not mean that it is fastly and conveniently accessible (especially if only a hash of a whole meerkle tree is stored) and compatible with low ressource inference algorithm. We see a model where the sidechain makes that everyone can fact check, yet data mining company still have added value.

In most use case being a major trusted peer really influencing network by establishing correct trust an is a full time job (plus required bigger resources to get more info and do more treatment on them).