The bmannconsulting.com website

subconscious

+13
_journals/2024-05-16_1129.md
···
+
---
+
title: May 16th, 2024
+
date: 2024-05-16, 11:29:01 -07:00
+
section: journal
+
link: https://subconscious.substack.com/p/subconscious-is-winding-down
+
tags:
+
- Subconscious
+
- AI
+
- toolsforthought
+
---
+
The [[Subconscious]] team is announcing that they're [shutting down](https://subconscious.substack.com/p/subconscious-is-winding-down). The very short version from [[Gordon Brander]] "Today, if you want to amplify intelligence, you probably wouldn’t build a decentralized notes graph, you would go to work on personal AI."
+
+
Having just gone through this with Fission, I feel for Gordon and cdata and the whole team. Thank you for striving, for your writings, and for the wonderful community you built in your Discord.
+38
_notes/Directus.md
···
+
---
+
tags:
+
- headlessCMS
+
- baas
+
- BSL
+
- backend
+
- saas
+
link: https://directus.io/
+
github: https://github.com/directus/directus
+
---
+
Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.[^githubreadme]
+
+
Directus is a real-time API and App dashboard for managing SQL database content.
+
+
- **Open Source.** No artificial limitations, vendor lock-in, or hidden paywalls.
+
- **REST & GraphQL API.** Instantly layers a blazingly fast Node.js API on top of any SQL database.
+
- **Manage Pure SQL.** Works with new or existing SQL databases, no migration required.
+
- **Choose your Database.** Supports PostgreSQL, MySQL, SQLite, OracleDB, CockroachDB, MariaDB, and MS-SQL.
+
- **On-Prem or Cloud.** Run locally, install on-premises, or use our [self-service Cloud service](https://directus.io/pricing).
+
- **Completely Extensible.** Built to white-label, it is easy to customize our modular platform.
+
- **A Modern Dashboard.** Our no-code Vue.js app is safe and intuitive for non-technical users, no training required.
+
+
[^githubreadme]: This top part is all from the Github README
+
## Licensing
+
+
[[BSL]] licensed.
+
+
> Commercial license only required for entities over $5 million in total finances
+
+
## Pricing
+
+
Cloud version is $129/monthly or $99/month if billed annually. Database, "asset size", API requests, and bandwidth are metered.
+
+
Non-profit / open source discount:
+
+
> Yes, we do! Being open source ourselves, we're aware of how important it is to support open-source maintainers. If you are the maintainer of an open-source project (see policy below), contact us to discuss available discounts.
+
>
+
> our Directus Cloud owner account email must match a GitHub account that is the primary maintainer of an open source repository and must have existed for at least 6 months and/or have 100 stars.
+49
_notes/Grist Labs.md
···
+
---
+
link: https://www.getgrist.com/
+
tags:
+
- organization
+
- NYC
+
- software
+
---
+
Grist Labs is a software company. We care about software because it matters inordinately for today’s world — for productivity, communication, decision-making, human progress, and life pursuits.
+
+
## Pricing
+
+
Makers of [[Grist]], they run a SaaS cloud service.
+
+
The free-forever plan:
+
+
- Unlimited number of documents.
+
- Up to 5,000 records per document.
+
- Snapshot history goes back 30 days.
+
- 100 AI Formula Assistant credits (one time)
+
+
[Paid team pricing](https://www.getgrist.com/pricing/) starts at $8/user/month
+
+
## About
+
+
Below included from their very inspiring [About page](https://www.getgrist.com/about/)
+
### Our software principles
+
+
1. Software should be _for_ the people: to enable and serve them, not limit and control.
+
2. The security and privacy of software users are fundamental. They must not be for sale or treated as optional.
+
3. Free and open source software provides the basic foundation of trust in embodying the above values.
+
4. Quality of software is important, including functionality, reliability, usability, and performance.
+
+
### Who we are
+
+
Grist Labs was founded in 2014 and has been self-funded ever since.
+
+
The company was started by brothers Dmitry and Stan Sagalovskiy. Dmitry previously co-founded Hudson River Trading in 2002 (a high-frequency trading firm, which still exists and is going strong), and New York Math Circle in 2008 (an educational non-profit, which still exists and is going strong).
+
+
In 2017, Paul Fitzpatrick joined Grist Labs as CTO. Paul co-founded Data Commons Cooperative in 2012 (a co-op of over 30 member organizations, which still exists and is going strong). He brought his own passion for democratic flows of data, and experience as the creator and maintainer of multiple popular open source data tools.
+
+
<mark>Grist Labs was founded shortly after mass surveillance disclosures exposed the vulnerability of even the most respected cloud services. The best remedy we knew was open source code, transparent security practices, and enabling users to use their own infrastructure.</mark>
+
+
Grist was <mark>originally envisioned as installable software with end-to-end encrypted sharing – software that users can trust</mark>. Users would have full control of data, and would not need to trust the cloud. <mark>A SaaS service, however, is simpler for users, easier to start with, and easier to share with others.</mark> That’s what we released.
+
+
Since then, we’ve open-sourced Grist and made it possible to run a Grist instance on your own infrastructure. We’ve been working on making Grist run everywhere. A version of Grist can now run on the desktop of every major OS.
+
+
The original vision of “software users can trust” has grown into the vision and values described on this page.
+
+
Grist Labs is headquartered in New York City, with a distributed team that spans half the globe: from Canada to South Africa, and from California to Poland. (Our users span the rest of the globe!) Read more about [our team](https://www.getgrist.com/our-team/).
+38
_notes/Grist.md
···
+
---
+
tags:
+
- opensource
+
- app
+
- spreadsheet
+
github: https://github.com/gristlabs/grist-core/
+
---
+
Open source, Apache licensed cloud spreadsheet. Not quite an Airtable clone, but similar capabilities. Some of the layout and linking makes it feel like Filemaker.
+
+
> Grist is a modern relational spreadsheet. It combines the flexibility of a spreadsheet with the robustness of a database.
+
+
Grist is a hybrid database/spreadsheet, meaning that:
+
+
- Columns work like they do in databases: they are named, and they hold one kind of data.
+
- Columns can be filled by formula, spreadsheet-style, with automatic updates when referenced cells change.
+
+
There is a [user-created packaging of Grist](https://git.cloudron.io/walski/grist-app) for [[Cloudron]].
+
+
## Grist essentials
+
+
1. **Relational database** that’s easy to create and use by non-technical people.
+
2. **Data/view** separation, for app-like functionality, easy to set up and use by non-technical people.
+
3. Sharing and **access controls** that allow users to address complex real-world access requirements.
+
4. **Open source**, for transparency and trust in the software’s promises, and freedom for technical users to improve it. [Read more](https://www.getgrist.com/blog/grist-a-hacker-friendly-spreadsheet/) on this.
+
5. Options to run **self-managed**, or on the desktop; reliance on a service provider is optional.
+
6. Support for spreadsheet-like **formulas**, to extend use cases and empower users.
+
7. Extensibility via **APIs** and other integration points.
+
8. Data is **portable**, allowing lossless export in a well-supported format, and common export/import options.
+
9. Comprehensive **documentation** and learning materials.
+
10. **High quality** implementation, well-tested, with a focus on reliability and performance.
+
## Grist Labs
+
+
From Github README:
+
+
> The `grist-core` repo is the heart of Grist, including the hosted services offered by [Grist Labs](https://getgrist.com/), an NYC-based company 🇺🇸 and Grist's main developer. The French government agency [ANCT Données et Territoires](https://donnees.incubateur.anct.gouv.fr/toolbox/grist) 🇫🇷 has also made significant contributions to the codebase.
+
+
I've captured more on the [[Grist Labs]] -- a very inspiring team / company. They
+
+21
_notes/Headless CMS.md
···
+
---
+
draft: "true"
+
tags:
+
- CMS
+
- baas
+
- backend
+
---
+
Headless CMS or other data-first builder for information / API building.
+
+
Interested especially for events, where you want to model some of these elements:
+
* Events
+
* Talks
+
* Rooms
+
* Locations
+
* Venues
+
* Sponsors
+
* Speakers
+
* Attendees
+
## [[Directus]]
+
+
Available on [[Cloudron]]
+12
_notes/Open Social Protocols.md
···
+
---
+
tags:
+
- protocol
+
- openweb
+
---
+
+
+
The three protocols that I think are going to continue to grow and be adopted are:
+
+
* [[ActivityPub]]: Meta building Threads with ActivityPub support, and AP's status as a [[W3C]] standard will keep it around
+
* [[ATProtocol]]: most scalable architecture.
+
* [[Farcaster]]: crypto-adjacent while also being primarily off chain data. Will be the basis for many crypto-centric social experiences. Innovation of creating [[Farcaster Frames]]
+89
_notes/SoP 2024 Application.md
···
+
---
+
link: https://forum.summerofprotocols.com/t/pig-community-search-engines-event-chat-artifacts-as-research-building-block/879
+
tags:
+
- sop24
+
---
+
I applied to the Summer of Protocols 2024 program with this RFC plus a private personal submission that [[walkah]] and I sent in. It was not accepted. I now call this [[Community Search Engines]].
+
# Community Search Engines: Event & Chat Artifacts as Research Building Block
+
+
## Team member names
+
* [Boris Mann](https://bmann.ca)
+
* [James Walker](https://walkah.net/)
+
+
The protocol of in-person conferences, symposium proceeedings, and other classic gatherings are at best stuck in a published PDF or slide deck world. If you're lucky, event websites have permalinks that remain year over year, and maybe a youtube playlist or two.
+
+
And, we have yet to develop a protocol that better supports digital communities, hybrid events, unconferences, and other emerging forms.
+
+
We propose a Community Search Engine Protocol for events & digital communities.
+
+
### Short summary of your improvement idea
+
+
Events, Cozy Web digital groups, and other gatherings are all flow, no stock. Every group should have access to easy tools to gather community context.
+
+
Part community search engine with high relevance resources from people you have trust with, part serendipitious discovery from webring surfing.
+
+
In the age of AI, leaning into a trusted community context can further help to elevate signal from noise.
+
+
### What is the existing target protocol you are hoping to improve or enhance?
+
+
Today's events, from meetups to traditional full conferences, at best use a static snapshot of an event websitem, slides, and speaker bios. If the event has enough funding ($1000s of dollars), there are high quality video recordings, and maybe some attempt is made at transcripts.
+
+
For [Open Space Technology](https://en.wikipedia.org/wiki/Open_space_technology) / unconference techniques, images of sticky notes and personal write ups, and perhaps professional facilitation summaries or live graphic facilitation could be part of the artifacts.
+
+
### What is the core idea or insight about potential improvement you want to pursue?
+
+
Digital gardens with valuable backlinks are stuck in single-player mode or commercial platforms. Chat communities, especially those on commercial platforms, are constantly losing context, or their entire archives. An easy toolkit for communities to gather context, resources, and new insights that can grow over time. Community Search in a box.
+
+
### What is your discovery methodology for investigating the current state of the target protocol?
+
+
We've run events and communities of this form for years. We will look to find other pains and problems by interviewing other community leaders and recruiting early testers.
+
+
### In what form will you prototype your improvement idea?
+
+
We will produce a toolchain of code and configuration as well as test installs of a community search engine.
+
+
Some of the building blocks we will look to use as starting points:
+
+
* [Lieu](https://github.com/cblgh/lieu) an existing open source community search engine
+
* The [Noosphere](https://subconscious.network/) tool-for-thought protocol
+
* Social feeds of community participants from Bluesky, ActivityPub, and Farcaster as a source of new resources
+
* RSS feeds that are aggregated and synced p2p as local resources for each person using IPFS -- both as distributed archive and way to include ongoing content over time
+
+
### How will you field-test your improvement idea?
+
+
**Causal Islands Toronto 2023:** [Causal Islands](https://causalislands.com) as a traditional centrally organized multi-day conference. The current archive, including high quality. It has spawned a Discord and Podcast and desire for more "Causal Islands" style events, including one "community edition" in LA. Participants have said they'd like to see more of these events, as well as better find a home for computational research / future of computing topics embodied by the original conference.
+
+
Can we turn a conference into a community, and facilitate a template for future events?
+
+
We will start by using the 2023 event outputs, including inviting attendees of that event to add their personal resources, in creating a community search engine.
+
+
**The Discord formerly known as Fission:** Fission the company is shutting down, but the community Discord continues. Chat is notoriously bad at capturing long term context, and Discord as a commercial platform is not a good long term home.
+
+
We will explore extracting links and people into a community search engine.
+
+
This approach should be expandable to other Discord-based communities.
+
+
---
+
+
This approach may also be interesting for the SoP community itself.
+
+
We will look to recruit other communities to try out the process, including beta testing if technical people can effectively configure and deploy the tooling on their own, as well as differing approaches to activating the communities themselves.
+
+
### Who will be able to judge the quality of your output? Ideally name a few suitable judges.
+
+
* Gordon Brander
+
* Ronen Tamari
+
+
All of these might also be collaborators. Ideally communities and people who try and install / deploy this will be those who can help judge if it's helpful
+
+
### How will you publish and evangelize your improvement idea?
+
+
We will publish a repo containing the community search engine, configuration, and deployment guidelines to get up and running.
+
+
We will create an onboarding and community activation checklist to help communities be successful.
+
+
We will find seed communities to deploy into, and host introductions and kick off events both virtually and in person.
+
+
### What is the success vision for your idea?
+
+
Communities of interest that form around events, digital places like chat groups, and other gatherings have an easy way to deploy a community search engine that provides both archival as well as ongoing high context trusted resources over time.