Searching txt.sour.is

Twts matching #date
Sort by: Newest, Oldest, Most Relevant

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

​ Read More

Friday, my love, we meet again. I am going to take you to lunch, and pamper you. I will led you to believe you are the only one in my life, but then, as the working day sunsets, I shall leave you at the door, like a stood up girl by her prom date.

Weekend babies, here we come! 😂

​ Read More
In-reply-to » @movq Yeah, that would also be fine with me. I certainly do like the "arbitrary" in your comment.

@lyse@lyse.isobeef.org Mhm, yeah, I also think I like date := time.Date(2026, time.June, 19, /**/ 17, 0, 0, 0, time.UTC) the most. đŸ€” (My only gripe with this is that it isn’t obvious whether the third 0 is milli-, micro- or nanoseconds. These days it’s probably nanoseconds, but you never know.)

​ Read More
In-reply-to » @lyse Oh wow, we’re talking about such a detailed level. đŸ€”

@movq@www.uninformativ.de Yeah, that would also be fine with me. I certainly do like the “arbitrary” in your comment.

While writing the article, I also thought about something like that:

date := time.Date(2026, 6, 19,
    17, 0, 0, 0, time.UTC)

Or possibly:

date := time.Date(
    2026, 6, 19,
    17, 0, 0, 0, time.UTC,
)

But it’s four lines for a damn timestamp. I also contemplated whether a comment acting as a separator is all that’s needed:

date := time.Date(2026, 6, 19, /**/ 17, 0, 0, 0, time.UTC)

I might like that the most. Not entirely sure yet. It kinda feels like a hack, but still a little elegant. Add your comment on top and we’re golden. Maybe?

I deliberately excluded them as this only distracted from the points I wanted to make. And I also realized that this example was just not ideal at all. Perhaps I should add them nevertheless?

If I ever invented a programming language, a much more human readable timestamp representation of some sort, RFC 3339 or very close to that would be part of that language. Something along the lines of /pattern/ for regexes in certain languages.

​ Read More
In-reply-to » In the light of current events, I will first consult my pillow and only then write an article about readable code.

@lyse@lyse.isobeef.org Oh wow, we’re talking about such a detailed level. đŸ€”

I agree with most of what you said.

I probably would have written it like this:

// Arbitrary reference date.
//                   Y  m   d   H  M  S  nano
date := time.Date(2026, 6, 19, 17, 0, 0, 0, time.UTC)

Would this be better or worse? 😅

​ Read More
In-reply-to » Oh boy, I absolutely hate this stupid trend of not writing changelogs anymore! Why the fuck would one seriously consider it to be a viable option to just let some shitty bot spew all merge requests on a goddamn GitHub release?! First of all, these merge request titles suck balls. The order of the changes in this "changelog" is completely random (well, probably merge time, which is as useless as the dick on the Pope). They are not grouped by anything at all. Additions, changes, removals, deprecations, etc. randomly mixed up in one giant list. And then "Add feature X", seventeen kilometers further down "Revert 'Add feature X'". Fuck you! Don't include this shit in the first place!

@lyse@lyse.isobeef.org Thanks!

On the AI changelog part, though, I’d rather recommend to just not have a changelog at all.

I’m afraid that ship has sailed. You can rest assured that someone who uses AI/LLMs for their code (which is almost everybody at this point) will most certainly also use it for changelogs.

I actually considered not mentioning AI output at all, because this just opens a huge can of worms 
 😞

While going through these terrible GitHub release pages, I also found these “New Project Contributors” sections

Yeah, they play on a nerd’s pride.

Now, it’s just the same auto shitshow with MR titles in a rolling date-versioned release scheme. It’s just our team who has to deal with that, though. I think I’m the only one who is not a fan of it.

I’ve found that this whole situation is much worse at work than it is in the Free Software world. At work, it’s literally work and hardly anybody actually cares. We still don’t have all people convinced that writing good commit messages or using good branch names is worth the time. It’s 
 oh god, no, I’m going to stop here, this is bad for my mental health. 😅

