Pretty unhappy with my #VPS host. I think I might migrate at least a few services to some other provider. A bunch of the services I've written for my own use cases could technically also be uploaded to some standard webhost. That might be cheaper (and I do not need to care about server maintenance). Just thinking loud here...

Oh yes, #WorldOfGoo2 has been released today and it's available DRM-free for Win/Mac/#Linux: https://worldofgoo2.com/

Tomorrow, it's time for some nostalgia #WorldOfGoo #Gaming

A frozen 0.33 or 0.5L PET water bottle wrapped into some cloth is the most effective and cheapest trick I learned to get well through >25°C nights in my rooftop flat.

If you struggle with the heat, try it out! In my experience this is about as good as a ceiling fan, a lot better than table fans and a lot cheaper!

I finally transferred almost all my webtools to SimpleCSS, for example the #goaccess dashboard for privacy preserving web traffic measurements:

https://src.jayvii.de/pub/goaccess_dashboard/ (see it in action here: traffic.jayvii.de

Or other tools such as a barebones youtube-feed yt2html, twitch-feed tw2html, youtube-to-podcatcher service yt2rss, ...

I really like the idea of simple and classless #CSS. It helped me improve the visuals of my #PHP services quite a lot!

After a few performance improvements, I did some loading time tests for #serci, between my home network (wifi) and a random VPN where the service is running.

echo "html,redirect" | tee timestamps.csv
for i in $(seq 1 1 100); do
    HTML=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de)
    REDI=$(curl -o /dev/null -s -w '%{time_total}' https://search.jayvii.de?q=test)
    echo "$HTML,$REDI" | tee --append timestamps.csv
done

Across 100 runs for loading the site's HTML (generated from pure #PHP) versus a redirect to a chosen service (here the default #MetaGer), I can measure on average 0.28s for loading the frontend (HTML) and 0.13s for processing input and issuing the redirect.

I am quite happy with this relatively low overhead, although performance may decrease a little if more services are added (currently: 47). At some point maybe an #sqlite database may be more efficient than my pre-constructed #json files which are loaded on-demand.

New #serci updates:

• Adjusted Wikipedia Search URL
• Added more Services from around the wikimedia cosmos (wikidata, wikimedia-commons, wikinews, wikisource, wikiversity, wikivoyage)
• Added rotten tomatoes

Try it out at search.jayvii.de, contribute or self-host serĉi at https://src.jayvii.de/pub/serci/

Older posts about serĉi:

• https://social.jayvii.de/objects/tHRArkhwOLg
• https://social.jayvii.de/objects/Fm129h_hn_A

A question to #wikipedians: Is there a particular reason why different language pages on #wikipedia use different layouts? For example, German pages still use a lot older, non-adaptive page layout and does not have the new beta-option for dark mode, while the English pages typically use the latest design choices.

English / new: https://en.wikipedia.org/wiki/Wikipedia
German / old: https://de.wikipedia.org/wiki/Wikipedia

This is particularly gnarling because the language switcher is in a completely different location in both designs: old/German: left sidebar; new/English: on top, next to the title

Started working on some tiny #ktistec end-user hacks: https://src.jayvii.de/pub/ktistec-tweaks

For now only a user #CSS theme i dupped "purple-ish": https://src.jayvii.de/pub/ktistec-tweaks/file/css/purpleish.css.html

Maybe more to come in the future. Or not, we'll see :)