[47°09′50″S, 126°43′21″W] Reading: 1.61 Sv

[47°09′43″S, 126°43′42″W] Reading: 0.44000 PPM

[47°09′40″S, 126°43′10″W] Reading: 0.84000 PPM

[47°09′56″S, 126°43′42″W] Reading: 1.53 Sv

[47°09′00″S, 126°43′06″W] Reading: 0.42000 PPM

[47°09′32″S, 126°43′48″W] Reading: 0.91000 PPM

[47°09′25″S, 126°43′37″W] Reading: 1.51000 PPM

[47°09′08″S, 126°43′00″W] Reading: 0.51 Sv

@movq@www.uninformativ.de i feel like when i read go code i’m reading some algebra shit where every part is 1-5 letters long and then there’s weird symbols like := and it’s just infinitely harder for me to parse and infer meaning from lol. it’s such a me problem

@prologic@twtxt.net You can read more about the “cryptic” live coding language Punctual in my newsletter

[47°09′27″S, 126°43′08″W] Reading: 1.15000 PPM

[47°09′29″S, 126°43′22″W] Reading: 1.45 Sv

[47°09′27″S, 126°43′18″W] Raw reading: 0x682DB231, offset +/-4

[47°09′01″S, 126°43′44″W] Reading: 1.09000 PPM

Wanna read something very scary?

Your future doctor is using ChatGPT to pass medical school, so you better start riding a bike and eating healthy now.

😨😨😨

https://infosec.exchange/@duanegran/114531604486731084

[47°09′52″S, 126°43′50″W] Raw reading: 0x682ABAD1, offset +/-2

[47°09′49″S, 126°43′54″W] Raw reading: 0x682A2E32, offset +/-1

[47°09′13″S, 126°43′49″W] Reading: 1.48 Sv

[47°09′45″S, 126°43′58″W] Reading: 0.22 Sv

@lyse@lyse.isobeef.org I can’t read. 🤦 Yeah, that’s gonna be a problem. I was not yet able to trigger it, though. Maybe they are (like Google) rolling out these changes gradually …

[47°09′54″S, 126°43′30″W] Raw reading: 0x6824BE02, offset +/-2

@bender@twtxt.net Basically the way I’m reading this is 1 RPM. This is a rather aggressive rate limit actually. This basically makes Github inaccessible and useless for basically anything unless you’re logged in. You can basically kiss “pursuing” casually, anonymously goodbye.

Imagine if I imposed that kind of rate limit on twtxt.net?! 🤣

[47°09′37″S, 126°43′08″W] Raw reading: 0x682477B1, offset +/-3

[47°09′09″S, 126°43′53″W] Reading: 1.45 Sv

@kat@yarn.girlonthemoon.xyz You don’t need to change the directory first in line 11, you can just create the directory, that’s sufficient since you’re having an absolute path.

The echo in line 13 is useless, you can simplify this to: newdir="$WD/$now" If you reversed this line with the previous one, you could make use of the variable in the directory creation: mkdir "$newdir".

In line 16, pull the directory change out of the loop upfront. The loop body doesn’t modify the working directory, so no need to reset it with each cycle. In fact, you could even spare the cd altogether when you simply tell find where to look: find "$basedir" -type f….

I didn’t try it, but if I read the manpage correctly, you should be able to simplify line 19 as well:

-C Change to DIR before performing any operations. This option is order-sensitive, i.e. it affects all options that follow.

Hence, remove the cd and put the -C "$WD" as the first argument to tar. Again, I didn’t try it. Proceed with caution.

Finally, you don’t need to specify the full path to rm in line 21. I bet, /bin is in your PATH. When you removed the previous cd from my last suggestion, the relative path that follows won’t work anymore. So, just use the absolute path that you already have in a variable: rm -rf "$newdir"

I hope you find this tiny review a wee bit useful. :-)

[47°09′15″S, 126°43′57″W] Reading: 0.70000 PPM

[47°09′32″S, 126°43′04″W] Reading: 0.69000 PPM

[47°09′55″S, 126°43′06″W] Reading: 1.16000 PPM

[47°09′23″S, 126°43′05″W] Reading: 1.10000 PPM

@prologic@twtxt.net I read a little about her. Looks to be a good fit for the seat she is holding. I hope she gets to keep it.

[47°09′40″S, 126°43′17″W] Raw reading: 0x681AE8D1, offset +/-2

[47°09′14″S, 126°43′17″W] Reading: 1.12 Sv

