OI
Opening and decentralizing collaboration protocols
The vision of open-source information is to expand the ability for communities to coordinate and build with open access to knowledge. Open information (OI) includes relevant resources from public domains, individuals, both company and project's documentation, and etc. Open information makes use of collective knowledge that has the potential to simultaneously cover more surface area and be more in-depth than more centralized sources of truth.
Thereβs only two ways to make money in business: One is to bundle; the other is unbundle - Jim Barksdale (CEO) and Marc Andreessen (Co-founder) of Netscape
This also applies to how distributed sources of information can centralize over time. As information moves faster than ever this poses risk to collaborative decision making if information's origins are not known (closed-source) and controlled by a few gatekeepers (centralized).
Distributed technology, self-ownership of accounts, and data have the opportunity to make open information the norm for individuals, communities, and institutions, with inspiration from many projects, protocols, and organizations.
Strategy
- Make useful tools and processes for individuals and then expand usefulness to many people and organizations.
- Progressively improve upon open-source, decentralization, and security.
No existing platform has all of these features and some features have not been fully created yet.
Accounts
- Self-ownership of account
- E.g. Sign in with Ethereum (SIWE)
- Sybil resistant verification
Editor
- Markdown based (
.md
) files: Open info
- Keyboard shortcuts for productivity
- What you see is what you get (WYSIWYG)
- Graphical user interface (GUI) to write in Markdown
- Set metadata
- Sets the information that shows in the browser window/tab and link preview.
- E.g., Title, description, tags, image, and etc.
- Save templates based on use case/topic
- Spell and grammar check
Viewing
- Copy and paste content in all browsers
- Format ordered and unordered lists with multiple levels of nested children
- Autogenerated table of contents (ToC) for the page
- Autogenerated global navigation menu
- Dynamic re-sizing
- Table of contents and global navigation menu re-size with the screen
- Deeplink into Markdown and HTML elements
- Default readable links
- E.g.
hosted-platform's-domain.com/open-info
- Custom links using "owned" domain
- E.g.
my-custom-domain.xyz/open-info
- Search
- Shallow: Page titles
- Deep: Page contents
- Automatic light/dark mode based on user's device settings
- Customizeable user interface (UI)
- E.g., Font, colors, sizing, and etc.
Version control systems (VCS)
- UX for version control
- Powered by Git
- Manage versioning without interacting with Git directly
- E.g., GitHub, GitLab, and Radicle
Security
- Multi-factor authentication (MFA)
- Data stored and transferred is end-to-end encrypted (E2EE)
- Export and import Markdown (
.md
) files
- Self hosting
- Decentralized hosting
- E.g., Arweave and IPFS storage
Governance
- Access controls of team and contributors
- New member edit access
- User contribution tracking
- Contested info
- Ability to fork pages for heavily contested information
- Users can save their page fork preferences
- Information consensus mechanisms
- E.g. Snapshot voting: Open info
Programmability
- APIs
- E.g., Publishing to decentralized networks such as Arweave and IPFS, self-hosting, backups, and etc.
- Mobile app or great mobile web app
- Offline viewing and editing
- Desktop
- E.g., Microsoft, Mac, and Linux
- Sync files locally (Similar to Dropbox and Google Drive's apps)
Inspiration
This is not technical advice. Do your own research.