Sharing an open source SQLite extension

[Vince Scafaria]

Hello! 

Our non-profit created an open source project "Whosum Social Assistant" that uses Chrome's awesome SQLite (OPFS) in-browser database (thank you!). I welcome any thoughts, feedback, or collaboration. It was only just now submitted to the app store, but of course you can try it unpacked. 

Without requiring server-side APIs, it allows a Twitter user to cache their follower/following lists, search within them, flag favorites, and scan for Mastodon account links, email addresses, etc. Think of it as a DVR for caching and then personalizing online social networks and experiences, starting with Twitter. It includes generalized database code for versioned migration, Save, and more (a proto-ORM), especially see this file (and comments at top of file about use of RDF). It also avoids using third-party scripts (other than SQLite jswasm), so that all code can easily be understood by a single reviewer (which we believe is an important trust element.)

I'm a huge believer in local-first, privacy-first apps as a way of giving back power to end-users (video), who (let's face it) don't manage personal web servers (yet server nodes are the unit of power on the Internet!). That's why I'm so excited about Chrome with SQLite/OPFS. When the Chrome team implements the feature that Oliver described in his earlier reply to me (background workers accessing the database), it will open the door to a full suite of "digital robot butler" apps that serve the individual without exfiltrating private data. Very exciting! 

I'm excited to be part of this community! I'm also new here, so if you have suggestions on how I should best engage (sharing, meeting collaborators, this note, etc.), please let me know. 

Vince Scafaria

Positive Sum Networks

portable digital identity: https://whosum.com/gh/scafaria 

Create your own at whosum.com!