We have had the opposite problem in the past. A cert provider requiring us to exist in certain international directories of companies took weeks of waiting around on bureaucratic red tape.

Then they didn’t even call us to verify our existance, place of business or anything (yeah, this was one of the big certificate providers a long time ago).

Their website was horrible, and their support wasn’t better.

LetsEncrypt though hasn’t failed me once since it was setup, and that is over hundreds of domains with thousands of renewals.

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

Not exactly that layout, but I can strongly recommend MessagEase. Also optimized for phone use.

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

I was made aware of Lemmy through links on reddit, with the whole API horror show.

Also most happy about it, and although I’m still not that active, I’m participating a bit more now. It definitively feels better to contribute to a group effort like Lemmy than to a large corporation that makes me the product.

Somewhere along the lines of 10-15 years?

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.

If anyone is using specifically n8n and would like a small backup/change log, I could provide the workflow and the frontend code. A small change of n8n webhook URL is probably only what’s needed to get it running.

Yeah, tried that first, but the read onlyness was a slight problem :)

The look of ungit would confuse my users I’m afraid.

In the end I whipped up our own solution, with the added benefit of it being more efficient to the problem domain.

Take a look at https://files.ahall.se/n8n-gitted.mp4 where I demonstrate the functionality. The user makes changes to the n8n workflows, goes to the git system page and syncs the workflows to the git repo residing on the same docker as the n8n instance. User can then choose workflows with changes that are to be commited, types a message and is done.

Selecting an earlier commit does a git checkout on that commit and shows the files. Clicking on a file copies the contents of it. In this case, the workflow can be pasted into n8n and the user can pick and choose what was desired to bring back.

The git system page is static HTML and javascript, and communicates through webhooks to a git workflow in n8n. https://files.ahall.se/workflow-git.png

Only if it doesn’t need to be run in electron and can be embedded in a webpage, running with a git repo local to the kraken installation.

It will be used to put changes to n8n workflows into git repos. The n8n software is in the browser, and I can extract the workspaces and write them to a directory on the server, but the n8n users will not have access to this directory, nor are they especially well versed on git. Simple staging and commiting would be ok though.

Found a long list of git clients and among them found git webcommit and ungit, which seems to fit the bill. Still browsing the list, so haven’t had the time to try them out yet :)

I guess that means able to access services on the Internet over IPv6, not me being able to get a /64 and providing services myself to others.

Sort of ok for phones I guess, although not as great if someone doesn’t have access to fiber and have to use a mobile link in a residential environment.

Bahnhof actually just provides NAT:ed fiber connections as well as default, but will issue a public, unique IP if asked (at no additional cost).

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

In Sweden we have just one ISP for non-commercial customers providing native IPv6 adresses (Bahnhof) on fiber connections, and even then we can’t get a static prefix from them.

Not quite sure on the mobile ISPs though.

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.