This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Name of Project:
Memex + IPFS/Filecoin + TextileProposer: @blackforestboi @ShishKabab @andrewxhill
Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT and APACHE2 licenses?:
Yes
Potentially interesting for
Project Description
Problems:
WorldBrain's Memex is a browser extension for full-text history search, annotations and web archiving. This data is valuable to store on IPFS or Filecoin, but an integration is missing. What can be shared:
For app developers there are frictions in experimenting with IPFS because the entire architecture needs to be built on top of it, or suitable abstraction layers need to be considered from the start.
Solutions
At WorldBrain we developed StorexHub, an offline-first Zapier. Its original purpose is to enable developers/users to integrate Memex with any app or technology. However it also allows to connect any app with each other and has a database abstraction layer to flexibly use different database technologies and transport protocols like IPFS.
Adding a IPFS/Filecoin plugin gives users the ability to selectively store their (Memex) data on IPFS/Filecoin
Example use case:
A Memex user curates a list of articles, annotations and web archives with the most useful articles about the COVID crisis. They set up the IPFS integration to automatically sync this collection, and also everything that is tagged with "IPFS". (Video example with Gist)
Developers can also experiment more flexibly with IPFS since they can start with more traditional databases and then gradually migrate to IPFS without rewriting their application logic or just use IPFS for some of their functionality. A gradual decentralisation- and infrastructure migration process becomes possible.
Example Use Case
Memex's (or other apps) sharing functionality can be done with IPFS/Filecoin, while the rest of the system uses the browser internal database.
Migrating Memex entire application logic from IndexedDB (browser extension) to TypeORM (mobile) took 1 day.
Value
What are the benefits to getting this right?
Memex can provide that because its main users are developers, (investigative) journalists, 2nd Brainers and overall knowledge workers.
What are the risks if you don't get it right?
What are the risks that will make executing on this project difficult?
Nothing major we can think of. The only thing is that we are working with Textile.io's stack for the first time. With Andrew we have the right advisors on board to make the integration smooth.
Deliverables
Definition of done
Development Roadmap
Milestone 1:
Implemented IPFS/Filecoin plugin for StorexHub with Textile's Threads
Lead: Vincent den Boer
Advisor: Andrew Hill
Time: 2 days á 600€/day = 1200€
Milestone 2:
Added database abstraction to enable any app connected to StorexHub to use the IPFS integration.
Lead: Vincent den Boer
Time: 2 days á 600€/day = 1200
Milestone 3:
Written documentation for developers and users on how to use IPFS integration
Lead: Oliver Sauter
Advisor: Vincent den Boer
Time: 1 day á 600€/day = 600
Total Budget Requested
3000€
Maintenance and Upgrade Plans
This integration will be kept up-to-date with Textile's Threads latest versions.
The work provides a forkable reference implementation that can be maintained by the community.
The next step after this proposal is to add an end-user-friendly, Wordpress-like interface to setup, configure and maintain this plugin. This is potentially part of another proposal though.
See for more: https://www.notion.so/worldbrain/StorexHub-Interface-3a6024e9538e404ab4df41771302de3f
Team
Team Members
Team Website
https://getmemex.com
https://textile.io
Relevant Experience
We're the developers of Memex, StorexHub and Textile and offer all relevant product and technical experience to finish this project in a timely manner.
Team code repositories
https://github.com/WorldBrain
https://github.com/textileio