📚 node [[inbox]]

Inbox

  • I see my [[journals]] as my main [[inbox]]; see [[today]] in journal/.
    • In [[wiki vim]], ,w,w takes you to today's note.
    • In [[foam]], alt-d takes you to today's note.
    • In [[logseq]], gj takes you to today's note.

Inbox

Disorganized notes here, to be categorized later.

Inbox

  • Here you can write disorganised notes to be categorised later
  • Bullet points are useful, but it could be free form text as well
  • Sometimes it's better to just get things off your mind quickly, rather than stop to think where it belongs
  • But don't let this list get too long
  • Move information to more specific documents and link to them.
    • This helps you navigate between documents quickly
    • For example, you can Cmd+Click this: [[todo]]
  • Some notes don't end up making sense the next day
  • That's ok, you can just delete them!
    • You can always find them in your git history, if you really need it!

TODOversion control system that captures movements

  • file system implementation that records all of the operations performed on a file over time

  • editor that integrates with all of those changes and can easily visualize them

  • somehow logged to a file

  • perhaps converted to git or something? this goes along with the 'file system' in memory editor idea i had before.

etc

article: everyone is programming poorly visualization of all these no code and communication skills compare to real code

meme about academia: multi column beta (research paper) vs freewriting chad

TODOAdd CI

  • Currently the site is built on the client side

  • Add a CI configuration to build the site on upload

TODOAdd 'Edit on GitHub' button

  • Dependent on CI

  • Allows others to open PRs and edit content from GitHub that is then directly added to the site (and incorporated, via CI)

TODOConvert links to archive.org references on push

this way i'll actually have them in the future should be part of a CI job or something; maybe locally in the editor? could take a lot of time though.

TODOdynamically fetch and insert titles into .org files

this way i dont have to retype the title, as i do most of the time. easier to just go back and change it than to have to manually add the title

get wifi from a QR code

  • nautilus file manager (or some other drag n drop file manager)

  • install cobang:

    • install flatpak (services flatpak enable for nixos)

    • install the flathub repo on flatpak thing

    • install cobang from flathub (instructions are on github, i think)

  • segfault happened when trying to read from my non ir cameras, so i had to switch to the mode that had a drag and drop, install the nautilus file manager, then drag and drop an image onto cobang to get it to find the wifi configuratino

i think cobang uses networkmanager so its fine?

TODO: mimic the AUR pkgbuild as a nix flake

TODO

Idea: I want my window manager to have a 'reading mode' for any single buffer; that is, I want the buffer centered on the screen, in a sprcific size, surrounded by black text. Everything should be hidden but the buffer itself, and it should be constrained to a certain width and centered on the screen. It's hard to focus on long lines of horizontal information!

principles:

documentation should live with the source code rather than within the wiki for external applications, configurations, etc. this allows us to maintain a single source of truht for our repos; it's hard enough to remember to update inline documentation, and far, far more difficult to remember to update documentation in an entirely different repository!

(maybe when we achieve perfect reactive documentation across the system, we'll make progress - but while we're glued to static files, principled organization of the system really matters. the feature this really prompts is: if i modify file a at line a, or repo b, or something c, this should either automatically update, mark some notice (i.e. the thing upstream has been updated, but this may not have been updated to reflect it), or prompt the user to update the documentation associated with the function and not let then "commit" until they've updated it, similar to git)

ideas

  • learn ilp programs and problems - how does ilp work?

  • write a rough implementation of an ilp solver

  • build off of this to use scheduling problems

  • can schedule this like the pipeline of a compiler? feels like some sort of continuous delivery of content

what do i want from an editor?

  • lightning fast

  • builtin lsp (that i can turn off)

tool that shows the ui every single git diff to look back at app iterations as it changes

https://subconscious.substack.com/p/block-reference-mechanisms?utm_source=url

scrolling up in terminal with the mouse is inconsistent; when usign the arrow keys, you continue to see the buffer, but when scrolling up with the mouse you eventualyl hit a point at which we pass the scroll buffer and hit the prev part of the terminal. this shouldn't be possible! i shoulds be able to scroll up and do that too.

this actually makes my job simpler; we can convert the keyboard scroll handler to a text input (probably? how does this work with tui programs?) and work thoruhg our stuff that wya.

recreate the experience of someone browsing the internet, following references, with maps, with icons, with drawings. make them exp3erience the feeling of inspiration.

aaah

https://www.portlandmercury.com/Feature/2006/08/10/48767/the-best-of-3-am: Good article on the best things to do at 3AM in portland. https://online-go.com/: some cool tool for finding go games, written in golang?

credit card that declines if you try to purchase unhealthy food

TODOback up birthdays from people on facebook

this is the only way i will truly be able to delete my facebook account logging birthdays and information about people externally to any social media platform that is predatory seems very useful

TODOdetect arena links from those you follow during browser visit

if i view a link someone on arena has collected, i should see this information somewhere on the screen!

TODOracket-anonymizer

A build tool that allows for the implementation a #lang in the Racket toolkit, then expose its tools in traditionally expected ways, entirely separate from the Racket ecosystem. Gives you an LSP, a syntax highlighter plugin, a treesitter parser or something similar... these are all portable, statically linked binaries that can run standalone without Racket or any of that. Useful when you want to broadcast professionalism despite building off of this existing toolset - makes the abstractions far more "opaque".

Should we also consider attempting to repackage DrRacket as a new IDE? > : )

Inbox

  • Con alt-d podés ir a la nota del día, como en Roam.
  • Con ctrl-shift-s podés guardar todo y mandarlo a la nube :)

Inbox

  • Here you can write disorganised notes to be categorised later
  • Bullet points are useful, but it could be free form text as well
  • Sometimes it's better to just get things off your mind quickly, rather than stop to think where it belongs
  • But don't let this list get too long
  • Move information to more specific documents and link to them.
    • This helps you navigate between documents quickly
    • For example, you can Cmd+Click this: [[todo]]
  • Some notes don't end up making sense the next day
  • That's ok, you can just delete them!
    • You can always find them in your git history, if you really need it!
📖 stoas
⥱ context
⥅ related node [[2005 01 20 2005 will be the year my inboxes die]]
⥅ related node [[unified inbox startup]]