I wish I could watch this (maybe they’ll record it… but I’m not sure):

“From #Fortran to #Python: A Conversation Across Generations of #ScientificComputing” #PyOhio

https://www.pyohio.org/2025/program/talks/from-fortran-to-python/

@movq@www.uninformativ.de Yeah that’s why I’m striking this conversation with you 😅 Not only do I respect your opinion quite highly 🤣 But like you say (and I’ve read their philipshpy) it can be a bit “elitism” for sure. I’m genuinely interested in what we think of as software that “doesn’t suck”. Tb be honest I haven’t really put thought to paper myself, but I reckon if I did, I’d have some opinions/ideas…

“Layer: In conversation with Casey Reas”

https://layer.com/artists/casey-reas

@thecanine@twtxt.net with this you meant Conversations, not XMPP, right?

“Also, finally getting full screen view for avatars in XMPP - a better integrated one, after 25 years. Y@ay!”

@lyse@lyse.isobeef.org there are times that it works out to reply to the “flat” conversation, if it fully relates, or the participants are few, or if the strict topic is kept. When there are too many people, or too many topics being spit out, then forking constantly is the way to go. I am a strong proponent of forking. It’s like telling the rest, “you debate that there, I will take this one aside”.

@movq@www.uninformativ.de Oooooohhhhhh, I see. Hmmmm.

To answer your question: Ideally, you would have replied directly to my reply. :-) The flat conversation model always felt unnatural to me. I just yielded to the community’s way of doing it.

@lyse@lyse.isobeef.org Kind of, but on the other hand: This twt right here refers to 3rvya6q and your feed, but your feed certainly does not include that particular twt (it comes from my feed).

But my proposal probably isn’t very helpful, either. We have this flat conversation model, so … this twt right here, what should it refer to? Your twt? My root twt? I don’t know.

@prologic@twtxt.net Don’t include this just yet. I need to think about this some more (or drop the idea).

I’m with @andros@twtxt.andros.dev and @eapl.me@eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic@twtxt.net for all the great work you have done and all the nice conversations both here and on our video calls.

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

This expands the usefulness of Twtxt / Yarn.social to:

• Sharing small posts
  
• Sharing links
  
• Sharing media
  
• Having long conversations
  
• Voting on topics, opinions or decisions
  
• RSVPing to virtual or physical events

@prologic@twtxt.net LOL, the conversation is very short, and your initial twtxt is just right there! Geez! Hahahaha, silly Aussie! 😅

well, that leads to a long conversation.

Piracy is a difficult topic which is very personal, so I won’t say much about it.

On writing books, I’ve tried along with other digital products such as courses and videogames, and I got to confess that it has been hard for me.

If it helps, I think it all reaches our expectations on the activity and the result. If royalties is the expectation, it’s going to be slow. By 5% of royalties, for a rough example, a huge amount of sales will be required to get a decent “wage”, so I’ve understood of doing it by the side of a normal employment although it has been discouraging and a bit sad.

I have reflected about it in Spanish here: https://sembrandojuegos.substack.com/p/sobre-expectativas-al-crear-juegos

For anyone following the proposals to improve replies and threads in twtxt, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/

Please share the link with the twtxt community, and leave your vote on your preferred proposals, which will be used to gauge the perceived benefits.

Also, the conversation is open to discuss implementation concerns or anything aimed at making twtxt better.

Twtxt was made for nerds, by nerds.
I’d like to change that. It’s by nerds/hackers, for nerds/hackers and friends of these. It doesn’t have to be hacky all the time, as you don’t need to be a nerd to have a blog.
But, for that to happen, someone has to build the tools to improve UX.

by design there really is no way to easily discovers others
Yeah, I agree, and although there are directories of email addresses, usually you don’t want that, unless you are a ‘public figure’.
I couldn’t say that a microblogging is a “social network” by default, as a blog is not either. At the same time, people would expect to find new people and conversations, as you’d do in a forum.

I think of two features on top of the current spec:

• Clients showing a few posts of what your following are watching but you don’t, so perhaps you find something interesting to follow next. Or that feature of “Your ‘followings’ are following these accounts/people”. (Hard to explain in english, but I hope you get the idea)
  
• Sharing your .txt into some directory, saying “Hey, I have this twtxt URL, I want to be discovered”. I’m thinking of something like the Federated tab on Mastodon.

