topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Tuesday February 18, 2025, 4:14 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Dormouse [ switch to compact view ]

Pages: [1] 2 3 4 5 6 ... 78next
1
Backups used to be in json format; I'm not sure now, although they still seem to be readable.
I've had a very quick look in both text editor and Easy Data Transform.
Not json.
But pretty confident that I can extricate the text in a useful form, should that ever be needed.

The value of the workflows for general PKM notes has gradually become more apparent, so this is a useful confidence boost. My most recent stance had been to use Lattics for notes where using it had a clear advantage. I'm now shifting to a trial of using it for all notes, except when there's a strong reason for using a different program. The main advantages are practice and inertia, which has been the case since I started with putting writing related notes in. Those notes are my bread and butter and the pull of gravity has taken over.

2
From a writing perspective, I've found that the new timeline feature allows a new very productive workflow. It's use for historical events is obvious and can be pure research rather than writing.

But it also works as a way of starting with 'events' in fiction. Each event put on the timeline exists as a note, with all the notes' ability to put text into documents. Which allows an easy linkage between events and chapters without assuming the sequence of both will be the same. Everything modifiable as writing progresses. Clear separation of the 'events' themselves and the manuscript.

Many fiction writers imagine scenes completely out of sync with the manuscript. Creating the problem of what to do with that imagining. Is it worth writing them down when the manuscript realities may be different by the time the scene is reached? If so, where to put it? This solves that dilemma because it can simply be written as an event on the timeline, which can be modified later and put in the manuscript or not.

3
One (minor? major?) concern I haven't mentioned is the old Obsidian query of 'How many notes can it handle before it slows down?'.  I have no answer to this. So far it is very fast. Local ought to be fast. But I don't have a huge number of notes or books full of text. I did test Obsidian and found it choked with large books as a single note; I was never interested in outlandish numbers of notes. Do images matter? - I doubt it.

I don't treat it as a general dumping ground. But I am finding that it's the best home for an increasing number of categories of notes. I've even worked out that I could put everything in (untagged, unlinked notes effectively disappear except for search and the notes calendar). It's actually very good for ephemeral notes, which always made me uncomfortable with programs where notes=files.

4
I've not tried to use it with web clips. I'm not sure it has a web clipper, so that might be a limitation.
I don't think it does.
On reflection, it may be that this illustrates the program's focus on local and print (not on paper but file equivalent formats like PDF); idk if that will change. Academic and longform writing is perfectly suited by this. I'm aware that Zotero Connector does a form of web clipping, but I've never used it; possibly I might need to start working with Zotero assuming I continue with Lattics. It seems to me that most notes programs have a web focus (but most writing programs don't, even if they're only accessible online). The closest Lattics gets is the ability to sync over the web - WebDAV etc; OneDrive a recently added option - which has been gradually developing.

15 Jan 2025
For my personal use, I usually save pages and part pages into Readwise Reader. That deals with the clipping without cluttering Lattics. And very easy to cut and paste as needed from Reader. There are many other workflows to achieve the same thing.

5
I'm not a writer, but am fascinated by the how of it. So i really enjoy your descriptions of software and workflows.
Thanks. I've just had a good look at their landing page and it does give a good overview of what the program can currently do - much better than their last version.
I've not seen anything quite like it. It's not that there's anything unique about any given feature, but the way they fit together with what seems a clear idea about the program's purpose. The whole is definitely greater than the sum of its parts - and I can't say the same about all writing programs.

I'm afraid that my perspective is rather blinkered by my own needs. I suspect the use cases extend well beyond writing and academia. I can see that it seems a good fit for anyone doing family history. Maybe even stockmarket investing.
I've not tried to use it with web clips. I'm not sure it has a web clipper, so that might be a limitation.

The absence of tasklists, calendar and journal is very obvious (most PKM apps seem to regard them as obligatory). A very good thing imho. Clarity about what the program is for is helped by clarity about what the program isn't for. I wish more programs resisted the kitchen sink.




6
I'm very aware that I seem to have gone into reverse with using Lattics. And I'm not at all comfortable with that; I still remember all the drivers that pushed me away from databases and towards simple files. But then programs like Obsidian and Tangent aren't simple, and neither really are the files. And the limitations of the markdowns for anything except simple web markup are all too apparent.

And it seems that I have always been aware of what I really needed:-

Essentially I do two things, though many types of both: I write and I research.
I had quite a reasonable workflow using database style programs but was aware of increasing issues over long-term viability, which is where I started with this thread. Moved on to files (good), though without ever stopping using databases for short-term tasks, and plaintext (markdown is ubiquitous but not good).

