For me is the lack of virtual displays is Wayland.

I’m using a 49" monitor (with i3) and split it into virtual monitors/displays. For some tasks two displays are good, for others three, and all doesn’t need to be the same size.

The reason for not using i3 splits is that many programs have fullscreen functions that I often use.

Watching a movie is one example, where I have a script that automatically calculate the optimal width without borders and gives me an extra virtual display beside with whatever’s left.

“Crime was always with us, he reasoned, and therefore, if you were going to have crime, it at least should be organised crime.”

I’m also using it to script sessions of workflows with many programs, for instance a dev environment with a lot of microservices. Some windows with multiple panes each.

This kind of reminds of the BlackDog: https://en.m.wikipedia.org/wiki/BlackDog

It was a small computer that easily fit in a pocket and only had a single USB port. That was connected to a computer which powered it, and it connected as a virtual CD-ROM drive.

On that was an xming X11 server. The BlackDog ran your applications outputted through it. The applications it ran could also access the Internet through the host computer.

I’m using a 49" monitor and dividing it up in virtual X11 monitors/screens for flexibility. Running a tiling window manager with lots of virtual desktops, but with fullscreen support separate monitors are still needed. Wayland are still missing the support for dividing up the display, which is probably the last thing keeping me on X11.

They would have had my wife locked up then, who has a lot of Hello Kitty gear and clothing, now being 45 years old :)

Phew, looks good on the news with the packaging bug (if they didn’t just got cold feet for worse PR/backlash than they expected and this is a backtracking).

In this case, hopefully Garcia is employed for his expertise and can be deployed to further open source relations :)

I’m running a couple of Vaultwarden instances, and it would be really nice if Bitwarden employed Garcia to improve the Rust backend. But as the bitter cynic I am, I guess it is an effort to shut down and control as much of the open source use of Bitwarden as possible.

The worst case, someone will most likely fork Vaultwarden and we can still access it with Keyguard on mobile and the excellent Vaultwarden web interface :)

Daniel García, owner of the Vaultwarden repo, has recently taken employment for Bitwarden.

The plot thickens.

Same - Evolution offers one thing Firebird dosen’t - connecting to the work cloud Microsoft account!

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.

First thing I do on a new laptop is remapping a key I won’t be using much to Insert, which I use all the time :)

What if they DIDN’T have a chip in the ink cartridge, and just used it as a container that could be refilled and used in every printer they made? No hacking the cartridge then.

No, that’s crazy talk!

Big bucks for big trucks?

Been using the Kensington Expert Wireless a couple of years now.

My go to smartphone keyboard is MessagEase. A few larger buttons instead of many small. You can get quite fast on it, and larger buttons means fewer mistakes.

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

In Sweden we have had a version of self checkout for 20 years in the largest stores, and here it seems to work fine.

Instead of having to scan everything at a station, each product is scanned with a handscanner when walking through the store, and put directly into shopping bags. Then only the payment and possibly a randomly occuring verification is left before leaving the store.

The random testing is usually just an employee scanning three to five items from your bags, and occurs like once every four months (as long as you’re not actually stealing and caught).