Suffice it to say, all release notes at work are now AI-generated. Nobody gives a fuck.

​ Read More
In-reply-to » Oh boy, I absolutely hate this stupid trend of not writing changelogs anymore! Why the fuck would one seriously consider it to be a viable option to just let some shitty bot spew all merge requests on a goddamn GitHub release?! First of all, these merge request titles suck balls. The order of the changes in this "changelog" is completely random (well, probably merge time, which is as useless as the dick on the Pope). They are not grouped by anything at all. Additions, changes, removals, deprecations, etc. randomly mixed up in one giant list. And then "Add feature X", seventeen kilometers further down "Revert 'Add feature X'". Fuck you! Don't include this shit in the first place!

@movq@www.uninformativ.de Hahaha, great timing! :-D I love your article and agree with almost all your points.

On the AI changelog part, though, I’d rather recommend to just not have a changelog at all.

Another important thing for me is the deprecation notice section. What do I need to look out for in the future? Should I start to migrate to another API soon? Even right now? Or does it have time?

While going through these terrible GitHub release pages, I also found these “New Project Contributors” sections (yeah, for that, they found the time to make a section) annoying. Don’t get me wrong, sure, credit where credit is due. But come on. Soooooo much space for an inefficiently formatted (and also unsorted) list. At least it was easy enough to skip over it.

And then, there are also these changelogs or rather notice documents in general that are infested with multicolored emojis all over the place. My brain’s spam filter kicks in and shoves everything to /dev/null immediately. It’s especially a thing at work.

In my previous work project, we also used the Keep A Changelog Format. That was great. You wouldn’t believe how often I resorted back to that document. At least twice a week, often several times a day. I was very glad that we put in this effort. Of course, writing the changelog took its time, but it was worth every minute and more. Reading a many months old item, it was immediately clear. I was our best customer in that regard.

Now, it’s just the same auto shitshow with MR titles in a rolling date-versioned release scheme. It’s just our team who has to deal with that, though. I think I’m the only one who is not a fan of it.

​ Read More

A man kept asking his flatmate on dates. Talika’s idea might fix the problem
Years of soaring property prices have meant the age of renters extend well beyond young adults and into new generations. But for women, it can come with additional hurdles. ⌘ Read more

​ Read More

Jetstar flights lock in date for opening of Sydney’s new airport
The long-awaited launch of passenger flights to Western Sydney Airport will follow the start of cargo aircraft taking off from the new aviation hub next month. ⌘ Read more

​ Read More

Are Freo the team to beat this season? Behind the Bunbury belting where nothing went wrong
Meanwhile, on the same day, the Eagles didn’t just lose the match, but also their most consistent player to date this season. How will this impact West Coast’s hopes for the season ahead? ⌘ Read more

​ Read More

Anti-Vax Dating Apps Are Going IRL. People Are Mad as Hell About It
Unjected and PureBlood.Dating are hosting in-person meetups—and have transformed the dating landscape into a political battleground over bodily autonomy. ⌘ Read more

​ Read More

Alpha School’s Ritzy New York City Campus Costs $65,000 a Year—but Isn’t Actually a School
A homeschooling center in Manhattan is part of the company’s nationwide expansion. Internal documents reveal its strategy: “Opening date > safety.” ⌘ Read more

​ Read More

Data Brokers’ and AI Firms’ Opt-Out Forms Are Built to Fail, Report Finds
A new study finds AI companies, defense firms, and dating apps are among 38 data collectors allegedly using manipulative design to confuse users while collecting their data. ⌘ Read more

​ Read More

I just wanted to look up 9V block battery prices online and these automatically generated descriptions are getting dumber by the minute:

Datum der Erzeugung: Verfallsdatum minus 7 Jahre

(Date of manufacturing: expiration date minus 7 years)

Or look at this one:

Die leistungsstarke 9 V-Block E Batterie, auch 6LR61 genannt, eignet sich besonders gut fĂŒr Taschenlampen, Radio oder Kinderspielzeug, die einen gleichbleibenden Strombedarf haben. Ihre max. Spannung betrĂ€gt 1,5 V.

