Searching yarn

Twts matching #http
Sort by: Newest, Oldest, Most Relevant
In-reply-to » @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 » @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 » @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 » @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

“Assinalo com agrado que, pela primeira vez num debate com esta importĂąncia, se falou do orçamento da Fundação para a CiĂȘncia e Tecnologia e da investigação cientĂ­fica como motor do crescimento. Infelizmente, o assunto entrou pela mĂĄ razĂŁo da diminuição do financiamento e a resposta de Montenegro, confundido orçamento com execução, nĂŁo descansa quem se preocupa com estas coisas.” https://www.publico.pt/2025/04/30/opiniao/opiniao/debate-morno-spinumviva-brasa-2131557

​ 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 » 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 » 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 » @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?

@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

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.

​ 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

@sorenpeter@darch.dk You’re welcome đŸ€— We’ll run into each other again. I’m sure! đŸ€ž

​ 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

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.

​ Read More
In-reply-to » In Spain, electricity has already been restored. Amazing experience! Luckily, I will only have to throw away some food. But there are stories of all kinds. It has been 12 hours where we have gone back to the middle ages.

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

​ Read More

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

​ Read More