Mesa 25.3-rc4 Brings Fix For Many Steam Play Games To Properly Run On Intel Linux Driver
Mesa 25.3-rc4 is available for testing as the latest weekly candidate as we work toward the Mesa 25.3 stable release this month… ⌘ Read more

Intel’s Rewrite Of Linux MM CID Code Showing Some Nice Gains For AMD
Posted last month were new Linux kernel scheduler-related patches rewriting the MM CID management code. The main takeaway for end-users from this set of 19 Linux kernel patches from an Intel engineer was seeing 14~18% improvement in a PostgreSQL database benchmark but that more benchmarks were needed. Curiosity got the best of me and I recently tested these patches on an AMD EPYC server to seeing some very enticing results for this in-development c … ⌘ Read more

Intel’s Rewrite Of Linux MM CID Code Showing Some Nice Gains For AMD
Posted last month were new Linux kernel scheduler-related patches rewriting the MM CID management code. The main takeaway for end-users from this set of 19 Linux kernel patches from an Intel engineer was seeing 14~18% improvement in a PostgreSQL database benchmark but that more benchmarks were needed. Curiosity got the best of me and I recently tested these patches on an AMD EPYC server to seeing some very enticing results for this in-development c … ⌘ Read more

Amazon is Testing an AI Tool That Automatically Translates Books Into Other Languages
An anonymous reader shares a report: Amazon just introduced an AI tool that will automatically translate books into other languages. The appropriately-named Kindle Translate is being advertised as a resource for authors that self publish on the platform.

The company says the tool can translate entire boo … ⌘ Read more

Benchmarking The AMD EPYC 9V64H: Azure HBv5’s Custom AMD CPU With HBM3
Nearly one year ago Microsoft announced the HBv5 virtual machines powered by a custom-designed AMD 4th Gen EPYC processor with high bandwidth memory (HBM3). Finally today the Azure HBv5 series is reaching general availability for those with memory-intensive HPC applications and other workloads. Microsoft kindly provided Phoronix with HBv5 access in advance to begin testing these new VMs with the AMD EPYC 9V64H CPUs featuring HBM memory, so … ⌘ Read more

I had a looksie (just to be sure) at the database, and they were thankfully legit test events. But this did spark/trigger me to make sure I have some form of anti-spam measures in place. So I added some per-event / per-rsvp rate-limiting and honeypot(s).

@bender@twtxt.net Well see that’s just what the freak’n tests say about me haha 🤣

immigration and multiculturalism

What about it? I grew up in a multicultural country.

Test.

And I need to make something absolutely clear as well here. Twtxt was completely and utterly dead back in {Aug 2020](https://yarn.social/about.html) when I came across the spec and its simplicity and realised the lost opportunity. Since then we’ve continued to grow a small but thriving community. The extensions we’ve built over time have stood and lasted the test of time for the past ~5 years. We need not break things too badly, because what we have today and was designed years ago actually works quite well™ (despite some flaws).

@bender@twtxt.net A renewed vision test might be a good idea for some people. 😅 I mean, it is kind of curious that you get this license as a young person and then it lasts a lifetime, without any further tests. As long as you don’t screw up really bad, it remains valid …

@movq@www.uninformativ.de better than in the US. Our lasts only 10 years, and you need to go through the vision test, and, of course, pay). Recently they added a little gold star denoting “real ID” compliance, and we had to pay $10 to get the old one replaced—out of the regular renew “schedule”.

In here it is all about control, and money.

@zvava@twtxt.net @movq@www.uninformativ.de I’m not entirely sure about the spaces, but maybe they were omitted to simplify parsing of mentions in the form of @<nick url>. If the next token after the @<nick does not look like a URL, it’s not a mention but regular text. This is just wild guessing, though.

Looking at the regex and tests in the original twtxt reference implementation seems to confirm that theory in the sense as it relies on whitespace as the delimiter:

https://lyse.isobeef.org/tmp/screenshot-2025-09-17-21-30-25.png

Another thing about nicks is that the original twtxt reference implementation converts nicks to all lowercase:

https://lyse.isobeef.org/tmp/screenshot-2025-09-17-21-20-39.png

