summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndré Fincato <work@andrefincato.info>2021-07-08 21:38:25 +0200
committerAndré Fincato <work@andrefincato.info>2021-07-08 21:38:25 +0200
commit9a1ed525c41a40d63b44cb42b55837ea5ab27232 (patch)
tree87eb5ab1ddb1dfde42f852e3b78b0df6aa659c3b
parentfe55bfa423553addada4bbf619c47663c991eb66 (diff)
W23-27 init
-rw-r--r--content/worklog/2021-W23-27.txt62
1 files changed, 62 insertions, 0 deletions
diff --git a/content/worklog/2021-W23-27.txt b/content/worklog/2021-W23-27.txt
new file mode 100644
index 0000000..428edab
--- /dev/null
+++ b/content/worklog/2021-W23-27.txt
@@ -0,0 +1,62 @@
+---
+title: W23-27, 2021-06-07/07-08
+template: worklog-entry
+---
+
+this time only four weeks have gone. ideally i'd like to move to a two weeks log period. calendars should have an options to show you time in a two weeks period, the current week and the next after — so you can peek at what is going to come up. instead calendars UIs are 95% very terribly done.
+
+## dae.wiki
+
+two weeks ago we released the git integration coupled with the "official" login system. or, we releaed what's i've been woking on for the past 3-4 months, together with a few other people here and there. massive last stretch till 4 am the night before the introductory test-session was presented to a particular group set working as employed at the design school.
+
+there's so much to clean up now, which it kinda feels good — cause i've been peeling off and re-mould so much code written by someone else (luckily), that it's like equally painful and a great feeling.
+
+we aim to release all these stuff officially in a few months for the beginning of the new school year. also need to work on documentation.
+
+and: i also began workign on a article about the process some weeks ago, but it was a huge first bursts, and could not emotionally handle it afterwards due to too much deadline work.
+
+## hd-filesha
+
+me and Karl held the online meetup session (on video)! small group but very nice convos. we plan to keep working on this and even use the mailing list framework to explore more ideas. this has turned out to be a random project that it's the most interisting thing for me so far.
+
+## buycloud
+
+got follow up call this week, sketched out plans for next chunk of work. interfacing with "real" weather data to construct how the cloud archive site should behave, Noa liked the idea. goed.
+
+## dps x magdx
+
+on hold due to me being in Italy and under deadline season. will be back from next week.
+
+we're moving back to proper calendar stuff, now that most other website tasks have been implemented.
+
+last session a month ago (?) (been three weeks in Italy already) i ended up reading more specs about icalendar stuff, i am not so excited about the XML-like data format at this point, but came across of self-hosted calendar server integrating with git — ahah. well.
+
+## TWLA
+
+other big deadline for this past Monday. 50% met it, 50% too brain dead and little time to finish the hard stuff: vector math, so SVG UI stuff, etc. overall good, need to dedicate more daily time.
+
+## h&d v2
+
+it's been on my mind, but haven't done much. last time i got lost and stuck in reading how bad the mediawiki syntax is (full of edge-cases, badly specified) and how hard it is to write a proper parser. but some projects exists, and in trying to make them work i got confused even more.
+
+at the same time, i got inspired by these two projects — which i would like to use / take most ideas from:
+
+ - [Onion Mirror Guidelines ("OMG")](https://dark.fail/spec/omg.txt)
+
+ > Always fast, one server request. No tracking ever, no javascript ever.
+ >
+ > Accurate URLs verified by PGP. No direct linking in order to protect against DNS leaks from accidental clicking in a clearnet browser.
+
+ - [PublicInbox::WWW (PSGI interface) design notes](https://public-inbox.org/design_www.html)
+
+ - archive-first website: deliver .mbox, txt and very very simple HTML
+ - no JS, pull-based reading experience
+ - ... i just like how much consideration is put on being widely accessible and how this influence the overall design (UI included)
+
+the influece from these two websites is mostly for the website archivability interests i have in building this v2 of the H&D website. pulling data from the mediawiki SQL, and put it into a git repo, where each HTML page can be downloaded as is, or the raw wiki txt format can be saved, or .zip of th website can be downloaded, or a git clone / pull can be performed.
+
+playing with setting up a .onion address would be a novely thing and something i got curious to try out. same for veryfing content and URL with PGP keys. many of these things could be seen as superflous, but all these things go in the direction of a document-based, wiki-based website. let's slowly keep explore how far we can push in implementing more and more wiki-like features with existing tooling.
+
+---
+
+> 2021-07-08, this morning i went to swim in the mountain lake with my dad, it was light raining after we got in the water. so dreamy.