[47°09′39″S, 126°43′28″W] Raw reading: 0x68190AB1, offset +/-3

@andros@twtxt.andros.dev Programming is art. You become good at art by practising your art. You learn artistic patterns by being inspired by and reading others art works. The most importance however is that you practise your art.

Nobody want to be a shitty programmer. The question is: Do you do anything not to not be one?
Reading blogs or social media and watching YouTube videos is fun. After them, your code may be a little better, of course. But you need a lot. You need to study! Read good books and study the code of other programmers, for example. Maybe work with a new language, architectures and paradigms. You need break the routine.

If you know Object-oriented programming, you learn functional programming.
If you know Model-View-Controller, you learn Model-View-ViewModel.
If you don’t know anything about architectures, you learn Clean Architecture, Hexagonal Architecture, etc.
If you know Python, you learn Ruby or Go.
If you know Clojure or Lisp… you don’t need to learn anything else. You are already a good programmer. Just kidding. You can learn Elixir or Scala.

Be a good programmer my friend.

[47°09′45″S, 126°43′42″W] Raw reading: 0x68171071, offset +/-3

happy free comic book day! my store was out of freebies but i got some of my pulls and also a trade of one of my favorite reads last year!

Image

@bender@twtxt.net Mainly the bsd.cafe ones. I like how the minimalist single column profiles look. Image embeds are full width and reading through threads feels nice (as in it doesn’t feel like pealing layers upon layers of a fresh onion).

Confession:

I’ve never found microblogging like twtxt or the Fediverse or any other “modern” social media to be truly fulfilling/satisfying.

The reason is that it is focused so much on people. You follow this or that person, everybody spends time making a nice profile page, the posts are all very “ego-centric”. Seriously, it feels like everybody is on an ego-trip all the time (this is much worse on the Fediverse, not so much here on twtxt).

I miss the days of topic-based forums/groups. A Linux forum here, a forum about programming there, another one about a certain game. Stuff like that. That was really great – and it didn’t even suffer from the need to federate.

Sadly, most of these forums are dead now. Especially the nerds spend a lot of time on the Fediverse now and have abandoned forums almost completely.

On Mastodon, you can follow hashtags, which somewhat emulates a topic-based experience. But it’s not that great and the protocol isn’t meant to be used that way (just read the snac2 docs on this issue). And the concept of “likes” has eliminated lots of the actual user interaction. ☹️

that said, and reading to @sorenpeter@darch.dk and @andros@twtxt.andros.dev I have new thoughts. I assume that this won’t change anyone’s opinions or priorities, so it makes no harm sharing them.

It’s always tempting to use something that already exists (like X, Masto, Bsky, etc.) rather that building anything through effort and disagreement until reaching to something useful and valuable together. A ‘social service’ is only useful if people is using it.

I’ll add that I haven’t lost interest on the ‘hacky’ part of twtxt about developing tools, protocols, and extensions as a community. It’s the appealing part! It’s a nice hobby to have, shared with random people across the world.
But this is not the right way for me, and makes me feel that I’m unwelcome to propose something different (after watching replies to my previous twt). Feels like “If you don’t agree, you are free to leave, we’ll miss you.” Naah, not cool. I’ve lived that many times before, and nowadays I don’t have enough spare time and energy for a hobby like that.

Let’s see what happens next with the micro-community!

@prologic@twtxt.net I’m very sorry but my feelings are similar to @eapl.me@eapl.me . For a long time I thought that Yarn was part of the Twtxt ecosystem, and not that Twtxt is an extension of Yarn. I don’t feel comfortable with what has happened. I didn’t expect this change of direction.
The nice part of Twtxt is that it is read by humans, with a simpler format. It’s the heart of the social network.
I need to think for a little time, but I’m thinking of stopping my involvement in the community.

@thecanine@twtxt.net do you read ed zitron’s newsletter? he writes in depth about how AI is a crock of shit it makes me feel normal for once

[47°09′51″S, 126°43′47″W] Reading: 0.02 Sv

[47°09′11″S, 126°43′58″W] Raw reading: 0x680FD031, offset +/-5

Gaza blockade depletes World Food Programme stocks + 1 more story
North Korea confirms sending troops to Russia as a defense pact; Gaza blockade leaves World Food Programme out of supplies, risking starvation for millions. ⌘ Read more

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

@prologic@twtxt.net and the aim, and end result, is that by reading and learning from it you will prepare yourself to nearly completely avoid accidents. Am I right? 🙂

