prologic @twtxt.net
 (7h ago)

(#ie62rlq) @asquare@asquare.srht.site And actually…

does a one-off fetch of any feed @-mentioned by a pod member

What is true here is if someone visits your “profile” on a pod whilst logged, it, yes yarnd fetches it in the background if it wasn’t already cached, as a “once off”. This is true.

#a4v2xcq
prologic @twtxt.net
 (8h ago)

(#d2iwcwq) @movq@www.uninformativ.de Ahh yes, that is probably the case 🤣 To be fair I don’t think too much about how things enter my cache, I just assume it’s either someone on my pod following them or whatever.

I didn’t follow at first because:

asquare may not follow you

Which probably means @asquare is probably using a client that doesn’t publicise its user agent or has it turned off? 🤔

#t75uuza
movq @www.uninformativ.de
 (8h ago)

(#d2iwcwq) @prologic@twtxt.net Apparently not. 🥴

This is the twt of @asquare@asquare.srht.site I’m referring to:

(#4w3ilsa) @prologic@twtxt.net Actually, my twts from the last two days aren’t showing up on , so I guess that no-one is following me and the reason my earlier twts did show up is that yarnd does a one-off fetch of any feed @-mentioned by a pod member. Comments in the code suggest that this is the case, see internal/server.go, commit 7dcec70e, line 468. As the author of that code, can you confirm/deny?

#shgh45a
lyse @lyse.isobeef.org
 (1d ago)

(#xbi36aq) I do not notice any lag with my Logitech Lift. Haven’t changed the inital battery from July last year yet. I have to say I’m rather impressed. The only reason for this cordless mouse is that I haven’t found a vertical mouse with a tail. Otherwise, I’d 100% taken that.

#bzhmwja
prologic @twtxt.net
 (1d ago)

(#eo5c7oq) @bender@twtxt.net Fair enough 🤣 To be honest, I don’t really have an opinion either way, I think what he’s done is a bit “silly” of course, but I dunno. I’ve never. been invested in Wordpress as I said. I’d like to think I’d behave much better than Mat in a similar circumstance, but then again I’m not lucky? enough to be in that position (stink’n rich and wealthy), so who knows 😅

#oab2p6q
prologic @twtxt.net
 (3d ago)

I can’t decide which DCDC charger to. buy for my Camper trailer. Help me! 🙏 Currently it’s a choice between:

The only advantage of the Renogy over the KickAss/ITech models is it has Bluetooth monitoring and an App capabilities so you can check the state of the battery/charging/etc from your phone.

#tv5oq3a
movq @www.uninformativ.de
 (3d ago)

(#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”.

#w72qu5a
movq @www.uninformativ.de
 (4d ago)

(#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.)

#cf2y3za
lyse @lyse.isobeef.org
 (5d ago)

(#ljav2ea) Just to be clear, I’m 100% for mandating UTF-8 and only UTF-8. Nothing else. Exactly how it has always been.

I just like to send a proper Content-Type stating the right encoding to be a good web citizen. That’s all. :-)

#42qrkia
lyse @lyse.isobeef.org
 (5d ago)

(#aytfnca) Righto @anth@a.9srv.net, v2 is up again for me:

Clients (and human readers) just assume a flat threading
structure by default, read things in order […]

I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn’t happen very often. Anyway, just a personal preference. Nothing to really worry.

The v2 spec requires each reply to re-calculate the hash
of the specific entry I’m replying to […]

Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I’m probably just not getting your point here in the entire paragraph.)

Clients should not be expected to track conversations back
across forking points […]

I agree. It totally depends on the client.

#vc5howq
lyse @lyse.isobeef.org
 (5d ago)

(#zloep2q) @movq@www.uninformativ.de If my memory serves me right, I think v2 doesn’t mention UTF-8 at all. Then I came along and noted that the Content-Type: text/plain might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth@a.9srv.net’s comment that he doesn’t want to even have a Content-Type header in the first place.

I reckon it should be optional, but when deciding to sending one, it should be Content-Type: text/plain; charset=utf-8. That also helps browsers pick up the right encoding right away without guessing wrong (basically always happens with Firefox here). That aids people who read raw feeds in browsers for debugging or what not. (I sometimes do that to decide if there is enough interesting content to follow the feed at hand.)

#ljav2ea