hopefully there's nothing private in here anymore...

main
Anish Lakhwara 2022-02-26 22:23:54 +10:00
parent 9ce31eef66
commit 7ac0996e07
332 changed files with 5781 additions and 0 deletions

View File

@ -0,0 +1,11 @@
Starting in 2019 I want to complete 1 project a month. Each project can be as small or as big as i want, but ideally I'd work my way up to harder and harder projects
January: America Blogpost
Feburary: uHabits for desktop in elixir (cli?)
March: learn CSS for gitea and wallabag
April: theme for taskwarrior Andriod (more generally, learn to expand apps past where the navigation bar generally is)
May: NixOS install
June: One art (music/generative/word) a day
July: Wallabag client for linux desktop
#[[Archive]]

View File

@ -0,0 +1,18 @@
28032020: install nixOS on box
29032020: apply for centrelink
31032020: fineOS test
07042020: NAB Trader Account
08042020: buy beard oil,face wash, juice
10042020: bake cookies
24042020: write how to join hackers town matrix for ▐▚▖▗▜▒▖▗▝▝▜
25042020: replace gpg key for pass (look into subkeys)
29052020: vimTidal nix drv
01072020: buy frames for prints
02072020: find a place to volunteer
03072020: get some plants
01102020: pick up birks
02102020: update resume
03102020: follow up on oci card
07102020: invest in nasdaq fund
08102020: update resume

View File

@ -0,0 +1,79 @@
= Kitaab =
A lab notebook for a digital garden and a physical life
[[now]]
[[pipeline]]
= Plant Gardening =
A small garden of ideas
- [[Puralek]]
- [[Piracy]]
- [[Blog]]
- [[Infrastructure]]
- [[work]]
= The Lab =
Notes of alchemy
- [[dev]]
- [[hack]]
- [[web-devel]]
- [[generative]]
- [[linux]]
- [[nixOS]]
- [[fermentation]]
- [[gardening]]
= The Way =
Spiritual power reserves
- [[way]]
- [[quotes]]
- [[webnotes]]
- [[1thingaday]]
- [[░▟░▞▝]]
- [[notes.]]
- [[gratitude]]
- [[strategy]]
- [[brisbane]]
= Rock Keeping =
Rocks that bring to life information
- [[cube]]
- [[bowl]]
- [[box]]
- [[curve]]
- [[line]]
- [[dot]]
- [[tri]]
- [[pentagon]]
- [[rectangle]]
= Tadke =
Seedlings yet to see their dawn
- [[Yaad]]
- [[dmi]]
- [[lifeTracker]]
- [[contributions]]
- [[newpage]]
- [[wallabag]]
- [[link-store]]
- [[bots]]
- [[maze]]
= Scratch =
The humdrum of a chore list
- [[job]]
- [[sale]]
- [[debt]]
- [[purchases]]
- [[groceries]]
- [[chores]]
- [[media]]
= Travel =
Adventures in exploration
- [[india-2018]]
- [[america-2018]]
- [[sydney-april-2019]]
- [[smashstock2019]]
- [[korea2019]]
- [[brooyar2020]]
- [[canberra2020]]

View File

@ -0,0 +1,26 @@
%title work-log
%date 2020-09-21 14:54
working on vlad reports
includes:
- darkweb
- weekly report
- alarms
darkweb:
vlad sent me the template
- breach sources empty
- compromised by severity -> div by 0
- Vulnerability vele top 10 hosts empty
- compromised accounts not in report?
template.prep works correctly
weekly:
working
= tying it all together =
change checkDataNotEmpty to read the file based on reportType
find out why json.dump(finalJson, file) in all 3 scripts (reportlab, darkweb, weekly) is writing null instead of the data

View File

@ -0,0 +1,7 @@
%title De-facto proprietary software
:blog:future-of-foss:quote:
%date 2020-09-26 22:45
You want to download thousands of lines of useful, but random, code from the internet, for free, run it in a production web server, or worse, your users machine, trust it with your paying users data and reap that sweet dough. We all do. But then you cant be bothered to check the license, understand the software you are running and still want to blame the people who make your business a possibility when mistakes happen, while giving them nothing for it? This is both incompetence and entitlement.
https://13brane.net/rants/de-facto-closed-source/

View File

@ -0,0 +1,8 @@
%title sealight services intro
:sealight:writing:
%date 2020-09-27 00:10
sealight.services is the cove you wash up on after having drifted too far out from comfortable waters. As you look around you notice some of the rock is smooth, especially where the light from the gap in the roof shines through. You see scorched driftwood and a couple large stones laid out with intention. You feel the warmth on your skin.
Do you remember how you got here now?
Do you remember where you were going to go?

View File

@ -0,0 +1,4 @@
%title Just so
:writing:maze:
the stack of papers may seem like chaos, but LRU it's the most efficient solution organized solution you can make

View File

@ -0,0 +1,10 @@
%title Structure of Sorcery
:blog:maze:writing:
%date 2020-09-27 01:11
Magic, as we seem to understand it, is the ability to affect change in ways we didn't think possible.
Once you understand how the mechanism, by definition it is no longer magic.
In order to manifest impossible realities first we must be able to imagine them, hence belief is our primary tool. Those who search for these techniques are wixen. Our abilities tend to be localized and syncronicity the multiplier. Each may have their own rituals, but cooperation is our strength.
Enacting change is the purpose of all effort. Our tools must be as varied as the uses for energy, then. Change may be the only constant, but our mortality prohibits us from simply waiting for what we wish to happen.

View File

@ -0,0 +1,10 @@
%title Shaarli integration
:kitaab:dev:
%date 2020-09-27 01:49
A shaarli integration for Kitaab.
Start with a CLI client
https://github.com/shaarli/python-shaarli-client is a start
Find a way to wrap them in vim commands
Insert them by tag/search/etc

View File

@ -0,0 +1,6 @@
%title Weaving the story of magic computers
%date 2020-08-01 01:58
- What does it feel like to do magic?
- What can magic do?
- What can the magic NOT do?

View File

@ -0,0 +1,7 @@
%title Critical Engineering Manifesto
:webquote:dev:manifesto:
%date 2020-09-27 16:27
6. The Critical Engineer expands "machine" to describe interrelationships encompassing devices, bodies, agents, forces and networks.
https://criticalengineering.org/

View File

@ -0,0 +1,16 @@
%title Cosmo
:webquote:
%date 2020-09-27 16:51
And you may ask yourself
Well... How did I get here?
And you may ask yourself
"How do I work this?"
And you may ask yourself
"Where is that large automobile?"
And you may tell yourself
"This is not my beautiful house!"
Attention Conservation Notice: What follows is long, self-absorbed, and boring to look at; much of it was written ten or even twenty years ago.
http://bactra.org/

View File

@ -0,0 +1,7 @@
%title Getting Grasp to work with Kitaab
:dev:meta:
%date 2020-09-27 17:30
I need to find a command I can run that will start Vimwiki from command line. (Probably through .vimrc -> nvim.nix)
Then I need to make a pull request to grasp to run subprocess.call('vim ')
Paste the contents into the open file? Show the interactive session?

View File

@ -0,0 +1,19 @@
%title Standing on the Shoulders of Understandable Giants
:writing:blog:
%date 2020-09-27 19:36
Many people admire modern software. The ease with which we can do incredible tasks is truly powerful; navigation, translation, taxes. Consumer technology has changed the way people operate. But it is a brittle tool. Trying to do anything outside of the scope of what was designed it falls apart. We cannot inspect it's workings, or configure personalizations to our own benefit. We do not get to build on top of the giants, simply pass through them in a very specific way.
There are those who refuse these terms entirely and opt to build their own tools. These craftspeople will forge the tools that fit their needs best. Building foundations at bedrock allows for the most control. Make the tools exactly as you need them. These people garner a deep respect from me.
I land somewhere in the middle.
A big development in my understanding of the craft was from the realization that I can just inspect open source code. After all that is the point. For a long time I was scared to peek behind the curtain, afraid that the runes would be illegible. But that was a silly fear. A big part of how I learn now is just looking at how other people solved a problem. Afterall the patterns are adaptable.
Being able to inspect and understand code doesn't have the same benefits as having built them entirely yourself. In exchange you are granted height, and as much control as you can muster. Can you master somebody else's spell enough to make it your own? I know the limits of my own power and so limiting the complexity is desirable.
No single person can understand the entirety of their toolchain. We must depend on each other in order to wield our artifacts at all. There's always another layer below 'bedrock'. The operating system underlies application space. The instruction set underlies the OS and BIOS. The silicon underlies the BIOS. The silicon must be extracted which requires additional industrial scale tools to shape and form.
Will you chisel away at the void, to craft the perfect tool? Or will bow to cosmic powers of the corpers you summon, happy enough be granted outcomes of incantions.
I will choose to stand of the shoulders of the giants I can understand. Those that I can also control.

View File

@ -0,0 +1,6 @@
%title What is a type? | Lambda the Ultimate
:webquote: http://lambda-the-ultimate.org/node/5604
%date 2020-09-27 Sun 21:49]
Selection:
I'll repeat this here, since it seems quite relevant.

View File

@ -0,0 +1,7 @@
%title What is a type? | Lambda the Ultimate
:webquote: http://lambda-the-ultimate.org/node/5604
%date [2020-09-27 Sun 21:56]
> Types are mostly used in three ways:

View File

@ -0,0 +1,6 @@
%title grasp changes
:dev:meta:kitaab:
%date 2020-09-27 22:44
Add multi-line patch from issue https://github.com/karlicoss/grasp/issues/22
Get server to run vim -c VimwikiRegenerateTags +c ZettelGenerateTags webquote ~/vimwiki/webquotes.wiki

Binary file not shown.

View File

View File

