31 Matching Annotations
  1. Feb 2024
  2. Nov 2023
  3. Oct 2023
  4. Sep 2023
    1. In the author’s view, using a combination of content-addressing, signed content, and petnames would help decentralise that layer. It keeps centralisation around aggregators (because of the scarcity of attention), but mitigates their harmful lock-in.
  5. Aug 2023
    1. Does anyone has it’s Zettelkasten in Google Docs, Microsoft Word or Plain Tex (without a hood app like obsidian or The Archive)? .t3_15fjb97._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }

      reply to u/Efficient_Earth_8773 at https://www.reddit.com/r/Zettelkasten/comments/15fjb97/does_anyone_has_its_zettelkasten_in_google_docs/

      Experimenting can be interesting. I've tried using spreadsheet software like Google Sheets or Excel which can be simple and useful methods that don't lose significant functionality. I did separate sheets for zettels, sources, and the index. Each zettel had it's own row with with a number, title, contents, and a link to a source as well as the index.

      Google Docs might be reasonably doable, but the linking portion may be one of the more difficult affordances to accomplish easily or in a very user-centric fashion. It is doable though: https://support.google.com/docs/answer/45893?hl=en&co=GENIE.Platform%3DDesktop, and one might even mix Google Docs with Google Sheets? I could see Sheets being useful for creating an index and or sources while Docs could be used for individual notes as well. It's all about affordances and ease of use. Text is a major portion of having and maintaining a zettelkasten, so by this logic anything that will allow that could potentially be used as a zettelkasten. However, it helps to think about how one will use it in practice on a day-to-day basis. How hard will it be to create links? Search it? How hard will it be when you've got thousands of "slips"? How much time will these things take as it scales up in size?

      A paper-based example: One of the reasons that many pen and paper users only write on one side of their index cards is that it saves the time of needing to take cards out and check if they do or don't have writing on the back or remembering where something is when it was written on the back of a card. It's a lot easier to tip through your collection if they're written only on the front. If you use an alternate application/software what will all these daily functions look like compounded over time? Does the software make things simpler and easier or will it make them be more difficult or take more time? And is that difficulty and time useful or not to your particular practice? Historian and author David McCullough prefers a manual typewriter over computers with keyboards specifically because it forces him to slow down and take his time. Another affordance to consider is how much or little work one may need to put into using it from a linking (or not) perspective. Using paper forces one to create a minimum of at least one link (made by the simple fact of filing it next to another) while other methods like Obsidian allow you to too easily take notes and place them into an infinitely growing pile of orphaned notes. Is it then more work to create discrete links later when you've lost the context and threads of potential arguments you might make? Will your specific method help you to regularly review through old notes? How hard will it be to mix things up for creativity's sake? How easy/difficult will it be to use your notes for writing/creating new material, if you intend to use it for that?

      Think about how and why you'd want to use it and which affordances you really want/need. Then the only way to tell is to try it out for a bit and see how one likes/doesn't like a particular method and whether or not it helps to motivate you in your work. If you don't like the look of an application and it makes you not want to use it regularly, that obviously is a deal breaker. One might also think about how difficult/easy import/export might be if they intend to hop from one application to another. Finally, switching applications every few months can be self-defeating, so beware of this potential downfall as you make what will eventually need to be your ultimate choice. Beware of shiny object syndrome or software that ceases updating in just a few years without easy export.

  6. Jul 2023
    1. I think the only purpose of this is to detain programmers from doing anything a non-Microsoft way.

      Probably not really...

  7. Apr 2022
    1. The Hori key enters a Hori lock in such a way as to affirm your suspicion that every key you’ve ever inserted into every lock throughout your entire life was a sham. A false combination — jittery, sticky, imprecise. You realize how badly cut, forged by shoddy means, all the keys you own currently are. Using this Hori key and lock combination is similar to how you might have felt the first time you ever touched a masterfully finished piece of wood — shock at that glassy smoothness you didn’t think could be brought out from the material. The key enters. Within perfectly milled chambers, the driver pins — attenuated by precisely tensioned springs — push against the key pins as the key slides forward in the keyway. The driver pins align to a dead-straight shear line and you feel the key settle with a satisfaction of a meticulously-measured thing spooning its Platonic opposite. Then you twist. The movement of the bolt away from the frame is so smooth — the door having been hung by some god of carpentry with the accuracy of a proton collision path — that you gasp, actually gasp, at the mechanism.

      I love the visceral way Craig Mod describes these Hori key/lock mechanisms. Makes me want to go out and buy one.

  8. Jul 2021
    1. resist vendor locking

      This is a monumental reason for carefully choosing our suppliers. If I weren't able to export everything that I annotate from places like Readwise I would not be their customer.

  9. Jun 2021
  10. Mar 2021
  11. Jan 2021
  12. Oct 2020
    1. manually specifying the order isn't really a great solution (as tempting as it sounds) because you'll probably have broken behaviour if you subsequently move away from Rollup.
  13. Jul 2020
  14. Jun 2020
  15. Apr 2020
    1. They are proof that our openness about our data formats means that you do not have to fear data lock-in.
    2. It’s this third way that we avoid lock-in that is relevant to today’s topic. Our data format design is specified well enough so that people with no connection to AgileBits can write software to be able to handle it.
    1. If you don't—or can't—lock your users in, the best way to compete is to innovate at a breakneck pace. Let's use Google Search as an example. It's a product that cannot lock users in: users don't have to install software to use it; they don't have to upload data to use it; they don't have to sign two-year contracts; and if they decide to try another search engine, they merely type it into their browser's location bar, and they're off and running.
    2. it is far preferable to spend your engineering effort on innovation than it is to build bigger walls and stronger doors that prevent users from leaving
    3. Want to keep your users? Just make it easy for them to leave.
    4. Users are starting to realize, however, that as they store more and more of their personal data in services that are not physically accessible, they run the risk of losing vast swaths of their online legacy if they don't have a means of removing their data.
  16. Mar 2020
  17. Dec 2019
  18. Sep 2019
  19. Nov 2017
    1. Publishers previously lost a lot of revenue from textbooks because many students bought secondhand, rented, pirated or just skipped buying textbooks altogether. Inclusive-access programs have changed that.