Abstract: A Web 3 Building Block
May 2022
- DRAFT -
An independent content building block with an integrated revenue engine and value-interconnectivity, will allow a more financially-efficient, democratic and diverse web - allowing more people to become web-creators and benefit from their own creations.
Currently, most online content is controlled solely by the companies that own the medium where it originated - tweets are owned and controlled by twitter, Google Reviews are property of Google Inc and the beautiful pictures you take each and every day are owned by Meta. This coupling is fundamentally wrong. It gives too much power to the platforms, at the expense of the content's true creators. It allows them to censor, manipulate and grow into monopolies.
The Abstract protocol, combined with Abstract’s open tool-set - are empowering the creation, consumption and exploration of these content-blocks (or “Abstracts”) - Cultural digital objects that are free for everyone to create, consume, invest and build-upon.
Abstract allows any cultural object to attribute other cultural objects, creating an ever-existing value chain that benefits past creators with a portion of the success of new creations based on their work.
This new building block, network and model will place foundations for the next generation of web - commonly named web3 - a creators’ centric network open for all to advance and nurture.
[The early internet (1980s-2000s) was built on top of a series of open protocols like HTTP (websites) and SMTP (email). It was largely decentralised: users could trust that these protocols wouldn’t change and could build sites and services on top of them with no intermediation by a third party. However, building required technical skills, and it was hard to attract an audience. Web1.0 was niche.]
Web 1.0 is a retronym referring to the first stage of the World Wide Web's evolution, from roughly 1991 to 2004. According to Graham Cormode and Balachander Krishnamurthy, "content creators were few in Web 1.0 with the vast majority of users simply acting as consumers of content".[13] Personal web pages were common, consisting mainly of static pages hosted on ISP-run web servers, or on free web hosting services such as Tripod and the now-defunct GeoCities.[14][15] With Web 2.0, it became common for average web users to have social-networking profiles (on sites such as Myspace and Facebook) and personal blogs (sites like Blogger, Tumblr and LiveJournal) through either a low-cost web hosting service or through a dedicated host. In general, content was generated dynamically, allowing readers to comment directly on pages in a way that was not common previously.[citation needed]
-Excerpt From: James Bridle. “New Dark Age.” Apple Books. ]
- Short history of web2
- what went wrong with web 2? Hyper-growth on losing units
- The inevitable melting of web2
[The internet as we know it today is Web2.0 (2000s-2020s). Centralised companies like Facebook and Google solved these problems by allowing non-technical users to create pages, share photos and text, search, message friends and colleagues, share files and more. They wrapped the Web1.0 protocols in delightful user interfaces, trading off decentralisation and ownership for utility and distribution.]
Web 2.0 (also known as participative (or participatory)[1] web and social web)[2] refers to websites that emphasize user-generated content, ease of use, participatory culture and interoperability (i.e., compatibility with other products, systems, and devices) for end users.
The first time I encountered “Abstractization” as a kid
Mark Zuckerberg is known for the hacking culture he confers on his employees – rebelling against authority, building new things, and finding tricks or bypasses. The problem with Facebook is that this culture remains only inside the company and development teams.
The users themselves, meaning all of us, are given no room for “hacks.” If you have a Facebook profile and you revolt or upload unusual content, there’s a chance your account will get deleted. The ability to change and develop your Facebook profile, in ways that are yet to be developed, does not exist.
A natural evolution and development cannot exist with such narrow options. There is no room for new iterations and being cutting-edge. It does not allow for the necessary diversity needed to create a true city. This is the problem with Facebook.
Sterling, Bruce, Lorraine Wild, and Peter Lunenfeld. Shaping Things. Cambridge, Mass: MIT Press, 2005. Print.
Nakamoto, S. (2008) Bitcoin: A Peer-to-Peer Electronic Cash System. https://bitcoin.org/bitcoin.pdf
Berners-Lee Tim. Information Management: A Proposal. CERN, March 1989, May 1990
Ronfeldt David. Tribes, Institutions, Markets, Networks. https://www.rand.org/content/dam/rand/pubs/papers/2005/P7967.pdf 1995
Tung-Hui Hu. A Prehistory of the Cloud. MIT Press. 2016.
“Paul Baran and the Origins of the Internet” https://www.rand.org/about/history/baran.list.html 1996
Barlow John P. A Declaration of the Independence of Cyberspace. https://www.eff.org/de/cyberspace-independence 1996
[stick charts reference: https://www.smithsonianmag.com/smithsonian-institution/how-sticks-and-shell-charts-became-sophisticated-system-navigation-180954018/
https://decolonialatlas.wordpress.com/2015/04/19/micronesian-stick-charts/]
Niranjan Kundapur. On Integrating Physical Objects With the Internet. https://dspace.mit.edu/bitstream/handle/1721.1/89297/48379679-MIT.pdf
A prehistory of DAOs - explaining steps being taken in web3.0
Composability - A platform is composable if its existing resources can be used as building blocks and programmed into higher order applications. Composability is important because it allows developers to do more with less, which in turn, can lead to more rapid and compounding innovation.
Semantic web info from w3.org - discussing linked data (Tim Berners-Lee’s concept), queries, inference, vocabularies, and vertical applications
Tim Berners-Lee’s current projects at MIT - Solid Inrupt
Examples:
Abstract Car has its own Abstract - cultural and financial digital representation - that cites using “contain relationship” each one of its parts. Each part has its own abstract. These abstracts includes:
Not a tesla model 3
Let’s imagine Tesla model 3 as an abstract car - it means the entire car, including all its technologies is available for all. A small manufacturer can use these in its own car - by citing these parts. If he’ll become successful, Tesla will gain value automatically - without any need for specific business-terms. It’s an open-source car with built-in financial zero-mediators, zero-waste mechanism. The composability of this car is not just in content and technology, but also a “Financial Composability”.
You’ve ordered a dish in a Michelin starred restaurant. What are you eating? What are the ingredients? Is the recipe public? Is it homage to a traditional meal? We’re very ignorant regarding the source, value and history of our food - even if consumed in high-end restaurants. An abstract dish will include all the above information, with Abstractization to ingredients.
When you pay for the dish a value is being distributed to all its suppliers - both physical suppliers and intellectual suppliers.
Abstract software will spread value to all it’s abstract open-source software it uses. It’s an efficient and elegant solution that allows the availability of open source - but in a sustainably financial way.
I just bought a house. What is its energy rating? Which parts can be more efficient?
I need to make a paint repair - Which exact color was used for the walls?
Can I see the most recent inspection? Invoices of work done in the house?
A clear list of taxes?
Wanna buy? Sell? The Title is embedded in the Abstract of this house - no intermediaries are needed.
Abstract community projects will break down and deconstruct environmental projects like the redesign of the Los Angeles river. It will be implemented in participatory design processes that will involve the community’s perspective, through incentivizing collections of thoughts, ideas, and verifications. Right now there is a barrier to true community involvement in environmental projects, like rivers, that will affect those up and down the river. In order to make sure that a design has longevity for everyone affected, there needs to be a way to collect and relate information that is publicly accessed and created (through shared databases, interface technologies, and simulations). In order to do that, there has to be a peer to peer incentive for participation.