Searching We.Love.Privacy.Club

Twts matching #git
Sort by: Newest, Oldest, Most Relevant

Intel NPU Firmware Published For Panther Lake - Completing The Linux Driver Support
Ahead of Intel Panther Lake laptops expected to debut next month at CES in Las Vegas, the Linux driver support for the next-gen “50xx” NPU of Panther Lake is now complete. The last piece of the driver support puzzle is now in place with the NPU firmware binaries having been upstreamed today to the linux-firmware.git repository… ⌘ Read more

⤋ Read More

@movq@www.uninformativ.de @kiwu@twtxt.net it just so happens to be a happy coincidence that I’m extending mu’s capabilities to now include a native toolchain-free compiler (doesn’t rely on any external gcc/clang or linkers, etc) that lowers the mu source code into an intermediate representation / IR (what @movq@www.uninformativ.de refers to as “thick layers of abstractions”…) and finally to SSA + ARM64 + Mach-O encoder to produce native binary executables (at least for me on my Mac, Linux may some later?) 🤣

⤋ Read More

I cleaned up all my of AoC (Advent of Code) 2025 solutions, refactored many of the utilities I had to write as reusable libraries, re-tested Day 1 (but nothing else). here it is if you’re curious! This is written in mu, my own language I built as a self-hosted minimal compiler/vm with very few types and builtins.

https://git.mills.io/prologic/aoc2025

⤋ Read More

Early Linux 6.19 Benchmarks On AMD EPYC 9965 2P Excelling For AI & HPC Performance
As the Linux 6.19 merge window winded down this weekend, I began running this development kernel on more systems. While there are some scheduler regressions currently with Linux 6.19 Git, for HPC workloads especially I am seeing some encouraging results using a flagship AMD EPYC 9965 2P server configuration. ⌘ Read more

⤋ Read More

AMD ROCm’s TheRock 7.10 Released
TheRock is an interesting open-source build platform for ROCm and HIP that has taken shape over the past year. It’s become an official ROCm effort albeit still in early stages and relying on community contributions for enhancements for different consumer GPU targets and more. To date its users have largely relied on running the latest TheRock Git while today TheRock v7.10 was tagged… ⌘ Read more

⤋ Read More

Scheduler Woes: Bisecting Early Performance Regressions Found In Linux 6.19
Yesterday I noted some early performance regressions I’ve found on the Linux 6.19 kernel compared to Linux 6.18 LTS stable. Those initial benchmarks were on an AMD EPYC server. Since then I’ve seen many of the same workloads regressing similarly on an AMD Ryzen Threadripper workstation between Linux 6.18 and Linux 6.19 Git. Given the significant impact and AMD Threadripper processors always helping out to speed-up Linux kernel build time … ⌘ Read more

⤋ Read More

Early Benchmarks Of Linux 6.19 Git Showing Some Concerns
While just half-way through the Linux 6.19 merge window, over the weekend I began running some benchmarks of the current Linux 6.19 Git state compared to Linux 6.18 LTS stable. There are some minor performance improvements to note in a few of the tests on the first system I tested but also some regressions at this very early pre-RC1 state of the Linux 6.19 kernel… ⌘ Read more

⤋ Read More
In-reply-to » @prologic Bwahahaha! I tried to establish some form of “convention” for commit messages at work (not exactly what you linked to, though), but it’s a lost cause. 😂 Nobody is following any of that. Nobody wants to invest time in good commit messages. People just want to get stuff done.

@lyse@lyse.isobeef.org My theory is that these people simply don’t do “code archeology”. When something breaks, they don’t reach for git log. They simply don’t experience the pain that comes with bad commits / commit messages.

Or is that different in your company? 😅

⤋ Read More
In-reply-to » I'm contemplating the idea of switching my activity pub instance from Gootosocial to a Pleroma one. While GTS is kinda cute (lightweight and easy to manage) of a software, the inability to fetch/scroll through people's past toots when visiting a profile or having access to a federated timeline and a proper search functionality ...etc felt like handicap for the past N months.

@bender@twtxt.net yeah, I’ve been reading through the documentation last night and it felt overwhelming for a minute… +1 point goes to GTS’s docs. but hey, I’ll be taking the easy route: podman-compose up -d they provide both a container image and an example compose file in a separate git repo but I’m wondering why that is not mentioned anywhere in the docs, (unless it is and I haven’t seen it yet)

⤋ Read More

Scoped User Access In Linux 6.19 To Reduce Speculation Barriers & Its Performance Hit
Merged yesterday to the Linux 6.19 Git codebase was the “core/uaccess” pull that introduces new scoped user-mode access with auto-cleanup functionality. This can reduce the number of speculation barriers encountered when needing to access user-mode memory and thereby avoiding some of the performance penalties incurred by speculation barriers… ⌘ Read more

⤋ Read More

Intel LASS, SGX EUPDATESVN & Microcode Staging Features Land In Linux 6.19
In addition to new AMD CPU features being merged today for Linux 6.19, there are also some new Intel CPU features that hit Linux Git today that are worth highlighting… ⌘ Read more

⤋ Read More

