superkuh

I used to think techrights was biased but told the truth about the biased slice of things it did cover. Then the Freenode hostile take-over happened and I was right in the middle of it and techrights lied repeatedly about it.

Techrights is not a news source. It's propaganda and full of lies.

Excellent to read Tk is getting better acessibility support. I love using it for quick little Perl/Tk GUI applications but I'm also slowly going blind from retinal tearing. It's good to see progress in some GUI toolkits when major desktops like KDE have dropped accessibility in their latest releases.

I agree. Individuals have the right to chose to damage their bodies if they wish. And laws already exist covering hurting other people while irresponsibly intoxicated. I see no reason to try to use state violence to prevent people from hurting themselves with alcohol. This doesn't change that alcohol is a poison and seriously incapacitating compared to say, cannabis.

Indeed. Alcohol is so much more dangerous and damaging to peoples lives and the lives of those around them that it doesn't even compare. Alcohol would never be legal if discovered today. Compared to alcohol the risks of cannabis are a rounding error.

But that's only because alcohol is so incredibly dangerous. There is real risk with inhaling particulates and burning gases into your lungs. And it should not be ignored. It's just that compared to the lives ended by alcohol it is a rounding error and that makes it seem safe. Neither are.

It's not that some URLs change over time. It's that ALL URLS EVER suddenly stopped working all at the same exact time. This was the wholesale destruction of everything built on that darkweb. Nothing like it has ever happened to the clearnet web and nothing ever will. It is likely to happen again on Tor. And that is what I am warning about.

I also recently acquired some free e-waste android 6 devices (like a galaxy note 4 pad and a moto 4 phone). Using some vibe coding I was able to setup a dockerized build system for java/kotlin apps and managed to make a number of custom applications for the devices like turning them into timelapse+mjpeg streaming cameras (or irc client, or ice thickness estimation from chirped sounds+dsp). Since they're ewaste I don't mind if they get destroyed or lost.

Oh, and all the links got re-written to the new URLs then? Between every site? No, they didn't. If every link breaking, every write-up about sites, every single reference across the entire .onion web breaking doesn't seem like a problem to you I'm not sure what to say.

Yeah, some sites told their users about their new v3 domain. But the web was entirely destroyed.

A better bug covering this is at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147093

Basically for bullseye users with the bullseye-security repo in use there were packages that should have been included in the final point release before they (in bullseye-security) were deleted, instead there are some broken dependency chains because they weren't.

One doesn't need -security updates for bullseye, and this isn't about security or asking for extra extended support. It is about the repos not being in an independent state when bullseye-security went away. And this broke existing installs.

For others with the issue finding this post the mitigation is to use the snapshot servers:

    deb [check-valid-until=no] http://snapshot.debian.org/archive/debian-security/20260903T220410Z/ bullseye-security main
    deb-src [check-valid-until=no] http://snapshot.debian.org/archive/debian-security/20260903T220410Z/ bullseye-security main

The one thing I learned from hosting superkuhbitj6tul.onion (from a home computer) for ham radio and science stuff for about a decade was that EVERYTHING ON A .ONION IS EPHEMERAL. When the tor project correctly decided that for high security torv2 no longer was anonymous enough they unilaterally wiped out every torv2 .onion site that existed. Every link that was made between these sites came to an end in 2021 when they released a tor client without support for torv2 onions and tore the web to pieces.

Know this: the "dark web" is not for people who just want to own your domain name. It's for SECURITY and that use case is going to drive all their decisions. And if it wipes out every community in the entire tor dark web? So be it. And they'll do it again. Don't build your communities on the sand that is the dark web. You won't like the result.

For the past week I assumed my old Debian 11 box was having apt install problems because of something I did. It's only natural. The Debian project has been rock solid for longer than I've used linux. But it turns out Debian really did just lose the entire bullseye-security repo and no one knows or will comment on if it will ever be returned and restore the ability to use Debian 11. Since it is EOL they consider it a low priority that they just broke probably tens of thousands if not hundreds of thousands of machines.

This is not how it's gone with any other EOL version. And indeed older EOL *-security repo contents are on the archive server. The snapshot servers have the packages so it's just not important enough for anyone responsible for it to fix.

To read the page without Javascript turn off CSS. This restores the page to a readable state from it's intentionally unreadable state.

This shouldn't be a problem right? Javascript is by default allowed to execute on your PC in every modern browser. The days where people did not blindly execute arbitrary code from unknown and random sources are far in the past. Now if you don't do that you are considered weird and no websites actually display anything when you attempt to view them.

This is not a bug. This is the the entire design architecture's intent for modern JS application execution based "web". If this was the correct choice for the web then this should not be a problem at all. But we all know it is. The architecture choice forces this. Until we stop arbitrarily executing random third party code this will always happen. And the consequences will get worse and worse as more bare metal features are exposed in to browsers JS virtual machines.

Be the change in the world you want to see. Turn javascript off. Use real native applications that cannot change underneath you.

The same could be said about economist articles behind paywalls; worse than useless as it prevents linking to an article covering it at a different source. Perhaps https://www.unsw.edu.au/newsroom/news/2022/03/three-orthopae... or https://www.thetimes.com/life-style/health-fitness/article/h... instead

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The 2001 AUMF (authorization of us of military force) needs to be repealed so that these "special designations" are no longer allowed and war has to be declared. The US federal government will still perform the same acts but at least after the 2001 AUMF is repealed they'll have to go back to secret assassinations. Instead of flouting it in semi-public with the executive disposition matrix system.

For one: calling in false police reports on people who video recorded the Flock subsidiary buildings by claiming they are on their property and saying "We don't know if they're armed." in an attempt to get them killed by police. Flock corporation's shells corps really don't like being recorded from public spaces adjacent to them and respond with attempts to incite violence against those that legally and peacefully record them. Which would be hilariously hypocritical if it weren't so dangerous. ref: https://youtu.be/S3MQLlMbS-Y?t=1894 (sorry this is a youtube video, recording of the false and inciting police report)

And then there are the cities that Flock is forcing to keep cameras physical up and which have to resort to putting bags over them like in Dayton, Ohio.

I think what I explained is known by anyone in solar physics. I cannot believe they would not have discussed it. It's absence in the paper is weird. But I think unpredictable refers more to LEO in the context of the paper where things are indeed more dynamic that just the 11 year periodicity of cosmic rays from solar activity causing scattering in the heliosphere.

It's well known that higher solar wind/CMEs density/speed/etc that comes with the peak of the 11 year intensity cycles scatters cosmic rays before they enter the inner heliosphere. Combine this with the 1~3 years it takes for the solar wind to travel out through the heliosphere and you get the phase difference. Really cool unintended sensor empirical data on it though.

Don't try to correlate with the sun spots, correlate with the solar wind/cmes from the spots getting out far enough to effectively scatter the incoming cosmic rays away.

This is only fair play given the cities and DAs around the country have refused to indict or prosecute Flock surveillance when they break the law.