diff --git a/html/about.html b/html/about.html index b9c2634..98c6f5a 100644 --- a/html/about.html +++ b/html/about.html @@ -1,7 +1,7 @@ - + About @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -203,22 +203,23 @@

-it’s me ehehe -#chuu -dfdfd +chuuu +

+ +

+fdsfsdf

- - + \ No newline at end of file diff --git a/html/blogroll.html b/html/blogroll.html index e29912d..2749988 100644 --- a/html/blogroll.html +++ b/html/blogroll.html @@ -1,7 +1,7 @@ - + Blogroll @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -202,21 +202,17 @@
-

-last modified: 2022-03-21 -

- - + \ No newline at end of file diff --git a/html/experiments.html b/html/experiments.html index 8f9f57e..8e414ea 100644 --- a/html/experiments.html +++ b/html/experiments.html @@ -1,7 +1,7 @@ - + Experiments @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -208,16 +208,15 @@
- - + \ No newline at end of file diff --git a/html/index.html b/html/index.html index 97dd0ef..24c9e8e 100644 --- a/html/index.html +++ b/html/index.html @@ -1,7 +1,7 @@ - + Index @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -207,16 +207,15 @@ Welcome to my website! I’m Akko. I’m curr

- - + \ No newline at end of file diff --git a/html/posts/blog-tech.html b/html/posts/blog-tech.html index 191ed69..196599f 100644 --- a/html/posts/blog-tech.html +++ b/html/posts/blog-tech.html @@ -1,7 +1,7 @@ - + How this blog is built @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -203,31 +203,25 @@
-
-

Blog Tech

-
-
-
-

chuu

-
-

-last modified: 2022-04-18 -

+
+

Blog Tech

+
+
+

chuu

- - + \ No newline at end of file diff --git a/html/posts/dairy/week-3-2023.html b/html/posts/dairy/week-3-2023.html new file mode 100644 index 0000000..39839c7 --- /dev/null +++ b/html/posts/dairy/week-3-2023.html @@ -0,0 +1,402 @@ + + + + + + +Week 3, 2023, "Week of Systems" report + + + + + +
+ +
+
+ +
+

Week 3, 2023, “Week of Systems” report

+
+
+
+

Introduction

+
+

+Last week I worked on the issue of “life systems”, by which I mean systems such as to-do lists, good habits such as exercise, schedules, plans, that sort of thing. At various times in the past I’ve had various such systems, some working better than others. I used to make a list of the day’s goals every morning and cross them off throughout the day. I also keep a file called life.org where I keep track of to-dos and leads to look into at a later point and such. Other things I would consider “sytems” include my daily meditation practice and various attempts at regular exercise I’ve made in the past. +

+ +

+Keeping systems is hard because life is messy. Whole-life systems as these are truly all-encompassing, and thus they interact with all of life’s complexity. The Planning Fallacy turns any attempts at tying to-do lists and intentions to timespans and deadlines into an uphill battle. Changing your habits is famously hard. Unexpected things will happen with certainty; priorities change, capabilities fluctuate, problems spring up and solve themselves. +

+
+
+ +
+

Desirable Traits

+
+

+The primary issue with life systems is therefore the overhead, the burden of maintenance, the stress. Rather than simplifying life, it is easy to add an administrative burden. In light of this, I’ve isolated the following properties that I think a good system should have: +

+
    +
  • Simplicity. The overall system can not contain too many moving parts. In order to be simple to apply, it needs to be simple to explain; in order to be simple to explain, it needs to be simple.
    • +
  • Smooth scaling. As life’s difficulties and my capacity to handle them fluctuate, the systems of my life need to be able to scale smoothly up and down. During tough times I need to be able to simplify my life to the most important parts; during better times I should be able to smoothly pick the rest back up where I left it. Implicit in this is also a hierarchy of priority, an order in which I drop things, a notion of what is least worthwhile at any given time.
    • +
  • Malleability. As both my life and my understanding of it are liable to change, my systems need to be able to adapt with minimal burden. Because of this there ought to be few strict schemas; for, if the schema has to change, all data already within that scheme would have to be migrated.
    • +
  • Evaluation. There needs to be some measure of how well things are going, in order to catch problems early and prevent catastrophic failure, and furthermore to optimize the system. Other constraints enforce simplicity here; a system of regular deadlines, for instance, would be too inflexible.
    • +
+
+
+ +
+

Specifics and the Problem of Ends

+
+

+The above is about as far as I got in terms of definitives. I did not start there; I started at neither the level of specifics nor of generalities, but in between, dealing with things such as “managing stress” and “measurability” and “dimensions of personal development”. At this level, however, it was far easier to write things down than to strike them through; easier to complicate than simplify, and I ended up with a basket of disjointed ideas, aims and cautions that I realized would be difficult to unify into a simple, coherent system. I was able to extract properties that the system should have, but not specifics of how the system should work. +

+ +

+To find the common thread and unify everything, I realized that rather than working on the level of means, I should be working on the level of ends; before figuring out how to do things, I should be clearer about what I want to get out of life. As such I’m putting the project of systems on semi-hold; I will follow up on some of the generated ideas, but put further contemplation on hiatus until the matter of ends is further clarified. +

+ +

+But what does that mean? Am I going to go off and go “find a purpose in life”? Will I come brandishing a grand life quest, next time I return to this topic? That is not my intention. Frankly, I don’t really know what an answer to this question is supposed to look like. Still, I don’t think I am getting anywhere simply by listing desirable things, how I originally approached this. It’s easy to list desirable things, such as physical health, mental health, a good social life, sexual satisfaction, material possessions, creative expression, learning, and so on and so on. Yet this does not converge - I can’t seem to manage to unify all this in a way that helps me set up simple systems for how to act. These axes are pluriform and largely orthogonal, so that including all of them would only helplessly overcomplicate the system; yet they have no obvious natural ordering, so the set cannot be easily trimmed. +

+ +

+This, I think, is the biggest open issue in this matter, the issue of motivations. It is not enough to simply enumerate things which would be desirable, without having a discriminator that can rank them. That is what I mean by “the problem of ends”. And yes, ultimately that resolves to the difficult question of what is the meaning of life? I fear that that might take more than a week to resolve, but hopefully a partial solution should still help me make progress. +

+
+
+ +
+

Assorted Raw Materials

+
+

+What follows is more-or-less a brain-dump of generated ideas that do not fit in the earlier sections. +

+
+ +
+

Weekly Themes & Reports

+
+

+The astute reader will observe that this article itself, as a report on a weekly theme, itself constitutes a system. I have been playing with the idea of daily, weekly, monthly &c themes for a while; weekly themes seem like a good sweet spot. This is the first weekly theme so far, and I’m quite satisfied with it; having a theme gave me something to fall back on, something to work on when I didn’t know what I should be doing, something to keep in the back of my mind. Writing this kind of report on it is also helpful; it’s free-form enough that it’s not burdensome, yet the fact that I intend to report on my thoughts helps keep me focused and organized. +

+ +

+This gives me hope; it’s quite difficult to balance all the constraints on a good system, it’s hard to balance flexibility and structure, yet this system of weekly themes and reports seems to tick all the boxes. +

+
+
+ +
+

Dynamic Automatic Recall of Intentions

+
+

