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. ☹️
@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 … 🤔
@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”.
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.
@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”. 😃)
@@twtxt.net The fact that it has an SDK and process management is quite amazing g! 🤯
This is up @movq@www.uninformativ.de 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?!
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
3rvya6q
and your feed, but your feed certainly does not include that particular twt (it comes from my feed).
@movq@www.uninformativ.de No problems 🤗
@kat@yarn.girlonthemoon.xyz Whoop, whoop! Congrats 🥳
@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).
git checkout main && git pull && make build
. Few bug fixes 😄
@bender@twtxt.net Haha 🤣
@kat@yarn.girlonthemoon.xyz Please git pull and rebuild 😂 Off of main
. I merged the catcher
branch already!
git checkout main && git pull && make build
. Few bug fixes 😄
@bender@twtxt.net LMAOOO
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
git checkout main && git pull && make build
. Few bug fixes 😄
@prologic@twtxt.net I can hear the moans of regret already. They are loud, and steady. 😅
@kat@yarn.girlonthemoon.xyz @xuu@txt.sour.is Recommend you git checkout main && git pull && make build
. Few bug fixes 😄
@aelaraji@aelaraji.com oh fuck yea snac would be a good use of that! makes me wanna do the same… GTS also has a new profile view for profiles that shows only images which makes it great as a photo posting place
@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.
@bender@twtxt.net You’re kind of right though 😄 It makes it more engaging IMO 😅
@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!
@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 🤣
@movq@www.uninformativ.de Shall I add this to the spec I’m writing? ✍️
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).
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. 😅
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?
@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 😅
@aelaraji@aelaraji.com gotosocial is epic
@yejokjanan@texto-plano.xyz hahaha wow muy cool.. bienvenido a twitter desde una terimal y decentralizado xD
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.
@movq@www.uninformativ.de I think we can make this work 👌 As long as it’s just a client hint.
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!
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.
@bender@twtxt.net It’s great if I’m sitting on the balcony and horrible otherwise. Gah.
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.
@movq@www.uninformativ.de absolutely yes!
@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.
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.
@kat@yarn.girlonthemoon.xyz Should be fine 🙌
@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
@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:
- 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
.
@bender@twtxt.net Fuck I meant “bugs” 🐞 Geez 🙄
@prologic@twtxt.net running the dame, oh my! TMI! :-P
@andros@twtxt.andros.dev what makes Kagi “the best search engine”? It is premium, alright. Allegedly you don’t get ads, but pay up-front for it, monthly.
@kat@yarn.girlonthemoon.xyz Unless you’ve found buds in this branch it should be fine 😆 Um running yhe dame!
@prologic@twtxt.net yayyyy
@prologic@twtxt.net oh these posts showed up on a page refresh without me needing to restart so maybe it’s starting to work again?
@movq@www.uninformativ.de Lwt me think on this.
@kat@yarn.girlonthemoon.xyz Nope it’s totally fine 🤗
@kat@yarn.girlonthemoon.xyz No new peers shoyls show up automatically.
@kat@yarn.girlonthemoon.xyz what did i fuck up this time lol