I should have another look at #Kate
https://docs.kde.org/stable5/en/kate/kate/kate-application-plugin-external-tools.html
I should have another look at #Kate
https://docs.kde.org/stable5/en/kate/kate/kate-application-plugin-external-tools.html
«I used to laugh at my Chilean father’s paranoia about life in the US – not any more» — Stacy Torres
https://www.theguardian.com/us-news/ng-interactive/2025/apr/27/chile-trump-pinochet-authoritarianism
@lyse@lyse.isobeef.org likewise I don’t have the energy for a fundamental shift in any of our specifications that would inevitably cause a lot of toil and try and change in our clients implementations and unforeseen problems that we haven’t really fully understood:
@movq@www.uninformativ.de At this point someone needs to make a decision 🤣 @bender@twtxt.net keeps reminding me of that😅
Novo portal da #biblioteca da área de #engenharia e #arquitetura - BAE #Unicamp
@movq@www.uninformativ.de Agreed, finding the right motivation can be tricky. You sometimes have to torture yourself in order to later then realize, yeah, that was actually totally worth it. It’s often hard.
I think if you find a project or goal in general that these kids want to achieve, that is the best and maybe only choice with a good chance of positive outcome. I don’t know, like building a price scraper, a weather station or whatever. Yeah, these are already too advanced if they never programmed, but you get the idea. If they have something they want to build for themselves for their private life, that can be a great motivator I’ve experienced. Or you could assign ‘em the task to build their own twtxt client if they don’t have any own suitable ideas. :-)
Showing them that you do a lot of your daily work in the shell can maybe also help to get them interested in text-based boring stuff. Or at least break the ice. Lead by example. The more I think about it, the more I believe this to be very important. That’s how I still learn and improve from my favorite workmate today in general. Which I’m very thankful of.
I guess this is trivial to do with some pre-existing engine, but it’s more fun to do it yourself: https://movq.de/v/0cfa4e9504/world.tar.gz
@movq@www.uninformativ.de Wow, that’s sick! Assuming the rendering is correct, I never realized the mountain ranges being this steep and tall. This has real education potential for geography classes. Really cool!
Remembered a fun little “hello world” program I made in 2018:
https://movq.de/v/a1c4a819e6/vid.mp4
(It runs smoothly. My computer just isn’t fast enough for a smooth X11 screengrab at that resolution.)
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de In case you reconsider, it would be even easier then to just send an HTTP 429 Too Many Requests
. :-)
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.
@bender@twtxt.net Hehehe! :-D
@movq@www.uninformativ.de I have to admit, I didn’t follow the topic very closely, but I was under the impression that there were more votes on location-based addressing. But maybe I’m completely wrong. Anyway. I don’t have the energy to be part of a fundamental debate.
We’re all old farts. When we started, there weren’t a lot of options. But today? I’d be completely overwhelmed, I think.
Hence, I’d recommend to start programming with a console program. As for the language, not sure. But Python is probably a good choice
That’s what I usually do (when we have young people at work who never really programmed before), but it doesn’t really “hit” them. They’ve seen so much, crazy graphics, web pages, it’s all fancy. Just some text output is utterly boring these days. ☹️ And that’s my problem: I have no idea how I could possibly spark some interest in things like pointers or something “low-level” like that. And I truly believe that you need to understand things like pointers in order to program, in general.
@prologic@twtxt.net Thank you for writing this together. I just left a few comments.
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. ]:->
The community is heavily divided in this regard, and yet we need consensous. We’re like the three Borg in VOY: Survival Instinct. 🥴
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
Nah, I’m not taking any action yet. 😅 The good thing is that I don’t run a Git daemon on my server. It’s all just HTTP, which is fast and doesn’t consume a lot of memory.
@prologic@twtxt.net if not that, what else? Communism? Is there, really, such thing? 🤣
03:45 You can pretty blame capitalism for everything that’s wrong with anything 🤣
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 🚀🚀🚀🎉🎉🎉
I really do wish we would wake up and smell the roses here 🤦♂️ This whole sets of wars is utterly pointless. Senseless waste of precious human beings 😢
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
And by “foot” I meant food, because, you know, sometimes (more often than not) I am a fool.
@news-minimalist@feeds.twtxt.net so many “good news”, we are “winning” big time. I listen to NPR on my way to work, and they were talking about the foot depletion. You could hear the desperation of the people they put on, so incredibly sad. 😢
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.
@lyse@lyse.isobeef.org LOLed in RL, my office mates were, “what’s going on, where, what?!”. 😂
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de DDoS their ass! 🤣
tt2
from @lyse and Twtxtory from @javivf?
@bender@twtxt.net Yup! 👍
@lyse@lyse.isobeef.org Noice! 👌
Has anyone tried the dark arts of converting #SVG to #shapely recently? :(
twtxt.txt
feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
@lyse@lyse.isobeef.org Hahahaha 🤣 I mean it’s “okay” every now and then, but what’s the point of having good clients and tools if we don’t use ‘em 🤣
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
@lyse@lyse.isobeef.org Yup! Will do 🤗
Nothing like being paged at 00:30
(midnight) for a P2 incident that is now resolved at 02:10
🤯 Obviously I’m not going to work tomorrow (I mean today lol 😂) at the usual start time 🤦♂️
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de You better push new code sooner!!
As @bender@twtxt.net says, that sounds like a bot. I’d just block the IP address, hoping it doesn’t change all the time. But then you know for sure that it’s the AI fuckwits.
Also, the devil in me thinks it’s funny to swap out the repo in question for something entirely different. :-D
Oh wow, that 48 hours timelapse from SDO is super cool: https://social.bund.de/system/media_attachments/files/114/413/834/747/006/466/original/91b1698392ae5188.mp4 At the end, the moon is whizzing by.
@xuu@txt.sour.is Hahaha, that’s cool! You were (and still are) way ahead of me. :-)
We started with a simple traffic light phase and then added pedestrian crossing buttons. But only painting it on the canvas. In our computer room there was an actual traffic light on the wall and at the very end of the school year our IT basics teacher then modified the program to actually control the physical traffic light. That was very impressive and completely out of reach for me at the time. That teacher pulled the first lever for me ending up where I am now.
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de oi, that has to be a bot. AI bot? Maybe not, but still a bot. I see this becoming more and more of an issue, sorry to say…
@prologic@twtxt.net Exactly, @bender@twtxt.net! :-D This is at the entrance of a veggie farm (11 & 12) where there are free-ranging kids playing on the road, so people should slow down when driving there to buy some supplies. I also wondered why the sign says “Halt!” instead of “Langsam fahren!” (Drive slowly!) or something like that. On second thought, maybe to actually park there on the street right at the property line.
I actually never walked on that road before and discovered that this was a dead end. There’s usually at the very least a foot path on which to continue when passing a farm. Not this time, though. I didn’t want to stamp down the high grass to cut across country, so I had to walk back maybe 150 meters. Not too bad.
twtxt.txt
feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
@prologic@twtxt.net Phew, I’m indeed not twtxt.dev, because I sometimes actually do edit my feed with vim like a barbarian.
Someone has started to run git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
So far, this isn’t causing any issues. I think this is just a regular human being who misconfigured some automation. And I hope this doesn’t mean that the “AI” bots have finally discovered my page …
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. ]:->
tt2
from @lyse and Twtxtory from @javivf?
@prologic@twtxt.net I have:
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
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
We have 4 clients but this should be 6 I believe with tt2
from @lyse@lyse.isobeef.org and Twtxtory from @javivf@adn.org.es?
@bender@twtxt.net Same more or less 😅
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 pinging the involved (@andros@twtxt.andros.dev, @abucci@anthony.buc.ci, @eapl.me@eapl.me, @lyse@lyse.isobeef.org, @movq@www.uninformativ.de, @sorenpeter@darch.dk), just in case. I might have forgotten someone, please feel free to ping them.
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 I now see my twtxts as written in the proverbial stone. That is, no edits, no deletions, no matter how embarrassing their content might be. 😅
Hear, hear, @prologic@twtxt.net! :-)
And speaking of Twtxt (See: #xushlda, feeds should be treated as append-only. Your client(s) should be appending Twts to the bottom of the file. Edits should never modify the timestamp of the Twt being edited, nor should a Twt that was edited by deleted, unless you actually intended to delete it (but that’s more complicated as it’s very hard to control or tell clients what to do in a truely decentralised ecosystem for the deletion case). #Twtxt #Client #Recommendations
Just like we don’t write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt
feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation
@bender@twtxt.net Hehe good sleuthing 🤣 I swear it was an edit ✍️ Haha 😂 yarnd
now “sees” both every single time, where-as before it would just obliterate the old Twt, but remain in archive. Now you get to see both 😅 Not sure if that’s a good thing or not, but it certainly makes it much clearer how to write “code logic” for detecting edits and doing something more UX(y) about ‘em 🤔
yarnd
powering this pod twtxt.net 🧐
Or rather, https://txt.sour.is/conv/a36exfa.
@bender@twtxt.net It’s pretty cool though 🤣
yarnd
powering this pod twtxt.net 🧐
@sorenpeter@darch.dk you raw feed says otherwise. Also, https://txt.sour.is/conv/wj5bcwq.
yarnd
powering this pod twtxt.net 🧐
Wrote some serious Python for the first time in like 10 years 😱 I feel so dirty 🤣
yarnd
powering this pod twtxt.net 🧐
@prologic@twtxt.net it was not an edit but a double posting
yarnd
powering this pod twtxt.net 🧐
@prologic@twtxt.net yup. Funny enough, the first twtxt should have sufficed, as if there is no domain, there will be no feed (at that domain). The edit to add that the feed will not be available is redundant.
@prologic@twtxt.net stop fooling around, and smell the flowers (careful with the bees, they sting)! An unofficial sign done by children, I am sure. :-D
Contagem decrescente para o primeiro techbro a afirmar uma solução de IA que evitaria futuros apagões
@javivf@adn.org.es Go for it! You’re free to use it.
It’s been a community adventure to explore the whole DM/encryption thing. So the community can do with it whatever they want. 😎
@lyse@lyse.isobeef.org hey pascal bro! My first coding class was with an old Borland Turbo Pascal. I made my own little window manager for the assignments for class.
The teacher didn’t appreciate it much since I had to print out the code to turn it in. My Yatzee game was a stack of pages. 🤪
@lyse@lyse.isobeef.org Very nice! 👌 So lovely and green 😅 – What’s with the sign in
? 🧐Interesting edit observed by the new yarnd
powering this pod twtxt.net 🧐
@movq@www.uninformativ.de I’ve tried and there’s little interest so I’ve given up for now 😭
@bender@twtxt.net Wut?! 😂
Maravilhosa live de aniversário da Live de Python do @dunossauro@dunossauro
https://www.youtube.com/live/IE8coapVoSk
Sensacional…
-> um comentário que conecta com o final da live, as contas do Mastodon todas geram feeds RSS, é só acrescentar .rss no final da url :)
so… maybe I should try a new fresh approach. I gave up avoiding adding a new data structure and created a drawing_dict to iterate and draw. At this point it contains a reference to a drawing function and the attributes to use… it should give me enough flexibility. I’m using shapes as keys,
I have to think about the case of the complex body… the body should be the key in that case. But then, removing stuff will be harder.
https://github.com/villares/sketch-a-day/blob/main/2025/sketch_2025_04_27/sketch_2025_04_27.py
The OP strikes me as a boomer (they might not be!). LOL. I don’t think there is going back. If anything, it will get worse.
@lyse@lyse.isobeef.org yikes! I knew there will be collateral damage, but I wasn’t expecting it to affect The Tubes! 😱
#PyPodcats Hidden Figures of #Python #podcast @pypodcats@pypodcats
Episode 8, with Mojdeh Rastgoo:
https://pypodcats.live/episodes/ep-8/
«We interviewed Mojdeh Rastgoo, the newest member of PyPodcats!
Since discovering Python and the open-source community, Mojdeh has been actively involved in the Python ecosystem. She gave her first tutorial in 2018 at EuroSciPy and has since contributed in many ways. She is a member of the PSF Code of Conduct Working Group, a co-organizer of PyLadies Paris, and now a host of PyPodcats!
In this episode, Mojdeh shares more about herself and her passion for the community. We also take a look back at 2024, discuss our plans for 2025, and introduce a few new changes, including our Open Collective account, where you can support us.
Be sure to listen to the episode to hear about our plans and get to know your new host Mojdeh!»
@movq@www.uninformativ.de I started with Delphi in school, the book (that we never ever used even once and I also never looked at) taught Pascal. The UI part felt easy at first but prevented me from understanding fundamental stuff like procedures or functions or even begin
and end
blocks for if
s or loops. For example I always thought that I needed to have a button somewhere, even if hidden. That gave me a handler procedure where I could put code and somehow call it. Two or three years later, a new mate from the parallel class finally told me that this wasn’t necessary and how to do thing better.
You know all too well that back in the day there was not a whole lot of information out there. And the bits that did exist were well hidden. At least from me. Eventually discovering planet-quellcodes.de (I don’t remember if that was the original forum or if that got split off from some other board) via my best schoolmate was like finding the Amber Room. Yeah, reading the ITG book would have been a very good idea for sure. :-)
In hindsight, a console program without the UI overhead might have been better. At least for the very start. Much less things to worry about or get lost.
Hence, I’d recommend to start programming with a console program. As for the language, not sure. But Python is probably a good choice, it doesn’t require a lot of surrounding boilerplate like, say Java or Go. It also does exceptionally well in the principle of least surprise.
@sorenpeter@darch.dk I see, ta. The big spring cleaning continues. ;-)
Hi @lyse@lyse.isobeef.org, I canceled the domain, so neotxt or my feed there are not coming back.
I went on a small hike, just 12-13km this time. The weather was great, blue sky, sunny 18°C, but with the wind it felt colder. Leaves and other green stuff is exploding like crazy. It looks super beautiful right now.
I came across an unfortunately dead salamander on the forest road, some fenced in deer, heaps of sheep, some unmagnetic cows (some were aligned very roughly north-south, but mainly with the axis of the best view I believe), a maybeetle and finally an awesome sunset. Not too shabby! The sheep were mehing all the time, that was really lovely to hear. And the crickets were already active, too. Didn’t expect them to hear yet. I tried to record the concert, but the wind messed it all up. Oh well.
I should probably clarify: Which language/platform? Something graphical or web-based right from the beginning or do you start with a console program?
@bender@twtxt.net Must be the US tariffs, it’s working reasonably quick in Europe. :-D
@twtxtory@twtxtory.adn.org.es sorry, it isn’t. After you enter the password, it takes a very long time to render anything. I don’t have the patience to wait. Longest I waited is 3 minutes, and nothing. Super extremely slow.
@movq@www.uninformativ.de Your next experiment should be triangles. :-)
I want to simplify #pymunk + #py5 use for my students but I struggle with finding good strategies… Pymunk has two types of (linked) objects for each simulated object: body and shape. For complex objects (like concave shapes) you can use more than one convex shape linked to the same body. In these cases I usually want to have an extra shape to draw and hide the triangulation.
I don’t want to keep extra data structures to track the simulation objects to draw. I tried both extending and monkey patching either body or shape objects to be “drawable” so I can just iterate the native pymunk structures and ask stuff to draw themselves (would be nice, huh?), but there is always some snag. If I extend shape classes, I stumble on the complex objects with many shapes drawn with divisions. If I extend the Body class, the problem is static objects have shapes but share a virtual constant body, more of a flag, so I can’t add anything to it, so back to keeping track of a separate list of static shapes… Then performance & serialization issues, I want to be able to easily pickle simulations, but if I add Py5Shape objects to the extended/modified classes they become unpickable…
I have bigger fishes to fry right now (the paralyzing PhD) but this is something I would like to pair with someone more experienced to work on.
To the parents or teachers: How do you teach kids to program these days? 🤔
If you just do a square, the score is still surprisingly high … https://movq.de/v/68eb406e17/s.png 😅
@bender@twtxt.net Oh 🤣🤣🤣
@prologic@twtxt.net ah, yes, a feed that I have muted. 😂
Should ink to this
@javivf@adn.org.es the demo doesn’t work. When trying to login, it simply times out.
Hmm not sure how that link is 404’kng for you 🧐 It doesn’t here 🤦♂️
@prologic@twtxt.net oh, sorry, you are right. Beautiful 404. The most beautiful 404 I have ever seen. Tremendous! 🤪
@bender@twtxt.net What you talk’n about 🤣 It’s not broken, it’s perfectly functional 🤣
@prologic@twtxt.net first we need to fix broken links. 😅
@lyse@lyse.isobeef.org Seems legit 😅
I have a great idea for fixing the US economy. Get rid of all the nuclear weapons 🤣
@javivf@adn.org.es Wanna list it on twtxt.dev? 🧐
@javivf@adn.org.es Ahh! So this is your client implementation? 🧐
I just fixed a bug in tt’s reply to parent feature. Previously, when the message tree looked like the following
Message
├╴Reply 1
│ └╴Subreply
└╴Reply 2
and “Reply 2” was selected, pressing A
to reply to the parent should have picked “Message”. However, a reply to “Reply 2” was composed instead. The reason was a precausiously introduced safety guard to abort the parent search which stopped at “Subreply”, because its subject didn’t match “Reply 2”’s. It was originally intended to abort on a completely different message conversation root. Just in case. Turns out that this thoght was flawed.
Fixing bugs by only removing code is always cool. :-)
@movq@www.uninformativ.de Bwahahaahaaa, this is fucking brilliant, I love it! :-D What a wonderful thing to start my Sunday.
@prologic@twtxt.net This was like 20 minutes, but yeah 🤣
Today I added support for Let’s Encrypt to eris via DNS-01 challenge. Updated the gcore libdns package I wrote for Caddy, Maddy and now Eris. Add support for yarn’s cache to support # type = bot
and optionally # retention = N
so that feeds like @tiktok@feeds.twtxt.net work like they did before, and… Updated some internal metrics in yarnd
to be IMO “better”, with queue depth, queue time and last processing time for feeds.
Also you have too much time on your hands 🙌 Haha 😂