Most of the thread has been about research. By definition that's long-term and so file solutions were always best. I keep two types of research - actual hard research or reflections, most of it in highly focused fields, and a scrapbook, which is anything I see I find interesting and might be able to use in future. I can be quite adventurous in looking for research techniques. Everyone has their own techniques, efficiency and effectiveness is hard to prove and most of what I need is in my head anyway. But files and links have big advantages. And similar techniques could work for fiction too.

But the writing is ultimately more important - I could live by writing without research, but not vice versa. Three essential elements in writing are content, structure and words. With the words, the ultimate is being in the flow and the wrong editor gets in the way of that.
..
Ideally, I'd have an editor that joined the research with the writing .. And it's hard for me to avoid the need for me to be in rich text/docx at some point. My markets are print not web.

And if I ask myself whether Lattics ticks those ideal boxes, I'd have to say that it does. And does it well. The concerns are purely those that started me off. And if I'd had a database program that met my needs as well as Lattics does then I wouldn't have reached the point of actually setting out on this journey.

7
PS your link doesn't work (the http is doubled http://https//lattics.com/).

https://lattics.com


Thanks. I've changed it.

8
I'll just add that I'm also looking at Lattics.

Over the year since this post, I have increasingly played with Lattics and now use it for everything writing related; effectively it's the stage before Word where it has many advantages over the Word/OneNote combo.

I've done some sort of summary here - Comments on Lattics

9
Lattics - a program for PKM notes and writing. Only for Windows and Mac; iOS apparently coming sometime.

This isn't really a review, and I haven't systematically tested any features. I have seen a number of 'reviews' on the internet and my impression is that they are from people who have given the program a onceover, maybe for the purpose of writing the review, and I haven't noticed any systematic testing in those either. However, over the last year, I have found myself moving from looking at it, to testing it, and using it more and more, to the point where I now use it for everything writing related; effectively it's the stage before Word where it has many advantages over the Word/OneNote combo. I have received no request, nor inducement to write a review; initially I used the free version and moved to a subscription once I realised that I was going to use it; I hadn't felt limited by the free version, but didn't want to come across one once I realised I was using it. For a modern writing program, I believe the price is reasonable - I'd avoid the monthly price ($4) and go for annual ($21) or five yearly ($90).

It wouldn't suit everyone.
  • It's Chinese.
  • There's no mass export. Backups used to be in json format; I'm not sure now, although they still seem to be readable.
  • It's local and there's no web version.
  • No mobile version either (iOS apparently coming).
  • Subscription ($4 monthly, $21 yearly), but the free version is very usable.
  • Uses @links rather than [[wikilinks]]; I've noticed that this is more common in east Asian apps.
  • It's not open source. It has optional simple markdown syntax, but mostly works like a rich text app.
  • Communication is very limited. There are few responses on their Discord and they don't even seem to have a routine to ban spammers. They do however respond to in-app communications, usually in a couple of days.
  • Documentation is extensive, but far from complete.
It can be surprisingly difficult to work out the best way to use the program. For a long period, I believed it was best to follow the workflow they describe (make notes, set up projects as needed and make documents within those projects, copy notes into projects - each note can be in multiple projects with edits updating all), but this isn't strictly true.
There are imho many infelicities where a minor tweak would enable a much smoother workflow. Initially I made suggestions, but I've come to accept that it works the way it does for reasons that make sense to the developers, and maybe they'll implement suggestions and maybe they won't but discussion will be limited.

It's widely recommended as a PKM notetaking program. It does indeed have links, backlinks, an excellent card view, #tags, fast search, transclusions, and an integration with Zotero; but for most purposes there are other apps with significant advantages. Since there are many different camps of users - the productivity focused, the visual, the markdown purists, those wanting automation/coding or AI etc - I see no point in berating Lattics for not having features that lie outside its focus. And it is quite clear in aiming at the student/researcher/academic market - I feel that creative writers are a more recent addition although they have developed another writing app (Zine - for iOS, Android and web). It has Zotero integration and spaced repetition cards which many apps don't; personally i have no need of either since I have no use for spaced repetition and don't use Zotero (though I acknowledge its popularity). But the core search is limited (filters can't be stacked), the notes don't live in folders - they need to be organised by tags and sub-tags. It does have folders for documents and they could be repurposed for notes, but then you lose the ctrl-n for new notes and introduce potential conflicts because folders are designated as projects; I did test this out, and would advise keeping the two distinct - if you genuinely need your notes in folders, then use another program. Personally, I wouldn't use Lattics if all I wanted to do was keep PKM notes. otoh the notes are pretty comprehensive and useful if you anticipate using them with, or as an adjunct to, a writing program - which is what most academics, students and researchers will do.

