(we are switching to a new theme,
don't worry if things look different for a while!)

Site Navigation

Plans

Massive Wiki Roadmap
Pier2Pier
Massive Wiki Builder redesign

For Testing

wiki link test page
Mistletoe parser test page
Mistletoe & the ampersand story

Edit on GitHub


Massive Wiki Wednesday, 2024-01-31

Recording

Topics

Waggle Dance

previous notes: Waggle Dance, 2024-01-24 aka Waggle Dance, 2024-01-24 - Developer Wiki (Massive Wiki)

Desired outcome:

Notes From Pete's Overview

Feedback/commentary

Pete's Important Things to Discuss

A page from Pete about types of transcriptions in handwriting -- might there be something similar with audio transcription?

🔗

Diplomatic and Normalized Transcriptions

First version created by copying in from Pete's local personal wiki, 2024-01-31

In handwriting transcription, we have "diplomatic" transcription and "normalized" transcription. (And semi-diplomatic and semi-normalized....)

"Diplomatic" transcription tries to copy the text exactly, with archaic orthography and what-have-you.

"Normalized" transcription tries to make the text readable by a modern reader.

Resources:

Zoom Chat

two space characters appended to each line

00:12:42 Pete Kaminski: https://hackmd.io/@peterkaminski/BJrV07O5a/edit?both
00:12:46 Flancian: Reacted to "https://hackmd.io/..." with 👍
00:13:24 Jerry Michalski: ah, I had this doc that u started before: https://hackmd.io/a8n8NAYXRweKSSjws977KQ?both
00:14:01 Pete Kaminski: d'oh we were supposed to use that one! let's stay on the new one i made
00:14:07 Jerry Michalski: kk
00:15:58 Flancian: sorry, zoom/pipewire issues
00:16:04 Flancian: will be back eventually I guess :)
00:17:14 Flancian: https://anagora.org
00:17:19 Flancian: e.g. https://anagora.org/nuggets
00:19:12 Jerry Michalski: similar/same list, as represented in my Brain: https://bra.in/5j88Pk
00:22:21 BentleyDavis.com: you could keep the sidebar a page by allowing lists in all pages to be hierarchical expandable. htmx?
00:24:18 Jerry Michalski: my wet brain doesn’t cross wiki/vault boundaries well, so my pref is to have a large name space in one place
00:27:11 Jerry Michalski: Kindle Direct Publishing, but here we likely mean KFF, the Kindle File Format
00:29:33 Jordan Nicholas Sukut: Lulu - alternative to KDP - that allows for distribution and print on demand at Amazon ++ vs. only Amazon
00:29:51 Pete Kaminski: Reacted to "Lulu - alternative t..." with 🙏
00:30:16 Flancian: Reacted to "Lulu - alternative..." with 🙏
00:31:53 Jerry Michalski: Replying to "Lulu - alternative t..."

Lulu has its own format?
00:32:33 Jerry Michalski: Replying to "Lulu - alternative t..."

seems like they use epub and pdf
00:33:27 Jerry Michalski: from 2018: Can I publish the same book on KDP and Lulu?

If Lulu allows you to de-select Amazon for the print edition, you can certainly do that, but the usual system is to buy your own ISBN and publish the two versions as the same book. Some experienced self-publishers do this with Amazon (first using CreateSpace, now using KDP Print) and IngramSpark
00:34:43 Jerry Michalski: ooooooh
00:39:32 Jerry Michalski: sounds like even simple styles like headline won’t make it through?
00:41:45 Flancian: https://github.com/flancian/flancia/blob/master/pages/Makefile
00:48:43 Flancian: https://anagora.org/transcription+bot
00:48:53 Flancian: -> https://maya.land/monologues/2021/08/05/matrix-bot-transcribe-speech-audio-messages.html
00:52:28 Pete Kaminski: speaking of transcription, Whisper and the its large model is WONDERFUL at transcript, and converts an interview into nice text without clumsy disfluencies. it's better than Otter and Descript on a one-pass good transcript.
00:52:57 Flancian: +1, whisper is amazing
00:53:03 Pete Kaminski: (i use Whisper in MacWhisper)
00:59:47 Jerry Michalski: https://en.wikipedia.org/wiki/Planning_poker
01:00:33 Jerry Michalski: angora is the fuzzier version
01:00:52 Flancian: angora is the fuzzier version
love it!
01:01:43 Pete Kaminski: And at Socialtext "Planning Game" was something different, where we did something similar to what Jerry just described -- a list of candidate projects, and a budget of poker chips to "spend" as votes.
01:02:36 Bill Anderson: makefiles can rule
01:06:38 Jerry Michalski: commenting
01:07:16 Jerry Michalski: metadata

