@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
@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://yarn.girlonthemoon.xyz/search?q=%23123467">#123467</a>) hello foo bar
you would have
(<a href="https://yarn.girlonthemoon.xyz/search?q=%23123467">#123467</a> http://foo.com/tw.txt) hello foo bar
or maybe even:
(<a href="https://yarn.girlonthemoon.xyz/search?q=%23123467">#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.
@movq@www.uninformativ.de Yes! There is a cause: The renewable energies.
In Spain there is a lot of dependence on renewable energies and this is a problem for maintaining the voltage in the network. Thus, a 60% loss was lost for 5 seconds. In cascade, the circuit breakers were automatically switched off.
The B-side of renewable energies. They produce electricity but not dynamic energy.
Pensar sobre o desenvolvimento e utilização da Inteligência Artificial a partir de uma perspetiva filosófica aprofundada - este é o objetivo excecional da formação em “𝗘́𝘁𝗶𝗰𝗮 & 𝗜𝗻𝘁𝗲𝗹𝗶𝗴𝗲̂𝗻𝗰𝗶𝗮 𝗔𝗿𝘁𝗶𝗳𝗶𝗰𝗶𝗮𝗹” 🧠🤖 Não perca! Pode fazer a sua candidatura até 𝟬𝟭 𝗱𝗲 𝗺𝗮𝗶𝗼! Calendário: 09 de maio de 2025 Modalidade: e-learning 🔗Mais informações em https://s.up.pt/7fyq #Ética #InteligênciaArtificial #FormaçãoContínua #EducaçãoContínua #FLUP #Letras #LetrasUPorto #SomosLetras #ConstruiroFuturo #Uporto
@kat@yarn.girlonthemoon.xyz Well some! 🙌
ya estoy perdiendo la cabeza!! hahahha https://0x0.st/8WZO.png
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
@peron@texto-plano.xyz wow 1650 cd??? ahi tiene que estar hasta la lambada. xD cuanto emites? quiero escucharlo! xD
Jupiter Core
⌘ Read more
@kat@yarn.girlonthemoon.xyz which was your last post? 😊
@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
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
@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.
@kat@yarn.girlonthemoon.xyz I CAN’T SEE TWTXT.NET ANYMORE?! WHAT’D I DO IN THE MIGRATION HELP LOL
@movq@www.uninformativ.de oh dear lord, take it away, take it away! LOL.
@thecanine@twtxt.net Yeah this is where I think all the hype really falls down. It’s all just a really really expensive search engine and auto-complete 🤦♂️ That’s it!
@kat@yarn.girlonthemoon.xyz My eyes hurt, though. 🥴