@ -0,0 +1,14 @@
%title Kitaab on line
:dev:line:meta:
%date 2020-09-28 00:48
Problem: nix-on-droid doesn't allow you to browse the rest of the system -- see https://github.com/t184256/nix-on-droid/issues/78
Fix: have a git repo I can pull to do initial config
Problem: Can't build vim-zettel, taskwiki, etc... because no nixpkgs
Fix: clone my fork TODO
Problem: nvim.nix still doesn't install node.js necessary for coc
Fix: include nodejs in nvim.nix? TODO

View File

@ -0,0 +1,5 @@
%title Puralek for Line
:puralek:line:meta:
%date 2020-09-28 00:59
grasp for android?

View File

@ -0,0 +1,5 @@
%title PDF pipeline
:dev:kitaab:
%date 2020-09-28 13:51
Firefox extension or shaarli grabber that takes pdf links downloads them and adds them to non-fiction syncthing directory to be available on [[hyperplane]]

View File

@ -0,0 +1,5 @@
%title Data stores (ie not streams)
:puralek:
%date 2020-09-29 20:26
I need to find a data store for pdf recipes and a way to store workouts.

View File

@ -0,0 +1,7 @@
%title Dealing with Thrashing
:organization:
%date 2020-09-30 19:21
I thrash around a lot and don't tend to focus on one task at a time. This, I have known for a long time, and have tried to build systems to help me keep track of all the things I am doing so I can continue to operate in this way. But I think something needs to change.
I was thinking of setting a bi-weekly (once in 2 weeks) 'focus' and only doing tasks in that 'project'. This combined with a [[1thingaday]] that I follow well, will hopefully help me achieve the things that I want to.

View File

@ -0,0 +1,10 @@
%title Rules for Backups
:puralek:
%date 2020-09-30 23:16
3-2-1 rule
* 3 backups
* in 2 mediums
* with 1 in a remote location
backup should be automatic, with monthly/weekly schedules running to ensure no dataloss

View File

@ -0,0 +1,19 @@
%title Flows
:puralek:
%date 2020-09-30 23:17
* music/tv/books needs to be curated -> [[Piracy]] needs to be configured
* images
* phone photos
* images i like/content online
* writings/notes
* consolidate jrnl - only has entries from April onwards.
* old forgotten projects (boss man boss?)
* other things from a forgotten age saved
* Habits
* Fitness
* Location
* Financial
* Calendar/meetings
* Tasks
* School stuff

View File

@ -0,0 +1,11 @@
%title Why have an HPI?
:puralek:writing:
%date 2020-09-30 23:19
story:
when thinking about how to view and save and store data such that it makes the most sense, having an interface that classifies arbitrarily tagged data (podcasts, files, rss feeds, etc etc) to show the content you're looking for sounds interesting. Having the same set of tags across all the formats seems like a good place to start this endeavour but I fear this may be not concrete enough to work with yet
A collection of my raw data from the past that should be organized. A curation of the media ive enjoyed, my creative endeavours and things that i saved. Ultimately aims to be a museum of me to help me understand myself. how can a museum also be living though? my computer is a delicate dance atop the terminal, how could it be static?
The problem is that my information is scattered, unindexed, and of an unknown quality
This goes beyond just collecting data, but using a collection of data to create new tools to interact with it. Formatting and organising my own information so that it's accessible to learn from

View File

@ -0,0 +1,7 @@
%title Vim tricks
:kendrit:vim:
%date 2020-10-01 19:06
Screen: H (top of screen), M (middle of screen), L (bottom of screen)
taken from: https://missing.csail.mit.edu/2020/editors/

View File

@ -0,0 +1,22 @@
%title My journey with Linux
:blog:writing:
%date 2020-10-01 19:49
Started out experimenting with VMs in high school (2013)
never got very far (dont think i actually got an install working)
get sick of windows slowing down my laptop in college (2015?)
decide to install Arch to bootloader because I'm hardcore (and was on break from school)
try many times to get it installed
get it working, install WM only -- bspwm was trendy at the time
learn shell, git, vim because all the r/unixporn and /g/ desktop threads were doing that
learn about AUR
keep forgetting to run pacman -Syu and then when I do it breaks my computer
get sick of that and install debian net-install
continue running bspwm
become indoctrinated into the FOSS zealotry
continue with debian net-install, bspwm, vim -> happy with my setup
...
buy librem13v3 (2019)
get sick of having to do everything by hand on desktop and switch to mostly using laptop
laptop keyboard sucks though (using ErgoDox EZ on desktop)
learn about nixOS

View File

@ -0,0 +1,5 @@
%title Keyboard changes
:ops:
%date 2020-10-03 16:07
Add backtick

View File

@ -0,0 +1,7 @@
%title taskwiki fix
:meta:dev:
%date 2020-10-06 23:10
currently taskwiki is broken because it requires a new version of tasklib (2.2.1)
tasklib is in nixpkgs/pkgs/development/python-modules/taskwiki
I need to change the sha256 hash to update to the new version

View File

@ -0,0 +1,3 @@
%title
%date 2020-10-13 05:46

View File

@ -0,0 +1,8 @@
%title HDD Catalouge
:puralek:backup:
%date 2020-10-13 21:43
Silver -> Memories + Nostalgia
Black ->
Mother of all HDD -> Music
Big Black -> Movies + TV

View File

@ -0,0 +1,23 @@
%title Bowl to NixOS Migration
:puralek:bowl:
%date 2020-10-13 21:44
Wish to migrate all the services on bowl to nixOS from Ubuntu
As part of [[Puralek]]
Necessary in order to add wireguard
= Services =
* VPN -> Wireguard
* AirSonic
* [[Nextcloud]]
* Contacts
* Calendar
* Files
* Pictures
* GpxPod
* TaskWarrior
* Wallabag
* Shaarli
* NFS share (TV/Movies)
* Headphones/Lidarr/Sonarr [[Piracy]]
* beancount + fava ([[finances]])

View File