Which brings me on to considering it as a writing program. Again it won't suit all writers - if you write for the web, you might as well stick to simple markdown; if you need detailed formatted output as in Scrivener, then you might as well stick to Scrivener (I'm not sure there are many of these); if you want to write according to a fixed story beats system (Snowflake, Hero's Journey etc), then you might prefer a program with the templates built in; ditto if you want templates for characters, locations etc. Lattics' only 'specialist' features are useful in academic writing - LaTeX, templates for journals, styles for citations, PDF annotation to notes, automated bibliography, tables and charts. These features are essential requirements in academic writing but
general writing, fiction or non-fiction, doesn't actually require the specialist features mentioned above and they may actually be experienced as claustrophobic (they're always too rigid for me).

Lattics does though have a long list of features and options typical of writing apps. It's actually a pretty comprehensive list. It includes focus mode, dark/light modes, typewriter mode, stats (by document or card which includes goals, and user by date), first line indent, spell checker, bi-article comparison, ability to drag sections and blocks around, ability to view/edit individual sections or all sections together. It doesn't have folding. There's good export options into docx, pdf, markdown, txt.

So how does it work? Conventional main structure: Folder/Project pane on the far left, File/Documents pane on the near left, both hideable. Multiple layers of sub-folders and document possible. Can be resequenced at will, as can the blocks in the main pane. Usual text formatting options, including colour and footnotes. Can add comments (show in margin), which is less common. Shortcut to copy links to a block. Buttons will open card, mindmap, flashcard and timeline views on the right.

As a writing app, Lattics' superpower is obviously its well integrated PKM notes feature. Useful for students and researchers, but also useful for creative writers who want to have notes on characters or arcs; the notes can be added so quickly that making them needn't interrupt the flow.
But there are two other major features - the timeline and the mindmap. Both can be very helpful.

The mindmap is a simple mindmap of the document and sub-documents with the ability to add other connecting arrows. I was under-impressed when I first saw it. But then I realised that note cards can be dragged onto the mindmap and connected (the notes are differentiated by colour)); it's possible to connect them to the mindmap but also for them simply to connect to each other. This makes it significantly more useful. There are three views - mindmap, plot of story and aerial - only differentiated by the amount of content shown. They all have the ability to be expanded into the full editable document or note which means that it would be possible to write a complete book while never leaving the mindmap. I'm not sure why anyone might wish to do that, but recognise that it might be easier to write or edit some sections while seeing them in the visual context of the mindmap.

The timeline allows events to be specified with a start and end time precision down to the second. They are placed in lanes, each lane with multiple tracks, which makes viewing and organising easy. Cards, document and articles can be dragged into the timeline. This has obvious uses for real world events eg in historical research or genealogy, but is also helpful in intricate plotting in fiction. Again all the cards etc can be fully expanded for writing and editing.
Effectively it means that you could write a book by accessing the sections from the usual document hierarchy, from the mindmap or from the timeline, or from all three in turn. Now the mindmap isn't near the capability of a standalone mindmap program like Mindomo, and the timeline isn't close to AeonTimeline, but both are quick and easy to use and sufficient for my writing needs, and I suspect for those of most writers.

For me, the combination of features puts Lattics far ahead of all other writing apps, even though it has taken time to build my confidence and workflows.

It may be worth emphasising the need to look after your data, since so many users seem to believe that that's not something they need to bother themselves with. Lattics keeps its data local; it's not available to the developers; it's worth making sure that the backups are frequent enough and in a location suitable for you. I've not experienced a problem, but like all database apps (and apps that operate simultaneously on multiple files) there's the possibility of something going wrong. It's clearly quite a complex app and updated frequently.

10
I also read a post on the Workflowy Slack from user Frank G - “I have been using Msft Word for Mac  (Windows before) for as long as I can remember. I have also played with Craft, Ulysses , Scrivener, Speare, Author , Typora , all excellent alternatives. Today WF finally ate them all up too for my long form docs . The blank page with a few basic formatting choices plus WF’s speed (once opened) , simplicity, and flexibility, has made WF my go to choice for long form doc drafts . I will still need to export to Word (or Craft)  for final formatting and PDF conversion, but 95% of my time I will be with WF .”

Essentially this refers to the Roamlike feature where bullets can transform into text blocks. Logsec has had this for some time too.
It struck me that it might be worth comparing the editors in (some of) the apps that I use, what makes them good and how Upnote compares.

I did a short experiment using Workflowy like this - I thought it might be easier if I'm already using it for short zettelkasten notes. Being able to move blocks around is certainly an advantage in some notes/articles where there's a bit of brainstorming and of puzzling through to a, hopefully, coherent outcome. But found I hated it.

A bullet always showed on any section where the mouse was hovering.
And, worse, all the bullets that potentially go lower in the hierarchy remain visible. Can be solved with hoisting and folding etc, but not ideal.
Neither Upnote nor markdown editors help here because they don't allow blocks to be dragged. But OneNote is fine. and easy to put a link in Workflowy, and will also export to .md.

