Some ideas about possible adjunct hyperservices for consideration

[liquidstars]

First, your project looks very thoughtful and significant. I wish to contribute to building Web 3.0 and your project looks like it is heading in a good direction to those ends. I had looked at IPFS but the design/build OSI layer is lower than I would like to work in. Hope that makes sense. I would like to use Beaker and its Hyper components for building persistent web presence for content, free from censorship and other such impediments.

When looking at IPFS I had a number of questions. How does the universe not become flooded with junk, which could well be deliberate. How are incentives arrange for people to contribute and maintain resources to support/grow the network. and other similar considerations. There is much that pertains to the social and behavioral activities of people, beyond the technology layer.

Here are a few thoughts, for your consideration. Thinking ahead about some of these items in an architectural sense may be of benefit for fitting in adjunct, supportive services in the future:

Suggesstions for adjunct Hyper Services to increase participation and provisioning, reduce vulnerability to abuse/flooding

Liquidstars 2021-01-15

Hyper-Services:

peer based adjunct services running as independent processes on peer devices to support searching, storage, anonymity, payment for provisioning, using Beaker Browser as services control panel

**Publishing/Searching (separate from hosted content)**
	[_] - access/visibility control (public, restricted, non-discoverable)
	[_] - plain query
	[_] - hashed meta tag query
	[_] - content to meta tag processor utility
	[_] - cleaner utility for cache purge and republishing

**Persistance (as a service)**
	[_] - distributed peer cloud storage
	[_] - free-or-fee provisioning (effects quality of service)
	[_] - controls via: amount, time, peer spread, speed

**Anonymizing Routing (like TOR or Nord VPN)**
	[_] - randomized inter-peer routing
	[_] - selectable security level, speed, hop depth
	[_] - forced rerouting based on connection fatigue/aging
	[_] - P2P co-ordinated connection hopping or spreading

**Payment for Services, Service**
	[_] - integrated microwallet
	[_] - pooled contributions
	[_] - proportional distributions (based on quantity/quality)
	[_] - possible use of exponential costing to curb abuses of network
	[_] - dynamic throttles based on network conditions
	[_] - provisioning ecosystem credits for contributions of resources

[liquidstars]

Sorry if this is a lot all at once but I had some time to think about this today and wanted to put it all together in one spot since many aspects overlap and interrelate.