TransferableContext

Mutable Web

Welcome to the μWeb, a groundbreaking evolution of how users, developers, and businesses interact with the internet. Traditional web experiences are static and rigid, offering limited opportunities for customization and adaptability. The Mutable Web changes all of that by enabling seamless, dynamic interaction with web content, creating a more personalized, powerful, and efficient online experience.

Introduction

The internet has become an essential part of our lives, yet its current structure often limits creativity, flexibility, and personalization. The Mutable Web addresses these limitations by introducing a paradigm shift that benefits users, developers, and businesses alike. Here’s why the Mutable Web is the next big thing in the evolution of the internet.

Why Mutable Web?

In today’s web, users have little control over how they interact with content. Websites dictate their design, functionality, and even the policies that govern user interactions. But what if the web could be molded to your preferences? That’s the power of Semantic Contexts within the Mutable Web—a revolutionary approach that shifts control from centralized entities to individual users and communities.

Semantic Contexts

The Mutable Web is built on a set of foundational components that work together to redefine how we interact with digital content. Each component plays a critical role in enabling customization, integration, and collaboration, making the web more dynamic, user-centric, and adaptable. Let’s explore these key components:

Key Components

The Mutable Web thrives on the interplay between various roles and operations, which collectively drive its functionality and adaptability. This decentralized ecosystem empowers users and developers to collaborate, customize, and innovate, making the web more dynamic and user-centric. Let’s dive into the key roles and operations that make this ecosystem work.

Roles and Operations

In the Mutable Web, every interaction with applications, mutations, and objects follows a consistent workflow, ensuring a seamless and efficient user experience. This universal lifecycle comprises three key stages: Local Change, Publish, and Pull Request.

Universal LifeCycle

Picker — a tool that allows users to select a contextual area on a web page in order to perform actions on it or extract useful data. This tool is provided by the platform for application developers, who define how and for what purposes the Picker will be used.

Picker tool

Streamlined Identity Management Across Web2 and Web3.

Connected Accounts

WebGuide is a lightweight application within the Mutable Web ecosystem. It empowers users to enhance their browsing experience by offering intelligent navigation and customization options.

WebGuide

AI Crawler is a web exploration tool designed to help individuals and organizations gather, analyze, and utilize web data efficiently. By simplifying the data extraction process, AI Crawler enables users to unlock actionable insights with ease and precision. As an added incentive, users are rewarded with cryptocurrency for their data scraping activities, making the experience not only productive but also financially rewarding.

AI Crawler

DappletContextPicker is a component that enables context picking mode, provides latches for specific contexts, and onClick callback functions.

DappletContextPicker

Use the function to get Connected Accounts list.

getConnectedAccountsNet

Highlighter is a component that highlights a target element using specified styles.  The DappletContextPicker feature uses this component under the hood to highlight the contexts that are available for selection.

Highlighter

InjectableTarget

LatchProps

TargetCondition

Target

What is Applications

This example describes the configuration of an onboarding app for multiple platforms, such as GitHub and LinkedIn, X.

Onboarding App

A simple example of configuring an app for document handling.

Document App

This example shows the configuration of an app for storing and retrieving data linked to specific context (e.g., a Twitter post).

Link DB

A web guide example that can be displayed on any website.

Web Guide App

This example shows callouts for the onboarding and web guide apps. Callouts appear after the text in a Twitter post.

Test Callouts

The mutation schema is designed to enhance accessibility to intelligence across various platforms. This document provides an overview of the schema configuration, including its metadata, target applications, and contextual conditions.

Mutation Schema

The parser configuration is designed to facilitate the parsing and management of content across various websites. This document provides an overview of the parser type, target conditions, and contextual structures.

Parser Configuration

Track the key updates, improvements, and changes in the Mutable Web ecosystem throughout 2024. Stay informed about the evolution of our platform.

Changelog 2024

Explore the major updates, improvements, and milestones achieved in the Mutable Web ecosystem throughout 2023. Stay informed about the progress and innovations that shaped our platform.

Name	Type	Default	Description
`namespace`	`string`		Specifies the namespace to work with. Options: `'engine'`, `'mweb'` or site specific parser config, for example `'bos.dapplets.near/parser/twitter'`. By default, all available namespaces are used.
`type`	`string`		Specifies the context type in the selected namespace to work with. Is equal to the `contextType` of `Target`.
`level`	`ContextLevel`	`'default'`	Options: `'default'`, `'system'`, `'callout'`. Specifies the z-axis position (z-index) relative to the extension’s UI components.
`id`	`string` or `null`		Specifies the exact context identifier.
`parsed`	`any`		Context payload.
`parent`	`TransferableContext` or `null`		Parent context.
`isVisible`	`boolean`		If `true`, only visible contexts will be active.

API REFERENCES