+I like to keep to-do lists, both short-term and long-term, but long-term lists can be hard to manage. It’s natural to add things to them faster than you can tick them off, it’s normal to have more things you want to do than you actually end up doing. However, unless you are very aggressive about cutting things out, this tends to lead to a large to-do list over time, with many things of low priority on it. This makes it much more effortful to maintain and to extract activities from it, defeating the purpose of a to-do list, which for me is primarily to get all of these things out of my head and onto a document. +

+ +

+It would be much better if to-dos were instead served up to me automatically, letting me choose on the spot how to deal with them. Options for “dealing with them” could be, for instance: +

+
    +
  • Move them from long-term to-dos to short-term to-dos
    • +
  • Delete them
    • +
  • Ask again later
    • +
+

+This way, I would not have to personally worry about forgetting anything; I would not have to manually sort through the long-term to-do lists. Metadata such as deadlines could also b eattached to the to-dos, though I need to be careful not to overcomplicate things. +

+
+
+ +
+

Chatbot as UI

+
+

+In context of the previous section I’ve been thinking about how to best send myself notifications. I’m sure there’s turnkey solutions for this, but the matter is personal and simple enough that I’d rather roll my own thing than rely and work around something readymade. I considered phone notifications and email notifications, but I found what I think would be a nicer interface: a Discord bot. +

+ +

+I use Discord to communicate with most of my friends, so it is under my eyes a lot of the time; furthermore, it allows for bidirectional communication with the bot, something which would be harder or at least clunkier with, say, email. I don’t like relying on a proprietary platform like Discord, but realistically I rely on it for the more important matter of communication with loved ones already, so I’m willing to compromise. +

+ +

+I would not want this to be the only interface, however; I would want the underlying data to be stored in a simple, human read- and writeable format. Currently I write to-dos using org-mode, and I quite like that experience, but I don’t know how I feel about having an automated program read and write to an org file. +

+
+
+ +
+

Catastrophic Failure

+
+

+I’ve spent a good chunk of time thinking about “catastrophic failure”. By catastrophic failure I mean the bad days, weeks and months. The times when you get nothing done. When you fail to wake up in the morning, brush your teeth, clean the house, exercise. When getting meaningful work done is not even on the table. I sketch here an extreme case; milder equivalents are possible. +

+ +

+The mechanism at play here two me seems two-fold. First of all, there’s a failure to measure; we push ourselves past the breaking point because we fail to realize that we are close to the breaking point. Second, there’s a failure to scale things. It really shouldn’t ever be the case that we fail to even take care of ourselves, surely we can muster at least that amount of bandwidth? We often spread ourselves too thin, we are reluctant to drop less important things for more important things, and end up failing at both. This helped me derive the desirable traits of evaluation and smooth scaling. +

+ +

+I am now armed with some principles for preventing catastrophic failure, but I haven’t made much progress on recovering from catastrophic failure. That’s still an important open problem. It’s important to have a plan for this scenario, because when we are in that deep dark well, it becomes very hard to muster the level of clarity and willpower necessary to climb back out. +

+
+
+ +
+

The Matter of Mood

+
+

+Mood matters. Inspiration matters. It is far easier, it takes far less energy, to do something we feel inspired to do, something that we are in the mood for, than something that’s a pain in the butt. This is a natural part of the dance of life, the chaos of existence, but my models currently do not take it into account. I have taken into account variations in the quantity of our capabilities, through the trait of smooth scaling, but I have yet to deal with variations in the quality of our capabilities and desires. +

+
+
+ +
+

The Practice of the Practice

+
+

+My meditation practice intersects strongly with this topic, yet I have not yet managed to marry them effectively. This is a very promising direction of thought that I fully intend to follow up on. +

+
+
+
+ +
+

Weekly Diary

+
+

+This week was pretty tough, but I managed to mostly turn it around towards the end. I struggled with depression, loneliness and avolition. I dropped my daily meditation streak and indulged in too much cannabis. I spent a lot of time reading, mainly LessWrong. Having this weekly theme helped, since at least I was managing to make some progress on some things. In the end this report ended up being far longer than I had anticipated, certainly far longer than my notes for it, so I guess I made more progress in the end than I thought I did. +

+ +

+I struggled with all the things that this document is supposed to help resolve. Too many things I feel like I ought to be doing, too little progress on anything material. Doing nothing causes ennui, but choosing to do one thing over another feels pointless and arbitrary. It’s hard to keep many plates spinning, it’s hard to know where to start picking them up when you drop them. +

+
+
+ +
+

Next Week

+
+

+I’m gonna leave this topic here for the time being. I don’t think I have what I need to continue the research, so I’m just gonna wait. I’ll try and follow up on some of the more actionable things, try and pick earlier systems of to-do lists and so on back up. I intent to follow up on the Discord-bot-as-planning-interface idea too. +

+ +

+I’ve been enjoying reading and learning a lot lately, so maybe next week (really, this week; it is Monday) will be the Week of Learning. I also want to try writing more. I’ll take it easy, keep things flexible and open-ended, not put too many expectations on myself. +

+
+
+ +
+

Closing Words

+
+

+I feel a lot better now! Bringing myself to write for this blog was quite a hurdle, but overcoming it has energized me. I look forward to writing more. Bless you, dear reader. May you be happy, may you be at peace, may you be free from suffering. May you be kind to others, may you find meaning, may you be victorious. +

+
+
+
+
+
+ +
+ + \ No newline at end of file diff --git a/html/posts/decisionmaking/bad-arguments-against-become-arguments-for.html b/html/posts/decisionmaking/bad-arguments-against-become-arguments-for.html new file mode 100644 index 0000000..b96c1e8 --- /dev/null +++ b/html/posts/decisionmaking/bad-arguments-against-become-arguments-for.html @@ -0,0 +1,239 @@ + + + + + + +Bad Arguments Against Something Can Become Good Arguments For It + + + + + +
+ +
+
+ +
+

Bad Arguments Against Something Can Become Good Arguments For It

+
+

+A decisionmaking trick I often use is to take bad arguments against something as arguments for that thing. As a general qualitative principle this of course does not work - Reversed Stupidity is not Intelligence. Rather, I use this technique in a quantitative way. +

+ +

+Often we have to deal with large aggregates of critiques and praises; say, product or media reviews, or political arguments, or comments on an article or video. In these cases I expect a certain base rate of detractors, people who simply do not like the thing being evaluated and will go looking for arguments against it. Many nonsensical criticisms thus represent a failed search for better arguments; they are evidence that we do not live in the counterfactual world where better arguments could be found. Furthermore, in cases of taste, my disagreeing with detractors is evidence that I am liable to have similar sensibilities as proponents. +

+ +

+As added benefits, this signal is easy to evaluate, since it is easy to recognize particularly poor arguments at a glance, and it is somewhat resistant to manipulation, since my interpretation of it is unusual - most people will interpret weak arguments against something as weak evidence against that thing, rather than evidence in favor of that thing, and therefore few people trying to sway the public opinion towards something will argue against it. +

+ +

+Apply with caution, of course, as it is not a particularly high-fidelity signal. I mainly apply this principle when it comes to things like product or media reviews, as those tend to have high volumes of opinions easily sortable by emotional valence. Sometimes I also apply it to the comments sections of theoretical pieces, especially for the kind of author you’d expect to get hate regardless of whether they are right or wrong. +

+
+
+
+
+ +
+ + \ No newline at end of file diff --git a/html/posts/framework.html b/html/posts/framework.html index 124491b..6c9c65e 100644 --- a/html/posts/framework.html +++ b/html/posts/framework.html @@ -1,7 +1,7 @@ - + Framework Laptop Review @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -203,13 +203,13 @@
-
-

