@bender@twtxt.net You saw it in person, I suppose? I watched the stream last night. 😅

@movq@www.uninformativ.de pretty cool, thanks for sharing! We saw the rocket go up yesterday, but it didn’t occur to me to pull out the camera and take a shot until it was gone. I mean, the visible window is also quite short! 😅

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

@falsifian@www.falsifian.org Thanks for clarification. I already thought something along those lines. Wow, so, you can really mix different encodings in a single file, crazy. My Perl experience is limited to maybe 10, 20 or at the very most 30 written lines of code over the decades.

@falsifian@www.falsifian.org Thanks, I’ll keep this in mind in case I’m ever around your neighborhood. ;-)

@falsifian@www.falsifian.org wow, it has been a while since I saw Fossil. I am surprised it is still around!

@lyse@lyse.isobeef.org For reasons I can’t fully explain, we have a bunch of courses in the area, most in public parks (they integrate nicely since they can be built with the existing landscape, only adding some yellow baskets, concrete starting pads, and maybe signs).

In my experience, the main difference between a disc golfer and a frisbee thrower is that the disc golfer will often have a bag full of different shapes of discs (including drivers of varying ranges and/or putters). Even in my small bag, I’ve got some long range drivers (a Beast, a Cheetah, a Valkyrie, and a Wraith), my aforementioned MRV (Mid-Range Vector), an ultralight Aero (which feels similar to a “standard” frisbee), and 2 “rubber” putters (softer plastic, less “bouncy”).

Image

@bender@twtxt.net Thanks, and you are correct: MRV stands for Mid-Range Vector (I think) as it is a stable mid-range driver (it says so on the disc):

Image

@itsericwoodward@itsericwoodward.com Thanks! To be clear, my contribution was literally adding that sentence to the documentation, after other people did the work.

@falsifian@www.falsifian.org Congrats! That’s no small feat.

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

@lyse@lyse.isobeef.org how odd! I can’t replicate. 😩

Congratulations, @falsifian@www.falsifian.org! I don’t even know what “lexically enabled” means.

@bender@twtxt.net Hahaha, I love it! :‘-D Rolls right of the tongue.

@itsericwoordward@itsericwoodward.com @bender@twtxt.net Haha, same. Neither did I come across disc golf before. Who knows, maybe I just confused these people for regular frisbee players. But it’s been literally years, if not decades, that I saw people throwing disc shaped objects.

@bender@twtxt.net Hehehe! :-D

And a tiny, tiny bit of snow and hail again this arvo. Almost nothing. Right now, the sun is out.

@itsericwoordward@itsericwoodward.com @bender@twtxt.net Well, even hard-reloading doesn’t change anything. I also just noticed that hovering over the tab title makes it completely invisible. In contrast to the buttons, here, the text color is exactly the same as the background color:

Since I prefer the light theme, that’s no big deal for me. 8-)

@itsericwoodward@itsericwoodward.com today I learned about “disc golf”. I had no idea that existed. I am assuming the “MRV” is a model/brand for a disc? Any physical activity is good, specially one you enjoy!

@falsifian@www.falsifian.org that’s it, you ought to call your next child 2aea97bf3f5c2ea62cf5e701858694b7378ed58c! :-P

For what is worth, I am not experiencing what @lyse@lyse.isobeef.org described. Tested with Firefox on Ubuntu, and Safari on macOS.

@lyse@lyse.isobeef.org Thanks (again) for the heads-up!. I’m not sure why you were seeing black text, but I just pushed a new version of the library (v0.10.1) with some updated colors in the demo’s themes (which should hopefully address the contrast issues).

The dark mode was an aesthetic choice by a designer with a strong preference for dark mode (and who thought the maroon looked better as a background color), but in the interest of being supportive of my audience, I added a localstorage-backed memory to the theme toggle (so when you turn it to light mode, it should remember for future visits).

@movq@www.uninformativ.de LOL.

@quark@ferengi.one

talk next to nothing

I could rant about AI a bit and how it ruins every day at work, if that helps? 🤣

and a reply to it, just for giggles. I miss the days all we talked about was twtxt. Now we have vans, and talk next to nothing. ;-) :-P LOL.

First twtxt after upgrading (as I don’t want a reply to count as one).

@quark@ferengi.one Ta-tah 🥳

@movq@www.uninformativ.de woot! 🥳

git pull
warning: redirecting to https://movq.de/git/jenny.git/
Fetching objects: 38, done.
From https://uninformativ.de/git/jenny
   ac51ce5..f44424c  main       -> origin/main
 * [new tag]         v26.03     -> v26.03
Updating ac51ce5..f44424c
Fast-forward
 CHANGES |  4 ++++
 LICENSE |  2 +-
 README  | 10 +++++-----
 3 files changed, 10 insertions(+), 6 deletions(-)

@movq@www.uninformativ.de cd ~/jenny && watch -n 25 git pull. :-D

@prologic@twtxt.net @lyse@lyse.isobeef.org Yay! Time for a new jenny release, then. 😊

@itsericwoordward@itsericwoodward.com Nice. I just wanted to let you know that the black text color on nearly black button background color in the twtHash tab is basically unreadable. I’ve no idea why the dark theme is preferred over the light one in my browser anyway. :-D

@movq@www.uninformativ.de @itsericwoordward@itsericwoodward.com @prologic@twtxt.net These are excellent news! \o/

@itsericwoodward@itsericwoodward.com pretty cool!

@lyse@lyse.isobeef.org Thanks for the heads-up.

It lead me to publish an updated version of twtxt-lib (v0.10.0) which supports the v2 hashing algorithm: https://twtxt-lib.itsericwoodward.com/

@prologic@twtxt.net 🥰

@lyse@lyse.isobeef.org This is good! 💪 Let’s merge this.

Hey all my dear twtxters! Again, please have a look at https://git.mills.io/yarnsocial/twtxt.dev/pulls/28 so that we can button the Twt Hash v2 Extension up soon. Love to get some feedback, comments, questions, doubts, critiques, improvements, etc.

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.

@movq@www.uninformativ.de that’s it, fork it!. I am forking vim. :-D

@zvava@twtxt.net rooting for it, and you! As soon as there is a stable (no future truly breaking changes) working alpha (can post, can follow, can reply), I will give it a spin! And yes, I understand the contradiction of “stable” and “alpha”; hoping my meaning comes through, LOL.

@kiwu@twtxt.net that’s exactly right. Pretty niche, occasionally exuberant. 🤭

@zvava@twtxt.net 💪🏻💪🏻💪🏻

@zvava@twtxt.net how is that client coming along? “/me gently pushes zvava towards a working desk” 😂

@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 @bender@twtxt.net That sounds great! I, too, have taken Friday off work. But I’m slaving away again at the move of one of my best mates.

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

@thecanine@twtxt.net congrats on the win! Hopefully it will not turn sour with the next “enter period of time here”. It seems flip-flopping is the law of the land around here.

I never got to ask you, are you affected by this as a developer, or end user, or both?

@movq@www.uninformativ.de Thank you! I uploaded the full resolutions with uppercase extensions.

@movq@www.uninformativ.de I like the new one!

@lyse@lyse.isobeef.org Thank you for the suggestions. I will probably do some of that when I have time. For the thumbnails, I’m also thinking about trying the loading=“lazy” img attribute. Top on my mind is actually understanding why the big images don’t load. Maybe my VPS’s network connection is saturated, for example. I’ve never needed to worry about such things until now. I’m looking forward to spending some time on it.

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