(The high performance 9 V block E battery, also known as 6LR61, is particularly suitable for torches, radio or child’s toys, which have a steady power demand. Its max. voltage is 1.5 V.)

The battery is best suited for
 devices where it fits. No shit, Sherlock! Has anyboy ever come across 9V block torches? O_o I haven’t.

​ Read More

The Secret to Amelia Dimoldenberg’s Online Superstardom? Control
The host of Chicken Shop Date joined WIRED’s Big Interview podcast to talk about turning down bad deals, beating the algorithm, and the importance of being over-prepared. ⌘ Read more

​ Read More

They Wanted to Join Raya. They’ve Been on the Waiting List for Years
Getting into Raya, the exclusive members-only dating app, has become nearly impossible for some. We met people who have waited as long as two, five, and even seven years to join. ⌘ Read more

​ Read More

Growers warn ‘watered down’ lavender oil widespread in surging imports
Despite an Australian lavender industry dating back to the 1850s, you’re more than likely using an imported and “watered-down” product, local growers say. ⌘ Read more

​ Read More

@movq@www.uninformativ.de I noticed that your feed’s last modification timestamp was missing in my database. I cannot tell for certain, but I think it did work before. Turns out, your httpd now sends the Last-Modified with UTC instead of GMT. Current example:

Sat, 03 Jan 2026 06:50:20 UTC

I’m not a fan of this timestamp format at all, but according to the HTTP specification, HTTP-date must always use GMT for a timezone, nothing else: https://httpwg.org/specs/rfc9110.html#http.date

​ Read More
In-reply-to » Which actively maintained Yarn/twtxt clients are there at the moment? Client authors raise your hands! 🙋

@lyse@lyse.isobeef.org Damn. That was stupid of me. I should have posted examples using 2026-03-01 as cutoff date. 😂

In my actual test suite, everything uses 2027-01-01 and then I have this, hoping that that’s good enough. đŸ„Ž

def test_rollover():
    d = jenny.HASHV2_CUTOFF_DATE
    assert len(jenny.make_twt_hash(URL, d - timedelta(days=7), TEXT)) == 7
    assert len(jenny.make_twt_hash(URL, d - timedelta(seconds=3), TEXT)) == 7
    assert len(jenny.make_twt_hash(URL, d - timedelta(seconds=2), TEXT)) == 7
    assert len(jenny.make_twt_hash(URL, d - timedelta(seconds=1), TEXT)) == 7
    assert len(jenny.make_twt_hash(URL, d, TEXT)) == 12
    assert len(jenny.make_twt_hash(URL, d + timedelta(seconds=1), TEXT)) == 12
    assert len(jenny.make_twt_hash(URL, d + timedelta(seconds=2), TEXT)) == 12
    assert len(jenny.make_twt_hash(URL, d + timedelta(seconds=3), TEXT)) == 12
    assert len(jenny.make_twt_hash(URL, d + timedelta(days=7), TEXT)) == 12

(In other words, I don’t care as long as it’s before 2027-01-01. 😏😅)

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

​ Read More
In-reply-to » I just noticed this pattern:

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 
 ?

​ Read More
In-reply-to » @aelaraji tell us all about it, without omitting details!

@bender@twtxt.net You are totally correct! The thing is: The Caveman within was thinking how minimal can one go before things start to get too uncomfortable? And if cavemen weren’t supposed to be too self-conscious about their spelling, I could have just ssh remote echo "$(date -Is)\tTwt Twt Mother-Lover! đŸ€ŁđŸ€Ł" >> /path/to/twtxt.txt and called it a day.

​ Read More
In-reply-to » @aelaraji tell us all about it, without omitting details!

Just typing twts directly into my twtxt file.

Details:

  • Opening my twtxt file remotely using vim scp://user@remote:port//path/to/twtxt.txt
  • Inserting the date, time and tab part of the twt with :.!echo "$(date -Is)\t"
  • In case I need to add a new line I just Ctrl+Shift+u, type in the 2028 and hit Enter
  • In order to replay, you just steal a twt hash from your favorite Yarn instance.

