Wine-Staging 11.18 Adds New Patches To Further Improve WoW64
Building off yesterday’s Wine 11.18 bi-weekly development release is now Wine-Staging 11.18. This experimental flavor of Wine is presently carrying 273 extra patches over that upstream Git state, including some new patches for helping enhance the WoW64 support… ⌘ Read more

Also apologies. If you want to chat to me in more ~realtime, I’m more active on something we’re calling Parley – A truly decentralised federated IRC chat system. You have to spin up your own instance (ideally) or join someone else’s, but otherwise you use a normal IRCv3 capable client, but the entire “network” (so to speak) automatically forms a decentralized mesh.

👋 Calling all decentralised enthusiasts that still remembers and use IRC 😎

Please come join us in a new, truely, decentralised IRC-based chat experience by standing up your own Parley instance on your own domain (bring your own OIDC auth or use the built-in).

Pick your favourite IRCv3-compatible client (there’s heaps out there!).

And peer with either me james@mills.io or Admin -> Peers -> Add mills.io or @david@daiwei.me via david@ratha.us or simply ratha.us (in Admin -> Peers -> Add).

See you online! 🤞 #decentralised #irc #chat

@itsericwoodward@itsericwoodward.com Then by all means, follow the instructions at https://git.mills.io/prologic/parley and setup your own instance on your own domain. It’s partly inspired by Twtxt/Yarn.social and Salty.im – in at least the way teh DNS discovery and WKID works. Once your instance is up and running and you’ve gone through the /setup and created yourself an account (or seti it up with an appropraite ODIC IDP) try something like /msg james@mills.io Hey! at which point you should automatically start peering with my instance. You should then be able to /join #lobby1 (a globally federated channel already across 2 instances so far). 🤞

Gitte As Git Client For GNOME Continues Maturing Quite Nicely
For those in pursuit of a graphical Git client for GNOME or the Linux desktop at large, the GTK4-powered Gitte continues advancing rather well and out this week is its v0.10 release… ⌘ Read more

Git 2.56-rc0 Released With Updated Contribution Guidelines, Improvements For Swift
While still ultimately working toward Git 3.0 with SHA-256 hashes by default and the “main” branch name by default, among other breaking changes (and potentially coming around the end of 2026), Git 2.56-rc0 is now available for testing… ⌘ Read more

Does anyone have time this weekend to manually test and validate and prove out this spec I’m calling Gitxt? A Twtxt-inspired purely decentralised Git federation/forge? 🤔 Hit me up! You need only git, curl and a web server of some kind.

LLVM Developers Begin Debate Over AGENTS.md For Helping AI Agents
LLVM developers have begun a discussion on whether the project should host an AGENTS.md file (and CLAUDE.md) in their Git repository for helping to guide AI agents… ⌘ Read more

@movq@www.uninformativ.de Ahh, no you can. Much like what we’ve built here with Twtxt / Yarn. I’m building a spec, clients can implement the spec, or you can ya know, just curl and git your way through. I’ll link the spec soon™, just need to keep refining and testing and make sure this actually works properly 😅

gitxt is a purely decentralised git forge. There is no federation protocol, no instance-to-instance API, no accounts on other people’s servers. Each forge instance is fully independent; collaboration is an act of publishing and reading plain text files over HTTP

@movq@www.uninformativ.de In the meantime tell me all your “wishes” and things you wish/want a good decent “pure” decentralised Git forge should do 😅

I am finally building a Twtxt / Yarn.social inspired Git forge. I’m actually quite confident that y’all will quite like it, but I won’t post links yet until I’m quietly confident in its design, functionality and behaviour(s).

Stay tuned 🤞 It’ll be like no other Git forge you’ve ever seen! 🤣 Actually, it’s already more like cgit than anything with plain text feeds that power it’s “pure decentralization” as you can no doubt imagine 😅 #twtxt #git #forge

EDAC Changes Merged For Linux 7.3 After Being Forgotten About During The Merge Window
While the Linux 7.3 merge window officially closed on Sunday with the Linux 7.3-rc1 release, the Error Detection And Correction “EDAC” subsystem changes were mistakenly forgotten about during the two week window. The pull request ended up being sent out on Monday evening and the late feature changes were already merged to Git… ⌘ Read more

@movq@www.uninformativ.de I am seriously rethinking and re-contemplating building a new Git forge of some description that avoids all of these stupid problems that we’re now seeing in the wild

FTR, I’m seeing veeeeeeeeery few actual git clone operations in the logs. Most crawlers simply don’t do that and rely on the Git history being available as HTML pages.

So that’s a win. (For now.)

AI’s ‘Creepy’ Crawlers Criticized by Linux Foundation’s IT Infrastructure Director
The Linux Foundation’s director of IT infrastructure says they now spend more CPU cycles “rendering commits for scrapers than we spend on all other kinds of legitimate access.”