From a writing pov, what Workflowy is good at is brainstorming/organising/constructing using bullets as headings and notes as text. Options to view as bullets, kanban or cards. Exports cleanly to Mindomo, which then exports cleanly to Word. A good workflow once I switched to Word.

Upnote is fine, but has nothing that improves this workflow. It exports to markdown and HTML, but that's not quite as good as a direct export to docx (for me). Longform note writing is okay, but not as nice as Tangent. Its big advantage is mobile. And decent webclips for those who don't have other established workflows for them.

11
I actually use multiple desktop applications ... I use obsidian, tangent, vscode mostly.  this is all primarily markdown stuff.  For catch all archival purposes, I put everything in trilium

For work purposes when i need to collaborate with less techy people, i've started using Notion.

For static generated sites, I first started using emanote, but then moved to Docusaurus.  I think Docusaurus is beautiful.
Sounds good.
& nice to hear from you!  :)

I haven't gotten good at atomicity type writing yet, but do plan on going more in that direction as it will help in putting together longer form writings more easily.

I'd ask why. You've been going well without it. I don't think it automatically makes it easier to construct longform: it depends on what you're doing; how you do the putting together; how you take the initial, potentially atomic, notes. I'm not absolutely sure Luhmann was 100% atomic - I haven't read all his cards; Beatrice Webb certainly was.

Most of my notes probably are atomic, without being short, but it would certainly be possible to argue that that they could be split. Like a diamond is atomic, but has many facets, at least after being cut.

I do not think we need to stick so strictly to the original paper based zettel method with the numbers and stuff because the software and yaml covers that pretty well now, and I found it more of a hindrance at this point.  So i've loosened up on that a lot.

I;m not sure what you mean by the numbers. Luhmann's numbering was primarily to preserve his sequences; I'd argue that sequence is essential. Also it is as a UID, and that's what most zkn programs have by using a date/time stamp. I'm not convinced that they help at all except for linking - and there are other ways of doing that.
But I suspect that the main reason you have loosened up is that you're not using notes as a zettelkasten - and there's no reason why you should because there are many note-taking methodologies and all have their uses.

Wearing an academic hat, I'd typically read 20-50 journals in an hour or two. Naturally this involved a lot of scanning, skimming and skipping, with the occasional check on detail and more rarely a deep dive. I'm quite clear in my own mind that typical obsidian-like systems would produce little value except for the last group. I'm not sure how much I'd want to use a zettelkasten approach for that group, but for all the others it would be essential to create useful notes. The process is like going through a haystack finding individual interesting straws, but the value comes entirely form placing them in sequences, whereas the deep dive value is always mostly in the clump. I'm not sure this was entirely the case for Luhmann - he seems always to have been most interested in what he might write and may have selected and moulded straws entirely on that basis. oc that's just nuance.

And having got a system that works to do it, I can see that it can be applied to anything where building chains is the key process. The plural being key - if you are building one chain your needs are quite different from working simultaneously on 1000 without a blueprint and with the need to do crosslinks from time to time.

I think that one of the problems with zettelkasten discussions is that the focus is always on the notes, and there's only som much anyone can say about that without adding lots of ideas of their own. There's very little discussion about the decisions involved in chain-making, and oc it's irrelevant anyway if your system doesn't make chains.

12
Can you recommend a book or article explaining the system in more depth?

Oh, how I wish I could!
I can explain why most of the well known books are actively wrong and misleading, in part at least.

This and this aren't  bad summaries, but hardly how to do its. (One poi - Luhmann actually started his second, differently structured, zettelkasten after attending a conference in the US)

There are many reasons why I believe that the published books and articles aren’t great:
  • most writers automatically add their own ideas; they’re very opinionated but try to give the impression that they are just describing the original
  • most writers started as academic wannabes rather than productive and successful academics (and therefore unable to discriminate what would work from what wouldn’t; let alone what needs to be done to make a system work) and a number have ended as zettelkasten publicisers
  • a marked discrepancy between them and Luhmann in terms of self-discipline and life circumstances
  • an obsession with improving the system when creating a digital analog
  • and with their ideas about zettelkasten being shaped by the programs they used
  • Luhmann’s target was writing, he had no need of a memory aid; many of the students are primarily interested in remembering