It looks tedious, but it’s fun to know I can twt no matter where I am, as long as can ssh in.

​ Read More
In-reply-to » @lyse it hasn't happened yet. It is this coming Saturday.

@bender@twtxt.net Hm, are we talking about different dates or are there different timezone offsets for this timezone abbreviation? With EDT being UTC-4, 2025-11-02T12:00:00Z is Sunday at 8:00 in the morning local time for you. Or were did I mess up here? :-?

@prologic@twtxt.net You want me to submit a reply with “I probably won’t show up”?

​ Read More

Terres rares : la Chine verrouille, Trump riposte, l’Europe paie
Coup de tonnerre sur le commerce mondial : les Chinois, d’habitude prudents, commerçants et cherchant le compromis, dĂ©cident d’imposer de nouveaux contrĂŽles drastiques Ă  l’exportation de leurs terres rares, y compris raffinĂ©es et utilisĂ©es dans les technologies modernes. Ainsi, dans une annonce rĂ©cente du ministĂšre chinois du Commerce datĂ©e du 9 octobre 2025, on apprend que [
] ⌘ Read more

​ Read More

Speed dating a solution to the slow dating lives of farmers
When the dating app radius won’t reach the edge of your property, and you’re harvesting grain from sun-up til sundown, how do you find a partner? ⌘ Read more

​ Read More

Adieu les pubs, bonjour les micropaiements AI ? Le partenariat Google Deepmind et Coinbase qui pourrait booster les créateurs
Enfin, les geeks vont enfin pouvoir avoir des copines virtuelles qui leur rĂ©clament de l’argent ! Eh oui, dans l’intelligence artificielle, les choses avancent dĂ©cidĂ©ment trĂšs vite et mĂȘme si le prĂ©cĂ©dent billet sur le sujet ne date que d’un mois, l’actualitĂ© impose d’y revenir alors qu 
 ⌘ Read more

​ Read More

M5 MacBook Air: Release Date, Features, and Performance Predictions
The MacBook Air is Apple’s most popular laptop – a thin, fanless machine that wields quiet power thanks to the efficiency of Apple silicon. While the M4 model isn’t exactly old, attention is already turning to its successor.

Image

Apple doesn’t telegraph new product launches ahead of time, but we can draw a surprisingly clear picture 
 ⌘ Read more

​ Read More
In-reply-to » https://zsblog.mills.io/ for anyone interested. I think I still have some small tweaking to do befor eI use this for realz.

the single posts have no date (intended?)

What do you mean by this? đŸ€”

​ Read More
In-reply-to » https://zsblog.mills.io/ for anyone interested. I think I still have some small tweaking to do befor eI use this for realz.

@prologic@twtxt.net need to work on the CSS. For example, the tags are too big, the code blocks (and the inline ones) are too small, the single posts have no date (intended?), and so on. It’s an alpha start!

​ Read More
In-reply-to » @bender Really? đŸ€”

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

​ Read More
In-reply-to » @bender Really? đŸ€”

@bender@twtxt.net Well honestly, this is just it. My strong position on this is quite simple:

Do the simplest thing that could work.

It’s one of the age old UNIX philosphies.

Therefore, the simplest thingℱ to do here is to just increase the hash length, mark a magicℱ date/time as @lyse@lyse.isobeef.org has indicated and call it a day. We’ll then be fine for a few hundred years, at which point there’ll be no-one left alive to give a shitℱ anyway đŸ€Ł

​ Read More

The driver’s license documents in Germany now have an expiration date. You have to renew them every 15 years. (Not the license itself, just the documents.)

I just got my renewed documents. Their expiration date says something like 01.09.40. Huh? That looks super weird to me, like an error. But no, it’s 2040 
 Just 15 years away.

​ Read More

Silent Component Updates & Redesigned Update Experience
Following on from our previous initiative to improve how Docker Desktop delivers updates, we are excited to announce another major improvement to how Docker Desktop keeps your development tools up to date. Starting with Docker Desktop 4.46, we’re introducing automatic component updates and a completely redesigned update experience that puts your productivity first. Why We’re
 ⌘ Read more

