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.
that's an economic solution (and a neat one at that) to a sociopolitical problem. societies use names to address, differentiate, and even affiliate each other.
economics concerns itself with the best allocation of productive resources. names don't really fall into that category (even if there is some marginal utility in the economic domain for edge cases like celebrities' names).
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.
That can certainly be an issue, yes. It's not one I personally have come across yet as I tend to have quite distinct 'domains' that don't change much.
At work, I'm a contractor and I typically spend 1-3 years on a project. Each gets its own system, nice and simple.
My home system has 10-19 capturing all of my 'personal, daily life' which leaves plenty of areas for my personal projects. For instance, 50-59 is Johnny.Decimal itself.
So far I've implemented JD:
- Managing a 2 year contemporary dance production, multiple locations, staff, ticketing, marketing, etc.
- Consolidating 200+ data centres in to 7; I did basically all of the hardware from procurement to having a green light on a NIC.
- Running an infrastructure upgrade project for a major bank.
- Running 2nd level desktop support for an international packaging company.
- My personal life, including managing the limited company that I contract through.
I plan on anonymising and documenting as many of these cases as I can on the site. I just need to find the time.
I need to write another page explaining this. You may have many non-overlapping ‘domains’, whose numbers don’t relate to each other at all. You just have to keep them separate: home computer, work computer. This job, the next job. Etc.
The system running my personal life has been going since 2012. Meanwhile, those other jobs have come and gone.
Maybe it’s just me – clearly I have a mind that loves numbers – but I haven’t found it confusing at all.
Weirdly I have found that I have developed my own internal standards. I generally need to travel with work, and that always ends up being ‘16 Travel’.
(10-19 is usually “Administration” at work.)
High on my list of stuff to write is a whole bunch of example pages. Drop me an email if you’d like me to let you know when they’re done.
I don't find the numbers confusing either. It's just my mind couldn't accept that you could fit everything in your life in 10 areas x 10 categories structure (well, 9x9 really, since 0s are for metadata). So thanks for clarifying (and this definitely needs to go on the page, IMO).
If I may ask here, how do you handle things that cut across two or more of your existing systems? Do you duplicate things? Or use references with target collection name, e.g. "Work Computer 12.34 Some shared stuff"?
This is why we need tags and other metadata in the filesystem. (Windows actually supports this via alternate data streams, but very few apps and tools use it) Used to have an overview of this here: (archive.org might have a copy) http://developeriq.in/articles/2013/aug/19/alternate-data-st...
- ~/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.
I'd argue that if you are writing text, you'll put the description first and then look up the link. Because the description is often part of the sentence, and the link is not.
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?
"Surely this is true of all markup languages. How you would represent this visually in a document?"
Not to be snarky, but the ML in XML and HTML stands for markup language..
I'd like my markup to be easy to read and also to map to a tree hierarchy. This seems essential for parsing and anything related to literate programming and reusing "blocks"
Like when I drop in a org mode clock (for logging time in my work logbook), without a tree hierarchy I have no means of binding the time to my description of the work I did. I mean... I see in visually, but its not programmatically linked as an attribute of that text block.
You can kinda get around with pepperin headers everywhere, but it's not as flexible
> Surely this is true of all markup languages. How you would represent this visually in a document?
An extra newline between the end of the inner part and the return to the outer part, which is what I do naturally. This can get unwieldy for breaking out of more than one level, but that's rare enough you can handle that with an alternative syntax like "--" alone to break out of two levels, "---" to break out of 3, etc.
Another possibility would be picking up ASCII SI/SO again. (Emacs already makes extensive use of FF.)
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.
I couldn't reply to that as it is too old, but wanted to tell you that we talked and we ended up parting ways. While things are still in a turmoil, it seems like some kind of window opened and hope is out there again.
Just wanted to thank you for the concern showed then.
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)