(#dbcqunq) @movq@www.uninformativ.de Just some rubbish trashy youtube videos on stupid crap I don’t believe in 🤣
#xosg7wq
(#dbcqunq) @movq@www.uninformativ.de Just some rubbish trashy youtube videos on stupid crap I don’t believe in 🤣
(#dbcqunq) @prologic@twtxt.net What happened now? 🥴
(#dbcqunq) @bender@twtxt.net No no, I’m quite sane 🤣
The world has gone mad.
(#d2iwcwq) @movq@www.uninformativ.de Yeah I noticed that earlier, and forgot 😅 That explains everything now 🤣
(#d2iwcwq) @prologic@twtxt.net They’re using Gemini, maybe that’s why?
(#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.
@asquare@asquare.srht.site By the way… It might be nice to set yourself up with an Avatar 👌
(#ie62rlq) @asquare@asquare.srht.site I see your reply now that I’m following you 🤣 The commit you’re ferring to btw is for WebMentions, which has little practical value IMO, it works but is rarely useful 😅
(#vt6echa) @asquare@asquare.srht.site Welcome to Twtxt 🤣 Discovery definately does work, but it also helps if you use a client that publicises your user-agent or you turn it on 🤣
(#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? 🤔
(#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, seeinternal/server.go
, commit7dcec70e
, line 468. As the author of that code, can you confirm/deny?
(#d2iwcwq) @movq@www.uninformativ.de eh? 🤔
(#4w3ilsa) @asquare@asquare.srht.site (I wonder if that will ever show up without me mentioning you. 😅)
(#k7bkhsa) @lyse@lyse.isobeef.org Jawoll. So machen wir das jetzt auch immer. 😅
(#k7bkhsa) @movq@www.uninformativ.de Und nicht behebt. Schlag ich morgen mal unserem Auftraggeber vor. 8->
(#7qox5ya) @movq@www.uninformativ.de Yup, I think that’s my favorite season.
(#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.
(#eo5c7oq) @bender@twtxt.net Haha 😛
(#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 😅
(#7qox5ya) @lyse@lyse.isobeef.org About time. %)
Liebe ist, wenn man die Bugs einfach akzeptiert.
(#xbi36aq) @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. 🥴
(#eo5c7oq) @bender@twtxt.net Did I say he was a “good guy”? 🤔 😅
@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 😅
(#vplonzq) @aelaraji@aelaraji.com Congrats 🥳
Autumn is there: https://lyse.isobeef.org/morgensonne-2024-10-11/
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 💩)
(#tv5oq3a) @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” 🤣
(#tv5oq3a) @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. :-)
(#tv5oq3a) If you mean, remote code execution, none of these devices are remotely, even connected to anything that resembles any kind of network connectivity.
(#tv5oq3a) @lyse@lyse.isobeef.org Sorry what’s RCE?
(#tv5oq3a) @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:
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.
(#tm2lnmq) @off_grid_living@twtxt.net This looks like a glass of water? hmmm 🧐
(#pjrulnq) @aelaraji@aelaraji.com Congrats 🙌
(#4w3ilsa) @asquare@twtxt.net I guess someone follows you from my pod (twtxt.net
) so welcome 🤗 (if you see this)
(#4w3ilsa) @asquare@asquare.srht.site Yeah, that would have been overkill. :-) Hello and welcome, btw. 👋
snapdrop looks amazing, but why should I run Docker to host it. I hate docker. https://github.com/SnapDrop/snapdrop
(#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”.
(#xizvsna) @slashdot@feeds.twtxt.net Isn’t that the pot calling the kettle black Jack? 🤔 Where are your principles? Or don’t you have any? 😅
(#gnovnwq) @aelaraji@aelaraji.com No that’s not normal.
(#zloep2q) @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 😅
(#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.)
(#5niffga) @doesnm@doesnm.p.psf.lt Nice 👌 I’ll send you a message later 😅
(#grzfzhq) @aelaraji@aelaraji.com Of course! 🤣 @xuu@txt.sour.is and I run saltyd
😅
(#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. :-)
(#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.
(#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.)
(#34f5xkq) Merci, @movq@www.uninformativ.de! Back to gray this afternoon again, mostly dry, though.