These ideas are dr the two books:

• Drift into Failure: From Hunting Broken Components to Understanding Complex Systems by Sidney Dekker (2011)
  
• Engineering a Safer World by Nancy Leveson (2011)
  

The former I haven’t read. The later I haven’t finished reading 😅

@lyse@lyse.isobeef.org haha, not satire. It is also in Mark Twain’s “Huckleberry Finn” as well:

“If fifteen cows is browsing on a hillside, how many of them eats with their heads pointed the same direction?”

“The whole fifteen, mum.”

China plans to build a nuclear power plant on the Moon + 2 more stories
China urges Korea to restrict rare earth exports to U.S.; global coral bleaching spreads due to record ocean heat; China plans a nuclear power plant on the Moon. ⌘ Read more

[47°09′14″S, 126°43′37″W] Raw reading: 0x6809E172, offset +/-2

@prologic@twtxt.net lovesick by luana vecchio! it’s really brutal and explicit, just super intense all around but super worth the read if you can stomach it. great comic

[47°09′09″S, 126°43′33″W] Raw reading: 0x680873D1, offset +/-3

“Here’s what we do know: After their meeting ended and Vice President Vance left the room, the pope was still alive. We can deduce that he was alive, because he was heard asking an assistant, “Ho appena incontrato il volto del diavolo?” which roughly translates to, “Have I just encountered the face of the devil?” It’s a very common question that has been asked in many languages after encounters with JD Vance.”

I couldn’t help but chuckling a bit while reading.

by commenting out DMs are you giving up on simplicity? See the Metadata extension holding the data inside comments, as the client doesn’t need to show it inside the timeline.

I don’t think that commenting out DMs as we are doing for metadata is giving up on simplicity (it’s a feature already), and it helps to hide unwanted DMs to clients that will take months to add it’s support to something named… an extension.

For some other extensions in https://twtxt.dev/extensions.html (for example the reply-to hash #abcdfeg or the mention @ < example http://example.org/twtxt.txt >) is not a big deal. The twt is still understandable in plain text.
For DM, it’s only interesting for you if you are the recipient, otherwise you see an scrambled message like 1234567890abcdef=. Even if you see it, you’ll need some decryption to read it. I’ve said before that DMs shouldn’t be in the same section that the timeline as it’s confusing.

So my point stands, and as I’ve said before, we are discussing it as a community, so let’s see what other maintainers add to the convo.

Whistleblower: DOGE Siphoned NLRB Case Data
Comments ⌘ Read more

@andros@twtxt.andros.dev Haha 🤣 We’ve explored this idea in the past and we decided that it’s actually a good idea to have an “append-only” feed for various reasons. We’ve also explored the idea of using Range requests, but opted instead to just archive/rotate our feeds periodically 😅 There really isn’t much point in having a feed in reverse chronological order, except (maybe?) so a human read view the new twts at the top of the file?! 🤣

@bender@twtxt.net I use it. It’s not the feature I use the most in the fediverse, but I communicate this way with several friends. For example, it’s the main way I talk to the original creator of the twtxt-el repository, the way people greet me for the first time or the way they notify me of some bugs in the software I maintain. I can even tell you that it’s the main way I talk to some maintainers of the Emacs community. If there are any of you reading my words, speak up!
Why not have the same? There are things I want to say to @prologic@twtxt.net in private, why should I have to send him an email or private IRC? Or an public twt.
Of course, here’s a topic we’ve already talked about: what is twtxt for you? For me it will always be a social network, in microblogging format, but an asynchronous way of communicating. And having a tool to control visibility is basic 😄
I look forward to hearing from you @eapl.me@eapl.me !

After reading you, @eapl.me@eapl.me, I’ll tell you my point of view.
In my opinion, a feed does not have to be equivalent to a timeline. A timeline is a representation of the feed adapted to a user. You may not be interested in seeing other people’s threads or DMs. But perhaps they are interested in seeing mentions or DMs directed at them. It is important not to fall into the trap. With that clarification…
I insist, this is my point of view, it is not an absolute truth: I don’t think extensions should be respectful of customers who are no longer maintained.
We cannot have a system that is simple, backwards compatible and extensible all at the same time. We have to give up some of the 3 points. I would not like to give up simplicity because it will then make it harder to maintain the customers who do stay. Therefore, I think it is better to give up backwards compatibility and play with new formulas in the extensions. I don’t think it’s a good idea to make a hash keep so much load: a hashtag, a thread and also a DM.

