W23-27, 2021-06-07/07-08

this time only four weeks have gone. ideally i'd like to move to a two week log period. calendars should have an option to show you time in a two week 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 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-moulded so much code written by someone else (luckily), that it's like equally painful and a great feeling.

we aim to release git+login officially in a few months, for the beginning of the new school year.

also need to work on documentation. and: i also began working on a article about the process some weeks ago, but it was a huge first burst, 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 from a random project to become the most interesting thing for me so far this year.

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 to proper calendar stuff again after the past 6 months.

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 some self-hosted calendar server projects 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, some SVG UI stuff, etc. overall good, need to dedicate more daily time to it.

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 exist, 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 many ideas from:

• Onion Mirror Guidelines ("OMG")

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

  • 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 in full, and the raw wiki txt format can be saved, and a .zip of the full website can be downloaded, or a git clone / pull can be performed.

playing with setting up a .onion address would be a novelty thing and something i got curious to try out. same for verifying content and URL with PGP keys. many of these things could be seen as superfluous, but they all 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.

tekken

i've been progressing during the last week of may and the first of june: finally having many bits coming all together. it's becoming a query-like program (eg pull data from disparate existing sources and build custom views with it).

i was joking i could spend an hour every other evening as a way to slow down and steam off, ideally it would be cool though i don't want to turn it into a stressful thing. that after five years of ideas and shy try outs i am getting at something feels pretty magical.

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.