(#zo4hvla) Thank you, thank you @sorenpeter@darch.dk 😃

(#lnlbnsq) Well I have been working on an update of Timeline, mainly improving speed. Getting a multiple of feeds can really become a big fetch. So I would advocate for ideas to maintain performance.

Regardings your points:

1. Agreed, but at the moment date+txt creates the unique timestamp
   
2. Preferably newest twt as the last line, will make for more structure.

(#4w3ilsa) @asquare@asquare.srht.site Yeah, that would have been overkill. :-) Hello and welcome, btw. 👋

(#4w3ilsa) More interesting aspects about Antenna:

At first, I thought that Antenna acted like a “traditional” blog aggregator, but that’s not really the case. You know, with a blog aggregator, you would normally contact the owner and ask them to include your feed. That step is not needed with Antenna.

So, when someone publishes a blog/gemlog post and you would like to “reply” to it, you can just do that: Write your post and then publish the link on Antenna. This means your Gemini capsule doesn’t need to be well known in order to participate. If I read something interesting and would like to reply, I could do that right now – instead of having to wait for the webmaster of the aggregator to include/unlock my feed.

Also, it’s just arbitrary Gemini links in Antenna – unlike a blog aggregator, where everything is a blog post. So I just saw someone publishing a link titled “A wild twtxt appears” and that’s just a link to their twtxt file.

In many ways, this thing is a bit more like a forum than a blog aggregator. Or maybe you could also call it a “bus”.

(#zloep2q) @lyse@lyse.isobeef.org Ahh, I see. So it’s not really a drama. 😅

(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)

(#jsj23rq) @anth@a.9srv.net (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has always mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)

(#34f5xkq) @lyse@lyse.isobeef.org That looks like lovely weather. We had nothing but rain. 🥴

(#j2ykgoa) @bender@twtxt.net So you stayed? Fingers crossed 🤞😵

(#qysxoba) @lyse@lyse.isobeef.org lol indeed 😆

I hope you guys in the US get safely through the next storm. 😳

That is a fun little rabbit hole: https://rodarmor.com/blog/whence-newline/

Signature PDF | https://signature-pdf.framalab.org/signature

Going through some old CDs.

Jam & Spoon - Angel (DJ Misjah Remix)

I’ve always liked this track, but ~30 years ago I didn’t have good headphones. Now I do and only now do I realize how “dense” the atmosphere of this track is. 😳 Guess my speakers back then simply didn’t render most of the bass … 🤦

(#rodltgq) @lyse@lyse.isobeef.org Did someone call perror() after something that does not change errno? 🥴

~bt | https://btxx.org/

(#eqgicaq) @3r1c@3r1c.net I think I’m gonna like that blog. 😅 https://unixdigest.com/articles/is-the-madness-ever-going-to-end.html

https://unixdigest.com/

What’s going on with the timestamps on HackerNews articles? 🤔 A lot of them are off: https://movq.de/v/1341904fa5/s.png

(#hpynjxq) @bender@twtxt.net As for stability, yes. As for “easy to understand”: Probably depends on how well you hide things like lists or hash maps behind library functions. 🥴

(#maojn6q) @xuu@txt.sour.is Yes, of course. This has been blown out of proportion anyway. All I originally wanted to say is that the b2sum program isn’t very widely available.

It would help to know how many different clients there actually are. I suspect that number is very close to 3.

(#rreyqya) @quark@ferengi.one This message of yours was another reason for writing 2hex and 2bin. It made me realize my existing hex2bin script was buggy. So now I have that portable version in C which runs pretty much everywhere: https://movq.de/v/31843f7317/s.png 🥳

(#4w3ilsa) @bender@twtxt.net Yup, that’s where my web search ended up as well. 🥴

(#4w3ilsa) @cuaxolotl@sunshinegardens.org Ah, I see. Thanks for the explanation. 👌

(#4w3ilsa) @cuaxolotl@sunshinegardens.org What’s “the gemini tx model”? 🤔

lxappearance pour configurer le darkmode sur dwm ?

ParaCyberBellum Security Review | https://library.paracyberbellum.io/review

Shrinkpdf : Shrink PDF files with Ghostscript | https://github.com/aklomp/shrinkpdf

Des favoris Nextcloud à twtxt et dmenu | https://galusik.fr/log/2021-12-12-dtwtbmk.html

twtxt via dmenu | https://git.sr.ht/~fredg/mybin/tree/master/item/twt

Aujourd’hui, petits changements de formatage de mes documents sur le style RFC. Le titre apparaît désormais au centre et en haut de page. On a aussi la date de rédaction suivie de la date de dernière mise à jour. Que c’est beau :)

(#tukxcsq) @prologic@twtxt.net YES James, it should be up to the client to deal with changes like edits and deletions. And putting this load on the clients, location-addressing with make this a lot easier since what is says it: Look in this file at this timestamp, did anything change or went missing? (And then threading will not break;)

https://renecoignard.com/

(#rksyfja) why can we both have a format that you can write by hand and better clients?

(#gg7ykkq) No, json is overhead. I love twtxt for simplicity where blog is just text file and not several json files where fields are repeated…

(#r7ee4ya) yes that works

(#2bsh7vq) (#<2024-09-24T12:53:35Z https://twtxt.net/user/prologic/twtxt.txt>) What does this screenshot show? The resolution it too low for reading the text…

(#j63urka) (#<2024-09-24T12:45:54Z https://twtxt.net/user/prologic/twtxt.txt>) @prologic@twtxt.net I’m not really buying this one about readability. It’s easy to recognize that this is a URL and a date, so you skim over it like you would we mentions and markdown links and images. If you are not suppose to read the raw file, then we might a well jam everything into JSON like mastodon

(#a73p7ma) (#<2024-09-24T12:44:35Z https://twtxt.net/user/prologic/twtxt.txt>) There is a increase in space/memory for sure. But calculating the hashes also takes up CPU. I’m not good with that kind of math, but it’s a tradeoff either way.

(#rksyfja) (#<2024-09-24T12:39:32Z https://twtxt.net/user/prologic/twtxt.txt>) @prologic@twtxt.net It might be simple for you to run echo -e "\t\t" | sha256sum | base64, but for people who are not comfortable in a terminal and got their dev env set up, then that is magic, compared to the simplicity of just copy/pasting what you see in a textfile into another textfile – Basically what @movq@www.uninformativ.de also said. I’m also on team extreme minimalism, otherwise we could just use mastodon etc. Replacing line-breaks with a tab would also make it easier to handwrite your twtxt. You don’t have to hardwrite it, but at least you should have the option to. Just as i do with all my HTML and CSS.

(#bz2mpca) (#<2024-09-24T12:34:31Z https://twtxt.net/user/prologic/twtxt.txt>) WebMentions does would work if we agreed to implement it correctly. I never figured out how yarnd’s WebMentions work, so I decide to make my own, which I’m the only one using…

I had a look at WebSub, witch looks way more complex than WebMentions, and seem to need a lot more overhead. We don’t need near realtime. We just need a way to notify someone that someone they don’t know about mentioned or replied to their post.

(#r6z66ta) lol, this flags looks like russian name

(#cu5bdda) Sorry but i dont undestand b. New feed author? But why?

(#j63urka) Aggred. But reading twtxt in raw form sounds… I can’t do this

Some more arguments for a local-based treading model over a content-based one:

1. The format: (#<DATE URL>) or (@<DATE URL>) both makes sense: # as prefix is for a hashtag like we allredy got with the (#twthash) and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.

2. Having something like (#<DATE URL>) will also make mentions via webmetions for twtxt easier to implement, since there is no need for looking up the #twthash. This will also make it possible to make 3th part twt-mentions services.

3. Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don’t follow.

Finally pubnix is alive! That’s im missing? Im only reading twtxt.net timeline because twtxt-v2.sh works slowly for displaying timeline…

(#52eajxq) @movq@www.uninformativ.de Heaps of mozzies and other stuff that wants to eats you. Yeah, I noticed that as well. But I don’t know if it’s really more than usual. I might just have forgotten how bad it was in the past by now. :-?

With the wet beginning this year, water-loving insects certainly got a head start.

(#senmxza) Voilà: https://git.mills.io/yarnsocial/yarn/pulls/1181

Hello!

(#senmxza) @prologic@twtxt.net Correct. The plan is that operators have to manually trust a peer before it is used for fetching missing conversation roots from. Preview of the horrible UI:

(#tr42vzq) @bender@twtxt.net Yeah, it was nice. 23°C and a bit of wind. Quite acceptable in my opinion. :-)