​ Read More
In-reply-to » @lyse i dont mind if the hash is not backward compatible but im not sure if this is the right way to proceed because the added complexity dealing with two hash versions isnt justified

@zvava@twtxt.net There would be only one hash for a message. Some to be defined magic date selects which hash to use. If the message creation timestamp is before this epoch, hash it with v1, otherwise hammer it through v2. Eventually, support for v1 could be dropped as nobody interacts with the old stuff anymore. But I’d keep it around in my client, because why not.

If users choose a client which supports the extensions, they don’t have to mess around with v1 and v2 hashing, just like today.

As for the school of thought, personally, I’d prefer something else, too. I’m in camp location-based addressing, or whatever it is called. There more I think about it, a complete redesign of twtxt and its extensions would be necessary in my opinion. Retrofitting has its limits. Of course, this is much more work, though.

​ Read More

Prosodical Thoughts: Debian repository key change
We have been working on some changes to our Debian/Ubuntu package repository.
If you use our repository to keep up to date with new Prosody packages, you
need to take action before 4th August 2025 to continue receiving updates
smoothly.

New repository instructions

The ‘apt’ utility has been moving towards a new format for specifying package
repositories. If you are familiar with putting deb lines in a sources.list
file, [that method is changing](ht 
 ⌘ Read more

​ Read More

Felt the need to make this stupid reference - nobody will get, most likely. Feel free to guess (the file name and todays date, are both a hint), any other notes and opinions appreciated too, idk if I ever drew a standing one, from the front, before.

Image

​ Read More

US-backed Gaza aid group closes all distribution sites after shootings
The Gaza Humanitarian Foundation, which last week started handing out meals to hungry Palestinians inside the war-shattered Gaza Strip, said the sites would be reopened, but did not provide a date. ⌘ Read more

​ Read More

Age of Dead Sea Scrolls pinned down with the help of AI
A new study has used AI to decipher the age of the Dead Sea Scrolls, potentially rewriting what we know about when some of the world’s most precious biblical texts were created. ⌘ Read more

​ Read More

UK unveils radical defence overhaul as Starmer eyes Russian threat
British Prime Minister Keir Starmer tells the UK the “moment has arrived to transform how we defend ourselves” but has not given a date when UK defence spending will rise to 3 per cent of GDP. ⌘ Read more

​ Read More

Kumanjayi Walker inquest findings delayed after death in custody
The long-awaited coronial findings into the 2019 death in custody of Aboriginal man Kumanjayi Walker will be delayed by a month, after the death of another Warlpiri man in Alice Springs last week. ⌘ Read more

​ Read More

** Admitting that they’re really never weekly notes **
While everyone is up to their eyeballs in puzzles playing Blue Prince I’ve been playing some Fire Emblem: Blazing Sword on the Gameboy Advanced. I’ve also set up the playdate to mirror at my computer and have been having fun exploring the games in season 2! Mostly just Dig! Dig! Dino!, so far.

I decided to learn OCaml a few weeks ago. I’ve been writing a rogue clone in it. I am enjoying is and the entire ML fami 
 ⌘ Read more

​ Read More

Tea & Peaches: KubeCon + CloudNativeCon London Recap, Atlanta Sneak-Peek
KubeCon + CloudNativeCon Europe 2025 in London was nothing short of historic. As the biggest KubeCon to date — with 12,418 attendees, including 46% first-timers — it was a moment of celebration, reflection, and connection for
 ⌘ Read more

​ Read More

slowing working away at my latest code project: learning PHP by recreating the 2000s fandom mainstay known as a fanlisting! it’s been super fun i added a dynamic nav bar and other modifications in the latest commit

fanlistings even to this day rely on old PHP scripts dating back to the early 2000s that need whole ass mySQL or postgres DBs and are incredibly insecure. you can look at them here they’re like super jank lol it’s sad that new fanlistings have to use them because there’s no other options
.

​ Read More
In-reply-to » Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! đŸ˜± #Twtxt #Update

@prologic@twtxt.net Can you please draft up a specification for that proposed change with all the details? Such as which date do you actually refer to? Is it now() or the message’s creation timestamp? I reckon the latter is the case, but it’s undefined right now. Then we can discuss and potentially tweak the proposal.

Also, I see what you did there in regards to the reply model change poll. ]:->

