If you've settled on Gnome then you don't have to change anything. Gnome will change it for you. Regardless of you. I really miss Gtk3/4 File->open dialogs having the ability to take pasted filepaths without erroring out.
But I will hand it to Gnome: they're the only wayland protocol desktop that supports accessibilty. That's huge. So even if I hate how it behaves right now while mostly sighted Gnome DE may be the only option for me in the future. And I guess I won't have to look at it when my retinas finish falling off.
Cloudflare's only goal here is to put themselves between everyone and charge a toll. They are running a protection racket where they themselves are causing much of the damage they offer protection from. This is another example.
No. You're assuming that you don't have control of your own computer.
Think about the pitch for removing the feature, "So, we're going to make this in the OS, where visually disabled users cannot highlight anything in any application, can't move text between applications, cannot get the window title, cannot get the window tree, cannot have applications automate or know where other applications are, and basically they won't be able to use their computers. But everyting will be super private. Even the human using the computer won't be able to read it." This is what modern linux desktop computer is on waylands thanks to this toxic privacy meme. It literally just doesn't work for me.
Privacy needs the kind you're talking about simply don't exist on desktop computers where the human actually controls everything (as opposed to smartphone model where the user controls very little and applications are hostile and opaque). If you want to break accessibility and functioning of smartphones, fine, go for it. But leave desktop computers alone.
Unfortunately, we are living in a world where we need to treat every third party application that we run (and in some cases, even the operating system itself) as a hostile attacker.
Gone are the days when you could download a software, run it, and trust that the developer isn't transmitting everything on your system back to their servers. Developers have poisoned the well and repeatedly demonstrated that they will run roughshod over the user's system, send telemetry back about everything the user is doing, enroll them in A/B experiments they didn't ask for, and take advantage of every resource, every peripheral and device, and every bit of personal information they can get their hands on.
Unless you are 100% running open source software that you have personally vetted, or that you trust that the package manager / maintainer has sufficiently vetted, you can't copy a password into the clipboard with any kind of confidence that other apps aren't sneaking a peek.
Let's assume I have control of my own computer. On this computer with Linux and X11, how do I restrict programs (such as Zoom client) from accessing the clipboard?
Narrowly, I don't think there's any technical reason why a better clipboard couldn't require the user to specify where to send text ("paste content into application X field Y") and then handle transmitting that data on the user's behalf. That way, the clipboard wouldn't be readable global state without intent.
The paste intent doesn't seem antithetical to accessibility. A keyboard combination states intent just as effectively as a voice command, mouse input, or other source.
Accessibility apps naturally require privileged access to other applications. Using the clipboard for accessibility is a hack though, as its intended purpose is occasional generalized data transfer. Also, Zoom isn't an accessibility app in the first place, and all capabilities it needs should be opt-in.
What are you going on about? Why shouldn't there be some temporary authorization prompt for clipboard access? You could even wire it up to control-V somehow such that the same keystroke would grant temporary access and communicate a paste to the application. Nobody is talking about making the clipboard unusable.
Seems like you think people catch lake sturgeon to eat them. This is a very rare thing these days. Sturgeon fishing is almost always catch and release. This doesn't mean there aren't any fish killed. Any catch and release is quite stressful and might kill one. But people aren't just eating them and sturgeon are quite robust. And there's certainly no commercial fishing for them like the issues with ocean/marine ecosystems you're describing.
At least in Wisconsin rivers/lakes you cannot legally keep any sturgeon with the normal fishing license. You have to pay an extra fee to keep 1 (per season). And according to the statewide Wisconsin statistics only 5 sturgeon were harvested from the St. Croix River in 2025, and a total of 58 were harvested across the entire state.
Years again I was gifted a sturgeon fishing trip on the Fraser and I still feel bad thinking about it. In hindsight knowing how much we stressed and probably harmed that animal. What a cruel way to entertain ourselves.
I personally only fish to eat these days. And I still sometimes feel bad about hurting them and ending the lives. I comfort myself knowing that most fish I catch are not very intelligent and that it is certainly less torture and a better life than, say, a factory farm pig with very high intelligence. And since I am doing the killing myself I do it quickly and minimize suffering. I know whataboutism isn't a strong argument and in no way refutes your point about catch-and-release fishing enjoyment coming from the fishes' struggle and suffering (in what capacity it has for this).
I accidentally caught 1 smaller (~meter length) sturgeon while fishing for the very tasty walleye (fish). I certainly enjoyed the "fight" in which the fish was suffering and it didn't really occur to me at the time. But I did return it to the water quickly.
I hope this kind of thing means Rust stops making so many rapid breaking changes in th compiler. I've tried it twice, once in early 2021 once 2025. Both times I tried to compile a few random projects I found on the web, stuff like a wordpress fanfic scraper, a software defined radio program, etc.
In 2021 my linux distro I was using had just been released 3 months prior but it's rustc already could not compile 2 of 3 projects due to the use of new features added to rustc in those 3 months. In the SDR case I knew the author and he was able to re-write it in more general rust code and it worked great. In 2025 my linux distro had been out for a couple years. None of the rust projects I tried would compile with my rustc.
Rust, in the past, seemed a very bleeding edge, move fast and break things community. I hope that with more people using it in more places the demographics change and people won't always target latest and greatest. A lifetime for the compiler of at least a few years would make it a very useable language. Adoption at microsoft might help this.
You can compile any old code with newer rustc as long as old project does not use unstable features that have changed/went away. What are you on? I recently recompiled project from 2015 with latest stable rust just fine.
All breaking changesin rust done via editions and you can mix-and-match editions.
I suspect GP is using system rustc to build random projects off of github and doesn't use one of the distros that actually updates rustc, like Fedora, SuSE or Arch.
Then the conversation is about forward compatibility, whether developers should wait X amount of time before using new std APIs or features, and whether the ease of using rustup and project expectation of it being accessible is reasonable or not.
It sounds like you are not running into breaking changes, you are just running into projects that like to use new features that are not available in your older compiler.
Correct. From the point of view of a stable desktop LTS system the code that the typical rust developer writes breaks within a few months as it starts using features from latest that are forwards compatible.
Growing proof that autonomous cars save lives in cherry picked temperate and clear environments that don't get things like snow. The article mentions this point and acknowledges it is a serious problem and then just leaves it at that as if it doesn't completely demolish the entire argument they're making. They don't try to refute it or anything.
>How Does Limited Fair-Weather Data Compare to Traditional Crash Statistics?
>A key question is whether Waymo’s robotaxis, currently limited to fair-weather operation in a handful of cities in the U.S., are directly comparable to humans driving a wider variety of roads in much more variable conditions.
That's literally all they say about the subject before moving on to talking about incomplete sampling of true crash rates.
It is fun. Now make it multiplayer over websockets/etc with some dev controlled signalling server (who peers register with/etc) and STUN check to get peer IPs locally.
Blackmagicdesign corporation's Davinci Resolve doesn't run on most OSes. So I can't tell you. But I can tell you that openshot allows me to edit videos quickly on linux. I like it.
No it doesn't. It runs on Windows and Mac. With a complex setup of wine or wine derived software you can create a windows compatibility layer and sort of run Davinici Resolve on linux. But just a random distro and random wine won't do it. There are containers like Davincibox Q too. But of course while this is "running" on Linux it is buggy, will have codec problems, and is still not really running on linux. Don't even try if you have an AMD GPU. And every time you reconnect to a new wifi AP it'll make you re-enter your license key, no sound on most linux distros that have ever existed, etc. It's not a good or even decent experience.
A torrent is fine. Things will settle out and the torrent with it's seeds, just normal people with normal human motivations to do so, will still exist for a long time. No need to bring in money and ruin things.
reply