A Roku stick requires the Roku streaming service to be functioning to be useful. If there wasn’t a service with streaming media, the stick would have nothing to stream.

In cases like this; it’s still only artificially dependant on Rokus services.

The hardware is perfectly capable of streaming from any number of services, including entirely self-hosted solutions like Emby/Jellyfin/Plex; yet the device can be remotely bricked just by nolonger providing Rokus services to it.

That’s Rathaniel to you.

I could understand that if you had been granted an account you’d successfully logged into, and then started receiving login refusal afterwards; but to have not actually had an account yet makes it pretty obvious when you try to login and fail that the application has not been accepted. Whether that’s an explicit refusal, or just an idle queue that’s being ignored, doesn’t really make a difference. If the instance admins wanted to talk about it, they’d have emailed you; or published some means of contacting them outside lemmy.

I wouldn’t expect to receive the reason for refusing the application via any other means than the email I’d provided in that application. That’s the entire purpose of providing an email; so you could be contacted when/if there are updates to your applications status.

If you’re going to provide false contact info, you can’t be all that surprised when you don’t receive communication(s).

And if they did give a reason via email, I would not see it. Not sure if that’s happening but that’s also a case of bad software.

No, that ones entirely on you. Don’t provide a false means of communication then blame them for using it.

… Why the google cache link?

https://apnews.com/article/abortion-restrictions-kansas-lawsuits-07b9d71bca29119ab4acc30c28a67099

its like taking the condom off and walking out of the room, which I have to imagine is legal.

Lmao. Beleive it or not; straight to jail.

We’ve been having some stability issues over the past few days

I was gonna ask about that. I had noticed several slow downs over the last couple days, but pretty brief. Glad to see it’s being looked into/sorted out.

Chears, m8!

I tend to drop the link into yt1s.com

Sometimes just for audio, sometimes for the full vid.

I’m rarely grabbing more than one video at a time though.

[re-commenting as I meant this to be a top-level comment, not a reply]

127.0.0.1 is the loopback address. Ie it’s your computer trying to reach a service its hosting (prowlarr)/talk to itself. Sonarr/Radarr should be using this address as long as prowlarr+sonarr/radarr are on the same machine.

Prowlarr is either not running, or port 8080 is blocked by your firewall.