​ Read More
In-reply-to » Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! đŸ˜± #Twtxt #Update

I will be adding the code in for yarnd very soonℱ for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes

​ Read More
In-reply-to » jenny really isn’t well equipped to handle edits of my own twts.

@kat@yarn.girlonthemoon.xyz It’s more like a cache, it stores things like “timestamp of the most recent twt we’ve seen per feed” or “last modification date” (to be used with HTTP’s if-modified-since header). You can nuke these files at any time, it might just result in more traffic (e.g., always getting a full response instead of just “HTTP 304 nope, didn’t change”).

@quark@ferengi.one Yes, I often write a couple of twts, don’t publish them, then sometimes notice a mistake and want to edit it. You’re right, as soon as stuff is published, threads are going to break/fork by edits.

​ Read More

@david@collantes.us If I run

printf '%s\n%s\n%s' 'https://aelaraji.com/twtxt.txt' '2025-04-16T22:49:11+00:00' "Am I tripping or `rsync` is actually THIS effing faster than `scp`!!? đŸ«š" | b2sum -l 256 | awk '{ print $1 }' | xxd -r -p | base32 | tr -d '=' | tr 'A-Z' 'a-z' | tail -c 8

I have xqfsv6a. It is raw text

But
 If I change de date to 2025-04-16T22:49:11Z I have si4er3q.

​ Read More

Erlang Solutions: Erlang Solutions’ Blog round-up
The tech world doesn’t slow down, and neither do we. From the power of big data in healthcare to keeping you up-to-date about fintech compliance, our latest blog posts explore the important topics shaping today’s digital world.

Whether you’re leading a business, building software, or just curious about the future of tech, check out what the Erlang Solutions team has been talking about.

Understanding Big Data in Healthcare

![](https://lh7-qw.goo 
 ⌘ Read more

​ Read More

Even though I really do like the shell, I always use Dolphin to mount my digicam SD card and copy the photos onto my computer. I finally added a context menu item in Dolphin to create a forest stroll directory with the current date in order to save some typing:

Image

The following goes in ~/.local/share/kservices5/ServiceMenus/galmkdir.desktop:

[Desktop Entry]
Type=Service
X-KDE-ServiceTypes=KonqPopupMenu/Plugin,inode/directory
Actions=Waldspaziergang;

[Desktop Action Waldspaziergang]
Name=Heutigen Waldspaziergang anlegen

Icon=folder-green
Exec=~/src/gelbariab/galmkdir "%f"

In order to update the KDE desktop cache and make this action menu item available in Dolphin, I ran:

kbuildsycoca5

The referenced galmkdir script looks like that:

#!/bin/sh
set -e

current_dir="$1"
if [ -z "$current_dir" ]; then
    echo "Usage: $0 DIRECTORY" >&2
    exit 1
fi

dir="$(kdialog \
    --geometry 350x50 \
    --title "Heutigen Waldspaziergang anlegen" \
    --inputbox "Neues Verzeichnis in „$current_dir“ anlegen:" \
    "waldspaziergang-$(date +%Y-%m-%d)")"
mkdir "$current_dir/$dir"
dolphin "$current_dir/$dir"

This solution is far from perfect, though. Ideally, I’d love to have it in the “Create New” menu instead of the “Actions” menu. But that doesn’t really work. I cannot define a default directory name, not to mention even a dynamic one with the current date. (I would have to update the .desktop file every day or so.) I also failed to create an empty directory. I somehow managed to create a directory with some other templates in it for some reason I do not really understand.

Let’s see how that works out in the next days. If I like it, I might define a few more default directory names.

​ Read More