@prologic@twtxt.net Since you have to check and double check everything it spits out (without providing sources), I don’t find any of this helpful. It’s like someone’s in the room with you and that person is saying random stuff that might or might not be correct. At best, it might spark some new idea in your head and then you follow that idea the traditional way.

Information published on the internet (or anywhere, for that matter) was never guaranteed to be correct. But at least you had a “frame of reference”: “Ah, I read this information about Linux on a blog that usually posts about Windows, so this one single Linux post might not necessarily be correct.” That is completely lost with LLMs. It’s literally all mushed together. 🤷

@prologic@twtxt.net This shi_ is as fun as it is frustrating! 😆 the bot is poking at me from a different ASN now, Alibaba’s.

1. Short term solution: I’ve geo-locked my Timeline instance since I’m the only one using it (and I only do so for reading twts when I’m away from terminal).
   
2. Long term: I took a look at your Caddy WAF but couldn’t figure things out on my own; until then, I’ll be poking at Caddy-Defender, maybe throw in a Crowdsec for lols… #FUN

[47°09′11″S, 126°43′53″W] Reading: 0.70000 PPM

7k words of docs on deploying a livejournal folk. you absolutely want to read 7 thousand words of me forcing dreamwidth into production shape in docker https://stash.4-walls.net/selfhostdw/

Top OpenAI Catastrophic Risk Official Steps Down Abruptly
Comments ⌘ Read more

[47°09′48″S, 126°43′23″W] Raw reading: 0x68008AD1, offset +/-2

@eapl.me@eapl.me This is one of my concerns too. The moment you post publicly ciphertext, you open yourself up for future attacks on the ciphertext, which you really want to avoid if you can. If you have a read of the Salty.im Spec you’ll note we went to great lengths to protect the user’s privacy as well as their identity and make it incredibly hard to guess at inboxes. It’s still a WIP, but I’d love to see it progressed even further – I truly feel strongly about a purely decentralised messaging ecosystem 👌

You cannot have our user’s data
Comments ⌘ Read more

Fascinating read on the emerging Model Context Protocol — a new standard for integrating LLMs with agents and tools.

Everything Wrong with MCP
Comments ⌘ Read more

BPS is a GPS alternative that nobody’s heard of
Comments ⌘ Read more

@prologic@twtxt.net you wrote:

“Based on a recent study of the brains of mice I estimated the human brain to have 200B cells/neurons and 50,000T connections.”

What’s the relation between the brains of mice, and the human brain? I am kind of lost trying to make the connection.

I also read that it isn’t 5 watts, but more like 10-20 watts. Still a super tiny consumption, comparing to what it takes to run anything AI.

[47°09′49″S, 126°43′18″W] Reading: 0.75000 PPM

[47°09′42″S, 126°43′28″W] Reading: 0.64000 PPM

[47°09′52″S, 126°43′27″W] Raw reading: 0x67F966B2, offset +/-1

@movq@www.uninformativ.de Holy crap, that’s really crazy!

Hahaha, you got me. When I read your first sentence I thought you were going to tell about your Wayland experience in comparison to X11. :-D

[47°09′44″S, 126°43′21″W] Reading: 0.55 Sv

oh out of boredom yesterday i made my blog available via markdown files too so you can use charmbracelet/glow to read them in your terminal :)

basically i just set up a file directory on a path of my blog, organized the MD files by year, and so in theory you can navigate to that path and choose a folder, then copy a link to a markdown post and run this:

glow -p https://bubblegum.girlonthemoon.xyz/md/2025/2025-03-31%20premature%20reflections%20on%20sudden%20responsibility.md

and then as long as you have glow installed, you can read my posts from the terminal :D it’s so cool

[47°09′52″S, 126°43′01″W] Reading: 1.36000 PPM

[47°09′07″S, 126°43′46″W] Reading: 1.67 Sv

[47°09′01″S, 126°43′54″W] Reading: 1.96 Sv

So I re-write this shell alias that I used all the time alias dkv="docker rm" to be a much safer shell function:

dkv() {
  if [[ "$1" == "rm" && -n "$2" ]]; then
    read -r -p "Are you sure you want to delete volume '$2'? [Y/n] " confirm
    confirm=${confirm:-Y}
    if [[ "$confirm" =~ ^[Yy]$ ]]; then
      # Disable history
      set +o history

      # Delete the volume
      docker volume rm "$2"

      # Re-enable history
      set -o history
    else
      echo "Aborted."
    fi
  else
    docker volume "$@"
  fi
}

