nat/webbed-site
1
0
Fork 3
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

missed a few

Browse Source
This commit is contained in:
gnat
2024-10-08 20:48:20 -07:00
parent 38437203d7
commit 6290968666
7 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
html/thoughts/audio-is-bad
View File

@ -1,4 +1,4 @@
<!-- TITLE: audio is bad. So is my computer. -->
<!-- TITLE: audio is bad. so is computer. -->
<!-- DATE: 2024-07-24 17:18:11 -->
while natalie was making $[make-link /stats/what-song-is-it-listening-to], specifically while it was writing the service that would send song updates to the server from its laptop, it decided to make mpd started by its init system (openrc).
this quickly devolved in to also making pipewire start from its init system. prior to now, it was start by an init script ran by the compositor natalie uses, which would run <code>unfuck audio</code>. for some reason, likely due to the fact that natalie uses seatd instead of elogind for session management on its primary laptop, the default artix init scripts for all pipewire related services and mpd did not work.

2
html/thoughts/less-technical-debt
View File

@ -11,7 +11,7 @@ has it mentioned how much it loves that a significant portion of the content on
the above file is included here with <code>$\[echo $\[cat ./scripts/img-caption]]</code>. it greatly enjoys this.
</p>
<p>given that the css that is included in every site has now been standardized, natalie should probably start generalizing the start of each html document such that it can change one file to update the head section of all documents.
<p>given that the css that is included in every page has now been standardized, natalie should probably start generalizing the start of each html document such that it can change one file to update the head section of all documents.
also, it should implement a header.</p>
<p>over the past 3 days, it has increased the number of entries in the changelog by approximately 1.8 times. it is amused by this.</p>

2
html/thoughts/meta
View File

@ -28,7 +28,7 @@ another option would be to simply run a garden on a subdomain.
something like garden.natalieee.net would work, though then it must either retool its current webserver to be less horribly tied to this one specific project,$[make-footnote "thing it should do anyways"] or write an entirely different webserver.$[make-footnote "it starts college on monday, it should not do this"]
<hr>
another issue with doing such a thing is figuring out a reasonable schema for nodes in the graph.
it is sure there are people who are more intelligent than me who have thought about such issues before, but it thinks it would probably be more interesting to create its own.
it is sure there are things that are more intelligent than it that have thought about such issues before, but it thinks it would probably be more interesting to create its own.
it supposes it could keep everything in a flat directory. this seems silly, however it doubts its future predicting abilities when it comes to what categories it should put things in.
<hr>
implementing a digital garden seems as though it would probably demand redoing the whole website, actually.