I’m now very opinionated, but it’s taken me a long time to get there. Many of the many detailed systems I’ve seen described struck me as procrastinatory rather than productive: the notes themselves are the purpose.
My own approach has been shaped most by studying how Luhmann actually worked and reading his cards. And comparing that with myself and the workflows of productive successful academics I know.
But being aware that I’m not the same (I pursue more subjects, I have less self-discipline, I am usually doing things rather than reprocessing what I read).
Like Luhmann, I’m very focused on output. Some of that is writing, but it is also investigating, also doing. Output quality is even more important than quantity. A system that isn’t visibly improving this is not one for me. (One reason I still write longer notes: I can usually write these straight off, remembering citations, rather than having to put them together from short notes. The zettels are for what I don’t know and haven’t yet thought.)
I rejected the wikilink/graph/backlink approach because I could see that it doesn’t do the same thing. It can be useful in itself, but tends to be passive and self-serving. At some point on my journey, I remember someone writing that they had looked at zettelkasten and it was just outlining: they were wrong of course, but also still right. Like everyone who has tried following a digital approach, I’ve been limited by software. Workflowy is well short of ideal, but it will do; for now. And it has analogues for all the features of Luhmann’s system.

What I would say is that you need a clear purpose for using the system. I would suggest that purpose being to do with thinking and doing. With that it is very quick to see whether it is helping or not. But the purpose doesn't have to be academic and doesn't have to involve writing as an output.
And don't eschew longer notes, outside the zettelkasten but being linked into it.

13
It's worth emphasising that a brief atomic note implies two conditions that have to be met, not just one
Do you list these conditions?
That it be :

atomic
Andy Matuschak;
If a note has more than one idea you care about, then break it down.
NoteDex explanation
The idea has a long history. Atomicity makes it easier to link because there's (supposed to be) only one idea available to link to.

and brief
Most descriptions of the system include the word brief. Index cards were themselves limiting. But I have seen definitions of brief range from less than A4, less than A5 to no more that 2 or 3 sentences (an index card is actually A6).
The reason I emphasise brief is because these notes need to be scanned very quickly when looking to place a new one. Usually the writer will retain a sense of the richness of the idea without have to dot every i etc.

Are you referring to the two bullet points, the second of which includes the quoted text?
No, there's only one bullet. Quoted text, tags, links etc go in the note to the bullet - accessed by pressing Shift-Enter rather than Enter. It's fainter and less obtrusive

14
I'm afraid this is a very long post. It seemed worth giving enough details for anyone else to be able to follow what I'm currently doing; it does assume some knowledge of outliners, Workflowy, zettelkasten and Luhmann.