You probably know this already, the original twtxt file format specification can be found here: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

As for extensions, I don’t know of anything outside of twtxt.dev that has actually been (partially) implemented. However, there is also the issue tracker of the official reference implementation. You might wanna dig through that. For example, there is an alternative suggestions of multiline messages: https://github.com/buckket/twtxt/issues/157

I corrupted my SQLite test database with sed -i s/… $(find …). Clearly, I found too many files. That’s the signal to go to bed.

@zvava@twtxt.net wow, this is a full change, and looking very, very, very good! I am ready to test it. 🙈

@lyse@lyse.isobeef.org Didn’t know that, either. 😂 The one guy even tried to test this theory with a Polaroid? And “confirmed” it? What the heck. 🥴

I’ve got a prototype of my hardcopy simulator going. I’m typing on the keyboard and the “display” goes to the printer:

https://movq.de/v/56feb53912/s.png

https://movq.de/v/235c1eabac/MVI_8810.MOV.mp4

The biiiiiiiiiig problem is that the print head and plastic cover make it impossible to see what’s currently being printed, because this is not a typewriter. This means: In order to see what I just entered, I have to feed the paper back and forth and back and forth … it’s not ideal.

I got that idea of moving back/forth from Drew DeVault, who – as it turned out – did something similar a few years back. (I tried hard to read as little as possible of his blog post, because figuring things out myself is more fun. But that could mean I missed a great idea here or there.)

But hey, at least this is running on my Pentium 133 on SuSE Linux 6.4, printer connected with a parallel cable. 😍

(Also, yes, you can see the printouts of earlier tests and, yes, I used ed(1) wrong at one point. 🤪 And ls insisted on using colors …)

@aelaraji@aelaraji.com I use Alt+. all the time, it’s great. 👌

FWIW, another thing I often use is !! to recall the entire previous command line:

$ find -iname '*foo*'
./This is a foo file.txt

$ cat "$(!!)"
cat "$(find -iname '*foo*')"
This is just a test.

Yep!

Or:

$ ls -al subdir
ls: cannot open directory 'subdir': Permission denied

$ sudo !!
sudo ls -al subdir
total 0
drwx------ 2 root root  60 Jun 20 19:39 .
drwx------ 7 jess jess 360 Jun 20 19:39 ..
-rw-r--r-- 1 root root   0 Jun 20 19:39 nothing-to-see

@prologic@twtxt.net Mosaic (2.7) works fine, I maintain that package in the AUR and test my website regularly. 😅

https://movq.de/v/d7787d6fb1/s.png

@movq@www.uninformativ.de yes, I think:

<!--[if !IE]><!-->
<link rel="stylesheet" href="../simplicity.css”>
<!--<![endif]-->

Should work, but I haven’t tested it.

@bender@twtxt.net Here’s a short-list:

• Simple, minimal syntax—master the core in hours, not months.
  
• CSP-style concurrency (goroutines & channels)—safe, scalable parallelism.
  
• Blazing-fast compiler & single-binary deploys—zero runtime dependencies.
  
• Rich stdlib & built-in tooling (gofmt, go test, modules).
  
• No heavy frameworks or hidden magic—unlike Java/C++/Python overhead.

Anyone want to help me alpha/beta test the new WAF I’m building? It’s a Caddy module. 🤔

Why are we testing, or playing with, an alternate non-fully-compatible feed format within the same feed that we use daily?

Hopefully I haven’t missed or messed anything upu 😅

* 101f3eb0 - (HEAD -> main) Fix a bunch of UX to do with following/unfollowing, bookmarking and unbookmarking (3 seconds ago) <James Mills>

Testing UI/UX is hard™ 😉

@lyse@lyse.isobeef.org You are of course right! 🤣 There are some low level components that can and should be unit tested for sure! 👌

I’m not even being facetious here either. I’d llove to see you “unit tests” this:

@lyse@lyse.isobeef.org Well you are being slightly rude 🤪 Sure you could write unit tests for this, but in practise testing emergent properties and behaviors of a system is actually a lot harder than you might realize. But I’m happy to always be proven wrong 😑

