@quark@ferengi.one Bwahahahahaha, yeah! :-D Well, birds can be considered descendants.

@movq@www.uninformativ.de my fault! Err, I meant to say, @bender@twtxt.net’s! LOL.

@lyse@lyse.isobeef.org ah, if only you were to finally clean up that code, and make that client widely available…! One can only dream, right? :-)

@lyse@lyse.isobeef.org I mean, dinosaurs “evolved” by getting wiped, right? :-D

@movq@www.uninformativ.de you said you liked seeing the hash (which is a fair choice!). All I am asking is for a reconsideration as a user configurable feature. ;-) It looks redundant, in my opinion.

@movq@www.uninformativ.de Oder gar ±inf Grad! Bibber, schwitz. Naja, passt auf jeden Fall zum Ortsnamen. :-) Mittlerweile haben sie ihr kaputtes JS repariert.

@lyse@lyse.isobeef.org Stell dir vor, es wären NaN Grad! 😱

This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png

@quark@ferengi.one I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔

@bender@twtxt.net Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?

So, by “evolve” you actually mean “remove”, @prologic@twtxt.net? :-?

Let me take this opportunity to recommend something to @bmallred@staystrong.run: https://staystrong.run/user/bmallred/twtxt.txt returned 200 but no Last-Modified header - can’t cache content :-)

Another modification I made is to actually cache it anyways. Otherwise, tt wouldn’t show anything. I implemented that for some other feed that doesn’t exist anymore.

@bender@twtxt.net it sure breaks the index formatting.

@quark@ferengi.one this is what I see:

Screenshot of neomutt running jenny, a twtxt client

@aelaraji@aelaraji.com, this one, @movq@www.uninformativ.de, is slightly breaking my neomutt index. Will post screenshot from @bender@twtxt.net’s account.

Correct, @bender@twtxt.net. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched) twtxt client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I’ve seen enough errors, I unsubscribe.

tt is just a viewer into the cache. The read statuses are stored in a separate database file.

It also happened a few times, that I thought some feed was permanently dead and removed it from my list. But then, others mentioned it, so I resubscribed.

@movq@www.uninformativ.de, that would be a nice addition. :-) I would also love the ability to hide/not show the hash when reading twtxts (after all, that’s on the header on each “email”). Could that be added as a user configurable toggle?

@falsifian@www.falsifian.org Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.

@movq@www.uninformativ.de I don’t know if I’d want to discard the twts. I think what I’m looking for is a command “jenny -g https://host.org/twtxt.txt” to fetch just that one feed, even if it’s not in my follow list. I could wrap that in a shell script so that when I see a twt in reply to a feed I don’t follow, I can just tap a key and the feed will get added to my maildir. I guess the script would look for a mention at the start of a selected twt and call jenny -g on the feed.

@falsifian@www.falsifian.org You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔

But you should not be seeing any requests from this pod

Just curious, how are you accomplishing this? Using egress iptables blocks?

Imagine if SMTP behaved like this. It would be mayhem! SMTP bounces are certain number of retries, thus alerting the user that the email address, or server, is wrong. By the way, this same problem happens on the various implementations of ActivityPub (Mastodon, all “romas”, all “keys”, and GoToSocial, which I use). Some have implemented a process to drop federation, after certain number of delivery attempts fail.

@bender@twtxt.net Yup! But you should not be seeing any requests from this pod, only the search engine ;‘(until I fix it) 😅

@prologic@twtxt.net is it more than this, right? For example, user “justamoment” (https://twtxt.net/user/justamoment/twtxt.txt) has netbros.com twice on its following list. Both feeds are long gone. There are more cases like that.

@bender@twtxt.net Hah! 🤣 Please remind me to try to fix this. Just been looking at the code, nothing is “quick”, except to add your domain to an internal blacklist, recompile and redeploy (uggh)

@prologic@twtxt.net you are welcome! :-)

@bender@twtxt.net Hmm I think you’ve uncovered a bug (or interesting side effect) of the crawler in yarns (the search engine) 😢

@prologic@twtxt.net he is referring to “ivermectin”.

Sent you some logs on Matrix.