I haven't done much with zettelkasten in the past - my usual need is for longer notes - but I have started one with Workflowy, and thought I'd explain it here.
  • The first point I need to make is that, despite "Smart Notes", Luhmann's zettelkasten is not a system designed for students - at least not until they are following their own streams of thought; Luhmann was always a researcher who published articles and books. But, if the phrase honing stage is ignored, it is a perfectly applicable system for anyone who is following their own streams of thought whether that be RPG, making bookcases or tracking health. It ought to help develop expertise in anything.
  • Second point is that it is a high effort system. Part of the productivity gain is from the repeated pondering when trying to locate the best place for a new zettel. The rest of the gain comes from the structure enabling brick to be placed on brick until a building emerges.
  • The third is that Luhmann's practice (aka "the rules") does matter.

  • Zettels have to be placed with time-consuming care in a sequence. Some may be new starters (for different subjects), but they need at least the same amount of thought before that decision.
  • Zettels have to be brief and to the point: they're not a string of sequential thoughts - if they're worth it, sequential thoughts need to be sequential zettels. This is hard and requires discipline. If a thought isn't worth that effort, it should not be put into the zettel. I don't put my frequent long notes into the zettelkasten, but I do write a zettel fo each one, with the the reference. It's worth emphasising that a brief atomic note implies two conditions that have to be met, not just one.

  • Workflowy supports this to a degree because it works best when each zettel is a bullet/paragraph.
  • I find that, for the purpose of future linking, it is useful to append a time/date stamp to each zettel. My sequence is title (in bold) + time/date, then the note/thought. All in a single mass of text. I have a time/date stamp as my (most used) shortcut in a text expander so that it can be used in any program. I put references and #tags in the bullet note (#tags are used as a form of index entry)
  • (Technically, all the content could be put into the note rather than the bullet - and I might do that if Workflowy offered the same viewing options for notes (show, hide, 1st line) as Dynalist - but it has no options, and always shows 1st line only.
  • I also find it useful to have an external library/hoard (which is part of the usual zettelkasten system anyway), Items can be highlighted & referenced. Zettels need the essence and not the clutter.
  • I'm aware that it's easy to add a zettel to the head of the list in an outliner. It should also be possible in a card index: idk if Luhmann ever did it; I doubt it since he was probably restricted by his numbering scheme, but I do sometimes.
  • If I want to see, or play, with the zettelkasten in a mindmap, I do OPML export to Mindomo. And export back again if necessary. Most mindmap programs should be able to do this. (Many might be able to work as the outliner too. I simply prefer to use Workflowy).
  • Workflowy doesn't have a wordcount. Which is fine for zettels, but is a pain for anything longer.
  • There's also the possibility of using notes or comments to add detail or successive reflections. At some point the comments could be made into zettels of their own.

Luhmann's phases are essentially: read/think - write zettel - refine note language - place in zettel sequence. Every note placement is an opportunity for further thinking, refining language and adding links/references.

The system I am describing has neural pathways through folgezettel outlines/mindmaps, wikilinks and backlinks, tags as well as optional structure notes. Plus search and filters.

There are a number of reasons why systems like the daily notes and wikilinks of Roam and Obsidian don't create a functional zettelkasten.
  • They encourage verbosity and lack of focus. (A frequent reflection from Roamans after leaving the cult.)
  • (Everything should NOT go into the zettelkasten; the thinking about exclusion is important.)
  • There's no targeted review.
  • The long folgezettel debate on forum.zettelkasten.de largely compares the use of alphanumeric folgezettel with numeric date/time stamps as links. The latter's review system is based on Structure Notes (aka index notes, or Maps of Content in ObsidianSpeak); but folgezettel placing can take place multiple times a day and cover all areas potentially receiving new notes, whereas Structure Note review will be infrequent and partial (I've seen weekly recommended apparently with an acceptance that most users won't manage it that often). The debate made me think of angels pogoing on an needle: everyone is righteous and no-one changes position.
  • No mental effort is used to find the precise place for a zettel/note. Everything relies on links, the automated backlinks and a graph.
  • Structure is expected to be self-emergent (ie automated) rather than the consequence of reflection during placement. There's an assumption that note value is demonstrated by its link density.

In use, I find that this system highlights trains of thought rather than individual notes, and that going through it later does sometimes stimulate further thoughts. Not only are thoughts/notes not islands, but they have active (or inactive) trading networks in a way that graphs of wikilinks don't. I therefore use it for all topics where I am interested in the chain developing (and, maybe especially, branching).

If I write a long note, I decide whether I'm interested in a chain, and, if I am, I add a zettel to reference it. I write as many long notes as I did; the type of mental focus used when writing a long note is quite different to working on the zettelkasten. Sometimes I might write the zettel and then the referenced longer note later.

I happily mine old notes, highlights, webclips, articles, books and add a zettel to reference them when it seems right. I never directly add an old note to the zettelkasten.

Everything is written, described or summarised in my own words. When I don't like my words or phrasing, I have never been able to stop myself working on the language whenever I read something I've written.

15
The thread has moved on, with no further comment on Upnote?
I decided to move it into test mode.
I also read a post on the Workflowy Slack from user Frank G - “I have been using Msft Word for Mac  (Windows before) for as long as I can remember. I have also played with Craft, Ulysses , Scrivener, Speare, Author , Typora , all excellent alternatives. Today WF finally ate them all up too for my long form docs . The blank page with a few basic formatting choices plus WF’s speed (once opened) , simplicity, and flexibility, has made WF my go to choice for long form doc drafts . I will still need to export to Word (or Craft)  for final formatting and PDF conversion, but 95% of my time I will be with WF .”

Essentially this refers to the Roamlike feature where bullets can transform into text blocks. Logsec has had this for some time too.
It struck me that it might be worth comparing the editors in (some of) the apps that I use, what makes them good and how Upnote compares.

One group is writing apps: ie those where there is a published output, especially those with longform output is in print formats. Important features include:
  • a look and feel that sustains focussed concentration for long periods;
  • a presentation that shows the reader experience, especially the white matter balance;
  • the ability to manage long documents, whether by putting together many small documents (eg Scrivener, yWriter) or working in a single long document with multiple sections (eg Word);
  • plus word count and other feedback about the output.
Many editors, especially those markdown derived or inspired, are weak in 2) because of the lack of first line indent and blank lines between paragraphs. Ones that tick all these boxes include Word, Inspire Writer & Ulysses. iAWriter misses different features depending on the OS and has first line indent only in Review mode. Tangent is pretty good but lacks the ability to manage longform (and I haven’t personally tested the first line indent CSS); Upnote isn’t quite as nice, can’t show white matter balance, but has quite nice document feedback and can manage longform; Typora is nice, can (to an extent) manage longform, has first line indent but also blank line between paragraphs (although this ought to be modifiable with CSS), and word count is okay.

otoh, if we look at note and PKM features Word, Inspire, Ulysses, Scrivener, Typora all fail (Word sort of passes if you include OneNote to make a dyad). Tangent and Upnote pass. For my limited usage, Upnote works well on Android (and it includes a Quick Action widget for new notes). Images are an issue for both (Tangent link only, Upnote limits quality). Both are comfortable for writing notes. Tangent better for following a thread, Upnote better for web clips. Workflowy can do notes and PKM but remains primarily an outliner (which automatically gives longform); its big advantage/disadvantage for writing is that it is block based (which can help for working out structures, but hinders seeing the document as a whole) and that it has an alternate kanban view. All work with tasks: probably WF>Upnote>Tangent. Writers for print/publish using a notes app such as these for their writing will typically export into Word for the review and editing passes and sending to editors or publishers.

