Starting the 2022-2023 period, more and more generative AI content has entered search engines.
The below queries give you some pointers on how to spot those. They return scholar articles from 2023 and later.
Note the list is in alphabetical order for easier reading, but the number of results (in parenthesis) are very different from that order. I was quite amazed to see “As an AI language model” scoring 45 results.
Ze is enorm goed in haar werk, en komt daarmee regelmatig in aanraking met vooringenomenheid over vrouwen. Daar verbaast ze zich terecht over, en ook dat het lastig om content (op allerlei soorten gebieden) te consumeren gemaakt door vrouwen. Dat overkwam haar bijvoorbeeld bij het luisteren naar muziek op de Nederlandse radio: daar kwamen veel meer mannelijke artiesten aan bod dan vrouwelijke.
Vandaar FemFM, en Felienne zou Felienne niet zijn als de source code niet openbaar was, dus hier wat linkjes:
> I'd suggest reverting to 5.3.1. Bearing in mind that there were security > fixes after that point for ZDI-CAN-16587 that would need to be reapplied.
Note that reverted to such an old version will break packages that use new symbols introduced since then. From a quick look, this is at least: - dpkg - erofs-utils - kmod
Having dpkg in that list means that such downgrade has to be planned carefully.
@_ruby: The setup behind the CVE-2024-3094 supply-chain attack is fascinating. I originally wanted to finish and share a tool to audit other OSS projects for anomalous contributor behavior, but I feel what I found tr……
How it was found:
FWIW, I didn't actually start looking due to the 500ms – I started looking when I saw failing ssh logins (by the usual automated attempts trying random user/password combinations) using a substantial amount of CPU. Only after that I noticed the slower logins.
— Andres Freund (Tech) (@AndresFreundTec) March 30, 2024
Interesting! The xz backdoor code was so unperformant under normal SSH password grinding on the public Internet, @AndresFreundTec noticed and dug in. Thanks for your discovery Andres! https://t.co/Ee5xm8kWJj
what I wanna know is what was up with the other repos on Jia Tan’s GitHub. Has anyone looked at *those* commits and libraries? Because there was a lot of other stuff on there I haven’t seen mentioned
"don't run xz –version to check if you're compromised"
haha, too late
If you have infected version of liblzma in your system, it's already loaded into EVERY process that depends on libsystemd. systemd's dependency on liblzma *was literally* the attack vector. pic.twitter.com/TsaH7d20r7
A while back, early in the Wednesday morning after Patch Tuesday I performed regular updates of all the systems noticing some updates failed because timeouts on the Microsoft download servers.
Note I perform the manual steps on Wednesday as Patch Tuesday as it starts at 10:00 AM PST which is in the evening in Amsterdam. The automated steps are automated and kick in when Microsoft tells the Windows machines to update themselves.
Microsoft schedules the release of security updates on “Patch Tuesday,” the second Tuesday of each month at 10:00 AM PST.
Depending on time zone(s) in which the organization operates, IT pros should plan their deployment schedules accordingly. Please note that there are some products that do not follow the Patch Tuesday schedule.
I posted a gist and a Tweet, but didn’t immediately thought of a good resolution so I postponed that until Thursday and found it:
We’re going to hold off on this feature for now. It’s complexity is high and it’s not common enough a workflow. One could also just comment out the lines and hit ctrl-s to get the same effect, pretty much. Status: WontFix –
The workaround is to comment out the line you want to skip and press Ctrl+S.
The problem is that the workaround fails when you have used the Chrome Dev Tools to format the source code: then you cannot edit the formatted code.
The workaround for that is cumbersome, but doable as in this bug report:
Many people assume that git does recognise rename (or mv) operations by itself. Often it does, but it fails, and when it fails it usually is in a complex situation where it is easy to overlook it did not recognise the rename.
Failing complex situations I have encountered in the past (combined they get worse):
rename across several directories
first edit, then rename
first rename, then edit
So it is better to proactively perform an IDE-assisted git mv operation that informs git of the rename.
Many IDE environments support a built-in rename that keeps git mv in the loop, but Visual Studio Code does not, hence the need for this extension.