AI Summary (hopefully useful, may be inaccurate)

Quick recap

The team discussed various projects, including a proposal writing wiki, a podcasting and publishing back-end infrastructure, and an open-source project. They also explored the idea of individual wikis working together and the potential of a chatbot for their project. Pete Kaminski discussed the ongoing development of the Wiki builder's homepage template and the potential of turning a massive wiki into a print-on-demand book. The team also discussed the idea of using AI to generate summaries of calls and the importance of documenting thoughts and actions. They also touched upon the potential of a podcasting infrastructure.

Summary

Projects and Collaboration in Massive Wiki

Pete Kaminski, Jordan Nicholas Sukut, Jerry Michalski, and Flancian discussed various projects, including a massive wiki for proposal writing and the development of a back-end infrastructure for podcasting and publishing. Jerry introduced the concept of 'tiles' and 'waggle dance', while Flancian discussed his work on an open-source project and his note-taking skills. Pete showed interest in collaboration between Massive Wiki and Agora, a note-taking and backlinking system. He also suggested improvements to Massive Wiki, such as adding an 'edit this page' button to the Github interface and building more themes. The idea of individual wikis working better together, including sister pages and interwiki linking, was also discussed.

Data Management and Visualization Ideas

Pete and Jerry discussed the need for efficient data management and standardized schemas for their project. They also explored the idea of incorporating metadata into their project to facilitate easier navigation. Jerry proposed the concept of a multi-plane mosaic, a semi-3D visual representation of their project, which could be used to inspect different layers of the project. Additionally, Pete suggested the idea of turning a massive wiki into a print-on-demand book or a Kindle publication. Lastly, they touched upon the potential of a chatbot for their project.

Wiki Builder's Homepage Template and Printable Book Proposal

Pete Kaminski discussed the ongoing development and potential issues with the Wiki builder's homepage template and its 'basso' theme. He mentioned that he was working on a new theme using simple HTML and CSS, but it might require a rewrite. Jordan Nicholas Sukut proposed the idea of creating a printable book from the modular content in the Lionsbird Wiki, which he was willing to pilot. He raised a challenge of finding a print-on-demand service that allows distribution to other e-book platforms, suggesting the potential use of Lulu. The team agreed to consider pushing a couple of packages through the process as a proof of concept.

Writing Tools and Documentation Process

Pete Kaminski discussed his recent experiences with different writing tools, such as Microsoft Word, Google Docs, Obsidian, and Typeora. He explained the process he used to transfer documents between these tools, which involved exporting HTML without styles, pasting it into Google Docs, and then submitting it for production. He noted that the process was fiddly and might be easier to do by hand at first. Jordan Nicholas Sukut and Flancian agreed with Pete's suggestion to thoroughly document the process before attempting to automate it. Flancian shared his experience with using Pando and suggested that there might be value in learning complex tasks to make them more manageable.

Intermediate Representation and Future Projects

Flancian discussed the development of an intermediate representation in the form of a preprocessor step that would produce an HTML file with simple markup. This could be further expanded and connected as needed. Pete Kaminski mentioned the native format used by Sphinx and others brought up the possibility of using restructured text. Jordan Nicholas Sukut suggested a next step of documenting the current process to improve it, using one or two manuals and podcasts as test cases. Pete Kaminski proposed a shift towards using Markdown for future projects, emphasizing its compatibility with other Markdown-based systems.

Content Creation and AI Summary Ideas

Jordan, Pete, and Flancian discussed the potential uses and applications of audio and written content creation. They considered the idea of creating podcasts, monological transmissions, and anthropological interviews. Pete suggested the concept of using AI to generate summaries of calls, and the need for a system that allows for iterative improvements to the AI-generated summary. Flancian proposed the idea of a universal labeling interface for all media, which could provide valuable insights from human interaction and consumption.

AI Plan, Company Building, and Project Prioritization

Bill expressed concerns about the AI plan's workload and questioned its problem-solving capacity. He emphasized the importance of documenting thoughts and actions. Jordan highlighted the need for documenting the process of company building. Pete suggested discussing the proposal list's sifting, sorting, and summarizing process and proposed creating simple themes. Jerry proposed assigning points to projects on a spreadsheet to determine their costs. The team agreed to rationalize the list quickly. They also discussed the Wiki project's publication process, the creation of an audio version, and potential connectivity problems. The team agreed to continue working on these projects while considering the importance of prioritization and planning. They also discussed the potential of a podcasting infrastructure.

Next steps

AI-generated content may be inaccurate or misleading. Always check for accuracy.