In-reply-to » @lyse errors are already reported to users, but they're only visible in the following list.

@prologic@twtxt.net Yeah, I’ve noticed that as well when I hacked around. That’s a very good addition, ta! :-)

Getting to this view felt suprisingly difficult, though. I always expected my feeds I follow in the “Feeds” tab. You won’t believe how many times I clicked on “Feeds” yesterday evening. :-D Adding at least a link to my following list on the “Feeds” page would help my learning resistence. But that’s something different.

Also, turns out that “My Feeds” is the list of feeds that I author myself, not the ones I have subscribed to. The naming is alright, I can see that it makes sense. It just was an initial surprise that came up.

​ Read More
In-reply-to » Just realized that phone came with a bunch of “hidden” Meta/Facebook services pre-installed and they cannot be uninstalled, so I guess me trying to “fight” WhatsApp is pointless anyway. đŸ€Ș

@aelaraji@aelaraji.com That’s good to know. đŸ€” Luckily, the phone wasn’t full of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.

​ Read More
In-reply-to » @bender I'm not a yarnd user, but automatically unfollowing on 404 doesn't seem right. Besides @lyse's example, I could imagine just accidentally renaming my own twtxt file, or forgetting to push it when I point my DNS to a new web server. I'd rather not lose all my yarnd followers in a situation like that (and hopefully they feel the same).

@falsifian@www.falsifian.org that’s the thing: Twtxt doesn’t care much about followers. It is not that kind of social media. Yet, I agree with the exponential back off approach. I just don’t want to keep constantly trying to fetch that which will not resurrect, nor want people to continue hitting my endpoint, which will not resurrect. 😊

​ Read More
In-reply-to » China Is Backing Off Coal Power Plant Approvals Approvals for new coal-fired power plants in China dropped by 80% in the first half of this year compared to last, according to an analysis from Greenpeace and the Shanghai Institutes for International Studies. The Associated Press reports: A review of project documents by Greenpeace East Asia found that 14 new coal plants were approved from January to June with a total capacity of 10 ... ⌘ Read more

@slashdot@feeds.twtxt.net oh oh! There goes the Australian economy đŸ€Ł

​ Read More

China Is Backing Off Coal Power Plant Approvals
Approvals for new coal-fired power plants in China dropped by 80% in the first half of this year compared to last, according to an analysis from Greenpeace and the Shanghai Institutes for International Studies. The Associated Press reports: A review of project documents by Greenpeace East Asia found that 14 new coal plants were approved from January to June with a total capacity of 10 
 ⌘ Read more

​ Read More
In-reply-to » @bender 404 could be indeed a temporary error if the file resides on a mounted remote filesystem and then the mount point fails for some reason. With a symlink from the web root to the file on the mount, the web server probably will not recognize the mount point failure as such. Thus, it might not reply with a 503 Service Unavailable (or something like that), but 404 Not Found instead. (I could be wrong on that, though.)

@lyse@lyse.isobeef.org errors are already reported to users, but they’re only visible in the following list.

​ Read More

đŸ‡©đŸ‡° OphĂžrt — venligst afbestil! // 🇬🇧 Discontinued — please unsubscribe! // tilfĂŠldige ord fĂžlger // random words follow

​ Read More
In-reply-to » I'm wrong! Both 404 and 410, among others, are considered dead feeds: https://git.mills.io/yarnsocial/yarn/src/branch/main/internal/cache.go#L1343 Whatever that actually means.

@bender@twtxt.net I’m not a yarnd user, but automatically unfollowing on 404 doesn’t seem right. Besides @lyse@lyse.isobeef.org’s example, I could imagine just accidentally renaming my own twtxt file, or forgetting to push it when I point my DNS to a new web server. I’d rather not lose all my yarnd followers in a situation like that (and hopefully they feel the same).

​ Read More
In-reply-to » I'm wrong! Both 404 and 410, among others, are considered dead feeds: https://git.mills.io/yarnsocial/yarn/src/branch/main/internal/cache.go#L1343 Whatever that actually means.

If case it wasn’t clear, and from the horse’s mouth itself (my emphasis):

// These are permanent 4xx errors and considered a dead feed

​ Read More
In-reply-to » @prologic, does this rings a bell to you? 159-196-9-199.9fc409.mel.nbn.aussiebb.net

@lyse@lyse.isobeef.org right, now, on this:

“The rightℱ way is to signal 410 Gone if the feed does not exist anymore and will not come back to life again. But that’s hard to come by in the wild. Somebody has to manually configure that in almost all situations.”

Even so, what does Yarn do if a 410 is sent? I don’t think it does anything at the moment, but I could be wrong.

​ Read More
In-reply-to » @prologic, does this rings a bell to you? 159-196-9-199.9fc409.mel.nbn.aussiebb.net

@bender@twtxt.net 404 could be indeed a temporary error if the file resides on a mounted remote filesystem and then the mount point fails for some reason. With a symlink from the web root to the file on the mount, the web server probably will not recognize the mount point failure as such. Thus, it might not reply with a 503 Service Unavailable (or something like that), but 404 Not Found instead. (I could be wrong on that, though.)

The rightℱ way is to signal 410 Gone if the feed does not exist anymore and will not come back to life again. But that’s hard to come by in the wild. Somebody has to manually configure that in almost all situations.

But yes, as @falsifian@www.falsifian.org points out, exponential backoff looks like a good strategy. Probably even report a failure to users somehow, so they can check and potentially unsubscribe.

​ Read More