My Experience with the Framework Laptop

-
+
+

My Experience with the Framework Laptop

+
-
-

Ordering

-
+
+

Ordering

+

I’d been eyeing the Framework laptop since somewhere in October 2021, but the EU release got delayed and they were very hesitant to give time estimates. I only managed to get my hands on it in late February, and I ended up having to have it delivered to France. I understand the difficulty of setting up logistics especially these days, but I broke my previous laptop and being stuck in limbo like this was not fun.

@@ -221,13 +221,13 @@ I asked their customer service to make a small change to the delivery address, b
-
-

Set-up

-
+
+

Set-up

+
-
-

Hardware

-
+
+

Hardware

+

I got the DIY edition with the (lowest-end) i5-1135G7 CPU, 2x16GB RAM. I brought my own 1TB SSD. The higher spec CPUs didn’t seem worth the money to me. The RAM is probably overkill.

@@ -255,9 +255,9 @@ The more you look at it, the nicer it gets!
-
-

Software

-
+
+

Software

+

I installed Gentoo GNU+Linux on the laptop, just like I have on my desktop. I used an Ubuntu live CD as the install medium together with the Gentoo stage3 tarball, and it worked well. I didn’t really have to jump through any laptop-specific hoops, it was a very nice experience. I did use the dist-kernel rather than configuring my own.

@@ -267,9 +267,9 @@ The laptop held up well during compiling. It’s not as fast as a desktop of

-
-
Display scaling
-
+
+
Display scaling
+

Simply setting Xft.dpi: 192 in .Xresources was enough for the vast majority of applications to use 2x scaling, which looks very good on this display. This is on X11 obviously; I don’t use Wayland.

@@ -279,52 +279,67 @@ The odd application requires its own scaling setting. Rofi requires setting
-
-
Display manager
-
+
+
Display manager
+

I used SDDM which works very well. I wanted to go for something a bit fancier looking, and this delivers. I don’t usually use things in the whole QT ecosystem, so it’s refreshing.

-
-
Hibernate/suspend-to-disk
-
+
+
Hibernate/suspend-to-disk
+

This required setting up a swap file and setting a kernel command line parameter to refer to it, but it was easy to do. It works well. I’ve observed the laptop auto-hibernating when the battery runs out, but it doesn’t do this reliably, so I should probably configure it myself.

-
-
Guake-like transient terminal
-
+
+
Guake-like transient terminal
+

-Using some fish scripts, bspwm, picom and xst I rigged up a transient, transparent terminal to use for quick shell jobs. I used the scripts and config file in Appendix A to do this. The implementation is a bit hacky, and it’s not impossible to break, but it serves my purposes well (and more important, it was fun to make)! +Using some fish scripts, bspwm, picom and xst I rigged up a transient, transparent terminal to use for quick shell jobs. I used the scripts and config file in Appendix A to do this. The implementation is a bit hacky, and it’s not impossible to break, but it serves my purposes well (and more important, it was fun to make)!

-
-
Wallpaper-setting script
-
+
+
Wallpaper-setting script
+

I wrote a script to set a random wallpaper.

-
+
#!/usr/bin/env python3
+import os
+from random import choice
+
+pape_path = os.path.expandvars("$HOME/Pictures/Wallpapers")
+
+def set_wallpaper():
+    files = os.popen(f"ls {pape_path}").read().split('\n')
+    pape = choice(files)
+    pp = os.path.join(pape_path, pape)
+
+    os.popen(f"hsetroot -full {pp}")
+    os.popen(f"echo {pp} > /tmp/wallpaper")
+
+if __name__ == "__main__":
+    set_wallpaper()
-
-
Lockscreen
-
+
+
Lockscreen
+

-I hacked together some pretty crappy code to lock the screen using i3lock, with my wallpaper composed with a little lock icon as the background. Very overengineered. +I hacked together some pretty crappy code to lock the screen using i3lock, with my wallpaper composed with a little lock icon as the background. Very overengineered.

@@ -338,34 +353,34 @@ Is there a better lockscreen out there that will let me set my own image as the

-
-
TODO
-
+
+
TODO
+
    -
  • Battery level notifications
    • -
  • sleep-then-hibernate
    • -
  • Battery tuning
    • +
  • Battery level notifications
    • +
  • sleep-then-hibernate
    • +
  • Battery tuning
-
-

Impressions

-
+
+

Impressions

+
-
-
Build Quality
-
+
+
Build Quality
+

The laptop is made of aluminium and feels solid but light. The screen does seem pretty flimsy, though. I probably wouldn’t want to drop this thing. It looks sleek and elegant, but pretty muted.

-
-
Screen
-
+
+
Screen
+

This is my first time ever using a high-DPI screen, and I’m very impressed by it. Text looks unbelievably crisp and pleasant to read. I was somewhat worried about the linux high DPI situation, but I am having no issues whatsoever.

@@ -380,27 +395,27 @@ The brightness goes up quite high, but colours feel somewhat washed out at high
-
-
Keyboard
-
+
+
Keyboard
+

Framework seems to advertise their keyboard as having particularly deep travel, but it mostly just feels like any chiclet keyboard to me. Not a bad chiclet keyboard, but not that great, either. The layout is fine, but it makes me miss the thinkpad.

-
-
Touchpad
-
+
+
Touchpad
+

I’ve never had a decent touchpad before, so I was pleasantly surprised. I expected to miss the trackpoint on the thinkpad a lot, but this is fine, though it’s still a step down. Pinch to zoom doesn’t work very well, but I don’t use that functionality a lot. I miss having dedicated mouse buttons; the clicking functionality on this touchpad works fine for me, but it’s hard not to mess up left/middle/right click. That’s a good incentive for me to practice relying on the mouse less, though. There’s plenty of work being done on the Linux touchpad experience software-side, too. It’s a nice time to be a linux laptop user!

-
-
Battery
-
+
+
Battery
+

With the disclaimer that I haven’t tested very intensely and I haven’t tuned power settings very much.
I seem to get about 6.5 hours of real-world use time when using Emacs and doing light web browsing. I don’t have a good benchmark for more intensive tasks, but compiling does hit the battery pretty hard. All in all I’m very happy with it, getting decent battery life on Linux is hard. It might be worth eventually buying a power bank for it though, for travel~ @@ -408,18 +423,18 @@ I seem to get about 6.5 hours of real-world use time when using Emacs and doing

-
-
Expansion cards/ports
-
+
+
Expansion cards/ports
+

The little expansion cards are one of Framework’s big marketing things. I think they’re pretty neat, though I don’t always quite understand the way people talk about them, as “dongle killers”. I would find hotswapping these about equally obnoxious as carrying dongles. The idea of aftermarket expansion cards is interesting, though - these are low level, high bandwidth ports, with I think similar capabilities to the ExpressCard ports on old business laptops, but more modern with a USB-C port. I’m looking forward to the USB4 era!

-
-
Performance
-
+
+
Performance
+

So far I haven’t felt limited by performance at all, the experience has been really snappy. I haven’t thrown particularly difficult things at it, though, but that’s fine - most of what I do on a laptop is reading, web browsing, and text editing. I played some Factorio on it and that seemed fine, but using the touchpad felt limiting so I didn’t play very much.

@@ -427,9 +442,9 @@ So far I haven’t felt limited by performance at all, the experience has be
-
-