@kat@yarn.girlonthemoon.xyz I’ve almost fixed this btw 🤗 Just testing it thoroughly and polihsing the code. In case you’re curious, I do this style of development called “Observability Driven Development” (ODD) whereby I make observations of the system via metrics and internal observations and adjust the system’s overall behavior to the desired outcome 😅

@andros@twtxt.andros.dev I set up a test feed here:

https://www.uninformativ.de/texudus.txt

I made some preliminary adjustments to my client so that it can work with the different threading model. (And I totally get the concerns, this can be quite a bit of work. Especially in a large code base like Yarn.)

@kat@yarn.girlonthemoon.xyz Don’t be nervous, I make sure I test the shit™ out of things before anyone else does 🤣

Hello @Yarn.social@yarn.social 👋 (testing something)

@test_dont_fetch@aelaraji.com Let’s raise another from the dead! “Facio, Voco, Ferre” 🧝 🪄 #ForScience

@xuu@txt.sour.is or @kat@yarn.girlonthemoon.xyz Do either of you have time this weekend to test upgrading your pod to the new cacher branch? 🤔 It is recommended you take a full backup of you pod beforehand, just in case. Keen to get this branch merged and to cut a new release finally after >2 years 🤣

I’ll see if I can fix this and write a test case for what’s going on here. I think this is made difficult now because folks like @eapl.me@eapl.me decide that it’s okay to have a . (period) in their # nick 🤣 tbh I think nick(s) should have rules of what they can and cannot be comprised of. i.e: no punctuation 🤦‍♂️

Testing mentions, immediately followed by commas. Let’s see: @prologic@twtxt.net, this one is local, it might not break. Now, this one @ isn’t local. Nor this @ one. Will they break. Let’s find out!

Scratch that, no bug in jenny. There’s actually a test case for this. Python normalizes -00:00 to +00:00, so the negative case never happens.

Hahaha! And now they show tiny! I had to reload the page. So, I see the problem on iOS and macOS Safari too. I have no other browser to test with, I exclusively use Safari.

Test

Hmmm? Test?

Yup, it is certainly something on the codebase here. /end of test

@bender@twtxt.neteapl.me@eapl.me test

@bender@twtxt.neteapl.me@eapl.me just testing this mention, to see which random nick will be picked. Related, I agree, those animations are truly awesome!

Test:

this is a code block
[2025-04-08 17:50:00] with a timestamp in brackets

The end.

Test: An emoji 🐧

Test: Just ASCII

@eapl.me@eapl.me Thank you for this!

I cast a test vote. Did it work? :-)

#testing @ Hi Bob, nice to meet you!

@lyse@lyse.isobeef.org OK. So how I have worked things like this out is to have the interface in the root package from the implementations. The interface doesn’t need to be tested since it’s just a contract. The implementations don’t need to import storage.Storage

• storage/ defines the Storage interface (no tests!)
  
  • storage/sqlite for the sqlite implementation tests for sqlite directly
    
  • storage/ram for the ram implementation and tests for RAM directly
    
• controller/ can now import both storage and the implementation as needed.
  

So now I am guessing you wanted the RAM test for testing queries against sqlite and have it return some query response?

For that I usually would register a driver for SQL that emulates sqlite. Then it’s just a matter of passing the connection string to open the registered driver on setup.

https://github.com/glebarez/go-sqlite?tab=readme-ov-file#connection-string-examples

maybe even an internal that has the shared test stuff

My hypothesis about that thing breaking my twts is that it might have something to do with the parenthesis surrounding the root twt hash in the replay twt-A when I replay to it with fork-twt-B; I imagine elisp interpreting those as a s-expression thus breaking the generation precess of hash (#twt-A) before prepending it to for-twt-B … but then I’m too ignorant to figure out how to test my theory (heck I couldn’t even recalculate the hashes myself correctly in bash xD). I’ll keep trying tho.

@andros@twtxt.andros.dev yes, that usually happens when twts get edited and we just made a gentlemen agreement to avoid edits as much as possible (at least for the time being). But the thing is, That is not what’s happening with my broken twts’ hashes. Since I’ve bee mostly replaying to my own twts as a test and I know for sure that I haven’t edited any. (I usually fork-replay instead of edit a twt when needed)