

Normally patches roll out before the vulnerability is disclosed. But I honestly don’t know the status on CopyFail


Normally patches roll out before the vulnerability is disclosed. But I honestly don’t know the status on CopyFail


No. Learning is changing behavior on past experience, not new information.


As I explained elsewhere there is no official app to change this setting. Users can hack their gsettings.
Support for middle-paste will slowly but surely bitrot and eventually be removed.


No default gnome app will be able to toggle that default. You can hack it in gsettings.
And worse, the fact there is a setting means that only the default will be tested. The feature will slowly but surely bitrot. In a few years we’ll see a proposal to remove it entirely. This is how software development works.
Many moons ago I did a project at uni where we implemented elliptic curve cryptography in Java and released it as open source. Unsurprisingly, we had no idea what we were doing. Some years later I get a random mail from someone using it on some embedded system…
I don’t want to know, and I fear that ist is paramount that I maintain plausible deniability 😂♥️🙏
Do it. DO IT


Most devs I know like recursion. Trouble is that many popular languages don’t support tail recursion, but throw a stackoverflow error after a few thousand levels. So you have to keep track of max recursion depth manually, and it starts to look like a complicated solution


Most devs I know like recursion. Trouble is that many popular languages don’t support tail recursion, but throw a stackoverflow error after a few thousand levels. So you have to keep track of max recursion depth manually, and it starts to look like a complicated solution
9 times out of 10, this “vibe draft” sends people down a terrible path that they would have never ventured had there been an adult in the room. I swear I review so much code that sets off in the wrong direction because of this, and I am sick of it.
Forgejo supports SSO, and from a quick skim of the diff it looks like they support GitHub and OpenID logins.


X11 is “complete” in the sense that we have followed it to the end of the road. X11 has a series of well documented fundamental problems that does not make it suitable for a modern OS. I will not belabor them here (except to note that security in particulat in X11, is exceptionally weak for modern standars). These issues are unfixable because they are built into core assumptions and behaviours of all legacy apps.
At some point there has to be a switch. There simply is not manpower to maintain 2 separate windowing systems. I am sure we would all want there to be an army of devs working on these things on maintain the 2 stacks. But that is not the timeline we live in. The number of devs working on these things is very low.
Was it too early? I don’t know. There will never be 1-1 feature parity with 30 years of legacy apps. I honestly believe that fixing things like a11y are gonna be much more tenable with only a single windowing system.


For someone who has not used Gnome in 14+ years you sure seem to know a lot about it…
X11 has effectively already been deprecated for years, seeing little to no development on it. No one should be surprised.
And still, there are SEVERAL Long Term Support distros out there that will support X11 for the coming years. Please stop pretending that stuff will start breaking. It will not.


I find that my projects hosted on codeberg are heavily deranked or entirely missing on the top mainstream search engines. My github projects are almost always top 3.
So if it is a library someone might gind useful it has to go in gh. My personal toys can stay on cb.
I see, they have been continvoucly morging the docs themselves, as per their developer docs