Closing words

-
+
+

Closing words

+

Getting this laptop set up has been really fun! It’s a good opportunity to take stock of where we’re at. On the hardware side, I am very impressed that it’s now possible to make a laptop that’s this user-servicable, this well-specced and still not that expensive. It’s a reminder of how much better things could be.

@@ -445,30 +460,28 @@ Personally, I’m getting a rare chance to critically examine all the little
- - -
-

Appendix A: Transient Terminal Sources

-
+
+

Appendix A: Transient Terminal Sources

+

togglescratch

-
#!/usr/bin/env fish
+
#!/usr/bin/env fish
 
-if test ! -e /tmp/scratch_id
-    exec xst -e makescratch
-end
+if test ! -e /tmp/scratch_id
+    exec xst -e makescratch
+end
 
-set nid (cat /tmp/scratch_id)
+set nid (cat /tmp/scratch_id)
 
-if test -e /tmp/scratch_on
-    rm /tmp/scratch_on
-    bspc node $nid --to-desktop z
-else
-    touch /tmp/scratch_on
-    bspc node $nid --to-desktop focused --focus --state fullscreen --flag private=on
-end
+if test -e /tmp/scratch_on
+    rm /tmp/scratch_on
+    bspc node $nid --to-desktop z
+else
+    touch /tmp/scratch_on
+    bspc node $nid --to-desktop focused --focus --state fullscreen --flag private=on
+end
@@ -476,14 +489,14 @@ end makescratch

-
#!/bin/fish
-set nid (xdo id)
-echo $nid > /tmp/scratch_id
-bspc node $nid --state fullscreen --flag private=on --to-desktop focused
-touch /tmp/scratch_on
-set decid (printf '%d' $nid)
-xdotool set_window --name "scratchterminal" $decid
-exec "$HOME/Scripts/cleanscratch"
+
#!/bin/fish
+set nid (xdo id)
+echo $nid > /tmp/scratch_id
+bspc node $nid --state fullscreen --flag private=on --to-desktop focused
+touch /tmp/scratch_on
+set decid (printf '%d' $nid)
+xdotool set_window --name "scratchterminal" $decid
+exec "$HOME/Scripts/cleanscratch"
@@ -491,11 +504,11 @@ exec "$HOME/Scripts/cleanscratch" cleanscratch

-
#!/usr/bin/env fish
+
#!/usr/bin/env fish
 
-$SHELL
-rm /tmp/scratch_id
-rm /tmp/scratch_on
+$SHELL
+rm /tmp/scratch_id
+rm /tmp/scratch_on
@@ -503,14 +516,20 @@ rm /tmp/scratch_on picom.conf 

-
+fading = true;
+#no-fading-openclose = true;
+fade-delta = 5;
+vsync = true;
+backend="glx";
+opacity-rule=["90:name = 'scratchterminal'"];
+#opacity-rule=["90:class_g = 'xst-256color'"];
-
-

Appendix B: lock.py

-
+
+

Appendix B: lock.py

+
#!/usr/bin/python3
 import os
@@ -533,24 +552,19 @@ rm /tmp/scratch_on
     os.popen("loginctl suspend")
- -

-last modified: 2022-03-21 -

- - + \ No newline at end of file diff --git a/html/posts/grocery-log.html b/html/posts/grocery-log.html deleted file mode 100644 index c3aff8c..0000000 --- a/html/posts/grocery-log.html +++ /dev/null @@ -1,794 +0,0 @@ - - - - - - -ssdfsdfs - - - - - -
- -
-
- -
-

09->26

-
-
-
-

Other

-
- - - --- -- -- -- -- -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemAmountPriceCategoryTimesTotal
Toilet paper24 rolls7.39Other214.78
Mayonaise650mL1.52Other11.52
Curry paste1 jar2.45Other49.8
Baguette11.29Bread67.74
Hamburger buns41.69Bread11.69
Spelt bread500g2.55Bread12.55
Raisin bread500g1.99Bread11.99
Croissant20.70Bread10.7
Milk1L1.99Dairy47.96
Camembert120g2.09Dairy2.55.23
Creme Fraiche200g1.19Dairy11.19
Goat cheese125g1.94Dairy11.94
Butter250g2.99Dairy12.99
Teabags11.99Drinks47.96
Grapefruit juice1L1.65Drinks34.95
Strawberries250g3.49Fruit13.49
Blueberries125g2.29Fruit511.45
Avocado22.79Fruit38.37
Cranberries250g2.99Fruit25.98
Mango11.79Fruit11.79
Blackberries125g3.49Fruit13.49
Carpaccio123g3.89Meat13.89
Minced meat300g3.19Meat2.37.34
Chicken275g3.99Meat3.212.77
Hamburgers220g2.91Meat38.73
Raw ham100g3.46Meat1.86.23
Beef chipolata250g3.39Meat13.39
Salami110g1.88Meat23.76
Tuna120g2.42Meat12.42
Montaignan Syrah750mL5.99Psych15.99
Monster500mL1.39Psych11.39
Merlot750mL4.99Psych14.99
Beer1 bottle2.40Psych49.6
Energy Drink250mL2.08Psych12.08
Pinot Noir750mL6.99Psych320.97
Cake450g2.05Sweets12.05
Ben & Jerry’s465mL5.39Sweets1.26.47
Pudding cakes300g1.99Sweets11.99
Eierkoeken200g1.73Sweets11.73
Sugar donut10.51Sweets10.51
Tomatoes52.89Vegetables1.33.76
Rice1kg1.90Vegetables23.8
Iceberg lettuce11.39Vegetables11.39
Carrots1 bag0.99Vegetables10.99
Pasta salad350g3.75Vegetables27.5
Mushrooms200g1.99Vegetables11.99
French fries750g1.12Vegetables11.12
Haricots400g2.09Vegetables12.09
Curry package14.99Vegetables14.99
Other:    26.10 EUR
Bread:    14.67 EUR
Dairy:    19.31 EUR
Drinks:    12.91 EUR
Fruit:    34.57 EUR
Meat:    48.53 EUR
Psych:    45.02 EUR
Sweets:    12.75 EUR
Vegetables:    22.64 EUR
Total:    241.49 EUR
-

-last modified: 2022-04-27 -

