@movq@www.uninformativ.de But even the same model behaves differently if you upgrade to a newer version. Or it hopefully should, why otherwise would one want to update in the first place? A fixed, predictable output would be the result of us oldtimers doing something with inferior, ancient technology!

@lyse@lyse.isobeef.org Oh, yeah, right, I hadn’t even considered that (we mostly use one model). Choose a different model and it does something completely different. Cool stuff.

@d6b80: Use gopher over the portal gopher.floodgap.com/gopher/gwlite . You always present the same ip to the internet. But of course you are logged. You can do so by any old browser and mobile, that id capable for http.

Another AI rant:

One of the “key features” of LLMs is that you can use “natural language”, because that is supposed to be easier than having to learn a programming language. So, when someone says to me, “I automated this process using AI!”, what they mean is: They have written a very, very large Markdown document. In this document, they list what the AI is supposed to do.

In prose.

This is a complete disaster.

Programming and programming languages have one crucial property: They follow a well-defined structure and every word has a well-defined meaning. That is absolutely brilliant, because I can read this and I can follow the program in my head. I can build a mental model. I can debug this, down to the precise instructions that the CPU executes. This all follows well-defined patterns that you can reason about.

But with these Markdown files, I am completely lost. We lose all these important properties! No debugging, no reasoning about program flow, nothing. It’s all gone. It’s a magic black box now, literally randomized, that may or may not do what you wanted, in some order.

People now throw these Markdown files at me … and … am I supposed to read this? Why? It’s completely random and fuzzy.

Sadly, these AI tools are good enough to be able to mostly grasp the authors intentions. Hence people don’t see the harm they cause, because “it works”.

We already have a ton of automations like this at work: Tickets get piped through an LLM and these Markdown files / prompts determine what will happen with the ticket, and maybe they trigger additional actions as well, like account creation or granting permissions. All based on fuzzy natural language – that no two humans will ever properly agree on.

Jesus Christ, we’re now INTENTIONALLY bringing the ambiguity of legal texts and lawyers into programming.

Using natural language is NOT easier than using a programming language. It is HARDER. Have you people never read a legal contract? And that stuff can STILL be debated in a court room.

I can’t begin to comprehend why we, tech folks, push this so hard. What is wrong with you? Or me?

(And, once again, we’re ignoring other factors here. LLMs use a ton of energy and ressources, that we don’t have to spare. It’s expensive as fuck. It doesn’t even run locally on our servers, meaning we give all these credentials and permissions to some US company. It’s insane.)

I love the smell of the rainy air. Sooooo good. The thunderstorm is gonna miss us now, two closer bangs, but that’s supposed to be it.

@movq@www.uninformativ.de I couldn’t agree more! I also have the feeling that it causes more people to just accept “it’s a software problem, there’s nothing that can be done about it”. Which is very frightning to me.

Up until now, I was successful in refusing to actively use that crap. I had to do one mandatory AI training, but even our hippest AI enthusiasts found it absolutely terrible. Probably also nailed together by the same rubbish they want us to now use everyday as much as possible.

Code reviews are the part that I have to deal with most. And I believe that the code quality is degrading.

Let’s hope the bubble bursts sooner than later. It will definitely burst at some point. That’s for sure.

@lyse@lyse.isobeef.org Yes, and that’s why I’m 100% convinced that we’ll see a massive brain drain in a couple of years. This will affect young people even more, because they don’t have all the “old” knowledge to fall back on.

It’s concerning, I’ve warned about it many times, nobody listens.

I think the best thing one can do is explicitly not use any AI tools but keep your actual skills intact. Might be out of a (good) job for a while, but once this bubble bursts, this is who is going to get hired again. (I think.)

And considering how insanely expensive all this is, I’m still (mostly) convinced that the bubble will actually burst. This stuff just isn’t sustainable.

… or I might be wrong. And if so, I see an even darker future that I don’t want to put into words right now.

