We would consider it if it has the blocklist function removed. Whether the fork gets ongoing maintenance is a concern though.
Thanks for your work uncovering this. Imposing this broad and undisclosed censorship upon the user is unacceptable, so we have stopped hosting Tesseract on our instance.
Okay, that was intense.
So sad. Loved him in The Hunt for Red October. Going to watch Possession now as I've never seen it, but it sounds good.
It was monochrome.tf but they've pivoted to doing something else now.
Won't somebody think of the Eloi?
You're right, I was thinking about 32-bit timestamps. Definitely not an issue for 64-bits.
Won't switching from an unsigned 64-bit integer to a signed one of the same size effectively halve how far into the future they can handle dates, exhausting it in 2038?
The hyprland issues I'm aware of, but what's the issue with suckless?
Yeah, same story - the few I looked at looked like they were from consumer ISPs. We had ~7m requests from Brazil, ~900k from Argentina, and a little less from Ecuador, Colombia and Russia.
We were getting DDoS'd by a bunch of South American IPs (mostly Brazilian) from maybe 18 hours ago.
We had this issue on and off for a few weeks at least, causing massive postgres CPU spikes. I ended up blocking large page params with an nginx regex.
I already use Navidrome, but I discovered Explo through your post, so thanks! It seems to work well in that it brings in the tracks that it should, but I don't think I can keep using it because it pollutes my 'Recently Added' list in Navidrome with 50 new albums, each with a single track. If I could somehow prevent that, I think I'd keep using it. I tried using an .ndignore file but that didn't work - it stops them showing up in Recents, but also prevents the tracks from working in the playlist that Explo generates.
Also been using it for years. Love the unique interface. Wish they'd do more substantial updates than those seasonal icon packs though, especially given the amount of income they must have from subscriptions.