Readit News“...surely not Dewey Decimal?”
Close! Johnny.Decimal. https://johnnydecimal.com
I’m Johnny. Feedback much appreciated, I’m working like a busy little bee on the site as we speak. Should have a show HN app ready in a couple of months, but I’m learning JS/React as I go so it’s taking time. :-)
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.
Few people here have referred to the /tmp directory. This is essential in my workflow. I put a lot of things there (this is also my Downloads folder) and when the computer reboots, its clean again!
One of the computers I use stay turned on for long times, so I have /tmp/t and a cronjob that cleans all files older than 1 day in this directory:
# Remove all files in /tmp/t older than 1440 min (one day)
*/10 * * * * find /tmp/t -cmin +1440 -delete > /tmp/.find-delete-1440.log 2>&1
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
BTW: if using Android, if FF is not for you, try Brave instead of Chrome.
It feels exactly like Chrome (it's Chromium-based), but has a built-in adblocker, tracker blocking, HTTPS everywhere, no nagging to sign in, and does not throw "suggested news" (with no opt-out) upon you. Brave's founder is ex-Mozilla's CEO (Brendan Eich).
However latest FF on Android is actually not bad, at least if you have a modern phone (the UI feels slowish though on pre-2016 phones).
Anecdotally, I have found that Brave chokes on some obscure websites (i.e. it won't play video or audio).
Often the link description is the most important thing, and may make sense without the link, so I'm not sure how well that would work.
To me putting the link first is extremely counter-intuitive, as if writing plain text I'd also be more likely to write out a description of what I'm referencing first, and then enclosing the link in parentheses.
Thankfully with Markdown that makes it easier to remember - the URL part is as it always was, and I just need to mark which part of the text makes up the description.
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.
I love orgmode, but what's the advantage over asciidoc? asciidoc looks cleaner to me
the other small disadvantage is that text isn't really bound to headers. So headers and text just kinda float around meaninglessly. So you can't have:
* Header topic1
introductory text
* * Subheader
some descriptive text related to the subheader
more text to wrap up topic1
> 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]
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?
1. A first-come-first-serve system like Twitter. I'd list drawbacks but this comment section is full of them.
2. A lease system like domain names, whose drawbacks are best explained in this tweet by @devonzuegel:
Does anyone know of another way to do meaningful names?1. When a person registers a name they declare a price they are willing to sell the name for. They can update their price at any time.
2. They pay an annual tax (about 1% to 5%) for the right to keep the name.
3. If someone is willing to buy the name for the declared price they are forced to sell the name to them.
This system has the advantage that the person who values the name the most will get to keep it, and the person who lost the name will be fairly compensated.
[0] https://www.law.nyu.edu/sites/default/files/upload_documents... (See the bottom of page 39 in particular)