Embedded Files
🐳 Problem: Todays 'Big Tech' whales are the handful that can manage at scale.
Version?
Open source alternatives?
Dependencies?
Patching?
Security?
Licensing?
($) Millions are spent annually and no public API management solution exists
Are there natural market incentives ($) to support this infrastructure?
Can we bring this process closer to the developer and/or end-user ?
Fig. 1: What's in the [api] box?
𝌣Solution: Haiphen ... owners can track and enforce API access through an immutable hyper-ledger.
...
With the digital copyright acting as an avatar on behalf of its' owner the individual developers can work at the scale of enterprises.
Early Exploration
Motivation: Most developers cannot afford to patent, trademark or legally protect their digital IP beyond a basic copyright which are rarely enforced.
Most fall into one of two buckets: enterprise level entities, well funded by corporate lawyers to fight tooth-and-nail in court ... or ... the open source, a.k.a 'copyleft', developers who do the minimum licensing to 'politely ask' you not to abuse their product.
(productivity)
☹️ 😀 ☹️
↓ ↓ ↓
(# of apps)
Bringing the modern copyright closer to the product itself transforms it from a nuisance into a utility with practical value to the developers.
Developers require less overhead to deliver a product
IP lawyers receive greater traffic because of template legal documentation standardized across the industry
Investors receive greater transparency and security into their investments
End users receive competitive, customized solutions to their specific needs.
Survey: 'How You Use The Internet'
fig. 1: Consumers, flooded with options, have to budget 'searching' into the time it takes to get to a solution
Ongoing Research
Fig. 3: Nordic API Blog
Fig.4: White Paper
Page updated
Google Sites
Report abuse