Pain points of OCaml
Comments ⌘ Read more

Fuck me sideways, trying to repair stuff that isn’t meant to be repaired is such a pain. So many pointless obstacles.

In 1776, Thomas Paine made the best case for fighting kings −and being skeptical
Comments ⌘ Read more

LED light blasts cancer cells and spares healthy ones
A new cancer treatment combines LED light and tiny tin flakes to neutralize cancer cells while shielding healthy cells and avoiding the painful side effects associated with chemotherapy and other treatments. ⌘ Read more

@kat@yarn.girlonthemoon.xyz yeah it’s pretty terrible these days. Most recent trouble I had was something as simple as installing and setting up the Tailscale client. On literally all my other devices (Linux and Android) that was a cinch, but on Windows…. ohh boy, I had to mess around with reg edits and all sorts of crap and eventually bludgeoned it into working, but it was a bloody pain.

@bender@twtxt.net yeah, my friend’s considering moving away from linode and instead self hosting. VPS stuff is a pain

Thank You, DataFusion: Queries in Rust, Without the Pain
Comments ⌘ Read more

How to install Windows NT 4 Server on Proxmox
Windows NT 4 doesn’t virtualise well. This guide shows how to do it with Proxmox with a minimal amount of pain. ↫ Chris Jones Nothing to add, other than I love the linked website’s design. ⌘ Read more

Pain in the dots
Comments ⌘ Read more

Interview: Chief maintainer of Qt project on language independence, KDE, and the pain of Qt 5 to Qt 6 •
Comments ⌘ Read more

On the relationship between Qt and KDE
Volker Hilsheimer, chief maintainer of the Qt project, says he has learned lessons from the painful Qt 5 to Qt 6 transition, the importance of Qt Bridges for using Qt from any language, and the significance of the relationship with the Linux KDE desktop. ↫ Tim Anderson at Dev Class Qt plays a significant role in the open source desktop world in particular, because it’s the framework KDE uses. Hilsheimer notes that KDE’s role in the Qt community is actual … ⌘ Read more

10 Fictional Species Designed for Battle
War is generally not something to aspire to. It’s a desperate measure to resolve one’s differences when all other options fail. Fighting forgoes people’s evolutionary intelligence and reduces them to their baser instincts. Such barbarism leaves both sides licking their wounds, coping with the pain and death that their actions have wrought. Granted, combat is […]

The post [10 Fictional Species Designed for Battle](https://listverse.com/2025/04/26/10-f … ⌘ Read more

HOLLY Mother of Euphoria !! Nothing can beat a late night run, I just hope I don’t regret it by tomorrow morning xD (the usual Knee Pain & Co.)

How we’re making security easier for the average developer
Security should be native to your workflow, not a painful separate process.

The post How we’re making security easier for the average developer appeared first on The GitHub Blog. ⌘ Read more

@mana@yarn.girlonthemoon.xyz grid has its places but it can be a pain!

@lyse@lyse.isobeef.org

Although, most software I use is decentish in that regard.

Is that because you mostly use Qt programs? 🤔

I wish Qt had a C API. Programming in C++ is pain. 😢

@suitechic@yarn.girlonthemoon.xyz yeah i’ve also used namecheap, though i will say if you want to do TLS on demand with them then it’s kind of a pain and i think you have to pay more last i checked so i’d try something different.

So this is a great thread. I have been thinking about this too.. and what if we are coming at it from the wrong direction? Identity being tied to a given URL has always been a pain point. If i get a new URL its almost as if i have a new identity because not only am I serving at a new location but all my previous communications are broken because the hashes are all wrong.

What if instead we used this idea of signatures to thread the URLs together into one identity? We keep the URL to Hash in place. Changing that now is basically a no go. But we can create a signature chain that can link identities together. So if i move to a new URL i update the chain hosted by my primary identity to include the new URL. If i have an archived feed that the old URL is now dead, we can point to where it is now hosted and use the current convention of hashing based on the first url:

The signature chain can also be used to rotate to new keys over time. Just sign in a new key or revoke an old one. The prior signatures remain valid within the scope of time the signatures were made and the keys were active.

The signature file can be hosted anywhere as long as it can be fetched by a reasonable protocol. So say we could use a webfinger that directs to the signature file? you have an identity like frank@beans.co that will discover a feed at some URL and a signature chain at another URL. Maybe even include the most recent signing key?

From there the client can auto discover old feeds to link them together into one complete timeline. And the signatures can validate that its all correct.

I like the idea of maybe putting the chain in the feed preamble and keeping the single self contained file.. but wonder if that would cause lots of clutter? The signature chain would be something like a log with what is changing (new key, revoke, add url) and a signature of the change + the previous signature.

# chain: ADDKEY kex14zwrx68cfkg28kjdstvcw4pslazwtgyeueqlg6z7y3f85h29crjsgfmu0w 
# sig: BEGIN SALTPACK SIGNED MESSAGE. ... 
# chain: ADDURL https://txt.sour.is/user/xuu
# sig: BEGIN SALTPACK SIGNED MESSAGE. ...
# chain: REVKEY kex14zwrx68cfkg28kjdstvcw4pslazwtgyeueqlg6z7y3f85h29crjsgfmu0w
# sig: ...

@movq@www.uninformativ.de

(I don’t really trust Android, though, and I suspect that apps can still install background services that are always active. Pure speculation and paranoid on my part, but still.)

Which is fair, but I would say the GrapheneOS devs in particular are also quite paranoid about this stuff and go to great pains to make sure this stuff can be controlled by the user.

“As HANNO says, ‘My music is a universal hymn to the primitive pain and pleasure of being human’”

A checklist and guide to get your repository collaboration-ready
In the world of software development, collaboration can make the difference between a brittle last-minute release and a reliable, maintainable, pain-free project. Whether you’ve been coding for a day or a decade, your colleagues are there to help strengthen your work. But they can only help if you’ve given them the tools to do so. ⌘ Read more

@shreyan@twtxt.net my condolences for the pain you no doubt will inflict upon others that will have to maintain whatever you write in Ruby.

@prologic@twtxt.net I get the worry of privacy. But I think there is some value in the data being collected. Do I think that Russ is up there scheming new ways to discover what packages you use in internal projects for targeting ads?? Probably not.

Go has always been driven by usage data. Look at modules. There was need for having repeatable builds so various package tool chains were made and evolved into what we have today. Generics took time and seeing pain points where they would provide value. They weren’t done just so it could be checked off on a box of features. Some languages seem to do that to the extreme.

Whenever changes are made to the language there are extensive searches across public modules for where the change might cause issues or could be improved with the change. The fs embed and strings.Cut come to mind.

I think its good that the language maintainers are using what metrics they have to guide where to focus time and energy. Some of the other languages could use it. So time and effort isn’t wasted in maintaining something that has little impact.

The economics of the “spying” are to improve the product and ecosystem. Is it “spying” when a municipality uses water usage metrics in neighborhoods to forecast need of new water projects? Or is it to discover your shower habits for nefarious reasons?

@lyse@lyse.isobeef.org Its just dead simple.. and others will salt which makes repeatability in examples a pain.

How Dependabot empowers you to keep your projects secure
We want to take away the pain and effort of keeping your code secure, so check out how Dependabot empowers developers to keep to their projects secure. ⌘ Read more

And my files are created on ext3, backuped on zfs, transported via fat and then viewed on hfs+ #pain