@movq@www.uninformativ.de Now, it’s official, I AM an idiot. Yeah, thank you, that’s it! Apparently, I’ve quickly unlearned to use my brain with great success. :-(

@lyse@lyse.isobeef.org

Disclaimer: Can’t guarantee that I’m fully awake and I’m being trained at work not to use my brain anymore, so maybe this is complete bullshit. 😪🧟‍♀️

It says here that SQLite uses signed integers:

https://sqlite.org/datatype3.html

In pure bits, 1 << 63 would be 0x8000000000000000, but as a signed value, it gets interpreted as -9223372036854775808. Subtracting 1 yields -9223372036854775809 – but that doesn’t fit in 64 bits anymore. It’s possible that SQLite doesn’t want to wrap around but instead saturates? Haven’t checked. 🤔

With 62 bits, there is enough room.

With 1 << 64, I have no idea how SQLite wants to handle this, because this should immediately trigger a warning, because it doesn’t fit right away. Maybe it gets truncated to 0?

sqlite> select printf('0x%x', 2 * (1 << 64));
╭──────────────────────╮
│ printf('0x%x', 2 ... │
╞══════════════════════╡
│ 0x0                  │
╰──────────────────────╯
sqlite> select printf('0x%x', 0 - 1);
╭──────────────────────╮
│ printf('0x%x', 0 ... │
╞══════════════════════╡
│ 0xffffffffffffffff   │
╰──────────────────────╯
sqlite> select printf('0x%x', 0 - 2);
╭──────────────────────╮
│ printf('0x%x', 0 ... │
╞══════════════════════╡
│ 0xfffffffffffffffe   │
╰──────────────────────╯

Everything changes, right? I know we sound like curmudgeons, and perhaps AI is the next step. We are living its early infancy, the struggles and dislikes, the errors and flaws, and generations after us will simply benefit from it, and see it as natural as my children see the Internet today (it isn’t natural to me, I was born way before it).

Or maybe AI isn’t the next step. Either way, whether we like it or not, there is truly absolutely nothing (or close to) we can do. Well, complain we can, of course. :-P

@bender@twtxt.net I’m in the US as well!

Using Marginalia Search’s Backlink Search ?~L~X https://thenewleafjournal.com/b/DyH

Via https://github.com/newsboat/newsboat/issues/3220#issuecomment-4198066671 I came across this nice selection on why not to use AI: https://github.com/Vxrpenter/AIMania/blob/main/WHY.md#why

This then lead me to the slopware list: https://codeberg.org/small-hack/open-slopware

Holy shit, there’s even more than I thought. :-O In addition to Vim, the following affects me more or less daily (but hopefully not my ancient versions): curl, VLC, ImageMagick, rsync, Python, systemd and even the Linux Kernel itself. Oh fuck me dead. :‘-(

@kiwu@twtxt.net what in the world?! Where? Long gone here (US).

Today I used minify and entr and bash scripting to replace gulp 🤓

So, you want to send an anonymouse message to Amazon? See the following link: https://www.bbb.org/us/wa/seattle/profile/ecommerce/amazoncom-1296-7039385

What do the Gopher Troopers think of the following? The Gopher protocol is a nearly-forgotten network protocol from the early 1990s, designed to serve and navigate text-based menus and documents over the Internet. While it’s far less common than HTTP/HTTPS today, there are still some security risks associated with Gopher and Gopher space. Let’s break them down carefully: 1. Lack of Encryption Problem: Gopher was designed long before widespread use of SSL/TLS. All data—including credentials, file transfers, and menu selections—is transmitted in plaintext. Impact: Anyone intercepting traffic (e.g., via a network sniffer, public Wi-Fi, or a compromised router) can read sensitive information, including usernames and passwords. 2. No Authentication or Access Control Problem: Gopher servers rarely implement robust authentication; access control is usually limited or non-existent. Impact: Unauthorized users might browse sensitive directories or download private files, particularly if servers are misconfigured. 3. Server Software Vulnerabilities Problem: Modern OSes can still run legacy Gopher servers, but the software is often unmaintained. Impact: Old software may contain buffer overflows, directory traversal bugs, or command injection vulnerabilities that attackers could exploit. 4. Malicious Gopher Links Problem: Gopher menus can contain links that point to scripts or other servers, similar to hyperlinks in HTTP. A client following a malicious link could inadvertently: Download malware Access sensitive internal network resources (server-side request forgery) Impact: Could serve as a vector for attacks if a user opens content from untrusted sources. 5. Legacy Protocol Weaknesses Problem: Gopher lacks modern web security mechanisms like: Content security policies Same-origin policies Cross-site request forgery protection Impact: If Gopher is bridged to other services (like modern browsers via gateways), old vulnerabilities may be exposed. 6. Information Leakage Problem: Gopher servers often provide directory listings without restriction. Impact: Sensitive files, backup directories, and internal documents may be exposed unintentionally. 7. Bridging Risks Problem: Some modern browsers access Gopher via gateways (HTTP-to-Gopher proxies). These bridges may: Expose sensitive internal resources to the gateway Introduce logging or tracking that wouldn’t exist on pure Gopher Impact: Attacks could occur indirectly through insecure intermediaries. Key Takeaways Gopher is inherently insecure due to its design in a pre-HTTPS era. Main threats: eavesdropping, unauthorized access, malware delivery, and exploitation of unpatched server software. Safe practice: Use Gopher only in isolated, trusted environments, or through secure HTTP(S) gateways with proper sanitization.

@movq@www.uninformativ.de Yeah. Unfortunately. :-( I tried to bring up the subject of dependency upgrade reviews a few times, but nobody else cared. We finally experienced a supply chain attack (luckily, didn’t turn out too horrible for us, could have been worse) and this got the discussion slowly rolling again. So, publication of this article is perfect timing. Let’s see. Admittedly, I don’t have high hopes. And I bet someone suggests to use AI agents…

Azabache returned just a few minutes later when the sparrow or great/blue tit was gone. Next time I will use a tripod to record the video. Also sorry about the sound, I used all my Audacity skills to remove the noise, but somehow, combining the video and audio track in kdenlive somehow messed up the sound. There’s some horrible sqealing towards the beginning.

The sun was out and tricked everybody to believe it’s nice and warm. However, with the wind, the 11°C felt way colder. Still, super nice out there, I enjoyed it a lot. The quick trip to the dairy farm took me more than double the regular time, because I took close to 400 photos. Oh boy, Lyse is such an idiot!

https://lyse.isobeef.org/waldspaziergang-2026-04-02/

@movq@www.uninformativ.de @bender@twtxt.net Waaaahhhh, they’re coming closer to earth one kilometer every second!! They’re crashing right into us!

I didn’t know either that we send people to the moon again! :-O Cool. And bender witnessed this historic moment in person. Awesome! :-)

@itsericwoordward@itsericwoodward.com Doesn’t matter if I use w3m or elinks. No, just kidding. Firefox 115. See also #47fl5jq.

@movq@www.uninformativ.de with the current regime, everything is, to put it politely, rather odd, and in disarray. They have yesterday’s window, otherwise the next one was on the 12 of April, or something like that. We knew it was going up for a few days, but we are used to that kind of thing, so it is not that super exciting any more. LOL.

Yeah, I saw it in person.

@lyse@lyse.isobeef.org That’s crazy! If you don’t mind me asking, what browser are you using when you see this?

@bender@twtxt.net Glad to hear it, I’ve neglected a Safari test thus far.

Thank you both for checking.

@itsericwoordward@itsericwoodward.com That’s a nice collection. :-)

It made me look at my single frisbee, that was last used maybe 8 years ago, possibly more. I immediately found it in the drawer I thought it was in. And alongside some other stuff I was unsuccessfully hunting for for literally months by now. Thanks, mate! ;-)

Hopefully, my good headlamp also reveals itself at some point in time.

@lyse@lyse.isobeef.org Oops, I guess the new text is a bit obscure. If you follow the link, the text is a bit more explicit, but you still need to know what a lexical scope is. Anyway, this is part of Perl moving very carefully toward being UTF-8 by default while also not breaking code written in the 90s. If you name a recent version like “use v5.42;” then Perl stops letting you use non-ASCII characters unless you also say “use utf8;”. The “lexically” part basically means that strictness continues until the next “}”, or the end of the program. That lets you fix up old code one block at a time, if you aren’t ready to apply the new strictness to a whole file at once.

You should study your tools if you’re planning to FAFO with them. Now use a live USB and see if the grub files are missing something, or just learn how grub works.

Let us send snail-mail to Google and ask them to keep Android open (https://keepandroidopen.org) physical addresses of offices can be found here: https://about.google/company-info/locations/

This one comes from this years (now scrapped) April 1st DLSS 5 gag, that was originally supposed to use Microsofts AI - in ways similar to the Nvidia technology, which produced interesting, overly detailed results. I wanted to see if I could beat the AI thing at drawing something like that myself and many redraws later, this is my best result.

@bender@twtxt.net both, but neither directly. I know every workaround there is, including those used by developers, to test apps, while working on them. However if “sideloading” becomes so tedious, even the more technical users, cannot be bothered to do it, competing appstores and independent developers, not wanting to send their money and ID to Google, loose users at such rate, they likely won’t be able to justify continuing to maintain their projects, people like me rely on.

@prologic@twtxt.net must be nice. Congrats! I am happy for you! 😂 Off jesting, enjoy mate! The rest of us will continue slaving ourvselves. 😅

In the interest of fairness and hopefully for the last time, I ever have to address this, Google has flip-flopped again and promised “sideloading” will not be removed from their version of Android, but instead have to be enabled in the developer settings, using the following “advanced flow”:

To be perfectly clear, this still falls short of what I wanted, but at this point, it is a compromise I’m willing to take, over further pursuing this, through the various available European courts, myself.

Here is their full statement:
https://android-developers.googleblog.com/2026/03/android-developer-verification.html

@fe55c : Hi, which client do you use on Haiku? It seems to me that the protocol has been removed from WebPositive?

@prologic@twtxt.net don’t! You might be into troubles. Just record something small, and masterful, for us to listen, forget the costume. 😅

I’m happy to report that, earlier today, I published an early version of express-twtkpr: an ExpressJS library that enables hosting (and directly posting to) a twtxt.txt file. It works great (otherwise you wouldn’t be able to read this), but it’s still in alpha and lacks documentation, examples, tests, installation flexibility, or polish, so please use it at your own risk. Enjoy! https://www.npmjs.com/package/express-twtkpr

I’m supporting incremental SQLite schema changes to just upgrade from an older database version to whatever the current software version supports. In the past, I already noticed that this is quite expensive in unit tests when each test case runs through the entire schema patches and applies them one by one.

To speed up test execution I now decided that I finally go through the troubles of maintaining both a set of incremental patches and a full schema setup in one go. A unit test verifies that both ways end up with the same structure. This gives me a set of SQLs to check the structures:

SELECT type, name, tbl_name, sql
FROM sqlite_schema
ORDER BY type, name, tbl_name

Unfortunately, the resulting CREATE TABLE SQL queries are formatted differently, depending on whether the full schema was set up in one big step or the structure had been modified with ALTER TABLE. Mainly, added columns are not on their own lines but appended in one physical line. That’s why I wanted an SQL formatting tool. Since I didn’t find one that works decently, I’m now doing some simple string manipulation. Joining consecutive whitespace into a single space character, removing spaces before commas and closing parentheses and spaces after opening parentheses. This works surpringly good enough. Of course, if it fails, the “diff” is absolutely horrendous.

Now for the cool part, my test execution dropped from around 5:05 minutes to just 1:32 minutes! I call that a win.

I just stumbled across PRAGMA table_info('tablename') https://sqlite.org/pragma.html#pragma_table_info, PRAGMA foreign_key_list('tablename') and friends. I guess, I have to play with that, now. It’s probably much better to use than the SQL text approach.

@rdlmda@rdlmda.me I am reasonably happy with jenny. If I find time for a twtxt project, I would like to make a web page that works as follows: you point it to your own twtxt feed (as a URL parameter), and then it shows you all the feeds referenced by your “# follow =” lines. So, if I put this up, anyone could use it to view their own feed, with no login required. (Probably a difficult project. For example, I’d want to make sure the backend couldn’t be tricked into helping ddos a web server by trying to fetch lots of “feeds” from it. Anyway, I have too many other projects.)

@falsifian@www.falsifian.org Correct, the two smaller versions are loading perfectly fine. The hickup is only for the originals. But in all reality, the middle ones are sufficient for me personally. Please don’t get me wrong, at least for the people photos, the subjects are large enough. The Japanese landscapes, however, would definitely benefit from a bit more detail. ;-)

I just tried it once more, and now, the tree with the sign (/photo/5Zy4pqVIt0oP/IMG_20251106_035048_448.jpg) fully loaded very quickly. Same with the Japanese dish (/photo/tJbmg8oleYbh/IMG_20251030_091719_086.jpg) and shopping center (/photo/qXG5ucIjpPju/IMG_20251029_045002_778.jpg). But the previous and next ones all ran into the same problems again. When I’m very lucky, I eventually get the upper half. Typically not even that much, a third, a fifth, or even less.

Waiting a bit before making an attempt, the wooden walkway through the forest or park (/photo/ojQpDLfBoGN4/IMG_20251023_043829_011.jpg) eventually also made it. But unlike the other successful attempts, it took a long time.

The more photos you add, the more beneficial it might be to separate the index into several different albums. I didn’t measure it, but it felt like 10 to 20 seconds for all the thumbnails to load. That traffic adds up.

Another idea would be to strip the EXIF data from the thumbnails and reducing quality to 90% or even 80%. Using the famous tree with the sign, I cannot tell the difference between the original thumbnail and the 80% quality one. I’m sure it depends on the subject. Here are the numbers:

$ convert -strip IMG_20251106_035048_448_size_400.jpg stripped.jpg
$ convert -quality 90 IMG_20251106_035048_448_size_400.jpg 90.jpg
$ convert -quality 80 IMG_20251106_035048_448_size_400.jpg 80.jpg
$ convert -strip -quality 90 IMG_20251106_035048_448_size_400.jpg 90-stripped.jpg
$ convert -strip -quality 80 IMG_20251106_035048_448_size_400.jpg 80-stripped.jpg
$ ls -lh *jpg | awk '{print $5 " " $9}' 
46K 80.jpg
45K 80-stripped.jpg
64K 90.jpg
63K 90-stripped.jpg
132K IMG_20251106_035048_448_size_400.jpg
127K stripped.jpg
$ ls -l *jpg | awk '{print $5 " " $9}'
46160 80.jpg
45064 80-stripped.jpg
65012 90.jpg
63916 90-stripped.jpg
135070 IMG_20251106_035048_448_size_400.jpg
129647 stripped.jpg

** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to “store now, decrypt later” attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html

😱😱😱

@rdlmda@rdlmda.me it is called, in Spanish, “the mother”. It is created through a bit (not by much) effort, and kept as a starting point. Just like Asian cuisine has dishes that never cool, always cooking leaving always a base on it.

How do you think a lathe (and just about any tool, etc.) is done? Yup, in part by using a lathe. 😅

@movq@www.uninformativ.de just use https instead:

git clone https://git.mills.io/yarnsocial/twtxt.dev.git

@bender@twtxt.net Yes, really should have chosen my words more wisely. As @movq@www.uninformativ.de mentions, we got a vague promise of an “advanced flow” being implemented, and in my case also a vague promise of a video call, with someone at Google, regarding it. Now when the backlash died down, it does not look like Google plans to follow through, with any of this and they’re completely unwilling to elaborate and get back to us, about if and how any of this will be implemented.

@rdlmda@rdlmda.me I never saw the point of a registry to be honest, as it defeated the point of what I believed to be a truly decentralised non-social social ecosystem. What can and does work however is a search engine and crawler. I used to run one, but I took it down, mostly because it got expensive to operate, at least the implementation I built… Maybe one day i’ll try again with a SQLite backend.

@rdlmda@rdlmda.me You might or might not find this useful: https://lyse.isobeef.org/tmp/twthash.py

@rdlmda@rdlmda.me most of our conversations used to be about twtxt, I am not going to lie. Lately? Not so much. It turns out (a) we don’t need a longer hash, (b) we don’t care so much about changing addressing, and © I am just Bender, what else can I say? :-D :-P

@movq@www.uninformativ.de Luckily, I’ve never encountered any bugs in Vim with my type of work and features I use.

HEY! I think we all noticed that privacy is dying. Government and corporate entities around the world are building the laws and tools to track you, from everything you write, to the media you consume, to where you drive your car and the people you associate with. Gopher I believe Is one of the last bastions of freedom away from what I call “Corpo web”. GopherSpace is free, I wrote my client so I know it’s safe, and I can route my traffic over tor or any proxy of my choosing. I think we should use gopher as a means to communicate and get out of the modern corpo web because soon everything you do and say on the modern web or possibly corporate owned devices is under scrutiny, even more so than it ALREADY IS. Right now I can use tor and my custom gopher cli to communicate privately here. With the ways the laws are going they are going to implement things like age verification to track you and they’ll deem privacy focused open source software as tools for circumventing these rules. It’s a slippery slope. I need to stop writing before I sound really crazy.

I call it a success! (Please excuse the terrible background noise and bad audio in general. I’m not a sound engineer at all. Also, no idea why I use plural in the beginning. :-?) https://lyse.isobeef.org/tmp/5mm-dowels/

@prologic@twtxt.net well, it isn’t rocket science, is it? 😅 Yet, without using the hashes and starting to follow people, it is very, very rudimentary. I know, I know, there were a couple of years during which people lived just fine without those. Yet, once you get used to certain things, there is no going back.

@rdlmda@rdlmda.me You need to use the RFC3339 format. I would recommend you read the specs at https://twtxt.dev – This is what is used by many moden clients these days 😅

Synced CSS across my Bear Blog and other site pages. Also using front matter in source markdown files, and outputting meta descriptions ✅