Things to do with Claude on the Week-End

See also the list of Things I did with Claude on a Week-End.

Fix wz indentation

I feel there's a better way to break lines in wz's tooltips (in particular) and in citations (in general); see for instance the horrendous indentation of Love's opening citation, and how the most perfect prose can be butchered by wrong line breakings:

Use my phone

I'm resisting using the phone which I see as a black box that is difficult of access except as a passive user. With AI, however, it's probably possible to make the most out of it, starting with cleaning all those viruses and pop-up that constantly shower me with stupid notifications. I already implemented a basic 𝕐 feature to upload directly phone-camera photos to the server; this could be made better (faster, offline, etc.)

Recover my old blog

This looked like a nightmare since I promised I'd do it one day: importing my old Wordpress blog to laussywiki. For AI it should be a piece of cake. Install the corresponding tarball of the time, make the conversion, and done. I should then recover my beautiful Gaudi and Sagrada Familia posts.

Optimize the site

The site can be quite sluggish. It has a lot of functionalities. AI could help optimizint it, which is both a complex and dangerous process!

Develop Laussywiki bots to maintain and tidy the site

One such bot should take care of things that get broken upon upgrades, such as broken youtube videos, or broken equations, or even broken references, e.g., as seen in my Blog post on CSI with frequency-filtering (a lot got broken here).

Another bot should clean behind me, such as removing the emtpy <wz tip=""></wz> put by automated figure uploads. Not a big deal, but if this can be cleaned, why not? I like the idea to have a swarm of little bots cleaning the mess after me. Such a bot—let's call it M-O—could be upgraded as time passes and realizations strike with a list of things to keep tidy. Another example is the double periods after citations or misplaced punctuation in references, e.g., (the comma should be put before the reference). Here's an example of doubled periods, with the expanded Spontaneous coherence buildup in a polariton laser. F. P. Laussy, G. Malpuech and A. Kavokin in Phys. Stat. Sol. C 1:1339 (2004). . I would have to keep M-O off this page too so that it doesn't clean it!

Here's a list of things for it to do:

1. remove <wz tip=""></wz>
2. fix template punctuation
3. fix broken bibTeX templates (redlink: populate them with bib2wiki)

Restore Right-Click Image Menu services

There was some nice KIM service-menu way to get essential shortcuts at the tip of your ring finger but this became nightmarish to install and maintain, so I essentially gave it up. Claude could probably bring this back in an efficient/portable way, to do things like:

• Compress images
• Move files (say to bib repository)

etc.

Redact yeets

Add a functionality so that only bit of a yeet is disclosed, possibly with an embargo. Something like this:

I have shown that ██████████████████████████████████ doesn't apply in the problem of ████████████████████████████████████████

The remaining 2kiB characters of this yeet have been embargoed until further notice.

I wouldn't like to use it, though.

Deep-zoom panoramas

Extend {{pan}} so that it loads a suite of images as one zooms: a first picture that can be zoomed down to some level, then higher-resolution tiles that take over as one zooms further, each level twice as fine as the previous one and only the visible tiles fetched. Like this, people who never zoom don't download a 260 MiB file, while those who do can go down to the most minute details. Since my figures are drawn from data, the tiles could even be rendered directly at the resolution they need rather than cut from one giant picture. To be settled: where the tiles live (hundreds of File: pages, or a folder on the server). Not needed now, but it will be when we enlarge the scope of panoramas such as Fig. (0OG5J).

Kanban

Design a tailor-tuned Kanban (かんばん) service to organize my tasks, called kairos (Greek: the opportune moment).

Platform. Build it on the best available open-source Kanban/board framework, backed by an SQL database and running in the browser on localhost. Everything must be stored in the database.

Board. Four columns: To-do, In progress, Waiting and Done. An alternative calendar view should show the same tiles laid out in time.

Tiles. Each tile is identified by its AF tag and carries:

• Priority: a category (Now, Urgent, High, Normal, Low, Maybe) plus a score from 0 to 10 within that category. Priorities should evolve automatically as time passes and deadlines approach. Tiles are piled up according to priorities.
• Dates: a start date (or should-start date), an official deadline and a hard deadline.
• Group and colour: tasks belong to groups, each with its own colour, and groups can have sub-groups shown as shades of that colour. For example:
  • Papers (green): each sub-group is a manuscript with its codename, e.g., Ergoli, and its own shade of green. Use pleasant shades only.
  • Microcavities (purple): broken down into chapters or other tasks.
  • Admin (black), Glosses (brown), Fun (yellow).
• Expanded view: clicking a tile reveals its attached content, links to llw and wl, notes, statistics, and so on.

Time tracking. The service also manages time. It records how much time is spent on each task and when, and time spent on sub-tasks adds up to the parent task. Time can be attributed automatically through the virtual desktop that has focus. For example, if Emacs is editing a paper on a given desktop, all time spent on that desktop counts toward the corresponding task, or even better, map Emacs buffer file paths or window titles to tasks, so that two papers open on the same desktop are told apart. Same with gmail, llw, twitter, etc.

Idle detection: stop the clock when there is no input, and ask on return whether the gap was thinking time or a break.

Everything should allow for Manual corrections, since an automatic log will be wrong sometimes, so make it easy to edit after the fact.

Estimates vs. actuals: store an estimated duration per task and report my personal calibration ratio. Most people underestimate by a stable factor, which kairos can then apply to its suggestions.

Aggressive storing: every status change, move and time slice are logged as events, so that any statistic can be reconstructed later, including ones I haven’t thought of yet.

Attention entropy: a single daily number for how scattered time was across groups. A nice physicist’s metric for time-tracking, to watch over months.

Wanted since 0Qmsy (af).

𝕋

Coupled 𝕐 to 𝕏 through 𝕋, i.e., add a □ button to 𝕐/ℤ posts that limit them to Twitter's size limit and post a copy online.

Sync llw & lw

I had my own suite of synchronising the online and local sites, but this was limited to 𝕐 (see syncY). It would be convenient to have it apply to the whole site.