There are many notes/PKM apps. The editors are generally adequate (occasionally some delay in keyboard response) but tend to the generic. They compete on their other features, not the editors. Upnote’s editor is better than most of them. I find Tangent better for reflective writing in depth, but Upnote feels better for notey notes - even quite long ones: there are many little features (eg open a note in new window + keep on top button, for taking notes when browsing or using another app).

I'd just add that this
the Roamlike feature where bullets can transform into text blocks
is pretty well the perfect design for a zettelkasten as used by Luhmann. Every note has a parent. There is no distraction from bullets. Links are possible.
Purely relying on wikilinks is a non-reflective semi-automation that dissipates the pondering and sorting that made his method productive.
A mindmap view of the outline/cards might enhance it but his use of the system was essentially conceptual and verbal, not visual.


16
many many Mac apps.
Yeah, quite a few Mac apps, but very few on Windows. Only one I've used is Zettlr, but I've not checked how that goes since I haven't used it in ages. Seems like there was a fair wind of Mac enthusiasm a decade ago, but then it died and has never picked up again.

I've read a Zettlr response to a request for textbundle to be settable as a default format:
thanks for the issue! Unfortunately, this is not possible. There are several reasons to that:

Both TextBundle and TextPack have been designed specifically for inter-application sharing of notes and cross-device sharing. They were never intended to be used as a default storage container.
TextBundles are basically just folders within folders, so using these by default would inflate the amount of folders within your application unnecessarily; additionally, information will be stored redundantly, thereby consuming more space than with the current setup. Additionally, it would take a longer startup time, as more information needs to be processed, and the current File System Abstraction Layer already has a lot to do parsing 10,000+ files due to the lack of caching methods.
The "good" way to work with Markdown files is to store notes in one directory and use a single img, assets, or images-directory to collect all images being used across the notes in that directory. This means: If you need an image a second time, you can simply link it to both files. Additionally, you'll have more control over what is stored where. Zettlr already gives you the option to automatically store pasted images in a predefined "collection" folder.
Markdown is intended to be used as a format that is both machine-readable and human-readable; to add additional layers of information makes it harder to write programs to address these issues.
TL;DR: The default way is and will be to have single Markdown files with the images in a different folder. TextBundle and TextPack, however, can be used to share specific information with other users, devices, or applications.
So that wouldn't work for me. I don't mind duplication if it guarantees security and I dislike the approved markdown default setup.

So file, like the same folder/directory?
No, as in a text file with images.
I'm okay managing folders of digital assets, but if I write something with images I want the image locked in with the text and not relying on a link.
docx okay, databases with good export okay, but .md isn't.
Luckily few of my notes or writing needs images, and my writing is in docx now anyway which is fine.

17
Vulnerable how?  Like you link to the directory with the images in it, and that link breaks?  Or they break when trying to sync between different systems (something I have had problems with)?
It just seems like that is something that should have been solved.

Solved by textbundle, except no-one supports it.
My experience is that directories move around and that when you move files around they may not have access to the original directory. Or they get renamed. Irritating rather than insurmountable.  If you have a highly structured approach and are disciplined enough to stick within it, there won't be a problem.

Except in the end I think they all break. Like images on web pages. Or web pages themselves. I worked out that if I have all the assets I refer to in the file, then nothing ever gets lost.

18
Out on the internet and youtube obsidian is dominating ...  I cannot believe more people do not know about tangent.
I think Obsidian was the first of the Roamalikes to get any traction. Started with some credibility (from Dynalist), had a techie crowd onboard from the beginning and took off with students - esp Comp Sci students. And it added features at a remarkable pace and then took off when the API came out. It's a program for hackers & players rather than users imho. A potential problem for the future is that students are high turnover and have a voracious appetite for the new.

