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

@lyse@lyse.isobeef.org Yeah I would never use something that is “Internet” connected 🤣 In any case, most of the places we go camping is basically in “tim buck too” 🤣

⤋ Read More
In-reply-to » I can't decide which DCDC charger to. buy for my Camper trailer. Help me! 🙏 Currently it's a choice between:

@prologic@twtxt.net Bluetooth still classifies as connecting remotely. The attacker has to be in close proximity, but yeah. If you use it only where noone else is around, you’re fine. :-)

⤋ Read More
In-reply-to » I can't decide which DCDC charger to. buy for my Camper trailer. Help me! 🙏 Currently it's a choice between:

If you mean, remote code execution, none of these devices are remotely, even connected to anything that resembles any kind of network connectivity.

⤋ Read More

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.

⤋ Read More
In-reply-to » There’s a lot more activity in Geminispace than I realized: gemini://warmedal.se/~antenna/

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

⤋ Read More
In-reply-to » Bluesky Is Now Courting Threads Users Bluesky, the decentralized social network cofounded by Jack Dorsey, created a Threads account to court users frustrated by Meta's moderation issues. Thurrott reports: This week, the Bluesky team also used Threads to share some tips on how to get started on Bluesky, how to get more engagement, and more. The company also emphasized its decentralized structure and more extensive customization options, ... ⌘ Read more

@slashdot@feeds.twtxt.net Isn’t that the pot calling the kettle black Jack? 🤔 Where are your principles? Or don’t you have any? 😅

⤋ Read More

Bluesky Is Now Courting Threads Users
Bluesky, the decentralized social network cofounded by Jack Dorsey, created a Threads account to court users frustrated by Meta’s moderation issues. Thurrott reports: This week, the Bluesky team also used Threads to share some tips on how to get started on Bluesky, how to get more engagement, and more. The company also emphasized its decentralized structure and more extensive customization options, … ⌘ Read more

⤋ Read More
In-reply-to » @anth (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.)

@movq@www.uninformativ.de Yeah this is why thin @anth@a.9srv.net is that and that any v2 spec we get around to actually publishing with far better quality than the bullshit half-baked attempt I tried to 🤣; should just mandate utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅

⤋ Read More
In-reply-to » @anth (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.)

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

⤋ Read More
In-reply-to » @movq 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's comment that he doesn't want to even have a Content-Type header in the first place.

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. :-)

⤋ Read More
In-reply-to » Cool, @anth, thanks for the followup! I have to reread the original v2 in order to really follow your explanation, but that document seems to be offline at the moment. I'll try again later. :-)

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.

⤋ Read More
In-reply-to » @anth (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.)

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

⤋ Read More
In-reply-to » New post (mostly follow-up on the previous with a few new points) on the twtxt v2 discussion. http://a.9srv.net/b/2024-10-08

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

⤋ Read More
In-reply-to » New post (mostly follow-up on the previous with a few new points) on the twtxt v2 discussion. http://a.9srv.net/b/2024-10-08

Cool, @anth@a.9srv.net, thanks for the followup! I have to reread the original v2 in order to really follow your explanation, but that document seems to be offline at the moment. I’ll try again later. :-)

⤋ Read More
In-reply-to » New post (mostly follow-up on the previous with a few new points) on the twtxt v2 discussion. http://a.9srv.net/b/2024-10-08

@2024-10-08T19:36:38-07:00@a.9srv.net Thanks for the followup. I agrees with most of it - especially:

Please nobody suggest sticking the content type in more metadata. 🙄

Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.

Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk. Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (source code) or RANDOMSTRING@garrido.io on https://webfinger.net

⤋ Read More