The bmannconsulting.com website
bmann.ca
1---
2tags:
3 - WIP
4---
5The base line tool that I am looking for to anchor [[Community Search Engine]] is a multi-player personal notes & publishing stack.
6
7You should feel comfortable putting meeting notes, quick scratch notes, pages on their way to be published, links and a few comments, research from multiple web pages, and other material in here. It is your companion for research, progress, and evolution.
8
9It wants to displace Apple Notes and Google Docs, and be a place where you stage short and long form social media.
10
11It wants to be the digital place where your family group, project team, or entire small business go to find, document, and extend a growing model of useful information.
12
13It's where you store the results from searching, browsing, or collaborative agent-based research sessions.
14## Notes
15
16Notes should have the following features:
17* a title
18* a unique identifier that is separate from the title (e.g. changing the title doesn't break links)
19* wikilinks or @-mention or similar affordance to easily link to existing or stub new notes
20* backlinks, where linking to a note also showcases a "backlink" when viewing the note. This creates a graph of linked notes
21
22There are some other features like tags, aliases or transclusion that needs some more thinking.
23
24## Journal
25
26Increasingly, the concept of author / creating / updating over time is an extremely useful anchor.
27
28Opening notes and having date / time stamps as a default entry is good. Simple mode is one "day" note per day. A more excellent mode that also fits with shorter content publishing and sharing is block-based unique notes.
29
30Visually, collecting notes into day / week / month chunks is one way to display aka a "log" or "work log". So a day becomes a view, but can contain multiple
31
32## Files
33
34Export and import of Markdown notes should be supported, but strict representation of one note == one file at all times is not necessary.
35## Multi Player Notes
36
37Multi-player does not necessarily mean real time collaborative editing. It starts with a single person having multiple devices where things are kept in sync, and goes from there to groups of people.
38
39The hardest part of multi player notes is permission management. "Open" collaborative notes like [[HedgeDoc]] are easy, but can suffer from spam. Security through security by sharing links to hashes can work pretty well.
40
41The "folder" model seems conceptually simplest. Make a folder, add access at that level, and then everything inside inherits that.
42
43Sharing the same info with multiple different groups outside of a strict hierarchy is a challenge. This might mean using something like tagging to grant access. This is both a UX (what do you do in practice to share) and UI issue (how do you display shared docs or approximate GDocs permission listing).
44
45Google Drive has ended up with this concept of "aliases", in order to have a document in multiple folders. Google Drive also complicates the folder model by allowing for different permissions inside a single folder. This means that everyone has a different view. Related: having variable "views" might be needed along with "baked" views where everyone has the same picture. Views might in fact be something that you collect or curate and then publish to a group.
46
47## Agentic Goal Workspaces
48
49How does one collect multiple people and agents into [[Goal Workspaces]]? A shared space with some goal, where different views, visualizations, interfaces, and data sources can be pooled to meet that goal.