Moyamo

The problem I'd have with that is that I'd never be able to commit to a fixed set of areas or categories since the type of work I do is constantly evolving. Plus I've always had trouble creating mutually exclusive categories.

What works well for me is to keep all things I'll need soon in the top level of my documents folder and when I'm done with it I move it into an archive folder.

This way my documents folder has few files and folders in an easily accessible flat heirarchy. While old files can be easily searched for in the archive folder.

Using /tmp for my downloads folder became problematic for me when downloading big files.

1. You may want to pause the download and restart it after reboot.

2. It's quick to redownload small files but a pain to have to redownload large ones.

3. Arch puts /tmp on a tmpfs, so big files can eat all your memory!

- ~/docsync: Files I edit on a daily basis and is synchronized with Syncthing to all my devices. I put all projects I'm currently working on in the top-level of this folder except for the categories below. Archived projects are zipped and then put in ~/docsync/old

Categories:

- ~/docsync/accounts: Accounting stuff

- ~/docsync/audiobooks

- ~/docsync/books: All my PDF books

- ~/docsync/dotfiles: git controlled dotfiles.

- ~/docsync/Pictures

- ~/docsync/Music: Lossy compressed music.

Other folders in home directory

- ~/hq-media: Mostly FLAC audio

- ~/git: Clones of other people's git repos

- ~/srv: File shares other than docsync.

- ~/Mail: offline copies of email

- ~/tmp: temporary stuff I'll probably don't want to keep.

- ~/Downloads: Random stuff I've downloaded

Anecdotally, I have found that Brave chokes on some obscure websites (i.e. it won't play video or audio).

In html the link comes first <a href="link">Link Text</a>. So I would bet that most people are more comfortable with the link coming first.

> what's the advantage over asciidoc?

Exactly what is states in the article.

Asciidoc has 3 different types of headings (prefix, pre-postfix and underlined).

    http://example.com[Text]	  

The form is simple but for complex URLs, the [Text] might look like being part of the URL itself. Not beautiful but at least something I could live with.

Additionally asciidoc uses ===== for underlining headings and for delineating code blocks.

the other small disadvantage is that text isn't really bound to headers

Surely this is true of all markup languages. How you would represent this visually in a document?

I've noticed this as well, do they even encrypt the backups the upload to google drive and if so with what key? If they use one key then the advantages of perfect forward and perfect future secrecy that the double-ratchet protocol provides is lost.