At any one time, across 5 geo-distributed nodes, there are 14 CPU cores doing nothing but rendering git commits as html….

[W]hen a s … ⌘ Read more

F2FS With Now Handle Multi-Device Flushes In Parallel With Linux 7.3
Coming in as a late pull request ahead of the Linux 7.3 merge window closing this weekend were the Flash Friendly File-System (F2FS) updates that have now made it into Linux Git… ⌘ Read more

Btrfs, EXT4, F2FS & XFS On Linux 7.2 vs. Linux 7.3 Performance
Earlier this week I showed off some of the very nice Btrfs performance gains on Linux 7.3. For those wondering what kernel optimizations may have carried over to other file-systems or other file-system specific enhancements, here are Linux 7.2 vs. 7.3 Git performance benchmarks across Btrfs, EXT4, F2FS, and XFS on the same system. ⌘ Read more

Benchmarking Some Incredible Performance Gains With Btrfs On Linux 7.3
With the Btrfs pull request for Linux 7.3 having delivered more performance optimizations with some ~3x and ~5x gains mentioned in specific areas, I was eager to test out the new Btrfs performance on the in-development kernel. In today’s article are some benchmarks of Btrfs on Linux 7.2 stable compared to Linux 7.3 Git with some very enticing performance gains confirmed in various workloads. ⌘ Read more

Early Linux 7.3 Kernel Benchmarks Show Some Performance Improvements, Some Regressions
Being halfway through the Linux 7.3 kernel merge window and prior to wrapping up and sending back the HP Z4 G6i workstation powered by the Xeon 678X Granite Rapids WS processor, I decided to run some benchmarks to see how Linux 7.3 Git is performing relative to the prior stable kernel series. Here are the first benchmarks of this early state of Linux 7.3 with some performance improvements as well as some regressions. ⌘ Read more

AMD RDNA 4m Firmware Published For Linux Ahead Of Launch
In addition to AMD’s Friday afternoon big code drop of all the UALink enablement patches for the Linux kernel and the AMDGPU driver, there was another big drop from AMD to end out the week… Upstreamed to the linux-firmware.git repository is all the firmware binaries needed by the open-source driver stack for initializing their forthcoming RDNA 4m “GFX 11.7” graphics… ⌘ Read more

Real tired of doing these, but here’s another Android developers vs Google update, this time there’s both good and bad news.

The good:
-Users will be able to enable “sideloading” for all current and future devices, attached to their Google account, rather than having to undergo the tedious 24 hour wait including process, on each device.

-Rather than these changes to “sideloading” and “advanced workflows” being implemented at random different dates, in different countries, we’ll all get them come 2027.

The bad:
As GrapheneOS developers recently mentioned “Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It’s completely ridiculous and they’ve gradually become very slow at handling requests. They’re in clear violation of the GPLv2 now.”

whole thread: https://grapheneos.social/@GrapheneOS/117057099753905023

PHP 7.4 To PHP 8.6 Benchmarks, PHP 8.6 JIT Performance
A Phoronix Premium supporter recently relayed a request to see some fresh PHP performance benchmarks. So here are some fresh numbers of PHP 7.4 through the latest PHP 8.5 code plus the current Git state of PHP 8.6 ahead of the official PHP 8.6.0 release later in the year. With PHP 8.6 is also a fresh look at the JIT performance enabled too… ⌘ Read more

Linux 7.1, Linux 7.2 Performance On The Intel Xeon 600 Series
With Linux 7.2 expected for its stable release this weekend, today’s testing has some additional testing of the Linux 7.2 Git kernel as well as Linux 7.1 stable compared to Linux 7.0 as used by default on Ubuntu 26.04 LTS. Phoronix testing previously conducted of Linux 7.2 have shown benefits for Intel Arc B390 Xe3 in some configurations, faster poll performance on AMD Ryzen Threadripper and other hardware, and some nice I/O performance gains on AMD EPY … ⌘ Read more

@david@daiwei.me Please report any logs from the Javascript console if you can. It’s possible the one commit I made to the Swag framework might be the culprit here. Not sure.

GCC 17 Compiler Adding “-m128bit-atomic” For 128-bit Atomic Memory Operations
Merged today to the GNU Compiler Collection Git code is the new -m128bit-atomic option for next year’s GCC 17 feature release… ⌘ Read more

Linux 7.2-rc7 Addresses A “Nasty” Race Condition Leading To Use-After-Free After 8 Years
The Linux kernel Git activity continues being quite heavy this week on fixes. It’s looking like the Linux 7.2-rc7 kernel release on Sunday will be another big one with the changes continuing to flow in from both developers and AI bots… ⌘ Read more

