@lyse@lyse.isobeef.org Jawoll. So machen wir das jetzt auch immer. 😅

@movq@www.uninformativ.de Und nicht behebt. Schlag ich morgen mal unserem Auftraggeber vor. 8->

@movq@www.uninformativ.de Yup, I think that’s my favorite season.

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.

@prologic@twtxt.net nick is skinshafi and domain is aelaraji.com 🫡

@bender@twtxt.net Haha 😛

@prologic@twtxt.net you are too nice. 😂

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

@lyse@lyse.isobeef.org About time. %)

Liebe ist, wenn man die Bugs einfach akzeptiert.

@prologic@twtxt.net nope, you didn’t. I am simply stating what it might come across as obvious. LOL.

@asquare@asquare.srht.site And let’s not forget the additional input lag! 😅 I have one wireless mouse, a Logitech M705, and the lag is noticeable. Maybe it’s a cheap model, I don’t know, I don’t use it that often. The batteries last forever, though. 🥴

@bender@twtxt.net Did I say he was a “good guy”? 🤔 😅

@prologic@twtxt.net I used WordPress from 2004 to 2011. Based on his behaviour, I don’t think Matt is a good guy. I wouldn’t want him as an acquaintance.

@aelaraji@aelaraji.com So, what’s your salty addr? I tried to guess it by doing a lookup, but I guess I didn’t guess right 😅

@prologic@twtxt.net :waves: So it seems! I must admit that it surprised me. I did not expect to have anyone following me quite this early. But it’s the nice kind of surprise :)

Say no to cordless peripherals! Real mice have tails! (I just like not having to charge and/or swap out batteries all the time)

@aelaraji@aelaraji.com Congrats 🥳

FINALLY!! I figured my way around daemonizing #saltyd with an rc.d init script with logs and all! 🥳 still have to try a tiny modification before writing that thing… I hope it doesn’t Bork it 😅

@prx@si3t.ch If you were to read this, I would’ve suggested that you gave Podman a try… alas, you won’t.

Autumn is there: https://lyse.isobeef.org/morgensonne-2024-10-11/

Colored leaves in front of dark sky

The WordPress ecosystem has lost its mind… - YouTube 👈 This is a pretty good summary of how fucked up the Wordpress ecosystem is now thanks to Mat 🤦‍♂️ (not that I’ve ever used Wordpress uggh 💩)

@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” 🤣

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

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

@lyse@lyse.isobeef.org Sorry what’s RCE?

@prologic@twtxt.net I have no clue, but the only thing that comes to mind is that chances of RCE are higher the more it exposes.

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

• KickAss 12V/24V 25A DCDC Charger With Solar MPPT + Pre-Wired Anderson

  
• iTECHDCDC25 12V/24V 25A DCDC & MPPT Battery Charger
  
• Renogy DCC30S 12V 30A Dual Input DC to DC Battery Charger with MPPT
  

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.

@off_grid_living@twtxt.net This looks like a glass of water? hmmm 🧐

@aelaraji@aelaraji.com Congrats 🙌

@asquare@twtxt.net I guess someone follows you from my pod (twtxt.net) so welcome 🤗 (if you see this)

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

Pulled an all nighter for nothing 😅 but hey, better paranoid than sorry!

A simple medium experiment

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

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

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

@aelaraji@aelaraji.com No that’s not normal.

@doesnm@doesnm.p.psf.lt Much appreciated!! 🙏 I’ll go through the files and see if I can understand any of it. I might learn a thing or two along the way.

Web interface is deleted in https://git.mills.io/saltyim/saltyim/commit/376de2702319686c902ec03b8ca1e17b020fc639 but seems incorrectly (in source i see git lfs metadata). Can be builded if you grab https://git.mills.io/saltyim/saltyim/src/commit/15a64de82829/internal/web/app.wasm and place it in source (go directory has cached source) and rebuild

@prologic@twtxt.net would you please check my web interface? is that a normal thing or am I missing something?

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

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

@doesnm@doesnm.p.psf.lt Nice 👌 I’ll send you a message later 😅

Im also have running saltyd at doesnm.cc (delegated to salty-doesnm.p.projectsegfau.lt) but maybe i do something wrong

@aelaraji@aelaraji.com Of course! 🤣 @xuu and I run saltyd 😅

Anyone has saltyd actually up and running? my deployment was a mess … will tell you all about it when I wake up 😅

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

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.

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