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. 🥴
@xuu@txt.sour.is, see this. The italics didn’t come out.
@kat@yarn.girlonthemoon.xyz yes, both the newsletter and the podcast, from time to time.
@prologic@twtxt.net I was not expecting much, but since the list of restaurants near company buildings, was hard coded into it, I did expect it to at least copy the menu text, from the websites, in its database. Ironically, the only restaurant where it got something right, is the only one, where the websites has the text as a transparent PNG, the AI has to convert to text.
@kat@yarn.girlonthemoon.xyz MinIO is a good choice for a self-hosted Object Storage (compatible with S3 APIs) 👌
@kat@yarn.girlonthemoon.xyz Don’t be nervous, I make sure I test the shit™ out of things before anyone else does 🤣
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 :)
i posted a patreon update that details the changes more: https://www.patreon.com/posts/i-am-now-working-127687614
that post says i didn’t update my guide yet but i actually did like right after i made that post lol so you can CTRL+F
for minio stuff there!
@prologic@twtxt.net exciting!!!!!! i’m SO SORRY i didn’t get to doing the migration for my instance though - i’ve been really busy! T__T but i hope to get to it sometime this week i really wanna upgrade i think i’m just a bit nervous for whatever reason lol
@thecanine@twtxt.net do you read ed zitron’s newsletter? he writes in depth about how AI is a crock of shit it makes me feel normal for once
@movq@www.uninformativ.de this looks really cool
@Yarn@yarn.social yo, what’s up? I am busy running my business here!
@thecanine@twtxt.net “*BuT cAnInE, tHe A(G)i ReVoLuTiOn Is NoW*” Hahahaha! Thanks for good laugh! 🤣
Hello @Yarn.social@yarn.social 👋 (testing something)
@thecanine@twtxt.net Sorry, but you were expecting what now?! 🤣
@eapl.me@eapl.me this would be, what, the third time you leave? 😅 I jest around quite a bit, act as Devil’s advocate, and am an overall maligned phaun, but please know that I appreciate you, and enjoy your engagement.
We will be here (maybe) if you ever decide to come back.
Once or twice a year, I make an effort to switch from dark mode / black terminals to light mode again.
It usually doesn’t end well, because the contrast is just not as good. There’s a reason that things like professional DAWs or CAD software use a dark theme.
With a heavy bold font, it’s much better:
https://movq.de/v/331aa40bde/s.png
My font doesn’t get any bolder than this, though. I’d have to make a new variant of it. Mhh. 🤔
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
@eapl.me@eapl.me I honestly believe you are overreacting here a little bit 🤣 I completely emphasize with you, it can be pretty tough to feel part of a community at times and run a project with a kind of “democracy” or “vote by committee”. But one thing that life has taught me about open source projects and especially decentralised ecosystems is that this doesn’t really work.
It isn’t that I’ve not considered all the other options on the table (which can still be), it’s just that I’ve made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and don’t consider all the possible things that could go wrong.
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
July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms.
Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a ‘micro consensus’ feels… not right.
I don’t know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.
@movq@www.uninformativ.de Oh, I see. I reckon I accidentally late April-fooled myself. :-D
It’s an interesting comparison. I really should have thought about that.
You’re right, the rendering would not be very spectacular. :-)
@bender@twtxt.net ROFL 🤣
@prologic@twtxt.net if I tell you I will lose the edge. I want to mass produce them, as a business venture. LOL.
@bender@twtxt.net How does it work? 🤔