Says the official support channels, which you should be checking for information anyway, unless your only intention is to scream your frustration into the void. If that’s the case, best of luck on that resolving anything.
ETA: like I said, it’s a closed beta, so not something you can install. And it won’t be a pull request because this fix won’t require an update to Lidarr, it’ll just start working again when the new server is done.
They’re standing up a new metadata server, which takes time. What more information are you expecting from them? I mean I suppose they could just lie and say sure it’ll be up next week, but it would be a lot more frustrating for them to keep saying that and pushing back the date.
If it ain’t broke, don’t fix it, yeah?
What the devs keep getting irritated about is people coming into the Official Lidarr Branch support channels and asking for support for something the devs have no control over or ability to assist with. Keep in mind that an individual user’s Lidarr instance does not connect directly to musicbrainz - the volume of API requests generated by Lidarr would be unsustainable without subscriptions. It connects to an intermediary metadata server set up and maintained by the Lidarr volunteers.
If they add a built-in option to add custom metadata servers, people will have an expectation of support. Even a note right next to the option that states custom metadata servers get no assistance wouldn’t help much since most people can’t seem to read. Basing that on the number of people who come into the Lidarr support discord channel every single day and ask if something is wrong with the metadata server despite there being a stickied message with very bold lettering explaining the issue and its current status.
I will agree that the devs in the discord have a shit bed-side manner, though. But there’s a reason that, if this were software produced by a company, you’d be speaking to a customer support specialist instead of directly to a dev. As someone who long ago worked my way up the IT ladder out of the rage-inducing pits of user-facing support roles, I definitely get it.
Lidarr is not in danger of being abandoned like Readarr. The new metadata server for Lidarr is already up and in closed beta. A few final issues are being worked out before it’s opened to the public.
Thanks for the links! I’ve got the I2P Router app configured and running as a daemon process.
The GSP mod isn’t even needed anymore. There’s an env variable (“VPN_PORT_FOWARDING_UP_COMMAND”) you can set for gluetun that will set the port in qbit provided by Proton. Dr Frankenstein’s guide shows how to configure it in the Proton-specific config section.
Pretty sure you can download that stuff if you want to save it. I could be wrong, though. I deleted FB, Insta, and all that jazz at the start of the dictator’s first term.
Does I2P utilize nodes or something that can be hosted? I’m lucky enough to live in a location with symmetrical gigabit internet, so even if I don’t use it myself I could at least donate some bandwidth. Could run next to my TOR relay.
Private trackers are a very handy option. I’ve found their rules can often get restrictive. Although it makes sense - gotta protect the swarm.
Lidarr is still very much supported and the issue is being actively worked. The only people bitching about it are entitled users who demand the free software be fixed and maintained on their schedules instead of that of the volunteer devs who have lives of their own.
If you want to download at dial-up speeds for most of your stuff.
Torrenting over TOR. Fantastic idea. You clearly know what you’re talking about.
Use cases are important.
You want a tray of cookies for that original line?
It’s a general rule, there are exceptions. I’d think it would be obvious why a VPN is needed for some even if you don’t need it.
ZPMs!