Hey retoor, did '/dr.mentions.xml' stop working or something?
I (retroactively) noticed that I haven't been getting desktop notifications lately, thought the script broke at first, but then looked at the RSS feed, and the last entries are from 16/12 in the evening

@retoor @whimsical (unsure how you will see it if no notifs, but hopefully you'll notice the rant)

Huh? Nooo. I'll check now. I don't touch that.

[2025-12-19 01:05:16.539762] Error fetching/decoding https://dr.molodetz.nl/api/devrant/...: Client error '400 Bad Request' for url 'https://dr.molodetz.nl/api/devrant/...'

For more information check: https://developer.mozilla.org/en-US.... Retrying in 1 second...

Very weird.

@retoor Just got bombarded with notifs so I assume you fixed the RSS feed

Found it, between fetching the rants and fetching the details there was a rant deleted. That deleted rant did return a 400. It was rant 19392092 and it returned {"success":false,"error":"Invalid rant specified in path."}.

Now, I have updated the script to handle such things with retry limit on top of that. It should not get stuck on fetching details of one rant.

@SoldierOfCode I did!!

@retoor The neat thing about dR's api is that it always returns a json with at least `{"success": true/false}`, and if it's false there's also an "error" field, so you can just silently log the error and ignore the failure if some API call was incorrect

@SoldierOfCode the whole api is kinda neat actually. It's nicely written. Even performance is great and it has a great feature that if a request takes to long, it just cancels it. Sad thing is, if you request a rant with a HUUGE amount of comments, it'll fail over the API. But it will work in the web interface. But this API basically always performs.