Yo @prologic@twtxt.net, apparently even ‘git clone’ is getting blocked by your Gitea or something (I’m using authentication, naturally)

@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)

@itsericwoodward@itsericwoodward.com Nice to see someone else also participating! 🥳

(Btw, they don’t want us to share our inputs: https://www.reddit.com/r/adventofcode/wiki/faqs/copyright/inputs/ Yeah, it’s a bit annoying. I also have to do quite a bit of filtering on my repo …)

Working on day 3 of the Advent of Code 2025: https://adventofcode.com/

My solutions repo: https://git.itsericwoodward.com/eric/aoc-2025

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

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

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

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

gitlog-vim a wrapper to view git logs without plugins ⌘ Read more

HACK: vim using terminal app window panes and git repo aware viminfo contexts ⌘ Read more

Broadcom “BNG_RE” Next-Generation RoCE Driver Slated For Linux 6.19
Queued up via the Linux kernel’s RDMA development Git tree is “BNG_RE” as the next-generation RoCE driver from Broadcom… ⌘ Read more

@prologic@twtxt.net Your gitea thinks the LICENSE file in the yarn repository is SSPL-1.0 instead of GNU AGPL 3.0,
and I can’t help but giggle at that

The funny thing is, Yarn moving to Twt Hash v2 sounds a tad more optimistic than Git adopting SHA-256.

Git is several years too late, while Yarn is pretty much on time.

Speaking of WAF(s) / Web Applicaiton Firewalls – I actually had forgotten that not only have I designed a new WAF from scratch, but I’ve actually implemented it already, and done some local testing. I just haven’t put it into production yet… What od you think @aelaraji@aelaraji.com ? 🤔 https://git.mills.io/prologic/caddy-waf

@prologic@twtxt.net I originally did that, then I git reset XD

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? 🤔

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?!

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 :/

Hm, so regarding the hash change:

https://git.mills.io/yarnsocial/twtxt.dev/pulls/28

How about 2026-03-01 00:00:00 UTC as the cut-off date? 🤔

Linux 6.18-rc7 Released With Late Hardware Improvements
Linux 6.18-rc7 just arrived in the Git tree as the newest weekly test build leading up to Linux 6.18 stable hopefully debuting next Sunday, 30 November… ⌘ Read more

6.18-rc7: mainline
Version:6.18-rc7 (mainline)Released:2025-11-23Source:linux-6.18-rc7.tar.gzPatch:full ( incremental) ⌘ 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/

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 … ?

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

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

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

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

6.18-rc6: mainline
Version:6.18-rc6 (mainline)Released:2025-11-16Source:linux-6.18-rc6.tar.gzPatch:full ( incremental) ⌘ Read more

@lyse@lyse.isobeef.org Well, they say you have to build up stocks, don’t they? 😅

The font is fiamf3 (scaled up 2x, it would be too small when printed). It’s the same one that I use in my terminal and the status bars. 😃

@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.

Done ✅ Will be available on this pod as soon as the publish workflow finished successfully.

My Git history was a mess of ‘update’ and ‘fix’ – so I made AI clean it up
Comments ⌘ Read more

6.18-rc5: mainline
Version:6.18-rc5 (mainline)Released:2025-11-09Source:linux-6.18-rc5.tar.gzPatch:full ( incremental) ⌘ 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

PR to clean up some unwanted specs and cleanup some invalid/bad references. 🙏

6.18-rc4: mainline
Version:6.18-rc4 (mainline)Released:2025-11-02Source:linux-6.18-rc4.tar.gzPatch:full ( incremental) ⌘ Read more

At the end you use Git bisect
Comments ⌘ Read more

🥳 Just released Gatherly v0.3.0 🤟 – My instance is available at: https://gatherly.mills.io (free for anyone to use)

(https://www.uninformativ.de/git/zalgo/file/README.html)

6.18-rc3: mainline
Version:6.18-rc3 (mainline)Released:2025-10-26Source:linux-6.18-rc3.tar.gzPatch:full ( incremental) ⌘ Read more

You already have a git server
Comments ⌘ Read more

You already have a Git server
Comments ⌘ Read more

Redistributing Git with Nostr
Comments ⌘ Read more

Discussion of the Benefits and Drawbacks of the Git Pre-Commit Hook
Comments ⌘ Read more

6.18-rc2: mainline
Version:6.18-rc2 (mainline)Released:2025-10-20Source:linux-6.18-rc2.tar.gzPatch:full ( incremental) ⌘ Read more

Add Rust Binder Driver
Comments ⌘ Read more

When I’m about to run a git status ⌘ Read more

Mergiraf - syntax-aware git merge driver
Comments ⌘ Read more

Git Developers Talk About Potentially Releasing Git 3.0 By The End Of Next Year
Comments ⌘ Read more

6.18-rc1: mainline
Version:6.18-rc1 (mainline)Released:2025-10-12Source:linux-6.18-rc1.tar.gzPatch:full ⌘ Read more