Main Area and Open Discussion > General Software Discussion

I'm thinking of going primitive, with discursion into zettelkasten

<< < (199/244) > >>

Dormouse:
How do you guys collaborate with others (if at all) when using plain text? Say real time (like gdocs; MDhack for example) or asynchronoulsly (github for example)?
-urlwolf (January 18, 2022, 10:00 AM)
--- End quote ---
I don't at all.
When other people send me stuff, I work with whatever format they are using themselves. Usually that will be a form of rich text.
I don't like joint working when I'm in the process, so anything I do I save in a number of formats (docx, md & txt, pdf, epub, mobi) and leave them to choose how they want to do it at their end. Sometimes they will read in epub/mobi and do detailed comments in docx, which we will then use going forward. Very few people I work with use plaintext, given an option.

Nod5:
The block protocol
https://www.joelonsoftware.com/2022/01/27/making-the-web-better-with-blocks/
https://blockprotocol.org/
I'm curious if it will take off and how it might change note taking software. Could help with interoperability and data migration.

Dormouse:
For me this process started as a response to a changing software environment.
I want to control what stuff is local and what is on the net. I want to control access. I want to be able to use my stuff on Linux, Android, iOS. Maybe even Mac. I want to be able to work on all my devices. I don't want my workflows constantly disrupted by software updates or bugs.
-Dormouse (October 23, 2019, 02:21 PM)
--- End quote ---

I think I've gone a long way, but it's starting to feel that software might be trying to pull me backwards.
I'm happy with large plaintext files and their OPML equivalents. Both interpreted accurately by many programs. They contain their own structures. I'm okay with wikilinks - they're workflow effective, understood by quite a lot of programs and are easily read
Not quite so convinced by markdown - it's designed around coder habits and needs - but it is ubiquitous. Supplementing it with what I need, or coping with it's design decisions is a constant irritant in my workflow.

Very uncomfortable with Obsidian's direction (I'll address that in another post). Am keeping a close on on alternative markdown editors and PKM programs. Am likely to spend more time in Workflowy. But I will still maintain focus on the standalone file foundation.

Dormouse:
Not quite so convinced by markdown - it's designed around coder habits and needs - but it is ubiquitous. Supplementing it with what I need, or coping with it's design decisions is a constant irritant in my workflow.
-Dormouse (February 01, 2022, 06:30 AM)
--- End quote ---
I've even thought about developing my own editor and markup language. Not seriously, but I have thought about what I'd remove (lots), what I'd improve (eg tables), what I'd add (eg colour, underline) and what I'd extend (eg header levels). Even thought about easiest way of doing it.

urlwolf:
Very uncomfortable with Obsidian's direction (I'll address that in another post).
--- End quote ---
Very curious, please link here.

Obsidian has better filtering for graph stuff.
I just use it to visualize things better than in zim, where graphs are static and cannot be filtered in any way.
Obsidian UX bugs me.

At that point you could just use a 'real' graph editor from graphviz format like https://github.com/ArsMasiuk/qvge.

Here's the author saying graph stuff is not in his priority list:
https://github.com/zim-desktop-wiki/zim-desktop-wiki/discussions/1892

Navigation

[0] Message Index

[#] Next page

[*] Previous page