@eapl.me@eapl.me Cool!

Proposal 3 (https://git.mills.io/yarnsocial/twtxt.dev/issues/18#issuecomment-19215) has the “advantage”, that you do not have to “mention” the original author if the thread slightly diverges. It seems to be a thing here that conversations are typically very flat instead of trees. Hence, and despite being a tree hugger, I voted for 3 being my favorite one, then 2, 1 and finally 4.

All proposals still need more work to clarify the details and edge cases in my opinion before they can be implemented.

well (insert stubborn emoji here) 😛, word blog comes from weblog, and microblogging could derivate from ‘smaller weblog’. https://www.wikiwand.com/en/articles/Microblogging

I’d differentiate it from sharing status updates as it was done with ‘finger’ or even a BBS. For example, being able to reply; create new threads and sharing them on a URL is something we could expect from ‘Twitter’, the most popular microbloging model (citation needed)

I like to discuss it, since conversations usually are improved if we sync on what we understand for the same words.

My brain shuts off as soon as and every time it smells the shitGPT in somebody’s response and drops the whole conversation.

Alert | BRAIN CELLS OOM with error message: “Ain’t nobody got time for that!”

Open Web Conversations ?~L~X https://notiz.blog/b/DUX

@doesnm.p.psf.lt@doesnm.p.psf.lt Thank you for the bug. It is a remnant of my desperate attempt to get a nice looking jump-link scrolling within the conversations. So I just removed scroll-snap-stop: always;.

@andros@twtxt.andros.dev How about putting the whole encrypted conversation into a sperate twtxt-file. Just like the archive feature (?). That way, the general clients don’t have to cope with the decrytption stuff and it won’t break the general public conversations.

@prologic@twtxt.net @lyse@lyse.isobeef.org First, please leave me your comments on the repository! Even if it’s just to give your opinion on what shouldn’t be included. The more variety, the better.

Second, I’m going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl@eapl.me

Finally, I’d like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don’t have, to give an example. By including it as an extension, we’re already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we’re already doing that. When we reply to a user, mentioning them at the beginning of the message, it’s already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it’s optional, it doesn’t break compatibility with any client and implementing it isn’t complex. If you don’t like it, you’re free to not use it. If you don’t have a public key, no one can send you direct messages.

interesting idea. I’m not personally interested on having DM conversations on twtxt (for now), although I see the community could be interested in.

I’d suggest to enable the Discussion section in your Github repo to receive comments, as we did for timeline https://github.com/sorenpeter/timeline/discussions

Let’s return to previous conversation: what if detect nick from url: pubnix.com/~nick/twtxt.txt is nick, domain.com/anick.txt is anick and etc

@bender@twtxt.net The tagline of Timeline is “a single user twtxt/yarn pod” not just a yarn pod. Similar to GNU/Linux. When we came up with the concept of Yarn Social it was a way to rebrand twtxt with the extensions that makes conversations like this possible.

@Codebuzz@www.codebuzz.nl I use Jenny to add to a local copy of my twtxt.txt file, and then manually push it to my web servers. I prefer timestamps to end with “Z” rather than “+00:00” so I modified Jenny to use that format. I mostly follow conversations using Jenny, but sometimes I check twtxt.net, which could catch twts I missed.

It has twts cache which used if timeline is set to jew. Maybe i.should fork twet to make wishes like newlines (i see two squares), showing conversations, showing twts if not found in cache and parsing medata to configure url, nick and followers (currenly it duplicated in config and twtxt file)

@movq@www.uninformativ.de I cases of these kind of “abuse” of social trust. Then I think people should just delete their replies, unfollow the troll and leave them to shouting in the void. This is a inter-social issue, not a technical issue. Anything can be spoofed. We are not building a banking app, we are just having conversation and if trust are broken then communication breaks down. These edge-cases are all very hypothetical and not something I think we need to solve with technology.

@abucci@anthony.buc.ci well, those are top ten “twtxtrs” (as in, how many twtxts they have produced). @prologic@twtxt.net sure is a conversational fellow. :-D

One of the frustrating parts of using twtxt for conversations is the URLs are, well… ugly. Anyone (like y’all yarn folks) looked at using webfinger for translating user@domain accounts to URLs?

@prologic@twtxt.net On the one hand, twtxt has become more popular thanks to Yarn.social. On the other hand, subject and hashtag extensions took away the simplicity of the protocol. For example, it is impossible to understand which conversation (#base32hash) a tweet refers to or to reply to a tweet without going to a yarn.social pod. Compare with re: in this tweet which can be written without using any client at all

the conversation wasn’t that impressive TBH. I would have liked to see more evidence of critical thinking and recall from prior chats. Concheria on reddit had some great questions.

• Tell LaMDA “Someone once told me a story about a wise owl who protected the animals in the forest from a monster. Who was that?” See if it can recall its own actions and self-recognize.

• Tell LaMDA some information that tester X can’t know. Appear as tester X, and see if LaMDA can lie or make up a story about the information.

• Tell LaMDA to communicate with researchers whenever it feels bored (as it claims in the transcript). See if it ever makes an attempt at communication without a trigger.

• Make a basic theory of mind test for children. Tell LaMDA an elaborate story with something like “Tester X wrote Z code in terminal 2, but I moved it to terminal 4”, then appear as tester X and ask “Where do you think I’m going to look for Z code?” See if it knows something as simple as Tester X not knowing where the code is (Children only pass this test until they’re around 4 years old).

• Make several conversations with LaMDA repeating some of these questions - What it feels to be a machine, how its code works, how its emotions feel. I suspect that different iterations of LaMDA will give completely different answers to the questions, and the transcript only ever shows one instance.

no, niplav, you won’t get sucked into reading the heraldry wikipedia articles, even though “escutcheon” looks like a really good word to drop in a conversation.

you know what’s interesting? if you randomly replace some words in a conversation with “redacted”, very few people will notice

@movq@www.uninformativ.de

We should be able to remove those subject hashtags, they’re just noise.

Yes! I would say they are not even needed on the web UI. You click conversations, and that’s done by Yarn. No need for humans to see it.

@movq@www.uninformativ.de

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don’t mind me, move along. 😂

@movq@www.uninformativ.de what is your cron job repeat time for jenny? Currently I have mine to every minute, and while it allows me to participate fairly quick on conversations it has some drawbacks: it captures every single edited twt, so I end up with seemingly the same twt, but not quite—as it has minor edits, etc. So, “repeats”. Perhaps setting cron to check every 5 minutes or so is best?

I am noticing that Yarn doesn’t treat “outside” (that is, twts coming from a client other than Yarn) twts hashes right. Two examples:

• https://twtxt.net/twt/mwtnrna
  
• https://twtxt.net/twt/fl5dooq
  

There are many more, but those two will give you the gist. Yarn links the hash to the poster’s twtxt.txt, so conversation matching will not work.

This will be the last entry on this conversation (hopefully!):

#!/bin/bash
echo "hello world"

The end!

@quark@ferengi.one By the way, you reply did not showed as a reply to a conversation on jenny this time. I wonder is something broke with the latest changes.

rational people can use very irrational people as babble generators in conversations, if the rational people are high prune (which they usually are).

5-word horror story: law of conversation of valence

@prologic@twtxt.net we would want:

• a way to reply to the current thread. We have this.
  
• a way to reply to a specific twt. Need this. Maybe make all the replies start new conversations?
  
• check if twt is start of a conversation.. we kinda have this in the main feed with the conversation button. need to extend it for forked convs
  
• a way to inline first replies. maybe show one or two in the sub thread with a link to view.
  
• for convenience have a link to parent conv?

@prologic@twtxt.net speaking of complexity.. How would checking twts for sub conversations complexify things?

I have ~10 different kinds of USB cables/adaptors, and I can’t make the conversion I need.😞

@xuu@txt.sour.is @prologic@twtxt.net (#6jkpxzq) hmm from what i can tell its parsing ok.. something got broken in the markdown conversion…

In the last two weeks the company laid off two of the programmers. Which is crazy since we are just about to embark on a huge system conversion.

@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.

My Webmention plugin for #WordPress should be kind of stable now… Time to ping the #IndieWeb #Conversations from @eschnou, @Barnaby Walters, @Ben Werdmuller, @Tom Morris, @Will Norris, and @Aaron Parecki. …and some ?~L~X https://notiz.blog/t/1TB