Linux Patched For Safe RET Interrupt Vulnerability
Made public minutes ago is the Safe RET Interrupt Vulnerability which is now patched in the newest Linux kernel Git code. The Safe RET Interrupt Vulnerability stems from improper handling within Linux’s Speculative Return Stack Overflow (SRSO) mitigation affecting AMD Zen 1 through Zen 4 processors… ⌘ Read more

The Performance Benefits To Upgrading Mesa With Intel Arc B390 On Ubuntu Linux
If you are an early customer of the Framework Laptop 13 Pro or other Intel Core Ultra Series 3 Panther Lake laptop and using Ubuntu 26.04 LTS, there can be real benefit from upgrading your Mesa stack for the newer Iris Gallium3D and ANV Vulkan drivers. In this article are some benchmarks of the Framework Laptop 13 Pro with Core Ultra X9 388H with Arc B390 Xe3 integrated graphics for looking at the performance impact of using Mesa Git on Ubuntu L … ⌘ Read more

Linux 7.3 Adding Support For MCTP-Over-USB v1.1
Within the Linux networking subsystem’s “net-next” Git branch there is now queued up support for MCTP-over-USB v1.1. This is the newest version of the standard for sending Management Component Transport Protocol (MCTP) packets over USB for tasks loike crash dumps, logging, and firmware updates… ⌘ Read more

Low stakes hot take: the most important good things in git were already in rcs. rcs→cvs→svn→git is better overall at each step, but the benefit/complexity ratio gets worse at each step and most things git gets used for would be fine with rcs+patch.

@prologic@twtxt.net Just out of curiosity, have you ever ran this on real hardware? 😃

Hm, interesting: https://git.mills.io/prologic/muos/src/branch/main/nucleus/nucleus.asm You’re clearing the VGA buffer in each mode (real mode, protected mode, long mode). Why’s that? Wouldn’t it be good enough to only do that after you’ve reached long mode? 🤔

So… my little experimental Mu (µ) OS is now ~8.7k of Mu and ~2k of Assembly, which makes this about an ~80/20 split. I’ve managed to achieve most of the goals I had set out, by ensuring a tiny Nucleus of only ~2k Assembly and all Policy, Services and Userland written entirely in Mu (a language I also deisnged and created, which still has no support for floats LOL)

Dunno if anyone will find this interesting… But some ~6 months or so ago I experimented briefly with creating a whole bootloader + kernel + userland – Basically an entire OS in the Mu programming language (which as you know I also designed and created) – 6 months later I’ve worked on it some more after spending the last week working on improvements to Mu itself, which is now able to compile itself with its own Mu implemented compiler and now have an os/arch backend called muos/amd64 that boots into a running shell, with a tiny little vfs, UNIX-like semantics, syscalls, read/write, etc. It works pretty nicely, and aside from a small Assembly “nucleus”, most of the Kernel and Userspace is written in Mu.

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

@dce@hashnix.club Was it ever really empty on the Codeberg side in the Git repo? 🤔

@david@daiwei.me Go down to “Releases”, there’s a link to the CHANGES: https://movq.de/git/jenny/CHANGES.html

@david@daiwei.me Is this better? 🤔 Pretty hard to keep this concise but also not miss anything. 🤔 https://movq.de/git/jenny/

Hmm …

My project pages have this “Downloads” section and I offer tarballs for each release:

https://movq.de/git/jenny/#downloads

I added this many years ago because an OpenBSD dev asked for it (but the project in question didn’t end up in their ports after all).

What are your thoughts on this? Is it necessary to offer tarballs?

I noticed that some distributions have already moved away from using tarballs and instead always clone from Git. 🤔

@prologic@twtxt.net Oh, yes, just for clarity: This wasn’t a “pro GitHub” argument. 😅 I won’t go back there (or to another “forge”).

I think we’re totally on the same page: Decentralized Git hosting is good, but we haven’t solved the “collaboration” part yet. Or rather: We have to modernize it. The tools are already there, but (many) people don’t want to use them and think they’re clunky.

@lyse@lyse.isobeef.org

How many tickets and merge requests did you get before moving to your own server?

Hm, these were probably some of the more active projects:

• https://github.com/vain/lariza/issues?q=is%3Aissue%20state%3Aclosed
  
• https://github.com/vain/pdfPres/issues?q=is%3Aissue%20state%3Aclosed
  
• https://github.com/vain/xiate/issues?q=is%3Aissue%20state%3Aclosed
  

So it’s not a ton of stuff and there are many “issues” I opened myself, but it’s certainly more than these days.

Haven’t used git send-email even once. I definitely have to look into that soon. Wanted to do that for several years. I typically upload the patch to my server and send a link via IRC.

