@prologic@twtxt.net Iām pretty sure thatās going to happen at some point or has already happened. š Is this āthe dark webā? š
It happened.
āCan you help me debug this program? I vibe coded it and I have no idea whatās going on. I had no choice ā learning this new language and frameworks would have taken ages, and I have severe time constraints.ā
Did I say ānoā? Of course not, Iām a ānice guyā. So Iām at fault as well, because I endorsed this whole thing. The other guy is also guilty, because he didnāt communicate clearly to his boss what can be done and how much time it takes. And the boss and his bosses are guilty a lot, because theyāre all pushing for āAIā.
The end result is garbage software.
This particular project is still relatively small, so it might be okay at the moment. But normalizing this will yield nothing but garbage. And actually, especially if this small project works out fine, this contributes to the shittiness because management will interpret this as āhey, AI worksā, so they will keep asking for it in future projects.
How utterly frustrating. This is not what I want to do every day from now on.
@bender@twtxt.net So far so good š Iāll let you know how things go though!
@lyse@lyse.isobeef.org In my case it was a silver necklace, a hummingbird with a wing connected with the cold welding I mentioned using thin brass wires.
It made it in a goldsmithing class (I went to a private craftmanship high-school) so no phones allowed (no photos of it) and no ātake homeā of the works.
Hereās a rough sketch of it drawn by memory, the dots in the wing is where it connects to the body.
The technique is basically the same as i described, but the scale is much smaller, the whole piece was about 5-6 cm on the largest side.
The rivet was made by drilling a hole through the parts, than with a short and thicker drill you widen the hole on the surface to let the rivet settle flatter on the piece, then with a rubber hammer you hit it to flatten the head until itās snug on the hole, lock them together by doing the same on the other side.
Note that widening the hole with a thicker drill head wonāt make a difference with bigger holes, mine had holes of about 1-2 mm of diameter maximum.
Hereās a sketch of what is going on for clarity.
@prologic@twtxt.net Oh, thatās cool! :-) Feeding magpies seems to be an Aussie thing, the Cutting Edge Engineering Australia videos usually also include a cute magpie feeding clip.
@bender@twtxt.net Off you go to the magpie hunt! We wanna see Florida pies!
Today, I experimented with Linux Capabilities as a continuation to my Unix Domain Sockets research from a few months ago: https://lyse.isobeef.org/caller-information-via-unix-domain-sockets/#capabilities
I learned that I donāt know hardly anything and there is heaps more to explore. Tomorrow, I will do the same in Go and see how that feels.
Now I feel the urge to go around looking for one of āmy ownā to share. š I love crows, ravens, magpies, all of them in the corvidae family.
@zvava@twtxt.net No HEAD
requests, but regular GET
s with If-Modified-Since
request headers if possible: https://git.mills.io/yarnsocial/yarn/src/branch/main/internal/fetcher.go#L270
Okay, I give up. The āshopping listā app⢠on my phone broke for no reason whatsoever, there wasnāt even an update. Iām going back to pen and paper.
@thecanine@twtxt.net content warning please! I had to go home and change, if you catch my drift. LOL. Well done!
url
metadata field unequivocally treated as the canon feed url when calculating hashes, or are they ignored if they're not at least proper urls? do you just tolerate it if they're impersonating someone else's feed, or pointing to something that isn't even a feed at all?
(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z)
, because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing
I like that property (an off-ramp to location-based addressing), so I think I could live with that approach. ā
(Iām not sure why weāre using text fragments, though. Wouldnāt that link to the first occurence of 2025-10-01T10:28:00Z
? Thatās not necessarily correct. And, to be proper URLs that Firefox and Chromium understand, it would also need to be written as 2025%2D10%2D01T10:28:00Z
. The dash carries meaning, sadly. I think all this just creates needless complication. How about we just go with https://example.com/tw.txt#2025-10-01T10:28:00Z
?)
@zvava@twtxt.net Iām not sure, I could just set up a cors-anywhere
via docker in a minute and it would work the same.
Still, I could write one with just a dozen lines of Go or Node.js, I might consider writing one after the client is working decently.
I think Iām just about ready to go live with my new blog (migrated from MicroPub). I just finished migrating all of the content over, fixing up metadata, cleaning up, migrating media, optimizing media.
The new blog for prologic.blog soon to be powered by zs using the zs-blog-template is coming along very nicely š It was actually pretty easy to do the migration/conversation in the end. The results are not to shabby either.
Before:
- ~50MB repo
- ~267 files
After:
- ~20MB repo
- ~88 files
Pretty happy with my zs-blog-template starter kit for creating and maintaining your own blog using zs š Demo of what the starter kit looks like here ā Basic features include:
- Clean layout & typography
- Chroma code highlighting (aligned to your site palette)
- Accessible copy-code button
- āOn this pageā collapsible TOC
- RSS, sitemap, robots
- Archives, tags, tag cloud
- Draft support (hidden from lists/feeds)
- Open Graph (OG) & Twitter card meta (default image + per-post overrides)
- Ready-to-use 404 page
As well as custom routes (redirects, rewrites, etc) to support canonical URLs or redirecting old URLs as well as new zs
external command capability itself that now lets you do things like:
$ zs newpost
to help kick-start the creation of a new post with all the right āstuffā⢠ready to go and then pop open your $EEDITOR
š¤
@bender@twtxt.net @movq@www.uninformativ.de Thank you! Not sure what I end up putting in there, but Iām sure I will find some tools to go in. :-)
Yes, this was a flat piece of sheet metal. It went together like a cardboard box, just much slower and with timbers clamped down to get a straight folding line. I donāt have a sheet metal brake, so I just carefully hammered the piece bit by bit. Like in this video by the Sheet Metal Dude: https://www.youtube.com/watch?v=WYgEfWEMXk0
@prologic@twtxt.net No, this is a Linux manpage from the man-pages
project: https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man/man7/ascii.7
I do have an idea whatās going on. Could be an unfortunate interaction between the table preprocessor tbl
and the man
macro package. š¤
Task for this weekend:
https://movq.de/v/b05a7ce782/vid-1758959332.mp4
When you call man ascii
, you get this nice table, but thereās a weird vertical line at the bottom. That line is supposed to be a vertical rule and is supposed to go from the bottom of the table all the way to the top.
Letās see if I can debug this. (Not getting my hopes up at this point, but Iāll try.)
@movq@www.uninformativ.de See hereās the thing⦠I just donāt fucking gt this whole āleftā vs. ārightā shit⢠anymore. None of it makes any sense whatsoever. When my wife tries to explain it to me itās completely the opposite to what you just said just now š± ā So from here on, Iām just going to keep things simpleā nuttersā and ānormalā š¤£
@prologic@twtxt.net you doing this reminded me of mkws, and Adi. Good times, we have seeing so many people come and go. It is kind of sad, when I think about ājjlā, and Phil, and the many othersā¦
I am feeling āmushyā today. Ugh, ageing sucks.
@alexonit@twtxt.alessandrocutolo.it Yeah I think weāre overstating the UNIX principles a bit here 𤣠I get what youāre trying to say though @zvava@twtxt.net š If I could go back in time and do it all over again, I would have gotten the Hash length correct and I would have used SHA-256 instead. But someone way smarter than me designed the Twt Hash spec, we adopted it and well here we are today, it works⢠š
Please donāt hate me today; Iām a bit grumpy and have too many reasons to be upset:
- 2 counts of pushing and trying to get the simplest things done at work (that for some reason are made more difficult than they should be)
- This whole Chat Control bullshit
- And some other person things going on that have been ongoing for 72 days and counting š¤¬
@zvava@twtxt.net Going to have to hard disagree here Iām sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) Iām sorry youāve completely lost me! Iām old enough to pre-date before Linux became popular, so Iām not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject)
whose contents is a cryptographic content-addressable hash of the āthingā⢠youāre replying to and forming a chain of other replies (a thread).
Iām sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a āMagic Dateā for which our clients use the modified function(s).
@alexonit@twtxt.alessandrocutolo.it My problem is I donāt see a world where we donāt employ some form of cryptography to use as keys for threads in databases and other such things honestly. Iām not going to use url#timestamp
as keys.
I just created a zs blogging template which Iām going to use for https://prologic.blog and I might starting writing long-form again soon⢠š So far the ābloggingā template/engine (if you weill) is quite simple. It comprises essentially of an index.md
a prehook
and a few utilities:
$ git ls-files
.gitignore
.zs/config.yml
.zs/editthispage
.zs/include
.zs/layout.html
.zs/list
.zs/months
.zs/now
.zs/onthispage
.zs/posthook
.zs/postsbymonth
.zs/prehook
.zs/scripts
.zs/styles
.zs/tagcloud
.zs/taglist
.zs/years
archives/.empty
assets/css/site.css
assets/js/main.js
index.md
posts/hello-zs-blog.md
posts/on-tagging.md
posts/second-post.md
tags/.empty
I was trying to say (badly):
Thatās kind of my position on this. If we are going to make significant changes in the threading model, letās keep content based addressing, but also improve the user experience. Answering your question, yes I think we can do some combination of both.
@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.
@alexonit@twtxt.alessandrocutolo.it Yhays kind of love you!! Stance and position on this. If we are going to make chicken changes in the threading model, letās keep content based addressing, but also improve the use of experience. So in fact, in order to answer your question, I think yes, we can do some kind of combination of both.
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 Herw you go: https://git.mills.io/yarnsocial/twtxt.dev/pulls/28
@kat@yarn.girlonthemoon.xyz nope, not normal. Something birdy (because why to use fishy all the time?!) is going on.
[2025/09/11 12:56:01.816] ā please set config.host
when trying to run "bbycll". How to bypass that tiny hurdle?
Woot, thank you! Using a config.json
like this:
{
"host": "localhost:31212",
"protocols": ["http"]
}
Indeed did the trick! I know it isnāt production ready, but I wanted to see with my own eyes, locally, how did it look. :-) I like where you are going! It is looking very nice, and polished. Canāt wait for an alpha, beta, and release!
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecasesā¦.my friendās feed with like four posts parsed correctly so i tried this accountās feed and well now im not going to bed on time
edit: remaking demo video
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecasesā¦.my friendās feed with like four posts parsed correctly so i tried this accountās feed and well now im not going to bed on time
future sophia is going to have Fun cleaning up this mess
I have a feeling that learning to play electric double bass through an amplifier was a big mistake.
At the core, this is an acoustic instrument. If you play it through an amp, you will instinctively only do the bare minimum to get some sound going, because the amp does the heavy lifting. But itās just not right.
This is a very physical instrument. It needs a lot of force and strength ā in comparison, an electric bass guitar is almost flimsy and delicate. I need to āfeelā whatās going on and thatās just not the case when using headphones.
I feel like I wasted ~3 years. 𫤠But maybe itāll get better from now on ā¦
Hmm, gnu.org is slow as heck. Shorter HTML pages load in about ten seconds. This complete AWK manual all in one large HTML page took a full minute: https://www.gnu.org/software/gawk/manual/gawk.html Is there maybe some anti AI shenanigans going on?
In any case, I find the user guide super interesting. My AWK skills are basically non-existent, so I finally decided to change that. This document is incredibly well written and makes it really fun to keep reading and learning. Iām very impressed. So far, I made it to section 1.6, happy to continue.
@zvava@twtxt.net Yes congrats and well done! Keep going! š„³
Fellow Gophers might find this interesting, too: https://flak.tedunangst.com/post/what-the-go-proxy-has-been-doing
@movq@www.uninformativ.de Sounds cool! I think Iāll also have a goā¦
Welp, my rentās gone out and my student loan wonāt be in for another week, so Iām not spending anything for a while. Howās everyone elseās September going?
@prologic@twtxt.net Iām doing that now as well, but I donāt think this is a good solution. This is going to hurt āself-hostingā in the long run: I cannot afford true self-hosting where I actually do host everything here at home ā instead, I must use a cloud provider / VPS for that. It is only a matter of time until my provider starts doing AI shit as well (or rather, the customers do it) and then what? I get blocked, e.g. I canāt send email to (some) people anymore. This is already bad and itās going to get worse.
It doesnāt pose a problem for my serverās performance ā yet. But if more bots/companies start doing this, my website will go down from the load.
We use all the Microsoft programs at work - Teams and Outlook especially.
After all kinds of technical problems with Teams, that sometimes go unresolved for over a year, Microsoft shifted their priorities away from fixing things and towards adding an annoying AI Copilot button, that just takes up space and all it does, is loads the website in Teams, so I disabled it. Soon they just add it back, but in a different row of icons, therefore itās now a different button, you have to disable (I think they added yet another one, to the Teams, on my work phone and I had to disabled that too). Not too long after, the desktop one just enabled itself, because of āan errorā and I can disable it, but doing so activates a popup, that begs you to turn it back on, every once in a while. You canāt disable the popup and can only click āYesā or āNot nowā on it. I still keep it disabled, out of principle, but yesterday I noticed yet another Copilot button, this time in the top right corner of my Outlook and this one cannot be disabled, on the business version of Outlook and even on the personal one, itās only possible to do it through hidden privacy settings, by prohibiting the program from connecting to Microsoft servers, for extra āfeaturesā.
Thereās people complaining about it online, so itās clear nobody really wants it, but at this point Microsofts position is that you will have at least one useless AI button on your screen, at any given time, and you will be happy. And yes, their AI sucks and if I absolutely have to use AI for something, thereās already 2 better options, we have access to, at work.
@prologic@twtxt.net Enjoy the weekend. š„³ (I rarely drink these days. I hope my tiny little Whisky collection doesnāt go bad. š)
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 ā¦)
@movq@www.uninformativ.de At this rate, Iām going to be carrying a feature phone in a few yearsā time.
@thecanine@twtxt.net I sure hope thereās going to be push back. Is it going to happen, realistically? I donāt know.
RIP Android:
https://9to5google.com/2025/08/25/android-apps-developer-verification/
Since nobody is going to push back on this (I donāt even know if that would be possible), this is going to be a reality on every platform sooner or later.
Iād guess in 20, 30 years, there wonāt be āPCsā anymore. No more home computing, no more āI just write my own softwareā. You wonāt own devices anymore, itāll all be rented and the landlord will tell you what you can do with it.
I hope that Iām wrong, but given where we are today, I donāt think that I will be.
@movq@www.uninformativ.de Nice picture, this hot air balloon has quite a large basket.
Yes, go for it! :-)
My grandpa went ballooning ages ago and liked it. The balloonist misjudged the height a bit and landed in an open-air pool. Well, not in the water, but on the sunbathing lawn just inside the fence. :-D After the ride, everybody was given a very long personal name that they had to memorize. Decades later, my grandpa still knew his assigned name.
The most important thing to know is that ā in German ā you donāt fly (fliegen) a ballon, but ride (fahren) it: https://de.wikipedia.org/wiki/Ballonfahren#Fahren_oder_fliegen Judging by the English wikipedia article, this is not an English thing, though: https://en.wikipedia.org/wiki/Hot_air_ballooning
@prologic@twtxt.net Yeah, those POS thingies are similar. Thereās āESC/POSā as a variant of āESC/Pā, if Iām not mistaken.
All I can say is, when I go to big stores like Amazon, then I have trouble finding ātraditionalā dot matrix printers for use at home. š Epson still sells them, but theyāre more expensive than my laser printer was. So yeah, they still exist, just expensive, by the looks of it.