Tangent came much later (via Taylor's dissatisfaction with Obsidian) and has far fewer features. Not the main focus for the developer who made it for his own daily use, whereas Obsidian quickly became the main full-time focus for its two developers. And no-one has battened on to it as a base for their own YouTube brand (I noticed that Capacities was quick to appoint someone to do that).

19
I just wish that notezilla allowed the ability to sync using my own choice of cloud services
Yeah. I think its main reliable income comes from the sync though.

I  would like those postit notes to be accessible outside the postit app
I haven't checked out other postit apps in a long time.
I always have NZ running, and I do like the abnility to wirk with the postis in the app/window they're attached to OR in the NZ notes manager.

20
Do you know what kind of database tangent uses?  Do have any information about if it lags as the data it has grows?
Just files and jsons.
I've not seen a problem with lags in general. It's rather like Obsidian in that there's some initial lag while it parses the files in the folder and that it can snarl up on files that are very big or otherwise awkward.

I've stopped using Tangent/Obsidian/markdown editors for notes with images. The links are too vulnerable.

what I like about tangent is it has a number of views
I find being able to switch between list and car view very useful. Easier to pick out the note I want as a card than from reading text.

I also like just being able to type.
This is the main thing for me. It's nice to work in. Nice to write in. Nice to review notes in. It's productive.
But you should check it has the features you need, or that you have a workaround.

I want a wholistic system I can tweak.
And Tangent is open source now, so anything is possible.

21
I did not know logseq was moving to be a database first.  Nor did I know there was org support other than what was offered by being plain text.
You can see what's going on org-wise by reading the Org section on its Discord. I think virtually all users chose to go with markdown, so it's unsurprising that org gets less love.

I think it's probably a wise decision for logseq to move to a database model. I don't think it ever gained much from being files based except a few users from Obsidian. It has problems with speed. My impression is that there has been a trend for users to move away from it, notwithstanding the widespread praise for its PDF handling. Again, you can catch up with complaints etc on its Discord.

oc reading the Discord is time consuming.

22
Integrating with mobile is also important. I have liked Joplin  but I have read about some frontmatter/yaml issues in addition to the way it handles each note's unique id. I have heard good things about qownotes which can be synched via nextcloud.
I've found that mobile is sometimes very important and sometimes not at all.
In general, I haven't found programs to be equally good on mobile and desktop, web apps usually coming closer than most. I've stopped trying to work with files on mobile and tend to rely on database progs (I think Joplin is a database) and import and export (or copy/paste) when I need.

23
I thought you had one vault/folder where with your files that Tangent, Obsidian and logseq accessed.
I did/do.
But I never had a YAML incompatibility because I never used it.
And all the programs kept their own indices, and so there was never a clash.

24
I am really interested in how you achieve using Tangent, logseq and obsidian together and how notezilla is layered ontop of your system

I don't really.
I've never done more than look at logseq. I don't like the appearance much, and I always hit a glitch. Org support is effectively deprecated and they are in the process of moving to be database first. I'm not intending to look again until the shift to database is finalised and stable.

My use of Obsidian with Tangent was only ever using Obsidian sometimes for features that Tangent lacked. I haven't done it for some time.
I don't actually use Obsidian at all now. I found it to be a consistently high maintenance program. They change things, they break workflows. Themes can break things. Plugins and themes are often not maintained. The maintenance and staying up-to-date might not always be a huge issue for all-in users who are programmers and/or students, and that's a fair proportion of its usebase. I'm also not sure how much it can genuinely considered a files program now - there are so many jsons, indexedDBs, etc, with many plugins bringing in their own set.

Which leaves me with Tangent as a standalone (occasionally with WM3), though it does work with file utilities and other standalones like Typora and Word.

I use Notezilla as an adjunct support program. For messages to myself and comments. I use it much less with programs that have sophisticated comment features themselves (eg Word). It's very flexible, and it's ability to sync across all the platforms I use (Windows and mobile) is very useful.

25
I would think that tangent's formatting would confuse logseq and obsidian. I realize that these are all text files but I thought that the front matter/yaml  wasn't really compatible.
I think the issue of frontmatter/YAML is important, and incompatibilities remove one of the major advantages of using files rather than a database.
(But syntax variations are also a huge problem. Ulysses/Inspire Writer are massively discrepant even with usual markdown which is one of the reasons I stay away. WM3 also to an extent. I tend to follow Obsidian syntax, but, in reality, I don't regard markdown as a standard to look for but rather to avoid. afaics the common standards I see are for text (bold, italic - though non-standard strikethrough, underline, highlight are also often seen), headings, lists and blank lines for new paragraphs; and from reading Obsidian media, it's my impression that nearly all users simply stick to the old rich text keyboard shortcuts.)

I don't use it at all, so I don't know whether there are any between these programs (I do know that Obsidian recently revised its YAML and garbaged the setups that many users were using. Driven by users' failing to understand or follow YAML definitions and upsetting plugins that relied on standards being followed. Thereby also enforcing plugins to follow a standard approach.

I did use YAML a little in Obsidian's early days, but deleted all of it when YAML was chosen as the preserve of plugins' metadata, and I've never used it ever since.

I think some databases offer the ability to process alot of information more quickly.

Seems very likely to me. They also have much more control of what is in the database and don't have to parse all the files in a folder to see what has changed. Personally, I see databases as a better solution to metadata.

I like my notes to be pristine, holding only my words (and tags - I use tags as a comment to self rather than any form of categorisation).

Pages: [1] 2 3 4 5 6 ... 78next