AMD Zen 6 RAS Preparation, AMD SDCI Features Merged For Linux 6.19
Linus Torvalds just merged another set of pull requests to Git for the in-development Linux 6.19 kernel. With the latest round of merges, there are two separate AMD changes worth highlighting… ⌘ Read more

⤋ Read More

Important Performance Work: Overhaul Of RSEQ & CID Management Merged For Linux 6.19
An important set of patches were just merged a few minutes ago to Linux Git for the ongoing Linux 6.19 kernel with some important performance implications… ⌘ Read more

⤋ Read More

Tired to re-enable the Ege route to git.mills.io today (after finishing work) and this is what I found 🤯 Tehse asshole/cunts are still at it !!! 🤬 – So let’s instead see if this works:

$ host git.mills.io 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:

git.mills.io is an alias for fuckoff.mills.io.
fuckoff.mills.io has address 127.0.0.1


PS: Would anyone be interested if I started a massive global class action suit against companies that do this kind of abusive web crawling behavior, violate/disregards robots.txt and whatever else standards that are set in stone by the W3C? 🤔

⤋ Read More

Oh fuck me! I had basically turned off the route to git.mills.io last night and went ot bed at ~2AM after unsuccessfully trying to control the attacks (bad bots) that were behaving like a DDoS attack. Tried to re-enable the route this monring and *BOOM, they’re back! As-if they never stopped?! what da actual fuq?! Anyone have any clever ideas of what I can do here to allows normal users, like you nice folk and block ths obnoxious traffic?!

⤋ Read More

Fark me again with the bots. This time DDoS-style crawling from hundreds of IPs and dozens of ASN(s) wtf?!
I’ve had to disale the Ingress to my Git instance for the time being, i need to sleep and I can’t fight this :/

⤋ Read More

All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. You’ve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].

After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?

Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(…) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.

But that was it. All test green. \o/

⤋ Read More
In-reply-to » I just noticed this pattern:

And regarding those broken URLs: I once speculated that these bots operate on an old dataset, because I thought that my redirect rules actually were broken once and produced loops. But a) I cannot reproduce this today, and b) I cannot find anything related to that in my Git history, either. But it’s hard to tell, because I switched operating systems and webservers since then …

But the thing is that I’m seeing new URLs constructed in this pattern. So this can’t just be an old crawling dataset.

I am now wondering if those broken URLs are bot bugs as well.

They look like this (zalgo is a new project):

https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/

When you request that URL, you get redirected to /git/:

$ curl -sI https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/
HTTP/1.0 301 Moved Permanently
Date: Sat, 22 Nov 2025 06:13:51 GMT
Server: OpenBSD httpd
Connection: close
Content-Type: text/html
Content-Length: 510
Location: /git/

And on /git/, there are links to my repos. So if a broken client requests https://www.uninformativ.de/projects/slinp/zalgo/scksums/bevelbar/, then sees a bunch of links and simply appends them, you’ll end up with an infinite loop.

Is that what’s going on here or are my redirects actually still broken … ?

⤋ Read More

Intel LASS Feature Looks Like It Will Be Upstreamed For Linux 6.19
Intel’s LASS functionality was queued today into tip/tip.git’s “x86/cpu” Git branch. With LASS now making it into a TIP branch, it looks like it will be submitted for the upcoming Linux 6.19 merge window barring any last minute issues or objections from Linus Torvalds… ⌘ Read more

⤋ Read More

Qualcomm Updates AI Accelerator Firmware To Fix Power / Performance Issue
Qualcomm upstreamed new Cloud AI 100 “AIC100” firmware today to linux-firmware.git to fix a rather significant power/performance issue for these AI accelerators… ⌘ Read more

⤋ Read More

Git 2.52 Released With More Preparations Toward Git 3.0
Git 2.52 is out today as the newest feature release of this distributed revision control system and in working toward Git 3.0 that will hopefully release by the end of 2026… ⌘ Read more

⤋ Read More

Intel Nova Lake Power Management Bits Prepped Ahead Of Linux 6.19
Intel engineers continue working on the Nova Lake next-gen processor enablement for the Linux kernel. In addition to the Intel Xe3P graphics and other early Nova Lake enablement work already queued in “-next” Git branches ahead of the Linux 6.19 merge window, the initial power management code is also ready for this next kernel cycle… ⌘ Read more

⤋ Read More
In-reply-to » It is harder to regain ownership of an IRC channel than crossing the Mexico/US border. 😅

@bender@twtxt.net Hahaha! :-D But I actually do like their approach. I don’t know what staff should do differently when they are not involved in the channel topic. At least in the general case. Maybe in this specific scenario here they could have cross-checked domains, git repos and stuff like that. But I also reckon that it’s only fair if they treat everybody the same.

⤋ Read More

Lenovo IdeaPad Linux Driver Adding Support For Rapid Charge Mode
Queued into the platform-drivers-x86 “for-next” Git branch ahead of the Linux 6.19 merge window is introducing the handling for the “Rapid Charge” USB-C charging mode to the Lenovo IdeaPad laptop driver… ⌘ Read more

⤋ Read More