@prologic@twtxt.net LOL. After that I ran Yarn on the apex, at netbros.com. Go to Matrix, let me drop you a snippet.

@bender@twtxt.net Btw, as you know, one thing the yarnd client has always lacked is some kind of “in-app” notification of sorts. Something to inform the user, “hey, you know what feed you follow, it’s looking like it’s kind of dead, maybe consider unfollowing it!” 🤣

I took a guess based on my shell history 🤣

prologic@JamessMacStudio
Thu Aug 22 20:50:32
~/Projects/yarnsocial/yarn
 (main) 0
$ ./tools/who_follows.sh 'https://arrakis.netbros.com/user/pedantic/twtxt.txt'
"darch follows https://arrakis.netbros.com/user/pedantic/twtxt.txt and was last seen 625 days ago"

@bender@twtxt.net No no, I get it. It’s just not as simple as any particular solution. Right now I don’t even know what the feed’s full URI was nor who on this pod (if at all) still follows it? I’ll bet it’s an inactive user right? Gimme the full URI was it was and I’ll have a poke at the DB? 🤔

@prologic@twtxt.net I understand. It is useful. But Lyse doesn’t use Yarn.

I think I am not successfully explaining the problem I perceive here. People checking non existing feeds with the hope they will come back, over and over, and no provisions in Yarn to do much about it. 🤷🏻‍♂️

@lyse@lyse.isobeef.org To be fair I think this needs to evolve anyway. Authoring new “personas” isn’t really that wildly used beyond the admin of a pod and even that’s really just me 🤣

@off_grid_living@twtxt.net What drug is that?

@falsifian@www.falsifian.org Hah! Remind me to talk to you about how yarnd peers with each pod in its own network to do exactly that. Maybe we could open up the protocol and you could potentially pee with other pods?

@falsifian@www.falsifian.org Same here! His server is notoriously unreliable but I know he is somewhat active on Twtxt 😅

@falsifian@www.falsifian.org This is why yarnd has never implement automatic un-following for this very reason. It’s hard (likely impossible) to get 100% right.

@slashdot@feeds.twtxt.net Hah! 😅 Totally didn’t see this coming 🤣 AI and LLM(s) as a “service” posing new security and privacy threats? 🙄

@lyse@lyse.isobeef.org It certainly looks like a reasonable approach to me so far 👌

@bender@twtxt.net If you look at your Following list yarnd is continually improving the tools and data available to you especially regarding feed acailabiliry and maybe this helps you manage who/what you follow? 🤔 – I’ve certainly found it immediately useful!

@lyse@lyse.isobeef.org so, is it safe to assume you occasionally, but carefully, vet your feeds, and have contingencies in place to not keep requesting a seemingly dead feed over and over?

To get this going, I implemented the easiest, next best option I could think of. Happy to get some feedback. Yes, it should be improved in the future, no doubt about that. Although, I have changed a few things in yarnd in the past, I’m not really familiar with the code base, so beware of bugs and other undesired side effects.

Microsoft Copilot Studio Exploit Leaks Sensitive Cloud Data
An anonymous reader quotes a report from Dark Reading: Researchers have exploited a vulnerability in Microsoft’s Copilot Studio tool allowing them to make external HTTP requests that can access sensitive information regarding internal services within a cloud environment – with potential impact across multiple tenants. Tenable researchers discovered the ser … ⌘ Read more

(@anth@a.9srv.net’s feed almost never works, but I keep it because they told me they want to fix their server some time.)

@falsifian@www.falsifian.org @bender@twtxt.net I’d certainly hate my client for automatic feed unsubscription, too.

I guess I can configure neomutt to hide the feeds I don’t care about.

@movq@www.uninformativ.de Is there a good way to get jenny to do a one-off fetch of a feed, for when you want to fill in missing parts of a thread? I just added @slashdot@feeds.twtxt.net to my private follow file just because @prologic@twtxt.net keeps responding to the feed :-P and I want to know what he’s commenting on even though I don’t want to see every new slashdot twt.

@bender@twtxt.net Based on my experience so far, as a user, I would be upset if my client dropped someone from my follower list, i.e. stopped fetching their feed, without me asking for that to happen.