Magnus Åhall

The Kame ipsec project (https://www.kame.net) has a turtle image which is animated if visited with an IPv6 address.

What, no websocket-based realtime statistics for number of total, daily and hourly mistypings?

I’m horrfied every day at work that copy/paste still is an issue. All my coworkers and customers are still struggling with copying some data, switching to another program, pasting it, switching back, copying some other data, and so on, especially when needing two or three data frequently.

In Windows, a (bad) solution is using win+tab, which literally no one knows about, much less uses.

In Linux (and should be in Windows too), it is trivial to implement buffers (say 0-9) to store and retrieve clipboard data for subseconds access.

Javascript/Preact/Lesscss on frontend with a backend written i Go, using Postgres for data needs. Sometimes with websockets in between if needed.

Author turned TCP/IP off on the server ☺

I have taken up the habit of being at work one-two hours before anyone else.

I get undisturbed, effective work done, and I leave earlier. More work done, more own time with family each day.

I’m still reachable through phone, add can fix most catastrophic problems from home, but that is so seldom occuring that it is OK, and collegues don’t complain about me not being in office after 15:00.

You are completely right about SwitchOS, and it is even more exciting that some models sells in two versions, with the only difference being called CSS* for SwitchOS, or CRS* for RouterOS. And the SwitchOS-enabled model is much cheaper, so customers ordering for themselves almost always pick the wrong one (that is, SwitchOS, which we can’t manage properly in our automations and other software solutions).

Can only agree on Mikrotik routers. All are using RouterOS, which works the same on all their devices, from routers to switches and access points.

They are relatively cheap for the capabilites you’re getting. They have their own scripting language, two APIs (their new one is REST-based).

GUI (winbox is recommended, and plays nice with wine. Wouldn’t recommend web interface, just cumbersome) and CLI exists.

They have a lot of builtin functionality, like DHCP server, DNS server with static configuration, and even file sharing. Some models are powerful enough to run Docker images on (yes, that’s builtin…).

We’re running a couple of hundred and don’t have much problem with them.

Depending on what one is doing, placing pv in between (usually with -s to specify size of data if known in advance) gives a progress bar, with speed and size of data passing through.

Say you have an SQL dump of 1048576 bytes:

cat dump.sql | pv -s 1048576 | mysql somedb

and now you know how far it is instead of just waiting :)

I liked the look of Dashy, but it felt somewhat too heavy software for the simple dashboard I needed, and so I wrote the first version of Dashie.

It only uses Javascript and doesn’t need any server components except a webserver. Configuration is done by editing YAML files.

Themes are implemented, and multiple pages which can be used to make more complex navigation of multiple dashboards.

Check it out :)

https://git.ahall.se/magnus/dashie

I have a 49" ultrawide, running a tiling window manager under Linux.

I heavily utilize virtual desktops in my workflow. Always 10 on each monitor, accessed by Ctrl-{0…9}. Switching between monitors by AltGr+{1…n}. Programs always stay on the same virtual desktop no, so terminals on 2, browsers on 3 and so on. This enables me to access more or less any window in under a second, never having to look for it visually.

I usually work with 4 or 5 24" monitors, as a single program seldom needs more space for me. What he ultrawide brings to the table is the capability under Linux to create arbitrary virtual monitors.

I can for example have two evenly created monitors (two 27"). My usual for development is three, split as 2:3:2.

Another possibility is using a small script that analyses movie resolution and creates two monitors, one with the exact aspect ratio of the movie, eliminating black borders, and another for using while watching said movie :)

As Linux sees them as separate monitors, I can also have easily managed screen sharing.

Having the flexibility of software defining my monitors has been great as a developer; separation of many, screenwise often small, applications is highly useful to me. A couple of quick scripts to switch between different setups has integrated it nicely into the workflow, and I usually changes monitor config at least a couple of times per day.