-
-
-
-
-
- -
- - diff --git a/html/sitemap.html b/html/sitemap.html index 0a8ff65..2af8965 100644 --- a/html/sitemap.html +++ b/html/sitemap.html @@ -1,7 +1,7 @@ - + Sitemap for project pages @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -203,30 +203,38 @@
- - + \ No newline at end of file diff --git a/html/snippets.html b/html/snippets.html index 693eeb6..4aa09db 100644 --- a/html/snippets.html +++ b/html/snippets.html @@ -1,7 +1,7 @@ - + Snippets @@ -188,7 +188,7 @@ { font-size: 10px; font-weight: bold; white-space: nowrap; } .org-info-js_search-highlight { background-color: #ffff00; color: #000000; font-weight: bold; } - .org-svg { width: 90%; } + .org-svg { } @@ -203,13 +203,13 @@
-
-

X11

-
+
+

X11

+
-
-

Reset xrandr

-
+
+

Reset xrandr

+
xrandr -s 0
@@ -219,16 +219,15 @@
- - + \ No newline at end of file diff --git a/html/static/fonts/Roboto-Black.ttf b/html/static/fonts/Roboto-Black.ttf new file mode 100644 index 0000000..0112e7d Binary files /dev/null and b/html/static/fonts/Roboto-Black.ttf differ diff --git a/html/static/fonts/Roboto-BlackItalic.ttf b/html/static/fonts/Roboto-BlackItalic.ttf new file mode 100644 index 0000000..b2c6aca Binary files /dev/null and b/html/static/fonts/Roboto-BlackItalic.ttf differ diff --git a/html/static/fonts/Roboto-Bold.ttf b/html/static/fonts/Roboto-Bold.ttf new file mode 100644 index 0000000..43da14d Binary files /dev/null and b/html/static/fonts/Roboto-Bold.ttf differ diff --git a/html/static/fonts/Roboto-BoldItalic.ttf b/html/static/fonts/Roboto-BoldItalic.ttf new file mode 100644 index 0000000..bcfdab4 Binary files /dev/null and b/html/static/fonts/Roboto-BoldItalic.ttf differ diff --git a/html/static/fonts/Roboto-Italic.ttf b/html/static/fonts/Roboto-Italic.ttf new file mode 100644 index 0000000..1b5eaa3 Binary files /dev/null and b/html/static/fonts/Roboto-Italic.ttf differ diff --git a/html/static/fonts/Roboto-Light.ttf b/html/static/fonts/Roboto-Light.ttf new file mode 100644 index 0000000..e7307e7 Binary files /dev/null and b/html/static/fonts/Roboto-Light.ttf differ diff --git a/html/static/fonts/Roboto-LightItalic.ttf b/html/static/fonts/Roboto-LightItalic.ttf new file mode 100644 index 0000000..2d277af Binary files /dev/null and b/html/static/fonts/Roboto-LightItalic.ttf differ diff --git a/html/static/fonts/Roboto-Medium.ttf b/html/static/fonts/Roboto-Medium.ttf new file mode 100644 index 0000000..ac0f908 Binary files /dev/null and b/html/static/fonts/Roboto-Medium.ttf differ diff --git a/html/static/fonts/Roboto-MediumItalic.ttf b/html/static/fonts/Roboto-MediumItalic.ttf new file mode 100644 index 0000000..fc36a47 Binary files /dev/null and b/html/static/fonts/Roboto-MediumItalic.ttf differ diff --git a/html/static/fonts/Roboto-Regular.ttf b/html/static/fonts/Roboto-Regular.ttf new file mode 100644 index 0000000..ddf4bfa Binary files /dev/null and b/html/static/fonts/Roboto-Regular.ttf differ diff --git a/html/static/fonts/Roboto-Thin.ttf b/html/static/fonts/Roboto-Thin.ttf new file mode 100644 index 0000000..2e0dee6 Binary files /dev/null and b/html/static/fonts/Roboto-Thin.ttf differ diff --git a/html/static/fonts/Roboto-ThinItalic.ttf b/html/static/fonts/Roboto-ThinItalic.ttf new file mode 100644 index 0000000..084f9c0 Binary files /dev/null and b/html/static/fonts/Roboto-ThinItalic.ttf differ diff --git a/html/static/style.css b/html/static/style.css index 0ae4487..36422dd 100644 --- a/html/static/style.css +++ b/html/static/style.css @@ -1,21 +1,31 @@ +@font-face { + font-family: Roboto; + src: url('static/fonts/Roboto-Regular.ttf'); +} + :root { - --site-width: 70%; + --site-width: 750px; --vert-content-margin: 1.5em; --accent1: #d2e8b0; --black: #222; --white: #FBFBFB; + --background: #FCFAF9; + --font-size: 1.35rem; + --line-height: 1.9rem; + --font-family: "Roboto"; } body { - font-family: "Baskerville"; - font-size: 1.2em; + text-align: justify; + font-family: var(--font-family); + font-size: var(--font-size); + line-height: var(--line-height); color: var(--black); - background-color: var(--white); + background-color: var(--background); } -p + p { - /* Prose-style indented paragraphs */ - text-indent: 1em; +code { + font-size: calc(var(--font-size) * 0.9); } hr { @@ -65,6 +75,15 @@ a, a:visited { margin: auto; } +#publish-date, #modified-date { + font-style: italic; +} + +.src, .example { + font-family: "monospace"; + font-size: 1rem; +} + /* Set the colors in 
 blocks from the Leuven theme */
 pre                                      {background-color:#FFFFFF;}
 pre span.org-builtin                     {color:#006FE0;font-weight:bold;}
diff --git a/html/todo.html b/html/todo.html
index 4d80f4e..7bb97f7 100644
--- a/html/todo.html
+++ b/html/todo.html
@@ -1,7 +1,7 @@
 
 
 
-
+
 
 
 TODO
@@ -188,7 +188,7 @@
     { font-size: 10px; font-weight: bold; white-space: nowrap; }
   .org-info-js_search-highlight
     { background-color: #ffff00; color: #000000; font-weight: bold; }
-  .org-svg { width: 90%; }
+  .org-svg { }
 
 
 
@@ -202,34 +202,17 @@
- -
-

literate dotfiles?

-
-
-

How this blog was built

-
-
-

project graveyard

-
-
-

food thing

-
-
-

fix picom.conf

-
- - + \ No newline at end of file diff --git a/org/about.org b/org/about.org index 725866e..91f093b 100644 --- a/org/about.org +++ b/org/about.org @@ -1,5 +1,5 @@ #+TITLE: About +chuuu -it's me ehehe -#chuu -dfdfd +# +fdsfsdf diff --git a/org/blogroll.org b/org/blogroll.org index 9281415..674d6ae 100644 --- a/org/blogroll.org +++ b/org/blogroll.org @@ -1,4 +1 @@ #+TITLE: Blogroll -#+MACRO: modified 2022-03-21 - -last modified: {{{modified}}} diff --git a/org/posts/blog-tech.org b/org/posts/blog-tech.org index c1c9c8f..7c1c4ae 100644 --- a/org/posts/blog-tech.org +++ b/org/posts/blog-tech.org @@ -1,9 +1,5 @@ #+TITLE: How this blog is built -#+MACRO: modified 2022-04-18 #+DATE: <2022-04-18 Mon 14:04> * Blog Tech ** chuu - - -/last modified: {{{modified}}}/ diff --git a/org/posts/decisionmaking/bad-arguments-against-become-arguments-for.org b/org/posts/decisionmaking/bad-arguments-against-become-arguments-for.org new file mode 100644 index 0000000..dfd77bd --- /dev/null +++ b/org/posts/decisionmaking/bad-arguments-against-become-arguments-for.org @@ -0,0 +1,11 @@ +#+TITLE: Bad Arguments Against Something Can Become Good Arguments For It +#+DATE: <2023-01-23 Mon 14:03> + +* Bad Arguments Against Something Can Become Good Arguments For It + A decisionmaking trick I often use is to take bad arguments /against/ something as arguments /for/ that thing. As a general qualitative principle this of course does not work - [[https://www.lesswrong.com/posts/qNZM3EGoE5ZeMdCRt/reversed-stupidity-is-not-intelligence][Reversed Stupidity is not Intelligence]]. Rather, I use this technique in a quantitative way. + + Often we have to deal with large aggregates of critiques and praises; say, product or media reviews, or political arguments, or comments on an article or video. In these cases I expect a certain base rate of detractors, people who simply do not like the thing being evaluated and will go looking for arguments against it. Many nonsensical criticisms thus represent a failed search for better arguments; they are evidence that we do not live in the counterfactual world where better arguments could be found. Furthermore, in cases of taste, my disagreeing with detractors is evidence that I am liable to have similar sensibilities as proponents. + + As added benefits, this signal is easy to evaluate, since it is easy to recognize particularly poor arguments at a glance, and it is somewhat resistant to manipulation, since my interpretation of it is /unusual/ - most people will interpret weak arguments against something as weak evidence against that thing, rather than evidence /in favor/ of that thing, and therefore few people trying to sway the public opinion /towards/ something will argue /against/ it. + + Apply with caution, of course, as it is not a particularly high-fidelity signal. I mainly apply this principle when it comes to things like product or media reviews, as those tend to have high volumes of opinions easily sortable by emotional valence. Sometimes I also apply it to the comments sections of theoretical pieces, especially for the kind of author you'd expect to get hate regardless of whether they are right or wrong. diff --git a/org/posts/diary/week-3-2023.org b/org/posts/diary/week-3-2023.org new file mode 100644 index 0000000..12c9065 --- /dev/null +++ b/org/posts/diary/week-3-2023.org @@ -0,0 +1,74 @@ +#+TITLE: Week 3, 2023, "Week of Systems" report +#+DATE: <2023-01-23 Mon 15:21> + +* Week 3, 2023, "Week of Systems" report +** Introduction +Last week I worked on the issue of "life systems", by which I mean systems such as to-do lists, good habits such as exercise, schedules, plans, that sort of thing. At various times in the past I've had various such systems, some working better than others. I used to make a list of the day's goals every morning and cross them off throughout the day. I also keep a file called =life.org= where I keep track of to-dos and leads to look into at a later point and such. Other things I would consider "sytems" include my daily meditation practice and various attempts at regular exercise I've made in the past. + +Keeping systems is hard because life is messy. Whole-life systems as these are truly all-encompassing, and thus they interact with all of life's complexity. The [[https://www.lesswrong.com/posts/CPm5LTwHrvBJCa9h5/planning-fallacy][Planning Fallacy]] turns any attempts at tying to-do lists and intentions to timespans and deadlines into an uphill battle. Changing your habits is famously hard. Unexpected things will happen with certainty; priorities change, capabilities fluctuate, problems spring up and solve themselves. + +** Desirable Traits +The primary issue with life systems is therefore the overhead, the burden of maintenance, the stress. Rather than simplifying life, it is easy to /add/ an administrative burden. In light of this, I've isolated the following properties that I think a good system should have: +- *Simplicity*. The overall system can not contain too many moving parts. In order to be simple to apply, it needs to be simple to explain; in order to be simple to explain, it needs to /be/ simple. +- *Smooth scaling*. As life's difficulties and my capacity to handle them fluctuate, the systems of my life need to be able to scale smoothly up and down. During tough times I need to be able to simplify my life to the most important parts; during better times I should be able to smoothly pick the rest back up where I left it. Implicit in this is also a /hierarchy of priority/, an order in which I drop things, a notion of what is least worthwhile at any given time. +- *Malleability*. As both my life and my understanding of it are liable to change, my systems need to be able to adapt with minimal burden. Because of this there ought to be few strict schemas; for, if the schema has to change, all data already /within/ that scheme would have to be migrated. +- *Evaluation*. There needs to be some measure of /how well things are going/, in order to catch problems early and prevent catastrophic failure, and furthermore to optimize the system. Other constraints enforce simplicity here; a system of regular deadlines, for instance, would be too inflexible. + +** Specifics and the Problem of Ends +The above is about as far as I got in terms of definitives. I did not start there; I started at neither the level of specifics nor of generalities, but in between, dealing with things such as "managing stress" and "measurability" and "dimensions of personal development". At this level, however, it was far easier to write things down than to strike them through; easier to complicate than simplify, and I ended up with a basket of disjointed ideas, aims and cautions that I realized would be difficult to unify into a simple, coherent system. I was able to extract properties that the system should have, but not specifics of how the system should work. + +To find the common thread and unify everything, I realized that rather than working on the level of /means/, I should be working on the level of /ends/; before figuring out /how to do things/, I should be clearer about /what I want to get out of life/. As such I'm putting the project of systems on semi-hold; I will follow up on some of the generated ideas, but put further contemplation on hiatus until the matter of ends is further clarified. + +But what does that /mean/? Am I going to go off and go "find a purpose in life"? Will I come brandishing a grand life quest, next time I return to this topic? That is not my intention. Frankly, I don't really know what an answer to this question is supposed to look like. Still, I don't think I am getting anywhere simply by /listing desirable things/, how I originally approached this. It's easy to list desirable things, such as physical health, mental health, a good social life, sexual satisfaction, material possessions, creative expression, learning, and so on and so on. Yet this does not /converge/ - I can't seem to manage to unify all this in a way that helps me set up simple systems for how to act. These axes are pluriform and largely orthogonal, so that including all of them would only helplessly overcomplicate the system; yet they have no obvious natural ordering, so the set cannot be easily trimmed. + +This, I think, is the biggest open issue in this matter, the issue of /motivations/. It is not enough to simply enumerate things which would be /desirable/, without having a discriminator that can /rank/ them. /That/ is what I mean by "the problem of ends". And yes, ultimately that resolves to the difficult question of /what is the meaning of life?/ I fear that that might take more than a week to resolve, but hopefully a partial solution should still help me make progress. + +** Assorted Raw Materials +What follows is more-or-less a brain-dump of generated ideas that do not fit in the earlier sections. + +*** Weekly Themes & Reports +The astute reader will observe that this article itself, as a report on a weekly theme, itself constitutes a system. I have been playing with the idea of daily, weekly, monthly &c themes for a while; weekly themes seem like a good sweet spot. This is the first weekly theme so far, and I'm quite satisfied with it; having a theme gave me something to fall back on, something to work on when I didn't know what I should be doing, something to keep in the back of my mind. Writing this kind of report on it is also helpful; it's free-form enough that it's not burdensome, yet the fact that I intend to report on my thoughts helps keep me focused and organized. + +This gives me hope; it's quite difficult to balance all the constraints on a good system, it's hard to balance flexibility and structure, yet this system of weekly themes and reports seems to tick all the boxes. + +*** Dynamic Automatic Recall of Intentions +I like to keep to-do lists, both short-term and long-term, but long-term lists can be hard to manage. It's natural to add things to them faster than you can tick them off, it's normal to have more things you want to do than you actually end up doing. However, unless you are very aggressive about cutting things out, this tends to lead to a large to-do list over time, with many things of low priority on it. This makes it much more effortful to maintain and to extract activities from it, defeating the purpose of a to-do list, which for me is primarily to get all of these things out of my head and onto a document. + +It would be much better if to-dos were instead served up to me automatically, letting me choose on the spot how to deal with them. Options for "dealing with them" could be, for instance: +- Move them from long-term to-dos to short-term to-dos +- Delete them +- Ask again later +This way, I would not have to personally worry about forgetting anything; I would not have to manually sort through the long-term to-do lists. Metadata such as deadlines could also b eattached to the to-dos, though I need to be careful not to overcomplicate things. + +*** Chatbot as UI +In context of the previous section I've been thinking about /how/ to best send myself notifications. I'm sure there's turnkey solutions for this, but the matter is personal and simple enough that I'd rather roll my own thing than rely and work around something readymade. I considered phone notifications and email notifications, but I found what I think would be a nicer interface: a Discord bot. + +I use Discord to communicate with most of my friends, so it is under my eyes a lot of the time; furthermore, it allows for bidirectional communication with the bot, something which would be harder or at least clunkier with, say, email. I don't like relying on a proprietary platform like Discord, but realistically I rely on it for the more important matter of communication with loved ones already, so I'm willing to compromise. + +I would not want this to be the /only/ interface, however; I would want the underlying data to be stored in a simple, human read- and writeable format. Currently I write to-dos using org-mode, and I quite like that experience, but I don't know how I feel about having an automated program read and write to an org file. + +*** Catastrophic Failure +I've spent a good chunk of time thinking about "catastrophic failure". By catastrophic failure I mean the bad days, weeks and months. The times when you get nothing done. When you fail to wake up in the morning, brush your teeth, clean the house, exercise. When getting meaningful work done is not even on the table. I sketch here an extreme case; milder equivalents are possible. + +The mechanism at play here two me seems two-fold. First of all, there's a failure to measure; we push ourselves past the breaking point because we fail to realize that we are /close/ to the breaking point. Second, there's a failure to scale things. It really shouldn't ever be the case that we fail to even take care of ourselves, surely we can muster at least that amount of bandwidth? We often spread ourselves too thin, we are reluctant to drop less important things for more important things, and end up failing at both. This helped me derive the desirable traits of /evaluation/ and /smooth scaling/. + +I am now armed with some principles for /preventing/ catastrophic failure, but I haven't made much progress on /recovering from/ catastrophic failure. That's still an important open problem. It's important to have a plan for this scenario, because when we are /in/ that deep dark well, it becomes very hard to muster the level of clarity and willpower necessary to climb back out. + +*** The Matter of Mood +Mood matters. Inspiration matters. It is far easier, it takes far less energy, to do something we feel inspired to do, something that we are in the mood for, than something that's a pain in the butt. This is a natural part of the dance of life, the chaos of existence, but my models currently do not take it into account. I have taken into account variations in the /quantity/ of our capabilities, through the trait of /smooth scaling/, but I have yet to deal with variations in the /quality/ of our capabilities and desires. + +*** The Practice of the Practice +My meditation practice intersects strongly with this topic, yet I have not yet managed to marry them effectively. This is a very promising direction of thought that I fully intend to follow up on. + +** Weekly Diary +This week was pretty tough, but I managed to mostly turn it around towards the end. I struggled with depression, loneliness and avolition. I dropped my daily meditation streak and indulged in too much cannabis. I spent a lot of time reading, mainly LessWrong. Having this weekly theme helped, since at least I was managing to make /some/ progress on /some/ things. In the end this report ended up being far longer than I had anticipated, certainly far longer than my notes for it, so I guess I made more progress in the end than I thought I did. + +I struggled with all the things that this document is supposed to help resolve. Too many things I feel like I ought to be doing, too little progress on anything material. Doing nothing causes ennui, but choosing to do one thing over another feels pointless and arbitrary. It's hard to keep many plates spinning, it's hard to know where to start picking them up when you drop them. + +** Next Week +I'm gonna leave this topic here for the time being. I don't think I have what I need to continue the research, so I'm just gonna wait. I'll try and follow up on some of the more actionable things, try and pick earlier systems of to-do lists and so on back up. I intent to follow up on the Discord-bot-as-planning-interface idea too. + +I've been enjoying reading and learning a lot lately, so maybe next week (really, this week; it is Monday) will be the Week of Learning. I also want to try writing more. I'll take it easy, keep things flexible and open-ended, not put too many expectations on myself. + +** Closing Words +I feel a lot better now! Bringing myself to write for this blog was quite a hurdle, but overcoming it has energized me. I look forward to writing more. Bless you, dear reader. May you be happy, may you be at peace, may you be free from suffering. May you be kind to others, may you find meaning, may you be victorious. diff --git a/org/posts/essays/aimish.org b/org/posts/essays/aimish.org new file mode 100644 index 0000000..70c59f2 --- /dev/null +++ b/org/posts/essays/aimish.org @@ -0,0 +1,53 @@ +#+TITLE: A Modest AI Alignment Proposal: Kill all non-Amish +#+DATE: <2023-01-24 Tue 14:07> + +* A Modest AI Alignment Proposal: Kill all non-Amish +so yesterday I had an idea abouth ow to deal with the +[2:00 PM] +AI alignment thing +[2:01 PM] +and I was thinking the Amish are probably a genetically distinct population right? +[2:01 PM] +or at least all these mennonites are +[2:01 PM] +I read up on them a bit and they do split their church a lot +[2:01 PM] +anyways they intermarry, they've lived closed off from their surroundings for a long time +[2:01 PM] +you can probably tell without too much trouble genetically +[2:02 PM] +I bet you could engineer a virus that leaves only Amish alive +[2:02 PM] +think about it +[2:02 PM] +if you wanted to delay the invention of strong AI it would be perfect +[2:02 PM] +the amish would never try and create an AI, especiall not having technology just killing 99.9% of the world's population +[2:02 PM] +they would see it as a clear message of God that technology is indeed bad and they are right +[2:03 PM] +also they would +[2:03 PM] +cope with it well +[2:03 PM] +they're already used to not using electricity and stuff +[2:03 PM] +if society broke down entirely I don't think the amish would care all that much +[2:03 PM] +they already live in tight, self-sufficient communities +[2:03 PM] +furthermore they speak English, most of them are bilingual I think +[2:03 PM] +they are literate, they get normal elementary school education pretty much +[2:04 PM] +they live in the US where there's a wealth of information +[2:04 PM] +not sure how much they'd do with all of humanity's collective knowledge but +[2:04 PM] +I'm sure at least some of it will be preserved and useful +[2:04 PM] +and they could be told what happened somehow, we could teach them about AI risk from beyond the grave +[2:05 PM] +I think as far as ideas go this one is +[2:05 PM] +quite reasonable if you're okay with killing billions of people diff --git a/org/posts/framework.org b/org/posts/framework.org index 3ef862e..799b645 100644 --- a/org/posts/framework.org +++ b/org/posts/framework.org @@ -1,6 +1,6 @@ #+TITLE: Framework Laptop Review #+DATE: <2022-03-17 Thu> -#+MACRO: modified 2022-05-17 +#+OPTIONS:date * My Experience with the Framework Laptop ** Ordering @@ -95,8 +95,6 @@ On the software side, I feel like the GNU/Linux end-user ecosystem has come a lo Personally, I'm getting a rare chance to critically examine all the little config files, scripts, programs, plugins and workflows I have. It's fun to re-ignite the spark of join in configuring software and figuring out fluent, comfortable ways of doing things. I look forward to once more exploring and documenting the joy of computers...! <3 - - * Appendix A: Transient Terminal Sources =togglescratch= #+INCLUDE: "~/Scripts/togglescratch" src fish @@ -112,5 +110,3 @@ Personally, I'm getting a rare chance to critically examine all the little confi * Appendix B: lock.py #+INCLUDE: "~/Scripts/lock.py" src python - -/last modified: {{{modified}}}/ diff --git a/org/posts/grocery-log.org b/org/posts/grocery-log.org index 3158188..6d83aff 100644 --- a/org/posts/grocery-log.org +++ b/org/posts/grocery-log.org @@ -1,5 +1,4 @@ #+TITLE: ssdfsdfs -#+MACRO: modified 2022-04-27 #+DATE: <2022-04-27 Wed 14:46> * 09->26 @@ -78,4 +77,3 @@ #+TBLFM: @>>>>>>>>$>='(format "%0.2f EUR" (apply #'+ (cl-mapcar (lambda (num sw) (if (eq sw 'Dairy) num 0)) '(@2$6..@-10$6) '(@2$4..@-10$4))));L #+TBLFM: @>>>>>>>>>$>='(format "%0.2f EUR" (apply #'+ (cl-mapcar (lambda (num sw) (if (eq sw 'Bread) num 0)) '(@2$6..@-10$6) '(@2$4..@-10$4))));L #+TBLFM: @>>>>>>>>>>$>='(format "%0.2f EUR" (apply #'+ (cl-mapcar (lambda (num sw) (if (eq sw 'Other) num 0)) '(@2$6..@-10$6) '(@2$4..@-10$4))));L -/last modified: {{{modified}}}/ diff --git a/org/posts/stigma.org b/org/posts/stigma.org new file mode 100644 index 0000000..1d13dc4 --- /dev/null +++ b/org/posts/stigma.org @@ -0,0 +1,4 @@ +#+TITLE: Stigma +#+DATE: <2023-01-27 Fri 21:39> + +* Stigma diff --git a/org/sitemap.org b/org/sitemap.org index 400d06e..ee172c3 100644 --- a/org/sitemap.org +++ b/org/sitemap.org @@ -1,11 +1,16 @@ #+TITLE: Sitemap for project pages -- [[file:todo.org][TODO]] -- [[file:experiments.org][Experiments]] - [[file:blogroll.org][Blogroll]] - [[file:about.org][About]] +- [[file:todo.org][TODO]] +- [[file:experiments.org][Experiments]] - [[file:index.org][Index]] - [[file:snippets.org][Snippets]] - Posts + - [[file:posts/grocery-log.org][ssdfsdfs]] - [[file:posts/blog-tech.org][How this blog is built]] - - [[file:posts/framework.org][Framework Laptop Review]] \ No newline at end of file + - [[file:posts/framework.org][Framework Laptop Review]] + - Dairy + - [[file:posts/dairy/week-3-2023.org][Week 3, 2023, "Week of Systems" report]] + - Decisionmaking + - [[file:posts/decisionmaking/bad-arguments-against-become-arguments-for.org][Bad Arguments Against Something Can Become Good Arguments For It]] \ No newline at end of file diff --git a/org/todo.org b/org/todo.org index 8a8c203..9c74d5e 100644 --- a/org/todo.org +++ b/org/todo.org @@ -1,7 +1 @@ #+TITLE: TODO - -* literate dotfiles? -* How this blog was built -* project graveyard -* food thing -* fix picom.conf diff --git a/static/fonts/Roboto-Black.ttf b/static/fonts/Roboto-Black.ttf new file mode 100644 index 0000000..0112e7d Binary files /dev/null and b/static/fonts/Roboto-Black.ttf differ diff --git a/static/fonts/Roboto-BlackItalic.ttf b/static/fonts/Roboto-BlackItalic.ttf new file mode 100644 index 0000000..b2c6aca Binary files /dev/null and b/static/fonts/Roboto-BlackItalic.ttf differ diff --git a/static/fonts/Roboto-Bold.ttf b/static/fonts/Roboto-Bold.ttf new file mode 100644 index 0000000..43da14d Binary files /dev/null and b/static/fonts/Roboto-Bold.ttf differ diff --git a/static/fonts/Roboto-BoldItalic.ttf b/static/fonts/Roboto-BoldItalic.ttf new file mode 100644 index 0000000..bcfdab4 Binary files /dev/null and b/static/fonts/Roboto-BoldItalic.ttf differ diff --git a/static/fonts/Roboto-Italic.ttf b/static/fonts/Roboto-Italic.ttf new file mode 100644 index 0000000..1b5eaa3 Binary files /dev/null and b/static/fonts/Roboto-Italic.ttf differ diff --git a/static/fonts/Roboto-Light.ttf b/static/fonts/Roboto-Light.ttf new file mode 100644 index 0000000..e7307e7 Binary files /dev/null and b/static/fonts/Roboto-Light.ttf differ diff --git a/static/fonts/Roboto-LightItalic.ttf b/static/fonts/Roboto-LightItalic.ttf new file mode 100644 index 0000000..2d277af Binary files /dev/null and b/static/fonts/Roboto-LightItalic.ttf differ diff --git a/static/fonts/Roboto-Medium.ttf b/static/fonts/Roboto-Medium.ttf new file mode 100644 index 0000000..ac0f908 Binary files /dev/null and b/static/fonts/Roboto-Medium.ttf differ diff --git a/static/fonts/Roboto-MediumItalic.ttf b/static/fonts/Roboto-MediumItalic.ttf new file mode 100644 index 0000000..fc36a47 Binary files /dev/null and b/static/fonts/Roboto-MediumItalic.ttf differ diff --git a/static/fonts/Roboto-Regular.ttf b/static/fonts/Roboto-Regular.ttf new file mode 100644 index 0000000..ddf4bfa Binary files /dev/null and b/static/fonts/Roboto-Regular.ttf differ diff --git a/static/fonts/Roboto-Thin.ttf b/static/fonts/Roboto-Thin.ttf new file mode 100644 index 0000000..2e0dee6 Binary files /dev/null and b/static/fonts/Roboto-Thin.ttf differ diff --git a/static/fonts/Roboto-ThinItalic.ttf b/static/fonts/Roboto-ThinItalic.ttf new file mode 100644 index 0000000..084f9c0 Binary files /dev/null and b/static/fonts/Roboto-ThinItalic.ttf differ diff --git a/static/style.css b/static/style.css index 0ae4487..36422dd 100644 --- a/static/style.css +++ b/static/style.css @@ -1,21 +1,31 @@ +@font-face { + font-family: Roboto; + src: url('static/fonts/Roboto-Regular.ttf'); +} + :root { - --site-width: 70%; + --site-width: 750px; --vert-content-margin: 1.5em; --accent1: #d2e8b0; --black: #222; --white: #FBFBFB; + --background: #FCFAF9; + --font-size: 1.35rem; + --line-height: 1.9rem; + --font-family: "Roboto"; } body { - font-family: "Baskerville"; - font-size: 1.2em; + text-align: justify; + font-family: var(--font-family); + font-size: var(--font-size); + line-height: var(--line-height); color: var(--black); - background-color: var(--white); + background-color: var(--background); } -p + p { - /* Prose-style indented paragraphs */ - text-indent: 1em; +code { + font-size: calc(var(--font-size) * 0.9); } hr { @@ -65,6 +75,15 @@ a, a:visited { margin: auto; } +#publish-date, #modified-date { + font-style: italic; +} + +.src, .example { + font-family: "monospace"; + font-size: 1rem; +} + /* Set the colors in 
 blocks from the Leuven theme */
 pre                                      {background-color:#FFFFFF;}
 pre span.org-builtin                     {color:#006FE0;font-weight:bold;}
diff --git a/util/postamble.html b/util/postamble.html
index e3045a5..df0c961 100644
--- a/util/postamble.html
+++ b/util/postamble.html
@@ -1,10 +1,8 @@
-
+All code on this website is licensed GPLv3 unless otherwise indicated. 

+Blog proudly built using org-mode!