git send-email is good for sending patches to a mailing list (because then the individual patches can be discussed easily), but since those are dying out as well, it loses its appeal. If you want to send patches to a single person, just sending the link to your repo is far easier. 🤔

@movq@www.uninformativ.de Finally, your software is just perfect and finished by now, no need to report non-existing bugs or send in code changes. :-) How many tickets and merge requests did you get before moving to your own server?

I have to admit that I use git format-patch so rarely, I always have to pull it up from my shell history. Haven’t used git send-email even once. I definitely have to look into that soon. Wanted to do that for several years. I typically upload the patch to my server and send a link via IRC.

Maybe I was just very unlucky, but my experience is that you can perfectly ignore people and their work who only do it for the “fame”. It’s almost always been from inferior quality to say the least.

@prologic@twtxt.net Hmmm, I have no idea how to solve that problem. 😅 Some jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.

I thought I had made that super easy, because you can just send me an email – no sign-up process, nothing. But that’s way too old-school, people don’t know how to use git format-patch (let alone git send-email) and they also don’t understand that they can just send me a link to their forked Git repo (which can be hosted anywhere). Git is super flexible and powerful, but those features are hardly ever used.

Maybe people even need some kind “reward”, or “fame”. Like those “achievements” that you can unlock on GitHub. (Something to put in their CV … ?)

Oh god 🤣 I mean I had this idea to re-invent “Git hosting”, but failed. Maybe I’ll try it again. I dunno. The thing is I hardly get “Issues” really, only when I ask nicely, of folks I know every well 🤣 So think at much “smaller scale” we need a different solution, and I think @movq@www.uninformativ.de is on to something, but not to the extend implemented, somewhere in the middle I think? 🤔

Okay, so this is live now under https://movq.de/git/. („Kurzen Prozess gemacht.“)

Okay, so, my website also includes my code / git repos, and those are made browsable by stagit. What I don’t like about this (these days) is that this includes all the diffs of my commits. In other words: All my code.

This makes it super easy for malicious crawlers to slurp up valuable data. I don’t like that.

I’m thinking about switching to this instead:

https://movq.de/git2/

It still shows project infos and there are Atom feeds, but to get the code, you have to actually clone the repos.

🤔

(If you spot any bugs, let me know.)

@dce@hashnix.club You may also be interested in the Twtxt App and the little tiny twtd publishing backend? 🤔

So just because I enjoy this kind of thing (looking into laws and trying to understand them…):

GDPR is about roles, not ownership

There’s no property right in personal data under GDPR. The whole regime hangs on three roles:

• Data subject — the person the data is about.
  
• Controller (Art. 4(7)) — “the natural or legal person … which, alone or jointly with others, determines the purposes and means of the processing of personal data.”
  
• The rights in Arts. 16 and 17 are exercised by a data subject against a controller. They compel a third party to rectify or erase. They are not self-executing duties that a piece of software must expose.
  

That’s the key. In your architecture, for a user’s own posts about themselves sitting in their own feed on their own device:

• the user is the data subject, and
  
• the user is also the only person “determining the purposes and means” of that data.
  

There is no third party controller to compel. The “right to erasure” is a right to make someone else delete — and there is no someone else. It is satisfied the instant the user can change the file. A UI button is a convenience, not a legal requirement. Omitting it removes zero rights, because the data is a plain-text file the user can edit or delete by any means — editor, sed, git, their file manager. Full practical control is retained; nobody is being denied anything by anyone.

@itsericwoodward@itsericwoodward.com Wrote it up 👌 Single-user twtd API is now documented (plain JSON, one bearer token) — posting, uploads, profile, followers + WebFinger: https://git.mills.io/yarnsocial/twtd/src/branch/main/API.md 🎉 Shout if anything’s unclear for TwtKpr 🙏

twtpub.com is just the default instance tho — it’s a multi-tenant twtd, AGPLv3. Run your own and I’ll list it in the app’s picker so folks choose where to land 🤗 keeps it decentralised + spreads the load. Docs → https://git.mills.io/yarnsocial/twtd

🥳 Finally! After nearly 4 years, yarnd v0.16.0 “Silver Sojourner” is out! 🚀 Twt Hash v2, SQLite FTS5 search, HTMX-powered UI, first-time setup wizard and literally hundreds of bug fixes 🐛

Release notes: https://git.mills.io/yarnsocial/yarn/releases/tag/0.16.0

Upgrading is fully automatic — the Twt Hash v2 migration re-fetches all feeds on first start, so expect the first cycle to be a bit heavier. Images on Docker Hub as prologic/yarnd:0.16.0 👌

cc @kat@yarn.girlonthemoon.xyz @abucci@anthony.buc.ci @shinyoukai@yume.laidback.moe @eldersnake@we.loveprivacy.club 🙏