@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. 😅
Hehe! it’s done! 🤡
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?
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. 🤡
@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
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?
i don’t think any of you know what a fan listing is but basically it was a fandom thing in the 2000s where people would make websites that other people could sign up for to show they’re a fan of something. more info here.
anyway i made a fan listing kinda thing in PHP to learn the language. it was fun af
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?
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.
@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
Otherwise assume normal behavior. Pretty easy to implement I think.
@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:
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
i don’t think it’s normal to have to restart my yarnd instance every time i wanna see new posts right
@movq@www.uninformativ.de oh this would be handy! i think my feed’s busted after the migration lol
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. 🫤
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?
Instead of
(<a href="https://we.loveprivacy.club/search?tag=123467">#123467</a>) hello foo bar
you would have
(<a href="https://we.loveprivacy.club/search?tag=123467">#123467</a> http://foo.com/tw.txt) hello foo bar
or maybe even:
(<a href="https://we.loveprivacy.club/search?tag=123467">#123467</a> 2025-04-30T12:30:31Z http://foo.com/tw.txt) hello foo bar
This would greatly help in reconstructing broken threads, since hashes are obviously unfortunately one-way tickets. The URL/timestamp would not be used for threading, just for discovery of feeds that you don’t already follow.
I don’t insist on including the timestamp, but having some idea which feed we’re talking about would help a lot.
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
@sorenpeter@darch.dk You’re welcome 🤗 We’ll run into each other again. I’m sure! 🤞
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
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.
@kat@yarn.girlonthemoon.xyz Well some! 🙌
i hosted a forgejo instance out of boredom. it’s pretty epic https://bytes.4-walls.net/kat
@bender@twtxt.net <333
@bender@twtxt.net i forgot it LOL
@kat@yarn.girlonthemoon.xyz which was your last post? 😊
help why didn’t my last post go through
@kat@yarn.girlonthemoon.xyz you are OK. Taking a deep breath, everything’s gonna be irie, mon. 😅
@kat@yarn.girlonthemoon.xyz i just did the migration to stuff on the cacher branch so i’m like WHAT IS HAPPENING
@kat@yarn.girlonthemoon.xyz oh ok i think it’s slowly rebuilding stuff
@kat@yarn.girlonthemoon.xyz I CAN’T SEE TWTXT.NET ANYMORE?! WHAT’D I DO IN THE MIGRATION HELP LOL
test can anyone see this pls reply if u can
@movq@www.uninformativ.de oh dear lord, take it away, take it away! LOL.