That sounds more like a compositor problem - typically a client should not have control over where windows are placed, and that X11 allowed that got heavily abused with negative impact on UI. Wayland fortunately fixed that, so it is now up to the compositor where to place windows. Those can send hints, but the compositor is free to ignore them.
In your situation your compositor should remember where to stick the windows.
A big issue I see here is retroactively applying the new legislation. While I do think designers absolutely should be paid extra in cases like this I also think applying it back until 2003 like Sweden is doing is already too long - it violates the principle of legal certainty. It'd be very interesting for somebody to take this up to ECJ.
Applying it back until the 90s like in this case I'd expect them to have no chance - while again I agree that this lady deserved the money it also seems she might have a legal claim to continued payments back then as the company was referring to the legal situation no longer valid when they stopped the payment it'd be way beyond statue of limitations by now.
Legally I don't think she has a chance, morally I think the company should just do as she suggests and start that fund.
Outside of tech circles pretty much nobody seems to have noticed how bad google search has become over the least years - unfortunately there's no single search engine that's "general purpose good", like google used to be.
It's somewhat ironic that nowadays using metasearch engines often makes sense again - for those too young to remember, that was the default way of searching in the mid to late 90s, until google came along with consistently good search results.
I now and then check Tesla share prices after that kind of bad news - and to my amazement it just keeps going up.
That they're not really good at the car building part has been well known for quite a while - and by now it should be blatantly obvious even for people not doing software stuff for a living that they're also not stellar at the software thing (which I assume their valuation is mainly based on, as it doesn't make much sense). They are better at least with the infotainment software than established car makers - but given how those suck at it that's really not hard.
I don't really see them spreading too much in the EU currently - they're currently trying very hard to piss off the Nordics, and I'd expect to see regulation eventually prohibiting new cards with touch only controls. It already is treated like a mobile device by law here - so touching any settings on your Teslas touch screen while driving can be very expensive, up to a temporary loss of license. Also having an accident while touching the screen will shift more of the blame to you.
Back in 2001 we got ext3, adding journaling to the most widely used filesystem on Linux - which can just roll back transaction on next mount, while previously you'd have to run fsck to get your filesystem back to a consistent state.
A non-journaling filesystem was easier to get into a state where things were broken in interesting ways, as a unclean unmount had a higher chance of impacting critical data.
In the early days of journaling filesystems fsck was also quite lacking - so when things got bad enough that you did need fsck there was a decent chance you'd end up in trouble.
Nowadays both robustness of the file systems as well as quality of fsck have greatly improved.
As a company it is pretty annoying. I have an outgoing payment for what we ordered - getting a commercial invoice for random gifts worth 5 EUR doesn't help me much.
Few weeks ago had a lenghty discussion with one vendor which ended with him asking if I shut up if he gives me everything I need to make my own invoices with his signature and company stamp.
Summary judgment seems unlikely given the vagueness of the email.
In other circumstances that kind of phrasing would be interpreted of intent to commit illegal activity - so I'd hope large companies can't just get away with openly planning shit by just ensuring vague phrasing.
I'm not aware of any correct email validations. I'm still looking for something accepting a space in the localpart.
Also a surprising number of sites mess with the casing of the localpart. Don't do that - many mailservers do accept arbitrary case, but not all. MyName@example.com and myname@example.com are two different mail addresses, which may point to the same mailbox if you are lucky.
This is an Xorg thing - for wayland you'd have to implement that kind of functionality yourself.
Just checked, it seems to be still there, and exposed via xrandr, see the --panning option in xrandr manpage. So you should be able to somewhat dynamically resize the virtual desktop used via xrandr nowadays. The maximum virtual desktop size supported is determined by your graphics card - so if you'd want that some infinity thing you'd have to do that yourself and just throw a small part of the screen in the graphics buffer for rendering.
The bit where you have a small view on a large virtual display exists in xorg (I assume it is still there - when I used that it was XFree86).
You'd configure a virtual screen with whatever resolution you want, and your physical resolution generates a view on that which is moving with the mouse focus. I used to run a 1200x1600 desktop on a 640x480 screen until my girlfriend said she got sick watching me and bought me a large screen.
Might be useful if you quickly want to prototype the general idea.
Ugh, Nextcloud. It is always touted but it is such a pain to set up properly,
The problem is mainly maintenance - they do YOLO style database handling, so you can't miss any release or you have fun upgrading. Plus you need to kick it after installing to upgrade the databases.
Other services (like SoGO) have proper upgrade scripts, and automatically adjust the database schema from pretty much any version on first start after upgrading.
Big problem here is that Microsoft seems to have given up on sleep states, and just does S5 and then hibernates (which is horribly slow), so S3 on newer machines is often horribly broken in the firmware and can't really be used. I'm not really interested in my system going to S5 - I want it in S3.
Unless you have one of the dumbed down Fido or whatever only versions yubikey is just a smartcard with key storage, and multiple different applications for interfacing with the keys - and as everybody (at least everybody sane) uses the same crypto algorithms those can be shared for whatever needs that.
For SSH you'll have at least two options - if you have a GPG key on that thing just use the auth-key on there (create one if you don't have that yet) for SSH, if not maybe adding a PIV key is the better option, that should be available via PKCS#11 then. There might be additional options as well, though.
If you want to stick with that "one key" approach - get a hardware token like a Nitrokey or a Yubikey. That should also work with most Android SSH clients.
Yeah, things are getting to the point where just having a mobile device running Linux and using Waydroid for some useful Android applications is less painful than trying to make Android work.
That sounds more like a compositor problem - typically a client should not have control over where windows are placed, and that X11 allowed that got heavily abused with negative impact on UI. Wayland fortunately fixed that, so it is now up to the compositor where to place windows. Those can send hints, but the compositor is free to ignore them.
In your situation your compositor should remember where to stick the windows.