Overcoming extensions limitations

Browser extension limitations:

• browsers usage patterns are several and unpredictable, hence some nodes could lead to high churn rates;
• browsers local storage could be limiting;
• AUTOIMPOSED: we'd like to avoid too much processing inside the extensions;
• TBD, AUTOIMPOSED: we are considering to avoid lax permissions (<all_urls>) to reduce security risks, hence crawling would not be doable;

We envisioned the following strategies for headless nodes independent from the browser:

• daemons running on public networks apparently equals to normal peers, relying searches and post processing results for enrichment and aggregation;
• daemons running on public networks offering a different set of functionalities (like URL content analysis), this would require L2 protocols to expose nodes capabilities;
• public daemons running on public networks specifically configured for enrichment options;
• private daemons running on local networks specifically configured for enrichment options;