@ -0,0 +1,23 @@
%title Flows for HPI
:puralek:
%date 2020-10-13 22:06
= flows =
[[shaarli]] (#music/#tv/#books) -> sonarr/radarr/headphones
~~ email (links) -> shaarli ~~
telegram chanel -> rss
telegram self messages -> ??
rss stars -> [[Blog]]
telegram messages more than 5 years old -> archive
firefox tab groups -> sync (i think this syncs), files
~~ are.na -> shaarli ([[read-imap]]) ~~
slack music -> shaarli?
#theStudio -> Shaarli
~~ gnome-pomodoro -> time tracker -> [[newpage]] ~~
uHabits -> habit-server -> [[habitsGtk]] / dijo
Kitaab -> [[Blog]]
Wallabag -> Annotations
Kobo -> Annotations
merveilles.town -> Notes
take [[media]] and throw it in shaarli

View File

@ -0,0 +1,16 @@
%title Idea behind Puralek
:puralek:writing:
%date 2020-10-13 22:07
i realized that this is about organizing information, but thats also literally the purpose of the data involved in creating kitaab. its important to remember to distinguish between the mix of meta data and data held in this "book" and all the data that is produced in using computers. however the organization principles apply to both. hence i am starting to use this more like a log of all things. in doing so, the idea of Puralek and Kitaab become inextriabcly intertwined and must be synthesized into something more
this struck me during the reordering of /now and seeing now listed down there as an intergration idea makes sense, but not the scope i originally thought.
use /now to order the index page of Kitaab
some sort of averaging between total itetms and change in items
= Integration ideas =
generate a calendar that updates over nextcloud through task warrior events
Be able to link the Tasks list from a specific directory into the /now page
automation based on the above tags idea: feedreader > star > based on content action (add to jackett for music, save to images for image, etc) and have a living orgamism of information

View File

@ -0,0 +1,32 @@
%title kendrit-puralek
:kendrit:puralek:
%date 2020-10-15 22:22
[[201101-2014|Kendrit Puralek Review]]
= Goals =
- HPI interface
- Automation to grab stuff from various services and have it be accessible ideally through commandline
- Ability to add to [[Kitaab]] through [[Puralek]]
- Borg backup running continously
- Ensure that grasp is running through nixOS
- Create a new zettel for each grasp quote
- Put all of [[quotes]], [[webnotes]], and [[webquotes]] into one file
- [[bowl]] running on nixOS with all HDDs attached *OR* a replacement for bowl
- Integrate all the old stuff that is in cold storage and make it accessible
- Integrate stuff that is currently android only into Puralek
- Habits
- Taskwarrior + Calendar integration
- build a startpage that features random things from Puralek
- album
- article
- kitaab page
- rss feed?
- quote
- story?
- [[lifeTracker]] integration
- finances
- location
- browser history
- sleep
- media consumption

View File

@ -0,0 +1,3 @@
%title
%date 2020-10-15 22:26

View File

@ -0,0 +1,32 @@
%title Services
:ops:software:
%date 2020-10-15 22:29
= Digital Infrastructure =
- nextcloud ([[bowl]])
- files
- calendar
- photos
- airsonic ([[bowl]])
- wallabag ([[bowl]])
- taskwarrior ([[bowl]])
- gitea ([[helix]])
- passwords
- blog ([[cube]])
- rss reader (feedbin.com)
- Mastodon (▚▕░▝▞▒▕▒▝▛▔▝ / merveilles.town)
- ~~Scuttlebutt~~ ([[line]] / [[curve]] / [[box]])
- Habits ([[line]])
- Fava + Beancount ([[finances]])
- Syncthing
- this notebook
- ~~tiddlyWiki~~
- drawing
- Telegram, ~~Wire~~, ~~Whatsapp~~, Signal, Matrix
- Slack / Discord
- wireguard
- OSMAnd
= Less used =
- Anki
- Duolingo

View File

@ -0,0 +1,3 @@
%title
%date 2020-10-15 22:33

View File

View File

@ -0,0 +1,14 @@
%title Travel
:travel:
%date 2020-10-15 23:06
Adventures in exploration
- [[india-2018]]
- [[america-2018]]
- [[sydney-april-2019]]
- [[smashstock2019]]
- [[korea2019]]
- [[newzealand2019]]
- [[brooyar2020]]
- [[canberra2020]]
- [[sydney2021]]

View File

@ -0,0 +1,11 @@
%title Invincible Computing
:writing:punya:
%date 2020-10-15 23:13
Computers are fragile things. Data is lost, for either hardware or software reasons. Software goes out of date, hardware becomes obsolete.
Why do we put up with this?
I want to be able to point any computer that I rightfully have ownership of, point it to a server of mine, and be jacked right back into my setup.
As a developer and enthusiast I refuse to have to configure my tools over and over again. I learn them deeply and set them up to be exactly how I want.
But I should only go through that process once. And just like the hammer of Thor, I should be able to summon them from anywhere.
That is the goal.

View File

@ -0,0 +1,5 @@
%title Taskwarrior Android Changes
:dev:PR:idea:android:
%date 2020-10-17 15:46
Instead of reports showing various different taskwarrior reports, have it show by project and be configurable

View File

@ -0,0 +1,18 @@
%title voiceNote
:dev:pebble:
%date 2020-10-18 21:28
A VoiceNote application that creates a new text note with the title and rest of the dictation to your phone as a txt file saved wherever you want it, optionally through some template.
This is going to need:
- Transcription API calls
- Sending data to phone
- Handling the data once on the phone (companion app?)
Some useful links:
- Rebble SDK examples https://developer.rebble.io/developer.pebble.com/examples/index.html
- TranscriptionAPI Docs https://developer.rebble.io/developer.pebble.com/guides/events-and-services/dictation/index.html
- Apps:
- https://apps.rebble.io/en_US/application/562eb6ebd2c136c34a00000b?section=watchapps
- https://apps.rebble.io/en_US/application/56231c63ade802b29d00002b?section=watchapps
- https://apps.rebble.io/en_US/application/5546dbbdab49e49cb40000ef?section=watchapps

View File

@ -0,0 +1,7 @@
%title Replacement Glass
:pebble:dot:
%date 2020-10-18 21:41
Need a 35.5mm width and 0.5mm thickness sapphire glass replacement.
Will probably need 1mm take to secure it back to the I-ring
Alternatively Suguru could work

View File

@ -0,0 +1,13 @@
%title The God Pebble
:pebble:craft:dot:
%date 2020-10-18 21:47
Endgame:
- waterproof
- Suguru sealed
- O-capped buttons (not sure if possible)
- Sapphire glass (polarized?)
- HR Smart Strop
- Higher battery capacity
- NFC Payments
- Take calls through the microphone

View File

@ -0,0 +1,10 @@
%title Linux Debugging
:ops:cli:
%date 2020-10-18 22:32
= Posix =
- /etc/ stores a list of config files for the software you have installed
- We can determine most log file locations, from config files
= Systemd =
- /etc/systemd/system shows you all the system services running

View File

@ -0,0 +1,7 @@
%title Memory Usage on cube
:ops:cube:
%date 2020-10-18 23:04
When I logged in, checking htop didn't reveal that gitea was running out of memory. it was sitting around 250mb of usage, well within what is available.
Restarting gitea, disabling hypercore and dat because they're broken and old has resolved the current problem

View File

@ -0,0 +1,48 @@
%title NixOS Quick Tips
:nix:dev:ops:
%date 2020-10-19 19:05
install a package:
`nix-env -i hello` <-- not reproducible and hence not advisable
or
edit `/etc/nixos/configuration.nix` to ensure system wide install
`nixos-rebuild switch` <-- create new generation
`nixos-rebuild test` <-- only active while computer on
`sudo nixos-rebuild test -I nixpkgs=~/usr/nixpkgs/`
^-- use local repo to build pkgs
find out where in the store a binary is:
`readlink -f $(which hello)`
search packages
`nix-env -qaP '.*hello.*'`
or
`nix search <pkg>`
search nix package options
`nixos-option <option>`
clear up space:
`nix-collect-garbage -d`
upgrade to new channel:
`nix-channel --list` # show what version we're on
`nix-channel --add https://nixos.org/channels/nixos-XX.XX nixos`
`nix-channel --update`
`nixos-rebuild switch`
remember to use `sudo` if you want to update the system
use a package through nix-shell:
`nix-shell -p <package>`
list generations
`nix-env --list-generations`
list installed packages
`nixos-option environment.systemPackages`
or
`nix-env --query`
install a nixOS .nix file through nix package manager
`nix-env -f nvim.nix -i neovim`

View File

@ -0,0 +1,130 @@
%title Buchi Flavors
:recipe:fermentation:buchi:
%date 2020-10-19 20:20
== 14/10/20 5th Batch ==
= Blueberry cream =
Same as before
= Mango + Pear =
1 mango
2 pear blitzed (only a lil added)
= Straw + Lime =
Blitzed strawberry 250g
Juice of some lime
= Pear + Apple x2 =
Blitzed pear (Only buy 1 of these!)
Blitzed apple (Only buy 1 of these!)
Some lime juice
= flavors ideas =
lime + mint
lime + ginger
vanilla, banana, blueberry, cinnamon, peach, basically any fruits
look into heating flavors, adding sugar before 2nd ferment
= 21/09/20 4th batch =
= Blueberry cream =
Blue bottle
same as below
= Tropical blast =
Red bottle
250g strawberry
- half chopped
- half crushed and heated
half a pineapple, chopped
some lemon
some lime
some blueberry
= Pineapple + passionfruit + lime =
Green bottle
quart a pineapple, blitzed
2 passionfruits
juice of 2 limes
= Kiwi + Lemon =
Blue bottle
3 kiwis, blitz
juice of 1 lemon
= Pineapple swirl =
quart a pineapple, blitzed
some kiwi
some lemon
some lime
= 23/08/20 3rd batch =
= Blueberry Cream =
230g blueberry
turned into jam
heated with 1 cup water
crushed
a little sugar
1 cap vanilla extract
3rd full batch
= Strawberry Cream =
250g strawberry
turned into jam
same steps as blueberry
3rd full batch
= Lemon Mint Musk =
3 full limes from jj
5 fresh mint leaves
half a pack dried mint
3rd full batch
= Banana Cream =
2 full bananas
1 cap vanilla extract
3rd full batch
= 3rd batch first stage 09/08/20 =
Madura organic green tea
All boxed water
= Review of 22/07 batch =
all undrinkably sour, should have re-made from the first stage
= Strawberry 22/07/20 =
~500g strawberry, chopped
about 1/3rd bottle
Diluted water batch
= Citrus 22/07/20 =
Oca/Orange blend
Half a large orange
3 chopped Ocas
Diluted water batch
= Orange OG 22/07/20 =
Ginger/Tumeric/Orange blend
Half a large orange
Diced ginger + tumeric 50/50
about a 1/4th of the bottle
Diluted water batch
= The OG 12/07/20 =
Tumeric/Ginger blend
Diced, roughly 50/50
About 1/4th the bottle
= Berry Buch 12/07/20 =
Strawberry + Blueberry blend
250g strawberry, diced
125g blueberries smushed
Around 1/3rd of the bottle
= Spiced Fruit 12/07/20 =
Strawberry, Pomogranite, Blueberry and Ginger
200g strawberry, diced
100g blueberry, smushed
1 pomogranite, sorta smushed
a teaspoon of ginger, diced and smushed
About 1/3rd of a small bottle

View File

@ -0,0 +1,5 @@
%title Alert when nixpkgs unstable is unavailable
:bot:dev:nix:
%date 2020-10-19 20:38

View File

@ -0,0 +1,6 @@
%title Pebble Battery Replacement
:link:pebble:hardware:
%date 2020-10-19 22:20
This website https://pebblejunkies.com/how_to-s.html has useful links

View File

@ -0,0 +1,10 @@
%title Kimchi Batch 2
:ferment:experiment:
%date 2020-10-19 22:21
= Spices =
1 cup gochugaru
1 half white onion
whole head of garlic
a chunk of ginger
2 Shallots, thinly sliced

View File

@ -0,0 +1,9 @@
%title Amazed at the NixOS Community
:writing:nix:micro:blog:
%date 2020-10-20 19:26
Even by FOSS zealot standards, I run an esoteric combination of hardware and software. My interests go beyond just "getting things done"; I have a strange fascination with tools themselves. I specifically choose tools I can customize to fit my hand like glove, and the FOSS world has plenty of choices for those so inclined.
This obsession with obscurity means I end up playing with software that looks like an ASCII video game, but is actually a [music tracker](orca), emulates [modular synthesizers](vcv-rack) or is a [DSL](domain specific language) in an already [esoteric programming language](haskell) for [livecoding](tidalcycles)
Even when it comes to hardware, I use a [phone](fx tec pro 1) you probably haven't heard of (it has a physical keyboard! in 2020!), and my [smartwatch](pebble time round) is literally no longer available for purchase, that I revived through a battery transplant.
And yet, the NixOS community has packages for all of these. There's a derivation of the Pebble SDK, TidalCycles and VCV-Rack. It's *awesome*. Even though they don't natively package all the vim plugins I'm using, I've gotten the hang of updating nixpkgs to include these plugins, and I've even made a couple PRs so they are available to the wider community! I didn't think the intersection between FOSS zealots who use NixOS, like livecoding or are die-hard Pebble fans would be greater than 1, but here I am😊

View File

@ -0,0 +1,6 @@
%title Somewhere at the end of History
:writing:story:
%date 2020-10-21 20:43
History was already over, but there aren't any endings. There never really were. Tomorrow always beckons, and things inevitably continue to happen. That's where I found myself. Just, happening at the end of history. With no reference to point to, I couldn't tell you what was different. Not even if I wanted to. Anyway, I'm sure you've done enough of this existing thing yourself to figure it out. Things were. How else do I describe it? Existence is. Even at the end of history. There isn't any other way to put it, not now, not before, and certainly not after. Look, look how our language became antiquated. Especially now it is illequiped to describe my time. For even though I can speak of before and now and after, there isn't really any. Distinction I mean. Now was now and will continue to be now, not before, not after.
And yet, if history is the chronicalling of time, haven't I just contributed a piece?

View File

@ -0,0 +1,321 @@
%title
%date 2020-10-21 21:02
= Generated Tags =
== jrnl ==
- [[201019-2345|4th October 2020 at 23:45]]
- [[201019-2325|30th July 2020 at 23:25]]
- [[201019-2250|20th August 2020 at 22:50]]
- [[201019-2246|10th August 2020 at 22:46]]
- [[201019-2240|22nd August 2020 at 22:40]]
- [[201019-2231|2nd September 2020 at 22:31]]
- [[201019-2220|22nd August 2020 at 22:20]]
- [[201019-2145|31st August 2020 at 21:45]]
- [[201019-1815|11th February 2020 at 18:15]]
- [[201019-1714|15th February 2020 at 17:14]]
- [[201019-1622|14th August 2020 at 16:22]]
- [[201019-1129|21st February 2020 at 11:29]]
- [[201019-0927|24th August 2020 at 09:27]]
- [[201019-0917|1st September 2020 at 09:17]]
- [[201019-0914|25th August 2020 at 09:14]]
- [[201019-0721|17th August 2020 at 07:21]]
- [[201019-0427|12th February 2020 at 04:27]]
- [[201019-0410|12th February 2020 at 04:10]]
- [[201019-0255|1st February 2020 at 02:55]]
- [[201019-0243|21st September 2020 at 02:43]]
- [[201019-0147|16th April 2020 at 01:47]]
- [[201019-0131|1st February 2020 at 01:31]]
- [[201019-0127|23rd February 2020 at 01:27]]
- [[201019-0029|19th September 2020 at 00:29]]
- [[201011-1612|11th October 2020 at 16:12]]
- [[201009-0117|10th October 2020 at 01:17]]
- [[201008-2335|8th October 2020 at 23:35]]
- [[201006-0038|7th October 2020 at 00:38]]
- [[201005-0102|6th October 2020 at 01:02]]
- [[200930-2329|30th September 2020 at 23:29]]
- [[200929-2258|29th September 2020 at 22:58]]
- [[200929-2250|29th September 2020 at 22:50]]
- [[200928-2136|28th September 2020 at 21:36]]
- [[200924-2227|24th September 2020 at 22:27]]
- [[200923-2310|23rd September 2020 at 23:10]]
- [[200922-2219|22nd September 2020 at 22:19]]
- [[200917-2335|17th September 2020 at 23:35]]
- [[200913-0101|14th September 2020 at 01:01]]
- [[200908-2350|8th September 2020 at 23:50]]
- [[200907-0000|8th September 2020 at 00:00]]
- [[200906-2220|6th September 2020 at 22:20]]
- [[200905-0142|6th September 2020 at 01:42]]
- [[200903-2306|3rd September 2020 at 23:06]]
- [[200829-2037|29th August 2020 at 20:37]]
- [[200827-2332|27th August 2020 at 23:32]]
- [[200826-2304|26th August 2020 at 23:04]]
- [[200823-2315|23rd August 2020 at 23:15]]
- [[200819-2322|19th August 2020 at 23:22]]
- [[200819-0818|20th August 2020 at 08:18]]
- [[200818-2215|18th August 2020 at 22:15]]
- [[200817-2249|17th August 2020 at 22:49]]
- [[200816-2036|16th August 2020 at 20:36]]
- [[200814-2009|14th August 2020 at 20:09]]
- [[200814-0054|15th August 2020 at 00:54]]
- [[200812-2118|12th August 2020 at 21:18]]
- [[200809-0011|10th August 2020 at 00:11]]
- [[200804-2319|4th August 2020 at 23:19]]
- [[200729-2255|29th July 2020 at 22:55]]
- [[200723-2257|23rd July 2020 at 22:57]]
- [[200720-0914|21st July 2020 at 09:14]]
- [[200713-2328|13th July 2020 at 23:28]]
- [[200706-2251|6th July 2020 at 22:51]]
- [[200703-0921|4th July 2020 at 09:21]]
- [[200624-2204|24th June 2020 at 22:04]]
- [[200622-2341|22nd June 2020 at 23:41]]
- [[200618-0029|19th June 2020 at 00:29]]
- [[200615-2355|15th June 2020 at 23:55]]
- [[200614-1451|14th June 2020 at 14:51]]
- [[200603-1542|3rd June 2020 at 15:42]]
- [[200531-1205|31st May 2020 at 12:05]]
- [[200516-0157|17th May 2020 at 01:57]]
- [[./jrnl/jrnl/200513-1945|13th May 2020 at 19:45]]
- [[200511-2204|11th May 2020 at 22:04]]
- [[200509-0222|10th May 2020 at 02:22]]
- [[200425-1347|25th April 2020 at 13:47]]
- [[200417-0139|18th April 2020 at 01:39]]
- [[200417-0135|18th April 2020 at 01:35]]
- [[200403-2210|3rd April 2020 at 22:10]]
- [[200326-1618|26th March 2020 at 16:18]]
- [[200301-2339|1st March 2020 at 23:39]]
- [[200301-0221|2nd March 2020 at 02:21]]
- [[200202-2315|2nd February 2020 at 23:15]]
- [[200130-2328|17th October 2019 at 23:28]]
- [[200130-2141|21st November 2019 at 21:41]]
- [[200130-2125|15th November 2019 at 21:25]]
- [[200130-0357|17th November 2019 at 03:57]]
- [[200130-0253|24th January 2020 at 02:53]]
- [[200130-0102|4th November 2019 at 01:02]]
- [[200113-0143|14th January 2020 at 01:43]]
- [[200102-1113|2nd January 2020 at 11:13]]
- [[191219-0256|20th December 2019 at 02:56]]
- [[191216-1009|17th December 2019 at 10:09]]
- [[191215-1112|16th December 2019 at 11:12]]
- [[191206-0512|7th December 2019 at 05:12]]
- [[191201-2240|1st December 2019 at 22:40]]
- [[191127-0010|28th November 2019 at 00:10]]
- [[191113-0226|14th November 2019 at 02:26]]
- [[191113-0222|14th November 2019 at 02:22]]
- [[191112-0548|13th November 2019 at 05:48]]
- [[191112-0258|13th November 2019 at 02:58]]
- [[191107-0315|8th November 2019 at 03:15]]
- [[191104-1930|4th November 2019 at 19:30]]
- [[191028-1746|28th October 2019 at 17:46]]
- [[191014-2327|14th October 2019 at 23:27]]
- [[191014-2316|14th October 2019 at 23:16]]
- [[191009-2333|5th August 2019 at 23:33]]
- [[191009-2250|29th September 2019 at 22:50]]
- [[191009-1837|29th August 2019 at 18:37]]
- [[191009-1832|13th September 2019 at 18:32]]
- [[191009-0630|12th September 2019 at 06:30]]
- [[191009-0055|5th August 2019 at 00:55]]
- [[191005-1700|5th October 2019 at 17:00]]
- [[190921-2130|21st September 2019 at 21:30]]
- [[190919-2223|19th September 2019 at 22:23]]
- [[190910-1839|10th September 2019 at 18:39]]
- [[190908-0036|9th September 2019 at 00:36]]
- [[190831-0004|1st September 2019 at 00:04]]
- [[190822-2302|22nd August 2019 at 23:02]]
- [[190822-2239|22nd August 2019 at 22:39]]
- [[190818-2234|18th August 2019 at 22:34]]
- [[190809-0143|10th August 2019 at 01:43]]
- [[190730-0021|31st July 2019 at 00:21]]
- [[190728-2311|28th July 2019 at 23:11]]
- [[190717-0138|18th July 2019 at 01:38]]
- [[190715-0447|16th July 2019 at 04:47]]
- [[190702-0158|30th June 2019 at 01:58]]
- [[190630-0607|1st July 2019 at 06:07]]
- [[190629-0813|30th June 2019 at 08:13]]
- [[190625-2318|25th June 2019 at 23:18]]
- [[190624-0020|25th June 2019 at 00:20]]
- [[190620-0145|21st June 2019 at 01:45]]
- [[190620-0124|21st June 2019 at 01:24]]
- [[190616-1624|16th June 2019 at 16:24]]
- [[190512-0309|13th May 2019 at 03:09]]
- [[190509-0219|10th May 2019 at 02:19]]
- [[190509-0101|10th May 2019 at 01:01]]
- [[190501-2337|1st May 2019 at 23:37]]
- [[190419-0416|20th April 2019 at 04:16]]
- [[190416-0019|17th April 2019 at 00:19]]
- [[190413-2101|13th April 2019 at 21:01]]
- [[190405-2235|5th April 2019 at 22:35]]
- [[190403-0454|4th April 2019 at 04:54]]
- [[190403-0443|4th April 2019 at 04:43]]
- [[190327-1835|14th February 2019 at 18:35]]
- [[190327-1354|19th February 2019 at 13:54]]
- [[190327-0818|11th February 2019 at 08:18]]
- [[190327-0734|22nd February 2019 at 07:34]]
- [[190327-0107|26th February 2019 at 01:07]]
- [[190325-0128|26th March 2019 at 01:28]]
- [[190320-0240|21st March 2019 at 02:40]]
- [[190320-0215|21st March 2019 at 02:15]]
- [[190316-1840|16th March 2019 at 18:40]]
- [[190306-1248|6th March 2019 at 12:48]]
- [[190302-0352|3rd March 2019 at 03:52]]
- [[190302-0151|3rd March 2019 at 01:51]]
- [[190129-2315|29th January 2019 at 23:15]]
- [[190129-0027|30th January 2019 at 00:27]]
- [[190124-2239|24th January 2019 at 22:39]]
- [[190123-1101|23rd January 2019 at 11:01]]
- [[190121-1650|21st January 2019 at 16:50]]
- [[190119-0449|20th January 2019 at 04:49]]
- [[190117-0115|18th January 2019 at 01:15]]
- [[190109-0321|10th January 2019 at 03:21]]
- [[190108-2332|9th December 2018 at 23:32]]
- [[190108-2228|8th January 2019 at 22:28]]
- [[190108-1803|8th January 2019 at 18:03]]
- [[190108-1500|14th December 2018 at 15:00]]
- [[190108-0804|9th January 2019 at 08:04]]
- [[190108-0459|10th December 2018 at 04:59]]
- [[190106-0018|7th January 2019 at 00:18]]
- [[190101-1639|1st January 2019 at 16:39]]
- [[190101-0301|2nd January 2019 at 03:01]]
- [[181231-2154|31st December 2018 at 21:54]]
- [[181229-2204|29th December 2018 at 22:04]]
- [[181226-2053|26th December 2018 at 20:53]]
- [[181220-1125|20th December 2018 at 11:25]]
- [[181219-1948|19th December 2018 at 19:48]]
- [[181217-0253|18th December 2018 at 02:53]]
- [[181212-0256|13th December 2018 at 02:56]]
- [[181210-0826|11th December 2018 at 08:26]]
- [[181130-2033|24th November 2018 at 20:33]]
- [[181130-1913|26th November 2018 at 19:13]]
- [[181130-1408|24th November 2018 at 14:08]]
- [[./jrnl/jrnl/181129-0042|30th November 2018 at 00:42]]
- [[181126-0714|27th November 2018 at 07:14]]
- [[181124-0413|24th November 2018 at 04:13]]
- [[./jrnl/jrnl/181123-1820|23rd November 2018 at 18:20]]
- [[./jrnl/jrnl/181122-0340|22nd November 2018 at 03:40]]
- [[181121-1445|21st November 2018 at 14:45]]
- [[181120-2109|14th November 2018 at 21:09]]
- [[181120-1651|16th November 2018 at 16:51]]
- [[./jrnl/jrnl/181120-1630|21st November 2018 at 16:30]]
- [[181120-0902|21st November 2018 at 09:02]]
- [[181120-0704|17th November 2018 at 07:04]]
- [[181120-0604|17st November 2018 at 06:04]]
- [[181120-0230|20th November 2018 at 02:30]]
- [[181119-0158|19th November 2018 at 01:58]]
- [[181116-0222|16th November 2018 at 02:22]]
- [[181114-0306|14th November 2018 at 03:06]]
- [[181112-1905|9th November 2018 at 19:05]]
- [[181112-1519|12th November 2018 at 15:19]]
- [[181112-0713|13th November 2018 at 07:13]]
- [[181109-1816|9th November 2018 at 18:16]]
- [[181106-1651|6th November 2018 at 16:51]]
- [[./jrnl/jrnl/181104-0044|5th November 2018 at 00:44]]
- [[181103-0458|4th November 2018 at 04:58]]
- [[181102-0251|3rd November 2018 at 02:51]]
- [[181102-0052|26th October 2018 at 00:52]]
- [[181031-2240|31st October 2018 at 22:40]]
- [[./jrnl/jrnl/181030-0015|31st October 2018 at 00:15]]
- [[181029-0228|30th October 2018 at 02:28]]
- [[181029-0038|30th October 2018 at 00:38]]
- [[181022-0400|23rd October 2018 at 04:00]]
- [[181015-2357|15th October 2018 at 23:57]]
- [[181014-0241|15th October 2018 at 02:41]]
- [[181013-0424|14th October 2018 at 04:24]]
- [[181012-1640|12th October 2018 at 16:40]]
- [[181012-0305|13th October 2018 at 03:05]]
- [[181004-1257|4th October 2018 at 12:57]]
- [[181003-1457|3rd October 2018 at 14:57]]
- [[181001-2206|1st October 2018 at 22:06]]
- [[180930-1215|30th September 2018 at 12:15]]
- [[180930-1202|30th September 2018 at 12:02]]
- [[180925-0755|26th September 2018 at 07:55]]
- [[180923-2255|23rd September 2018 at 22:55]]
- [[180919-1648|19th September 2018 at 16:48]]
- [[180917-2250|17th September 2018 at 22:50]]
- [[180917-2212|17th September 2018 at 22:12]]
- [[180916-2321|16th September 2018 at 23:21]]
- [[180913-0109|14th September 2018 at 01:09]]
- [[180908-0121|9th September 2018 at 01:21]]
- [[180903-1659|3rd September 2018 at 16:59]]
- [[180828-2324|28th August 2018 at 23:24]]
- [[180827-2346|27th August 2018 at 23:46]]
- [[180826-1014|26th August 2018 at 10:14]]
- [[180823-0808|24th August 2018 at 08:08]]
- [[180820-2311|20th August 2018 at 23:11]]
- [[180817-0247|27th July 2018 at 02:47]]
- [[180815-2139|15th August 2018 at 21:39]]
- [[180814-2307|14th August 2018 at 23:07]]
- [[180812-0002|13th August 2018 at 00:02]]
- [[180810-0122|11th August 2018 at 01:22]]
- [[180808-0036|9th August 2018 at 00:36]]
- [[180806-2200|6th August 2018 at 22:00]]
- [[180805-0030|6th August 2018 at 00:30]]
- [[180803-2131|3rd August 2018 at 21:31]]
- [[180730-2306|30th July 2018 at 23:06]]
- [[180724-2351|24th July 2018 at 23:51]]
- [[180716-2250|16th July 2018 at 22:50]]
- [[180710-0006|11th July 2018 at 00:06]]
- [[180708-0754|9th July 2018 at 07:54]]
- [[180705-2239|5th July 2018 at 22:39]]
- [[180705-0800|6th July 2018 at 08:00]]
- [[180704-0750|5th July 2018 at 07:50]]
- [[180703-2350|3rd July 2018 at 23:50]]
- [[180703-2341|3rd July 2018 at 23:41]]
- [[180702-1725|2nd July 2018 at 17:25]]
- [[180626-2318|26th June 2018 at 23:18]]
- [[180626-2255|26th June 2018 at 22:55]]
- [[180625-2344|25th June 2018 at 23:44]]
- [[180615-0212|16th June 2018 at 02:12]]
- [[180614-2324|14th June 2018 at 23:24]]
- [[180612-0317|13th June 2018 at 03:17]]
- [[180607-2345|7th June 2018 at 23:45]]
- [[180607-2338|7th June 2018 at 23:38]]
- [[180607-2323|7th June 2018 at 23:23]]
- [[180605-2156|5th June 2018 at 21:56]]
- [[180531-2233|31st May 2018 at 22:33]]
- [[180522-2356|22nd May 2018 at 23:56]]
- [[180522-2316|22nd May 2018 at 23:16]]
- [[180521-1704|21st May 2018 at 17:04]]
- [[180520-0040|21st May 2018 at 00:40]]
- [[180519-2327|19th May 2018 at 23:27]]
- [[180518-0123|19th May 2018 at 01:23]]
- [[180517-2224|17th May 2018 at 22:24]]
- [[180513-2304|13th May 2018 at 23:04]]
- [[./jrnl/jrnl/180510-1705|10th May 2018 at 17:05]]
- [[180510-1620|10th May 2018 at 16:20]]
- [[180509-1905|9th May 2018 at 19:05]]
- [[180508-1829|8th May 2018 at 18:29]]
- [[180507-1921|7th May 2018 at 19:21]]
- [[180506-1029|6th May 2018 at 10:29]]
- [[180504-2254|4th May 2018 at 22:54]]
- [[180502-2117|2nd May 2018 at 21:17]]
- [[180501-2314|1st May 2018 at 23:14]]
- [[180427-0021|28th April 2018 at 00:21]]
- [[180423-1911|23rd April 2018 at 19:11]]
- [[180423-0116|24th April 2018 at 01:16]]
- [[180417-2318|17th April 2018 at 23:18]]
- [[./jrnl/jrnl/180415-2239|15th April 2018 at 22:39]]
- [[180413-1928|13th April 2018 at 19:28]]
- [[180404-2128|4th April 2018 at 21:28]]
- [[180323-1509|23rd March 2018 at 15:09]]
- [[./jrnl/jrnl/180320-2334|20th March 2018 at 23:34]]
- [[180317-0444|18th March 2018 at 04:44]]
- [[180314-2231|14th March 2018 at 22:31]]
- [[180313-1931|13th March 2018 at 19:31]]
- [[180307-0001|8th March 2018 at 00:01]]
- [[180306-2251|6th March 2018 at 22:51]]
- [[./jrnl/jrnl/180305-2352|5th March 2018 at 23:52]]
- [[180228-1859|28th February 2018 at 18:59]]
- [[180227-2255|27th February 2018 at 22:55]]
- [[./jrnl/jrnl/180227-0927|28th February 2018 at 09:27]]
- [[180223-0924|24th February 2018 at 09:24]]
- [[180215-1819|15th February 2018 at 18:19]]
- [[180213-1418|13th February 2018 at 14:18]]
- [[180212-2321|12th February 2018 at 23:21]]
- [[180211-2315|11th February 2018 at 23:15]]
- [[180211-2312|11th February 2018 at 23:12]]
- [[180211-2227|11-February-2018 at 22:27]]
- [[180210-2350|10-February-2018 at 23:50]]
- [[./jrnl/jrnl/180210-2011|10-February-2018 at 20:11]]
- [[180210- 2018|10th February 2018]]

View File

@ -0,0 +1,6 @@
%title Why Kendrit
:writing:kendrit:
%date 2020-10-21 22:33
I bounce from project to project so much because there is a lot I want to do. This often leads to thrashing and not actually doing anything. So in order to Get Things Done™ I needed a way to focus on larger goals over longer periods of time. Hence Kendrit, literally translated as "To Center".

View File

@ -0,0 +1,24 @@
%title readImap dvlg
:dvlg:dev:readImap:kendrit:puralek:
%date 2020-10-25 23:52
= tasks | pro:readImap =
* [X] finish read-imap in spellbook #b4a148e7
* [X] parse email msgs #0e629167
* [X] import writing into kitaab #ea0f2f4d
= done =
download emails using `email` and `imaplib` in python
save to out file using `email.generator.Generator(fp)`
can read file through emails through `email.parser.Parser(fp)`
= parsing =
`for part in msg.walk():`
` r = str(part.get_payload(decode=True))`
= todo =
- avoid bytes and empty parts
- differentiate between links and passages/comments
- read tags from identified link blocks
- average links per day
- most common tag

View File

@ -0,0 +1,13 @@
%title Systems, not Goals
:writing:phil:way:
%date 2020-10-31 00:42
One of the founding principles by which I organize my life (at least rn). It's not a difficult concept. Implementing it is always personal though. Everybody has their own desired consequences that they solve in their own ways. It's part of what makes people beautiful.
What I mean by this is primarily that goals are ephmeral. Once achieved they vanish, as though that is the end of the problem, or action, or even outcome. The heroes journey is always cyclical. There are no level ups in real life, you continue with the tools you've delevoped. So build tools.
Architect systems of processes such that you can achieve your "goals" reliably, consistently. If a goal is of any value, in most cases it is worth repeating; better. So don't worry about how far you've come, just keep journey-ing. Embrace your ability to instantiate change. Create! Destroy! You are the opponent of Entropy! You cannot win, but at least enjoy the battle.
You get the idea.
"What is the purpose of dance?" - Alan Watts

View File

@ -0,0 +1,5 @@
%title Kitaab integration with Task Warrior
:dev:meta:kitaab:taskwiki:python:
%date 2020-10-31 01:14
Link text to Task warrior tasks in Kitaab. Maybe there is a description element for tasks in the wiki, or perhaps write a way to refer to specific tasks in [[Kitaab]].

View File

@ -0,0 +1,15 @@
%title kendrit-ops
:kendrit:ops:
%date 2020-11-03 21:09
New Kendrit, hopefully this one goes better.
Intimately related to the previous Kendrit, but not quite so focused on HPI as general ops regarding my infrastructure as it seems to have been falling down a lot lately.
Trying to have fewer tasks that are more important.
= Goals =
- Get nixOS on [[bowl]]
- Weekly and Monthly backups of [[bowl]]
- using Borg and Blackblaze
- Wiregaurd installation on [[helix]] to access [[bowl]] from anywhere
- Update keyboard keymap

View File

@ -0,0 +1,6 @@
%title On Noticing Your Own Reactions
:writing:phil:
%date 2020-11-05 19:33
By paying attention to how you feel, one begins to learn many things. One of these is the distinction between like and dislike. One can learn valuable information about oneself by noticing when we like and dislike things. This too is a spectrum, but nonethelss it can be distinguished at ends. Like and dislike. We learn to do more of what we enjoyed, obviously. We also learn an important lesson from what we dislike. We shouldn't learn the opposite lesson though: To turn away and do less of what we don't like. Instead, our goal should be to understand why. What part of ourselves are we afraid of that we experience fear of experiences. Instead we should seek to understand our discomfort and engage with it. Learn from it. That cannot happen if it is discarded. So look at it, don't through away your own reactions. Even if it is a bad reaction. Seek to introduce it into your life in the smallest manner you can handle. And work from there.
Heavy storms make deep roots.

View File

@ -0,0 +1,15 @@
%title The New Internet is being born
:blog:web:notes:
%date 2020-11-05 19:45
I've read many articles about the Old Internet being dead (those that write those articles seem implicitly aware that the "Now Internet" sucks)
I have a different take. The New Internet is taking root. If you know where to look you can smell the trees.
Something similar is the "Cozy Web". You probably have carved out your own cozy web too. "Private" groups filled with your friends. Things that you share with select group(s) and (generally) the corporations that provide that service. Messenger, Telegram, Slack, Discord, $X DMs, Snapchat, Zoom. Maybe you're down with technology or blessed by the Priesthood of Programmers and know someone that runs their own infrastructure, which is certainly much comfier as far as I'm concerned. Whatever it may be, the important factor in the Cozy web is that it's private.
The New Internet must happen in public by definition. It's already taking shape. Digital Gardens or Online Personal Notebooks. Some small blogs. IndieWeb. There's (generally) nothing to sell, no obligation to buy. They are welcoming spaces filled with personal expression. Many are just electronic Business Cards, some are dense tome's of intently researched knowledge. Some are Parks and some are Libraries. There are still certainly stalls and small businesses too. But there's no Amazon. No endless trackers. No enmourous data centres. Well, at least in my dreams
The tools obviously still need work. Creating and designing a website is not an easy task. Ensuring that it stays running is an ongoing obligation. Most people still don't know about `hyper://`, `ipfs://`, or `gemini://` hell Google is getting rid of `http://`! Yet even the alternatives have requirements beyond simply knowing them. Technical skills to use them, resources to have a constantly running computer, dedicated internet and electricity. So even if you can build websites, why would you choose this unknown alternative with all these related problems when you can just pay someone to deal with it.
But it is possible. Community oriented services. Public and Personal spaces wrapped in one. I'm trying to build my own Public Personal space here too. Working with the garage door up.

View File

@ -0,0 +1,12 @@
%title Desk Companion
:hardware:craft:
%date 2020-11-05 20:43
I want a little desk companion out of my RPi 0. It needs a (e-ink) screen, some batteries, and a (hand crafted) wooden holder.
I'm not sure what to make it display
= Ideas =
- Weather Calendar Tasks (Dashboard)
- Different plants and their information
- Tamogatchi
- Pomodoro Timer

View File

@ -0,0 +1,9 @@
%title Borg instructions
:tools:cli:
%date 2020-11-05 21:04
= Install & Quick Start =
`pip3 install borgbackup`
`borg init -e=none /path/to/repo`
`borg create /path/to/repo::Wallabag /var/lib/docker/volumes/x/data`

View File

@ -0,0 +1,11 @@
%title Wallabag Backup
:puralek:cli:sql:backup:
%date 2020-11-05 23:06
Had to enter the docker container
Go to a reasonable place in the filesystem
Run
`psql -U postrges -l`
`pg_dump -U postgres $database > outfile`
Then copy out of docker
`sudo docker cp wallabag-db:/$database wallabag`

View File

@ -0,0 +1,5 @@
%title Docker cp
:docker:cli:snip:
%date 2020-11-05 23:09
`docker cp <CONTAINER>:<SRC> <DEST>`

View File

@ -0,0 +1,5 @@
%title vim zettel Question
:idea:dev:vim:contribution:question:
%date 2020-11-05 23:16
How to go back to previous note after ZettelNew?

View File

@ -0,0 +1,10 @@
%title Nextcloud Backup
:cli:backup:
%date 2020-11-05 23:21
Because I'm running a snap I can do:
`sudo snap stop nextcloud`
`sudo cp /var/lib/snap/.. ./`
But because I'm paranoid I also did:
`sudo nextcloud.export`
`sudo cp /var/lib/snap/common/export/* ./`

View File

@ -0,0 +1,6 @@
%title vim zettel last 5 edited
:idea:contribution:vim:dev:
%date 2020-11-05 23:38
"Search" and insert the last X edited files.
Because when I'm doing things I create an atomic note for each, but I want to be able to link them later.

View File

@ -0,0 +1,11 @@
%title 3 Years of Owning a Server
:blog:writing:web:
%date 2020-11-06 02:58
Once I'd built my first computer (which was actually very late, perhaps sometime in 2016) I needed to figure out what to do with my old one. My old one was a mid-spec laptop from 4+ years prior to that, but it had a decent graphics card at the time that allowed me to play some of the games I'd wanted to -- Though in part the small specs lead me to prefer indie games and roguelikes, the only games I'm even remotely interested anymore.
I figured I'd try and configure it to run as a server. By this point I'd been running exclusively Linux for a couple years and had come across interesting server software. Perenially interested in Privacy and Free Software, I decided to see what I could muster up.
Thus began my on-going experiment with Docker. At the time I knew just enough system adiminstration to be dangerous and hadn't previously set up nginx. Since Docker seemed a lot easier, that's what I went with.
The docker instances I stood up then are the very same images that have been running on my server this entire time, I'm a little ashamed to admit. They're horrible out of date, and basically the only sort of server admin work I did was write scripts so they boot on startup and kick them when they fell down. Being the only one who used this software made that a totally fine solution for me.
Now, I'm trying to level up once again. I've learnt a lot more about server administration, and I'm trying to achieve [[201015-2313|Invincible Computing]]. The sad part is what stirred me to finally commit to doing this whole process (Backup, Automation and Reliable builds) is *losing* all the data that I had stored in my bookmarks server since it's inception. That place was a comfy little treasure trove for me I could turn to when I finally needed a tool, book or guide in order to accomplish something. It was a personally curated springboard from which whenever I had an idea, I knew where I should go. It was, in some senses, my Google. Rather than search for something through the public search indexes, I would always choose to search this first.
And now it's gone. And I never want to let that happen again. So here I am in the dead of night checking all my backups before wiping this ancient machine to imbue it with new life and new power.
I hope I don't lose any more data, ever. It's a small step for me, in removing a thorn that has been deeply embedded in my technical prowess. [[201106-0311|Controlled Difficulty]] and all.

View File

@ -0,0 +1,5 @@
%title Controlled Difficulty
:phil:advice:
%date 2020-11-06 03:11
Growth requires difficulty. Induce it in your life, in whatever portion you can sustain in order to learn and grow from the experience

View File

@ -0,0 +1,9 @@
%title bowl dying
:ops:bowl:hardware:
%date 2020-11-08 02:05
[[bowl]] is certainly nearing teh end of it's life. It has served me well. I will need to replace it imminently.
I feel so much weaker without it. I need it back now. Currently it will only boot after waiting for around 10 minutes (HDD failure?) and even then the nix installer was flashing error messages (I know the installer works because I booted on a seperate laptop)
Luckily I have all my data backed up. I was going to wipe it anyway. maybe look into getting a replacement drive to boot off of while I think of what to do in terms of building out a NAS.

View File

@ -0,0 +1,4 @@
%title
:bowl:ops:nix:
%date 2020-11-18 15:20

View File

@ -0,0 +1,36 @@
%title Getting Web-Services to run on NixOS
:ops:bowl:nix:reflection:
%date 2020-11-18 15:22
= Summary =
Shaarli
- Haven't configured a systemd service to ln -s the nix derivation yet
Wallabag
- Upstream seems broken
- Docker works, but data is not persistent
- Find a way to use overlay so I can use an older version
Wireguard
- broken on 20.09
- not sure what to do
LUKS / LVM
- does not mount the big partition
- not sure why
Borg
- Unconfigured
- Need to restore nextcloud data
- Most other data is missing
Basically I've learnt that running php web-apps are a nightmare, and that I don't really understand nginx, fastcgi, phpfpm at all really.
For the past ~2 weeks I've been trying to rebuild [[bowl]] to be running on NixOS, and I've come up against many difficulties, and lost all the data in both of these services...
I had issues with getting shaarli to read the environment variable as defined in it's nix derivation. So instead, Timo (the package maintainer) told me another solution is to just `ln -s` the package directory into somewhere it can read/write to since that's what the environment variable is supposed to do anyway. Once I did this it was easy enough to get Shaarli running. I did have to be careful with the nginx config because I'd accidentally disabled the API. Currently my Shaarli install
Wallabag has been another story. It seems like upstream is broken because it's overwriting a php function (`mb_string` is the package and `mb_str_replace` is the function) that php says it can't overwrite.
Before I managed to get these to run on bare metal, I was using docker once again to run the services. But since Nix is declarative, and I have no idea how docker volumes work, it wiped everytime I ran `nixos-rebuild switch`, which remains a problem I haven't quite solved. I somehow managed to get the docker install working, but I don't believe it to be declarative because I did exec into the docker container and ran some esoteric database migration in order to get it to work.
Further more my main issue currently is that in order to do anything in nixOS I need to be able to write the language, understand the options, and then all the services that the options declaratively define. The way I currently run any of the infrastructure is through googling around and hoping to find a module or someone else trying to run the same software, but more profficient at nixOS than I am. That needs to change, since even for services written in easy to run languages like Go, I can't write the nix file to get them to work.

View File

@ -0,0 +1,24 @@
%title Ops tasks for bowl
:bowl:nix:ops:
%date 2020-11-19 11:57
= bowl =
- wireguard
try and install latest linux kernel without rebooting, and then include wireguard.nix
- wallabag
overlay the pkg to include the patch that deals with mb_str_replace
- shaarli
hack the system to set password
- nextcloud
move dataDir to /data and import backup
- navidrome
change dataDir to data, copy over music, grant permissions
- run headphones, beats, and see if you can get huginn configured to connect to [[bowl]]
- run fava+beancount or alternative
- run grasp server?
- maybe setup telegraf agent?

View File

@ -0,0 +1,9 @@
%title Shaarli Setup
:ops:nix:bowl:
%date 2020-11-21 14:17
So I finally got Shaarli all configured. It turns out the `Network Redirection Error` that I was facing had to do with `nginx` Server Blocks aka Virtual Hosts
Setting the port and IP address as the virtual host name during Shaarli setup led to some strange re-direction that neither FF nor Chrome were happy to display (though cURL didn't have any issues). I fixed this by disabling nextcloud which previously owned the non-port server host and made shaarli the only web-app running. This led to the redirect working fine and able to continue as normal.
The setup still isn't quite reproducible because I need to do `ln -s $(nix eval nixos.shaarli.outPath)/* $dataDir` to place all the shaarli files in the dataDir, then `chown shaarli:shaarli $dataDir` and finally `cp config.php $dataDir/config.php` to get everything running.
I had much more sucess with debugging after setting `php_admin_value[error_log] = "/var/log/nginx/phpfpm.log"` and using `strace -p <phpfpm-pid>` so that I actually knew what was going wrong. I learnt that when using `root = pkgs.shaarli` and setting `SHAARLI_CONFIG` even though shaarli does read the right config file, it doesn't seem to apply that to reading the data directory as defined by the config and was still trying to access the nix store data folder which was causing issues.
Anyways I think I now know enough that I should be able to re-configure everything pretty easily if it breaks. So Success!!

View File

@ -0,0 +1,3 @@
%title
%date 2020-11-22 21:22

View File

@ -0,0 +1,3 @@
%title
%date 2020-11-22 21:23

View File

@ -0,0 +1,9 @@
%title Chords
:music:generative:theory:
%date 2020-11-22 21:42
The reason we care about the `degree` of a note in the scale, is because we can use it to talk about different kinds of chords in a sequence
For the each key we can talk about it's chords. A good way to think about some songs, is major chords numbered by degree of the note. That way we can talk about the same chord progression in different keys.
hence, chord progressions can be written as numbers 1 - 6
A chord progression and key unlocks your capacity to see the music matrix

View File

@ -0,0 +1,13 @@
%title Dev Stories
:writing:blog:dstory:
%date 2020-11-28 13:01
In the interest of sharing [[Kitaab]] online I wanted to include more written explanations of my understanding. My idea is to write stories to accompany what I did, in the interest of solidifying my own understanding.
= ideas =
[[201128-1333a|Getting to a Finished Song]]
Understanding Generative
[[201128-1456|Building Norns]]
NixOS & the Responsibility of Power
[[mossnet]]
[[sealight.xyz]]

View File

@ -0,0 +1,6 @@
%title Box Upgrade
:rock:box:
%date 2020-11-28 13:26
I want to turn box into a music machine. Run SuperCollider + Tidal, Ardour + Synths, VCV-Rack and route things all around. I need a microphone to record things, an audio interface to work with and a powerful enough system to pull it all together.
[[box]]

View File

@ -0,0 +1,3 @@
%title
%date 2020-11-28 13:33

View File

@ -0,0 +1,15 @@
%title Getting to a Finished Song
:dstory:music:generative:writing:
%date 2020-11-28 13:33
I've learnt a few ways to make digital music now, but I haven't actually *Finished* a Song. All I have is ways to make noise. In order to record a song I need a good microphone.
I can create sounds in TidalCycles, VCV Rack, lsdj, and nanoloop. Soon I'll also have a norns too.
I need learn how to mix and produce a finished track through something like ardour or reaper.
I've been able to install some synths (helm) and route those to Ardour.
I need to learn how to create midi notes that are played through that synth
I've configured patchage to route midi to various applications and been able to control VCV Rack and Helm through midi
I need to learn how to use a sequencer effectively
I need to learn to use synths to create the sounds I want and turn those sounds into loops and those loops into tracks and those tracks into songs
I can see a path to through the tunnel

View File

@ -0,0 +1,7 @@
%title Building Norns
:dstory:writing:generative:hardware:
%date 2020-11-28 14:56
Early on in my foray into digital music, I decided I didn't want to use a DAW. Partially because I knew doing so on Linux would be limiting, partly because I like to do things differently. My proclivity for single purpose devices naturally got me excited about norns when I heard about it. Not being a musicion I found it hard to justify paying $800USD for what could turn out to be just a toy.
When I learnt about the DIY versioun pased on an RPi, I knew I had to try it. A toy like the norns is certainly worth a hundredish dollars. Even more exciting to go from "no electronics experience" to "i built a music machine from PCB up".
So I'm now that guy. Decided to learn how to read electronics schematics so that I can build a linux machine to avoid using a DAW on a different Linux machine.

View File

@ -0,0 +1,37 @@
%title Getting Matrix Online
:sealight:ops:nix:dstory:
%date 2020-11-29 20:55
Finally taking steps in almost exactly 1 year since taking up the mantle of friend-hosting (https://anish.lakhwara.com/posts/fireplace/) and I finally have a runnig matrix server that I plan to keep in production as much as I can. I worked out how to configure everything I wanted correctly by using these resources:
- https://www.foxypossibilities.com/2018/02/04/running-matrix-synapse-on-nixos/
- https://kaushikc.org/posts/matrix-jitsi-nixos.html
- https://nixos.wiki/wiki/Matrix
= It's Always DNS =
I had two significantly large hurdles; DNS, NixOS + ACME. I started with an SRV Record to redirect all requests to chat.sealight.xyz if they were trying to reach that instance. But I couldn't quite get this to work right, and then ending up switching to an imperative step which was:
`echo '{ "m.server": "chat.sealight.xyz:443" }' > /<webroot>/.well-known/matrix/server`
Which removed the need for the SRV file. At this point I had a working SSL installation of NixOS 19.09 with only a synapse server running. Great first step I thought.
= Or SSL for DNS =
Then I had the bright idea to update to 20.09 so that I could run the Element web client instead of Riot (now rebranded). That was naive in hindsight. `ACME`, it's [[nixOS]] module and even perhaps the underlying software `logo` may have bugs that made their way into 20.09 and these bugs occur specifically when upgrading from the older ACME client. In order to fix this I had to delete the old user account and started fresh.
It didn't help that I would often run into Rate Limiting due to the way the nixOS ACME module works. I had to be particularly careful when running a rebuild otherwise I'd hit the rate limit. This meant I couldn't just try random fixes and hope it worked. I really had to read the logs, come to understand what was happening and why (and in case it was a rate limit just wait 1 - 3 hours before doing anything). This was a useful experience.
These resources were especially helpful in debugging ACME issues:
- https://discourse.nixos.org/t/lets-encrypt-on-20-09/9950
- https://github.com/NixOS/nixpkgs/pull/91121
- https://github.com/go-acme/lego/issues/1006
= Finally =
Once I fixed the Let's Encrypt requests being sent, I was left with a beautiful static site hosted at sealight.xyz, the matrix server that federates at chat.sealight.xyz; with all handles will be of the form @user:sealight.xyz, and an Element client running at element.sealight.xyz that points users to create an account at my instance by default.
If I'm being honest I still don't understand all the intracacies of my own configuration. NixOS does an excellent job of abstracting away so much of the configuration troubles. I'm finally beginning to understand how to do things with this tool.
However it cannot abstract away everything. I need to learn nginx configuration, and what the hell SNI, SRV and .well-known have in common that makes them able to mask the URL in handles.
= Next =
I need to configure monitoring agents and plan to go with the TIG Stack
Install the Slack Bridge to help my friends migrate
Install the Telegram / Discord bridge to consolidate my online profile

View File

@ -0,0 +1,5 @@
%title Taming Technology
:writing:blog:
%date 2020-05-13 21:50
there has been a common thread going through my mind of late that ive been meaning to write about for a while. originally i started with the idea of describing my own utilization of technology. the systems i\\'ve set up to orchestrate my life; a tour of my personal digital infrastructure. and of course being a hipster computer nerd, the manner in which i use technology is partically fringe even within my own community, and especially so when compared to the average comput er user, but other than being at best mildly informative, i came to view it as self indulgent naval gazing -- afterall I already k now how that infrastructure works and have laid out many plans for how to improve it, surely my time would be better spent activel y improving it rather than explaining it (largely just to myself) again.", "then i moved on to pondering my grand debut in \"the i ndustry\" and wanted to get my thoughts in order about how I actually feel about it. this scared me because I worried my honest op inions of the surveillance industry (or \"silicon valley\" as it is colloquially referred to) would stain my chances at a job in t he very same place. i wish i was strong enough in my resolve to my ethical framework to make these comments under my \"real\" iden tity and maybe one day i will be, but today is not that day.", "from there i bounced to various cliche topics at the intersection of technology and mindfulness. digital detoxes, curtailing addicition to our smart phones, an introduction for the non-technical, how tragically easy it is to imagine better technology, media diets, and the murder (not death) of privacy and how to ressurect it all feature empty pages in my git repo. beyond repeating kitchsy blogspam my trouble with writing about these is that the problem s and solutions i see to technology go beyond any one of these issues, and even describing these issues evades a clear essence to what technology truly is.", "and so i embark on another rabit hole, but this time i emplore you to join in on the discussion.

View File

@ -0,0 +1,23 @@
%title Refusing Rating
:writing:blog:phil:web:
%date 2020-12-13 16:41
I won't like, subscribe, comment, hit the bell icon, give 5 stars, a thumbs up, or other form of feedback. I'm sorry, I know it's helpful for your platform on <corp>. Even if I liked whatever service or content you provided, I (probably) still won't do it. I won't feed the <corp> data machine. It does not need more data. The aggregate effects of better calibrated surveillance apparatus are just worse for everyone. It will only grant the entrenched system more power. Metrics cease to be useful when they become goals, and <corp> doesn't know what else to do with metrics.
Living in the modern world requires compromises, which is why I am using the platform (and have the ability to leave a signal in the first place), but I see minimizing participation as beneficial. <corp> will still collect some unavoidable data from my interactions with them, and use this data for whatever they see fit. <corp> may also already have all your past data, but that doesn't justify handing over a continuous feed. Stop using the gambler's fallacy in regards to data privacy.
- Not drip feeds of ego-boosting like notifications.
- Not gated communities built out of follower counts and verified check marks.
- Not laser focused optimization of product ranking, and user {att,re}tention
I won't engage in these.
Instead, where appropriate I will engage in:
- Personal recounts of similar experiences
- Asking or answering questions and learning more
- Expressing appreciation explicitly
- Constructive criticism without being mean
- Ambient support
You want signals? Make them humane, understand the context. Leave messages of collaboration. Refuse parasocial relationships. Make the data open, playful, and in service of the people to which that data belongs. Technology alone won't solve social problems, and in many cases will exacerbate them. Metrics are for systems not people. Reactions aren't signs of support. I will try to minimize the power these signals possess.

View File

@ -0,0 +1,7 @@
%title random subtitle
:dev:blog:idea:
%date 2020-12-15 13:08
make 2 or 4 lists of adjective + nouns to describe myself and put asthe subtitle to my blog, selected randomly from each list updated once a day
[[210124-0033|The List]]

View File

@ -0,0 +1,9 @@
%title Brighter futures series II
:story:writing:blog:
%date 2020-12-15 13:10
The bright orange sun had become a familiar but iritable compainion along my quest. a node under my network had failed and unfortunately the redundancy hadnt planned for this. I hadnt planned for this. The inscriptions in the stone shouldnt he allowed this to happen
= idea =
the imagining better future series is about a (female) solarpunk adventurer, told in the form of diary notes. she quests around byboat or by bike and lives a nomadic life. its post-walkway, default still exists (and should reflect current civ-tech) but is unbearable to her. she meets with other walkaways learning, sharing and creating art. its a loose plot for slow life, and the kind i wish one day to lead.

View File

@ -0,0 +1,3 @@
%title
%date 2020-12-18 15:05

View File

@ -0,0 +1,30 @@
%title Vegan Chilli
:recipe:vegan:
%date 2020-12-19 18:25
= Ingredients =
- 2 tablespoons extra-virgin olive oil
- 1 medium red onion, chopped
- 1 large red bell pepper, chopped
- 2 medium carrots, chopped
- 2 ribs celery, chopped
- ½ teaspoon salt, divided
- 4 cloves garlic, pressed or minced
- 2 tablespoons chili powder*
- 2 teaspoons ground cumin
- 1 ½ teaspoons smoked paprika*
- 1 teaspoon dried oregano
- 1 large can (28 ounces) or 2 small cans (15 ounces each) diced tomatoes**, with their juices
- 2 cans (15 ounces each) black beans, rinsed and drained
- 1 can (15 ounces) pinto beans, rinsed and drained
- 2 cups vegetable broth or water
- 1 bay leaf
- 2 tablespoons chopped fresh cilantro, plus more for garnishing
- 1 to 2 teaspoons sherry vinegar or red wine vinegar or lime juice, to taste
= Instructions =
- In a large Dutch oven or heavy-bottomed pot over medium heat, warm the olive oil until shimmering. Add the chopped onion, bell pepper, carrot, celery and ¼ teaspoon of the salt. Stir to combine and cook, stirring occasionally, until the vegetables are tender and the onion is translucent, about 7 to 10 minutes.
- Add the garlic, chili powder, cumin, smoked paprika and oregano. Cook until fragrant while stirring constantly, about 1 minute.
- Add the diced tomatoes and their juices, the drained black beans and pinto beans, vegetable broth and bay leaf. Stir to combine and let the mixture come to a simmer. Continue cooking, stirring occasionally and reducing heat as necessary to maintain a gentle simmer, for 30 minutes.
- Remove the chili from the heat and discard the bay leaf. For the best texture and flavor, transfer 1 ½ cups of the chili to a blender, making sure to get some of the liquid portion. Securely fasten the lid and blend until smooth (watch out for hot steam), then pour the blended mixture back into the pot. (Or, you can blend the chili briefly with an immersion blender, or mash the chili with a potato masher until it reaches a thicker, more chili-like consistency.)
- Add the chopped cilantro, stir to combine, and then mix in the vinegar, to taste. Add salt to taste, too—I added ¼ teaspoon more at this point. Divide the mixture into individual bowls and serve with garnishes of your choice. This chili will keep well in the refrigerator for about 4 days or you can freeze it for longer-term storage.

View File

@ -0,0 +1,3 @@
%title
%date 2020-12-19 18:39

View File

@ -0,0 +1,7 @@
%title What history got wrong about the future
:story:writing:
%date 2020-12-23 01:01
Our history could only ever a fractured reflection of the time. To learn how those who lived it imagined the time after they would be gone crystallized their hopes, or fears. Our writing of imaginative futures that did not come to pass are filled with our species venturing out into the unknown, guided by belief in curiosity and justice. Cooperation on the galactic scale.
I imagine they'd be disappointed to learn that such scale was never achieved. Sure, those who desired got to venture out and explore the unknown. Generally in teams the size of whatever ship they could put together. Some even summoned worm-holes to other habitable planets for easy access, but there are no star fleets exploring the unknowns of space. We eventually learnt enough to prove that we are alone. The Fermi Paradox wasn't a paradox afterall, just an observation.

View File

@ -0,0 +1,32 @@
%title things for nye
%date 2020-12-29 10:53
toothbrush
toothpaste
mouthwash
beard oil
towel
casey ▟▞▞▒
my ▚▕▓▒
papers
juice
tabs
batteries
pebble charger
phone charger
work laptop
work laptop charger
3 shirt
2 short
1 pant
toggs
sandals, no shoes
===
▓▟▔▟░▘▙▓▜▜▘▙▓▖▗
beer in the fridge
battery charger

View File

@ -0,0 +1,3 @@
1. be more decisive
2. stand your ground
3. be honest even if it hurts

View File

@ -0,0 +1,6 @@
%title Training Mode
:writing:way:climb:
%date 2020-11-06 15:40
Mike taught me about training mode
Always think of your climbs as practice, then you will be deliberate with them. Your ambition should be to turn the currently impossible into routine.

View File

@ -0,0 +1,9 @@
%title Hardware Projects
:hardware:list:
%date 2021-01-02 22:23
- pi hole #fd42bdb6
- kobo hardware page turner
- mycroft ai
- pi0 project -> [[201105-2043|Desk Companion]]
- LED alerter

View File

@ -0,0 +1,12 @@
%title Matrix Bridges
:ops:nix:sealight:
%date 2021-01-03 23:19
running Matrix Bridges is generally a 3 step process:
- create a bot
- run the appservice so that it can be registered with the bot
- tell synapse of the bot's existence
step 2 is where nixOS comes in, if there is a module configured for the service it's not necessary to go through the configuration steps and instead write something like `services.matrix-appservice-discord.enable = true;` in `configuration.nix`
I don't yet know what to do in nixOS specifically if there is no module (write one, lol)

Some files were not shown because too many files have changed in this diff Show More