@boris perhaps @peterkaminski has thoughts, he's doing some community multi-tool stuff that includes wiki.... though it may be #MassiveWiki.
http://webseitz.fluxent.com/wiki/MassiveWiki

Finally, over the weekend I threw together a short video explaining how #massivewiki fits into the ecosystem, and how to get started: https://www.youtube.com/watch?v=qfYl3SiZJWU

Another post introduces the pilot project @peterkaminski & @band & I are working on: using #MassiveWiki to map the #ToolsForThought landscape. Apart from exploring decentralised collective intelligence, we hope to help newcomers adopt #TfTs, which create the "raw material" (networkable knowledge) required for collective intelligence: https://mathewlowry.medium.com/mapping-tools4thought-using-collective-intelligence-tools-9b5cd00a6309

Visit the community announcement at https://lu.ma/community/com-mmvGpDTZoRDsxou/library/e/entry-jO6dgMlM3GMPbfa for extended details on the #ToolsForThoughtRocks Mastodon server and @bmann experimenting with #MassiveWiki

@boris @vanderwal

(cont'd) Another good way to start with #MassiveWiki is to drop by one of our community spaces:

- weekly Massive Wiki Wednesday call, Wednesdays at 9am PT, 12pm ET, 5pm or 4pm UTC
- chat channel on CSC Mattermost, https://chat.collectivesensecommons.org/agora/channels/massive-wiki (free signup required)

We're a small group, but we're friendly and helpful. Massive Wiki is not conceptually too difficult, but it's more fun to get through gotchas with other people.

(more about CSC: https://collectivesensecommons.org/ )

2/2

@boris @vanderwal:

VS Code is a fine #MassiveWiki frontend.

I tend to avoid it because 1) it's needlessly more complicated for non-devs; 2) MS is actively enclosing open source dev ecosystems.

Thomas, thanks for pointing to the starter guide. It's okay, but needs a big rewrite...

Boris, you have background; all you need to know is that Massive Wiki is shared, versioned #Markdown files with wiki links. Git is one way to version and share.
https://massive.wiki/massive_wiki_conceptual_diagram

https://massive.wiki/massive_wiki_manifesto

1/2

@peterkaminski why not a VS Code plugin?

What’s the best “getting started” link for #MassiveWiki ?

#MassiveWiki: While we love using #Obsidian as one of the frontends for Massive Wikis, we are starting to evaluate #PulsarEdit (the community successor to Atom) for working with branches and pull requests.

To an Obsidian user who is willing and able to be a little adaptive, Pulsar's UI is reasonably similar, and the Git experience is more streamlined and more comprehensive.

(Obsidian Git can switch branches and commit to branches, but afaik it can't make branches or create pull requests.)

1/2

@gfriend @absamma Nice #ToolsForThought (anti-)writeup, thanks!

Inspires lots of thinking (lol), and maybe someday some followup writing.

+1 for using the best tool for the job. The #MassiveWiki pattern is also to simplify to core tech - #Markdown, #Git, filesystem - that can be found in or repurposed for many tools.

Will have to consider replacing some of my #Airtable use with #SQLite

It would be interesting to see him move from tools & tasks to thinking, knowing, remembering.

@kraken I have and participate in a number of #Obsidian #ObsidianMD vaults.

I'm in more vaults than normal because in the #MassiveWiki project we use Obsidian as a primary client, and I get a LOT of value from having personal/private vs. shared vaults, you need that split.

Plus, I have a few personal public vaults for specialty topics.

It's not perfect, but to maintain useful page connections, I just copy the same page to whatever wiki needs it.

It's okay if pages don't stay in perfect sync.

@ryanrandall

I've been brainstorming on a very related issue for #MassiveWiki, the conundrum of evolving wiki pages vs. #permalinks.

Here are my two takes so far:

- https://developer.massive.wiki/tech_notes/tech_note_-_permanent_html_snapshots
- https://developer.massive.wiki/tech_notes/tech_note_-_permanent_versions

For #RSS, I think a (non-trivially) edited version could be a new item in the feed, especially if it has its own permalink to that version.

@olasd:

Trigger warning: not automated. 🙂

In my collaborative projects we use #HackMD realtime editing.

We just have an established convention that pages get a good H1 `# Title` as the first line & that they get exported as #Markdown files to a #MassiveWiki when work is complete on that pad.

Then we edit the pad title to include the phrase "moved to wiki" or similar & delete the body of the pad so the wiki page is now obviously the primary version.

The steps are few & easy, even if manual.

Also back today digging into Massive Wiki and prepping to set it up for something over the next few weeks. #massivewiki

Also back today digging into Massive Wiki and prepping to set it up for something over the next few weeks. #massivewiki

I wrote a #MassiveWiki tech note on moving away from GitHub to another forge, perhaps Codeberg.

Massive Wiki is still alpha/beta, but if you like wikis or Git forges, maybe you'd be interested.

https://developer.massive.wiki/tech_notes/tech_note_-_preferring_a_different_git_forge

(you can use Hypothes.is to comment)

same page on GitHub:

https://github.com/Massive-Wiki/developer-massive-wiki/blob/main/Tech%20Notes/Tech%20Note%20-%20Preferring%20a%20Different%20Git%20Forge.md

(if you're a geek and a good person, I can give you write access to the repo)

@shibacomputer @richjensen Massive Wiki <https://massive.wiki/> is a "promising option", but it is still in early days (alpha for most people, beta for techies) and probably isn't a good option for your needs right now.

I mention it because some day it will be 🙂, and because it's open, pretty pure, and pretty good in a lot of ways.

DM or email me kaminski@istori.com if you'd like to discuss #MassiveWiki #tiddlywiki or other #wiki - I know a fair bit about #DigitalGarden stuff in general.

@band it does, although #MassiveWiki still doesn't seem quite user-friendly enough?

Or, perhaps #MassiveWiki is more or less as friendly as other wiki engines, and maybe we just haven't yet found many communities that are really engaged around growing and maintaining a wiki.

(Talk about weird synchronicity, I wanted to show somebody how to spelunk through Mastodon space, and in about 5 semi-random hops, I had navigated to that very post - before I had seen your post!)