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 🤦♂️_
As @bender 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
As @bender 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
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.
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.
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.
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.
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 …
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 …
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. ]:->
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. ]:->
* jenny
* buckket's original (patched, or not)
* tt/tt2
* Timeline
* Twtxtory
* Yarnd
yarnd very soon™ for this change, with a if the date is >= 2025-07-01 then compute_new_hashes else compute_old_hashes
tt2 from @lyse and Twtxtory from @javivf?
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~
Se confirma que en Red Eléctrica Española también odian los lunes.
#apagon ⌘ Read more****
Lógicamente tenía que pasar un lunes.
#apagon ⌘ Read more****
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
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 🤔
#apagão
Plano B à internet: rádio a pilhas
#apagão
Plano B à internet: rádio a pilhas
A bunch of oranges still in the tree
A bunch of oranges still in the tree
It's been a community adventure to explore the whole DM/encryption thing. So the community can do with it whatever they want. 😎
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. 🤪
16? 🧐
yarnd powering this pod twtxt.net 🧐
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 :)
I have to think about the case of the complex body...
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
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!»
begin and end blocks for ifs 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.
begin and end blocks for ifs 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.
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.
Sheephttps://lyse.isobeef.org/waldspaziergang-2025-04-27/
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.
Sheephttps://lyse.isobeef.org/waldspaziergang-2025-04-27/