Let’s be careful how we phrase things here. JavaScript form submission and navigation are choices, not needs.

Also, progressive enhancement / graceful degradation exists. When competent developers (or their bosses) want script effects on our sites, we can include them and make the sites continue to function with scripts disabled. It might require more work, but it is absolutely possible.

Framing the script-based approaches to these things as if they were needs contributes to the problem, IMHO.

(I am referring to the vast majority of web sites, of course, not special-purpose web applications like games.)

Web developers are complicit in browser fingerprinting, by insisting that sites require JavaScript (or WASM).

All of us are complicit in browser fingerprinting, because we tolerate this script dependence.

IMHO, a web site being allowed to execute arbitrary code on visitors’ hardware should be an anomaly. The vast majority of them could be built to deliver the same information without requiring that inherently dangerous permission.

If you put a SIM into a phone that has power and cell access, then an association between the SIM and the phone’s IMEI will be recorded somewhere.

If your identity is linked to that SIM, then it’s only one more step to link your identity to the phone, of course. You’ll have to decide for yourself whether that’s unsafe for you.

human brains are weirdos.

Truer words were never said. :)

the reason people post pictures of text is to give proper attribution, but also to distance themselves from the content,

If only we had some way to reference an original source. Something like a figurative link, if you will.

If only there was a way to copy text, and then paste it someplace else. Sigh… unsolved problems.

0. Getting users to post text instead of screenshots of text.

It’s also behind a third-party captcha service, which can fingerprint your browser, and collect a history of which articles you read and what pages you come from to view them.

Last I checked, archive.org usually didn’t work when articles are paywalled. Has that changed?

In my experience, it depends on when the snapshot is made. If made early enough that the paywall was not yet in place (probably because publishers want their articles to be indexed by search engines) then it will not have the paywall.

One nice thing about archive.org’s mirroring is that they list all their snapshots of a page by date and time, so if the latest one contains a paywall, you can sometimes go back to the first one and find it with no paywall.

It would be interesting to see the annual global power consumption from design choices like this.

If I wanted to do this, I think I would start by getting to know the IT staff. This would:

• Help me to understand the challenges they face in getting their work done: what’s problematic for them, what’s helpful, what skills they already have, etc. This would eventually guide me in how to approach suggesting changes with minimal friction.
• Make me a familiar person to them, and allow opportunities to build trust in my skills, knowledge, and judgment. If this is established before I ever suggest a change, it could avoid some of the doubt and resistance that would surely come if a stranger walked up and pushed for changes. I want to be a friend, not a foe.
• Potentially identify an ally within IT: Someone who might already want to make the switch (perhaps because they’re tired of Microsoft’s BS) or at least agree that it would make sense. An ally on the inside would not only make it easier to get others to seriously consider the change, but also potentially help gather information about how MS Office is currently being used so that I could prepare equivalent LibreOffice workflows for users who need them.

I suggest taking your time, and saving Linux for later so that it doesn’t create more friction against moving to LibreOffice.

Hm… Those options make it seem like like you’re configuring a widget within the panel (like the application launcher and task manager widgets) rather than the panel itself.

It’s possible that the options we’re looking for were moved in Plasma 6, but I don’t have a Plasma 6 installation at hand, so I can’t look for their new location. Maybe someone else who sees this will be able to.

Looks like a promising effort. I just wish their notion of “first-class Qt support” included Qt Widgets.

Or, if they’re unwilling to do that, exposing in Qt Quick the missing functionality that has been available in Qt Widgets for ages.

Your screen shots look like you right-clicked the desktop and selected its edit mode. Unfortunately, I don’t read German, so I don’t know what to make of the text shown there.

What I’m describing requires right-clicking a blank area of the panel and selecting its edit mode. When you do that, a bar should appear with buttons including Add Widgets, Add Spacer, and More Options.

Tested in Plasma 5.

Current web browser engines generally support JavaScript and WebAssembly, and no others (unless via a plugin, as with Java).

So, if I understand you correctly, your options are to find a language that transpiles down to one of those two (several such languages exist), or find an engine that isn’t precisely a web engine but supports some alternative language(s). I don’t know any useful examples of the latter, but perhaps someone else will chime in with something like that.

Can you clarify what you’re asking for?

If you mean a web browser that isn’t based on Firefox or Chromium, the Ladybird project might fit.

If you mean a web-like platform that doesn’t use fancy things like JavaScript, HTML and CSS, there is Gemini.

Do you mean something else?

Those are your desktop panels. This might help:

• right click a blank area on one of them
• Enter Edit Mode
• More Options…
• Visibility: Windows Can Cover

FWIW, they don’t normally show when a game is in full-screen mode. Is it possible you changed a setting from its default, or that the game (or your Wine/Proton version) is using a fake full-screen mode?

If you’re okay with Qt Quick, rather than Qt Widgets, start following the Qt Bridges project.

KDE development isn’t limited to a fixed number of developers. Lots of the things that go into it are contributed by regular users who want to see something improved.

You might be able to prevent a particular touchpad from affecting the desktop with an xinput disable command. Run xinput list to show the available device names and IDs, or man xinput for more details.

Another approach, assuming you’re using an X11 session (not Wayland), would be to disable the device in xorg.conf.

A custom udev rule could also do the trick, although it might be more complicated than an xinput command.