In-reply-to » (#l5awc2q) @kat That's what I was going for at first, I already have my compose file to go up -d, but then I took a look at a couple of #Snac instances at the last second and they looked pretty dope! Now I'm stuck in my own head šŸ˜…

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

⤋ Read More

@bender@twtxt.net Yes, you right. But is premium for more than that.
I use a feature I love a lot: customising different searches with different themes or links.
It’s easy to understand with an example. I have a search with the name ā€œDjangoā€. I set sources: Django documentation, stack overflow, topic ā€œprogrammingā€ and so on. It’s very quick to find Django solutions.
I also have another way to find my stuff: search my blog and repositories.
I had problems paying for the first mouths, now it’s a working tool for me.

⤋ Read More

We went on a 14Ā kilometers long hike in the heat, only a few spots were in the shade, most of our trip was in the open fields with the sun beating down on us. We reapplied the sun blocker after about two hours or so. All in all it took us about three and a half hours before we reached our destination Besigheim.

Last time I was there it was rainy, now we had the exact opposite. After some yummy Chinese lunch we visited the old town. There’s some gorgeous timer framing to see. When kept in decent shape, it just looks so dang cool.

Since it was too hot, we rode back by train. Despite the heat and some sections near the roaring Autobahn, this was a nice hike. Would do it again. Only in colder weather, though. I certainly don’t wanna trade my comperatively larger (still nothing to other more rural areas), covering forests with the wide open fields and vineyards in summer. That’s for sure.

Image

https://lyse.isobeef.org/wanderung-von-asperg-nach-besigheim-2025-05-01/

⤋ Read More
In-reply-to » I've just released version 1.0 of twtxt.el (the Emacs client), the stable and final version with the current extensions. I'll let the community maintain it, if there are interested in using it. I will also be open to fix small bugs. I don't know if this twt is a goodbye or a see you later. Maybe I will never come back, or maybe I will post a new twt this afternoon. But it's always important to be grateful. Thanks to @prologic @movq @eapl.me @bender @aelaraji @arne @david @lyse @doesnm @xuu @sorenpeter for everything you have taught me. I've learned a lot about #twtxt, HTTP and working in community. It has been a fantastic adventure! What will become of me? I have created a twtxt fork called Texudus (https://texudus.readthedocs.io/). I want to continue learning on my own without the legacy limitations or technologies that implement twtxt. It's not a replacement for any technology, it's just my own little lab. I have also made a fork of my own client and will be focusing on it for a while. I don't expect anyone to use it, but feedback is always welcome. Best regards to everyone. #twtxt #emacs #twtxt-el #texudus

@movq@www.uninformativ.de If you want, we can try it out between us. I’m just working on it (It was the easiest thing to do).

⤋ Read More

So, the ā€œAIā€ bots have reached my website. Looks like they’re just slowly crawling everything at the moment – no DDoS-like attack yet. I wonder if that has something to do with my website being 100% static HTML. There are no GET parameters they can tweak and, at the end of the day, there’s not that much data on my server anyway … And maybe they have no idea what stagit is, so it doesn’t trigger ā€œstandard behaviorā€, like ā€œthis is a Gitea instance, let’s crawl this like crazy!ā€?

⤋ Read More
In-reply-to » (#rm4wp7q) @movq "topic-based forums/groups", you mean what USENET used to be, and the "niche" that Reddit is fulfilling these days? :-D I get it, I agree. I think I find twtxt more fulfilling than anything else because of its small size. I feel like I truly know everyone (even if that might not be true), and find myself "at home". The bigger the place, the shyest I become, the less enticing it is.

@quark@ferengi.one Despite the Reddit part (I never understood it), this is a great analysis. I could not have put it any better. I also feel quite home here with the all feeds I follow. It’s a small bunch of good people.

⤋ Read More
In-reply-to » (#ona4qra) @movq @bender 28°C right now, but luckily, just 20°C tomorrow and rain. Even a thunderstorm at night. On Sunday we're down to 12°C. What a ride. Oh boys!

The temperatures are getting pleasant now. All the freshly cut grass really smells lovely. Looks like farmers are securing their harvests before the rain hits tomorrow in the arvo.

⤋ Read More
In-reply-to » Confession:

@movq@www.uninformativ.de ā€œtopic-based forums/groupsā€, you mean what USENET used to be, and the ā€œnicheā€ that Reddit is fulfilling these days? :-D I get it, I agree. I think I find twtxt more fulfilling than anything else because of its small size. I feel like I truly know everyone (even if that might not be true), and find myself ā€œat homeā€. The bigger the place, the shyest I become, the less enticing it is.

⤋ Read More
In-reply-to » Confession:

@movq@www.uninformativ.de this is so real… i think we need to bring back topic focused groups but like with a little off topic side of things just in case people wanna go off topic. so the option’s there but the intent is the topic! microblogging isn’t best for this yeah. i think this is part of why IRC still goes strong for many tech people

⤋ Read More
In-reply-to » it seems i do have to restart my instance to re-queue feeds or something so i definitely fucked up migration to v16 lol

@prologic@twtxt.net i gave up on trying to get my local branch clean and just git clone’d main into a new directory and built from there LMAOOO it was such a mess i’m not good at git

i saw your commits fixing queue issues, fingers crossed it works on my end!

⤋ Read More
In-reply-to » (#ffzq53q) @lyse 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".

@bender@twtxt.net It’s like having good manners at the table. Use forks and knives. ;-)

⤋ Read More
In-reply-to » I've just released version 1.0 of twtxt.el (the Emacs client), the stable and final version with the current extensions. I'll let the community maintain it, if there are interested in using it. I will also be open to fix small bugs. I don't know if this twt is a goodbye or a see you later. Maybe I will never come back, or maybe I will post a new twt this afternoon. But it's always important to be grateful. Thanks to @prologic @movq @eapl.me @bender @aelaraji @arne @david @lyse @doesnm @xuu @sorenpeter for everything you have taught me. I've learned a lot about #twtxt, HTTP and working in community. It has been a fantastic adventure! What will become of me? I have created a twtxt fork called Texudus (https://texudus.readthedocs.io/). I want to continue learning on my own without the legacy limitations or technologies that implement twtxt. It's not a replacement for any technology, it's just my own little lab. I have also made a fork of my own client and will be focusing on it for a while. I don't expect anyone to use it, but feedback is always welcome. Best regards to everyone. #twtxt #emacs #twtxt-el #texudus

@andros@twtxt.andros.dev@andros@twtxt.andros.dev <3

⤋ Read More

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. ā˜¹ļø

⤋ Read More
In-reply-to » I've just released version 1.0 of twtxt.el (the Emacs client), the stable and final version with the current extensions. I'll let the community maintain it, if there are interested in using it. I will also be open to fix small bugs. I don't know if this twt is a goodbye or a see you later. Maybe I will never come back, or maybe I will post a new twt this afternoon. But it's always important to be grateful. Thanks to @prologic @movq @eapl.me @bender @aelaraji @arne @david @lyse @doesnm @xuu @sorenpeter for everything you have taught me. I've learned a lot about #twtxt, HTTP and working in community. It has been a fantastic adventure! What will become of me? I have created a twtxt fork called Texudus (https://texudus.readthedocs.io/). I want to continue learning on my own without the legacy limitations or technologies that implement twtxt. It's not a replacement for any technology, it's just my own little lab. I have also made a fork of my own client and will be focusing on it for a while. I don't expect anyone to use it, but feedback is always welcome. Best regards to everyone. #twtxt #emacs #twtxt-el #texudus

@andros@twtxt.andros.dev You know, I’d really love to see how/if location-based addressing works in practice. I might fork jenny to judy and run both things in parallel for a while … šŸ¤”

⤋ Read More
In-reply-to » (#jkmi6pq) @movq Oooooohhhhhh, I see. Hmmmm.

@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ā€.

⤋ Read More
In-reply-to » (#3rvya6q) @lyse 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).

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

⤋ Read More
In-reply-to » This is up @movq ally, a tiny OS that runs in a boot sector. That's, it's only 510 bytes! But check it out, and see what it can do. Truly amazing. Can you beat that?!

@bender@twtxt.net Saw it this morning and I was like ā€œsay what nowā€. šŸ˜‚ I certainly can’t beat that. šŸ˜‚

(Also, cute name. The ā€œ-leā€ suffix is a German diminutive, so it means ā€œlittle OSā€. 😃)

⤋ Read More
In-reply-to » This is up @movq ally, a tiny OS that runs in a boot sector. That's, it's only 510 bytes! But check it out, and see what it can do. Truly amazing. Can you beat that?!

@@twtxt.net The fact that it has an SDK and process management is quite amazing g! 🤯

⤋ Read More

et baikal sous #openbsd n’est pas dispo avec sqlite, car il n’y a plus l’extension sqlite avec la version de php pour laquelle baikal est packagĆ©e…

⤋ Read More

I’ve just released version 1.0 of twtxt.el (the Emacs client), the stable and final version with the current extensions. I’ll let the community maintain it, if there are interested in using it. I will also be open to fix small bugs.
I don’t know if this twt is a goodbye or a see you later. Maybe I will never come back, or maybe I will post a new twt this afternoon. But it’s always important to be grateful. Thanks to @prologic@twtxt.net @movq@www.uninformativ.de @eapl.me@eapl.me @bender@twtxt.net @aelaraji@aelaraji.com @arne@uplegger.eu @david@collantes.us @lyse@lyse.isobeef.org @doesnm@doesnm.p.psf.lt @xuu@txt.sour.is @sorenpeter@darch.dk for everything you have taught me. I’ve learned a lot about #twtxt, HTTP and working in community. It has been a fantastic adventure!
What will become of me? I have created a twtxt fork called Texudus (https://texudus.readthedocs.io/). I want to continue learning on my own without the legacy limitations or technologies that implement twtxt. It’s not a replacement for any technology, it’s just my own little lab. I have also made a fork of my own client and will be focusing on it for a while. I don’t expect anyone to use it, but feedback is always welcome.
Best regards to everyone.
#twtxt #emacs #twtxt-el #texudus

⤋ Read More
In-reply-to » If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?

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

⤋ Read More
In-reply-to » @kat @xuu Recommend you git checkout main && git pull && make build. Few bug fixes šŸ˜„

@prologic@twtxt.net done! hey i got a question, you got any clue why my feeds aren’t updating? maybe it has to do with the new cache flag but i messed with that a bit and didn’t notice a difference. basically it’s like i have to manually restart yarnd to see new posts it’s really weird lol

⤋ Read More

The main reason I named my new pet machine Ephemera, is because I don’t trust SSD/NVMe’s … it’s always just a matter of time before everything goes to sh…rimps.

ā€`
$ mail

[…]

The following warning/error was logged by the smartd daemon:

Device: /dev/nvme0, number of Error Log entries increased from 1587 to 1590

[…]
ā€ā€œ`

⤋ Read More
In-reply-to » If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?

@movq@www.uninformativ.de When I reply to a message, I typically already mention the feed. Just like in this very message. I believe this mechanism should work for most replies. But there are of course the odd responses where I do not mention the original feed, but rather some other feed(s) instead to which I actually want to reply. Maybe ā€œforkingā€, as prologic calls it, would be the better option there.

⤋ Read More

I visited a good mate after a day in the office and went for a stroll in the evening. It still was really hot, phew, about 24°C. Must have been the aftermath of the fire in the morning! For sure! The firealarm went off during a meeting and we all had to leave the building. Anyway, I only managed to take one lizard photo, all the other ones we came across immediately vanished in the brush or cracks in the vineyard walls. The kestrels were way more cooperative:

Image

https://lyse.isobeef.org/asperg-2025-04-30/

⤋ Read More
In-reply-to » (#32zhfoa) @prologic not me. I hate monosyllabic replies, specifically on the written medium, so I am just typing this to make it longer. But that doesn't change the truth, and that is, I don't want, nor care, about twtxt, and Activity Pub integration. šŸ˜…

@bender@twtxt.net You’re kind of right though šŸ˜„ It makes it more engaging IMO šŸ˜…

⤋ Read More
In-reply-to » (#32zhfoa) @prologic not me. I hate monosyllabic replies, specifically on the written medium, so I am just typing this to make it longer. But that doesn't change the truth, and that is, I don't want, nor care, about twtxt, and Activity Pub integration. šŸ˜…

@prologic@twtxt.net hahahahaha! No, no, no. Every word has its use. But for things like these I like certain reactions. For example, I would have given a ā€œthumbs downā€ to the original twtxt, and done with it. Now, composing a reply, to simply say ā€œno, thank you.ā€, that I don’t like. It seems a waste of space, and it doesn’t ā€œlook goodā€. I like to see at least 140 characters! Ha!

⤋ Read More
In-reply-to » (#32zhfoa) @prologic not me. I hate monosyllabic replies, specifically on the written medium, so I am just typing this to make it longer. But that doesn't change the truth, and that is, I don't want, nor care, about twtxt, and Activity Pub integration. šŸ˜…

ā€œMonosyllabic repliesā€ refers to responses that consist of a single syllable. These types of replies are typically brief and concise, often used in situations where a simple, direct answer is given. Examples include words like ā€œYes,ā€ ā€œNo,ā€ ā€œOkay,ā€ or ā€œSure.ā€

šŸ˜‚ Can I imply you’re not interested in things like ā€œLIkeā€, ā€œReportā€, etc?! šŸ˜‚

⤋ Read More
In-reply-to » (#32zhfoa) @prologic not me. I hate monosyllabic replies, specifically on the written medium, so I am just typing this to make it longer. But that doesn't change the truth, and that is, I don't want, nor care, about twtxt, and Activity Pub integration. šŸ˜…

@bender@twtxt.net I knew you wouldn’t be interested in a Twtxt+ActivityPub šŸ˜‚ Now I have to go figure out what ā€œmonosyllabic repliesā€ means 🤣

⤋ Read More
In-reply-to » (#l5awc2q) @kat That's what I was going for at first, I already have my compose file to go up -d, but then I took a look at a couple of #Snac instances at the last second and they looked pretty dope! Now I'm stuck in my own head šŸ˜…

@aelaraji@aelaraji.com which snac instance did you see that looked pretty dope? On the ones I saw in the past, I found their web frontend to be rather messy (even more so on mobile).

⤋ Read More
In-reply-to » After yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?

@prologic@twtxt.net not me. I hate monosyllabic replies, specifically on the written medium, so I am just typing this to make it longer. But that doesn’t change the truth, and that is, I don’t want, nor care, about twtxt, and Activity Pub integration. šŸ˜…

⤋ Read More

After yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?

⤋ Read More
In-reply-to » So... I wanna take a stab at the #ActivityPub bee hive, but I'm not sure what to pick up, a #Gotosocial pocket knife or a #Snac2 bamboo stick? Any thoughts?

You know what, I can always run a separate Snac instance alongside the GTS one later on if I want to, maybe even use it for sharing Phtography stuff… a pixelfed alternative on budget kind of thing. 🤔

⤋ Read More
In-reply-to » So... I wanna take a stab at the #ActivityPub bee hive, but I'm not sure what to pick up, a #Gotosocial pocket knife or a #Snac2 bamboo stick? Any thoughts?

@kat@yarn.girlonthemoon.xyz That’s what I was going for at first, I already have my compose file to go up -d, but then I took a look at a couple of #Snac instances at the last second and they looked pretty dope! Now I’m stuck in my own head šŸ˜…

⤋ Read More
In-reply-to » (#3rvya6q) @prologic Not sure I’d attach any if clauses to this. My point is: Every time I see a hash, I’d like to have a hint as to where to find the corresponding twt.

The reason I think this can work so well and I’m in full support of it is that it’s the least disruptive way to resolve the issue of:

where did this hash come from?

⤋ Read More
In-reply-to » 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

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!

⤋ Read More
In-reply-to » 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

just for the record I didn’t say I was leaving the twtxt ā€˜community’ (did I?) but than I have other priorities to focus on in the following months. Please don’t be condescending, is not cool.

Development of Timeline (PHP client) has been stale for some reasons, a few of them in my side, so I think it won’t be updated to the new thread model, at least pretty soon.
So is not that I’ll stop using twtxt, just the client I use won’t be compatible with the new model in July.

⤋ Read More
In-reply-to » If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?

@prologic@twtxt.net Not sure I’d attach any if clauses to this. My point is: Every time I see a hash, I’d like to have a hint as to where to find the corresponding twt.

⤋ Read More
In-reply-to » 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

@movq@www.uninformativ.de I didn’t say I was leaving, just not that active here atm. I might be more active on mastodon at https://norrebro.space/@sorenpeter but I’m also rethinking that too tbh.

⤋ Read More
In-reply-to » (#4by73ea) @kat Unless you've found buds in this branch it should be fine šŸ˜† Um running yhe dame!

@prologic@twtxt.net LMAO it’s fine! i think it’s running ok i’m just nervous i might’ve messed it up because honestly i just backed up my DB then did a git merge and overwrote the merge conflicts because i was lazy and didn’t know how to properly do an upgrade with git

⤋ Read More
In-reply-to » If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?

Otherwise assume normal behavior. Pretty easy to implement I think.

⤋ Read More
In-reply-to » If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?

@movq@www.uninformativ.de If we’re focusing on solving the ā€œmissing rootsā€ problems. I would start to think about ā€œclient recommendationsā€. The first recommendation would be:

  1. Replying to a Twt that has no initial Subject must itself have a Subject of the form (hash; url).

This way it’s a hint to fetching clients that follow B, but not A (in the case of no mentions) that the Subject/Root might (very likely) is in the feed url.

⤋ Read More
In-reply-to » gah i've been so busy working on love4eva! TL;DR i switched image backends from the test/dev only module i was using to the S3 one, but with a catch - i'm not using S3 or cloud shit!!! i instead got it to work with minio, so it's a middle ground between self hosting the image uploads & being compatible with the highly efficient S3 module. i'm super happy with it :)

@andros@twtxt.andros.dev@andros@twtxt.andros.dev it’s epic!

⤋ Read More
In-reply-to » 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

@andros@twtxt.andros.dev @eapl.me@eapl.me @sorenpeter@darch.dk Sad to see you go. 🫤

⤋ Read More