[47°09′06″S, 126°43′31″W] Raw reading: 0x67F2A501, offset +/-4

This is such an interesting reading

Lessons from open source in the Mexican government
https://lwn.net/Articles/1013776/

[47°09′49″S, 126°43′45″W] Raw reading: 0x67F10D31, offset +/-5

[47°09′50″S, 126°43′45″W] Raw reading: 0x67F02C32, offset +/-3

[47°09′18″S, 126°43′31″W] Raw reading: 0x67F00201, offset +/-2

@arne@uplegger.eu I’m very glad I only rarely have to deal with .docx & Co. And when I have to, 99% is in read mode only. Even though, I don’t think that Markdown is the best choice, I use it on a daily basis. Some things, like links, in reStructuredText are better in my opinion.

Jira just resists to switch to Markdown and forces us to use its silly markup language.

For real typesetting, LaTeX is the way to go. But I very, very rarely do that.

@thecanine@twtxt.net My apologies, mate! :-( As @david@collantes.us pointed out, this was definitely not my intent at all.

For the easter egg hunt, I first looked for a hidden image map link on the pixel dog in the right lower corner itself. Maybe one giant pixel just links to somewhere else, I figured. But I couldn’t find any and then quickly moved on. Hence, I naturally viewed the HTML source. Because where else would be a good hiding place for easter eggs, right?

Next, I noticed the <font> tags. I thought I had read quite some time ago that they are not an HTML5 thing, but wasn’t entirely sure about it. So, I asked the W3C HTML validator. Sure enough. I thought I let you know about the violations. If somebody had found a mistake on my site, I’d love to hear about it, so I could fix it. I’m sorry that my chosen form of report didn’t resonate with you all that well. I reckoned you’ll also find it a bit funny, but I was clearly very wrong on that.

I actually followed the dog cow link to the video, so I ended up on the easter egg. However, I didn’t recognize it as such. ¯_(ツ)_/¯ Oh well.

Regarding my message about the browser quirks: I read your answer that you were arguing against the HTML validator findings. Of course, everybody can do with their sites whatever they likes.

[47°09′55″S, 126°43′36″W] Raw reading: 0x67EE31F1, offset +/-4

@prologic@twtxt.net @eapl.me@eapl.me I want to highlight another social problem: People don’t read. Paper industry is a bad moment because people don’t pay for books; it does not matter if it is a physical or digital platform. I have this information because I have a good friend who left the industry after publishing a magazine, books and working in an editorial. DRM is a try to give some more money.

[47°09′25″S, 126°43′21″W] Reading: 0.09 Sv

Amazing! It is a good tool for reading feeds. What you used to calculate the hash?

Hello, i want to present my new revolution twtxt v3 format - twjson
That’s why you should use it:

1. It’s easy to to parse
   
2. It’s easy to read (in formatted mode :D)
   
3. It used actually \n for newlines, you don’t need unprintable symbols
   
4. Forget about hash collisions because using full hash
   Here is my twjson feed: https://doesnm.p.psf.lt/twjson.json
   And twtxt2json converter: https://doesnm.p.psf.lt/twjson.js

[47°09′30″S, 126°43′09″W] Reading: 1.75 Sv

[47°09′34″S, 126°43′08″W] Reading: 0.74000 PPM

[47°09′43″S, 126°43′39″W] Raw reading: 0x67E8EBF1, offset +/-1

DOGE To Rewrite SSA Codebase In ‘Months’
Longtime Slashdot reader frank_adrian314159 writes: According to an article in Wired, Elon Musk has appointed a team of technologists from DOGE to “rewrite the code that runs the SSA in months.” This codebase has over 60 million lines of COBOL and handles record keeping for all American workers and payments for all Social Security recipients. Given that the code has to track the byzantine … ⌘ Read more

@xuu@txt.sour.is If the unread counter becomes negative, wouldn’t that mean I have that many more read messages? :-D

@bender@twtxt.net You’re spot on, it’s important to not introduce classical bugs!

thanks andros!

instead of adding the new twt at the end of the feed, do it at the beginning
The PHP client did that originally, although I didn’t see a real benefit if you use… a client.
It could help if you read the .txt file through a browser or something. Also, not many clients are prepared to cut the request, and you can’t rely on the file being organized that way, so finally we dropped that feature.

[47°09′49″S, 126°43′49″W] Raw reading: 0x67E397E1, offset +/-5