• 7 Posts
  • 653 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


  • Why do you want to use Shouko? Yeah it can bulk-tag anime but it doesn’t necessarily do a better job than Jellyfin with AniDB plugin. Also, it tends to hammer their API like an idiot and will get your user temp-banned or even perma-banned (depending on the size of your collection), while the Jellyfin plugin has rate limits.

    I used it once when I was moving my collection to Jellyfin and I barely got my account back.

    I would strongly suggest using just the regular Jellyfin plugins and adding titles to the directory in small batches and taking breaks if it stops recognizing them because it means the API is throttling you.




  • This whole debacle is a festival of stupidity:

    • It’s a personal project that taxes the sole maintainer disproportionately.
    • Millions of idiots use it blindly and end up building elaborate software on it. https://xkcd.com/2347/
    • I’ll bet you 99.99% of those idiots use it only for ip.isPrivate(), which you can write yourself in 5 minutes.
    • The CVE is a non-issue (who the fuck would call a function that takes string notation with hex numbers?)
    • Appealing and reverting or downgrading CVEs is super complicated.

    At this point the maintainer is fucked no matter what they do, so archiving the project and telling everybody to fuck off right back was really the only sane thing to do.


  • Then fork it and do that.

    These projects are structured as hobbyist projects and get whatever time the maintainer can spare. I have projects like that, they’re useful, but I’m not gonna prioritize them over… anything else, come to think of it.

    The fact so many people treat a hobbyist project with one maintainer as critical infrastructure is insane, but that’s on them. Everybody likes free software, nobody likes to help or pay the maintainer.






  • If you mean to do that in the public DNS records please note that public records that point at private IPs are often filtered by ISP’s DNS servers because they can be used in web attacks.

    If you don’t use your ISP’s DNS as upstream, and the servers you use don’t do this filtering, and you don’t care about the attacks, carry on. But if you use multiple devices or have multiple users (with multiple devices each) eventually that domain will be blocked for some of them.






  • If you were 100% specific you would be effectively writing the code yourself. But you don’t want that, so you’re not 100% specific, so it makes up the difference. The result will include an unspecified percentage of code that does not fit what you wanted.

    It’s like code Yahtzee, you keep re-rolling this dice and that dice but never quite manage to get the exact combination you need.

    There’s an old saying about computers, they don’t do what you want them to do, they do what you tell them to do. They can’t do what you don’t tell them to do.




  • Contact support and tell them how many you need and they’ll try to accommodate you. There were a lot of people abusing the service and hosting hundreds of domains so now they’re making everybody request them explicitly unfortunately. They’ve also had to suspend their .dedyn.io DDNS service indefinitely because of the abuse.

    That’s why we can’t have nice things.

    Please read up on DNSSEC because you will be required to turn it on for every domain you host with them.