My instance is running on a Server in my homelab. The dynamic IP is just how my ISP works. I’ve been running this instance since late 2019. So far Google has only ever blocked my IP whenever I hit their Servers with too many API calls too quickly. Last time they blocked me though was probably 1/2 - 2 years ago. The current version of Invidious does try to minimize API calls which helps a lot. Honestly Google changing API calls/value names and patching the source code is more annoying to deal with than IP bans.
The only way I can see them permanently blocking instances with non-static IPs is if they go down the Twitter route where you can’t even view anything unless you’re logged in.
Is it a public instance or just for you and your fam/comrades? But yeah, mandating a login requirement is what I’ve been afraid of. I would just stop using yt altogether if it came down to that.
My instance is running on a Server in my homelab. The dynamic IP is just how my ISP works. I’ve been running this instance since late 2019. So far Google has only ever blocked my IP whenever I hit their Servers with too many API calls too quickly. Last time they blocked me though was probably 1/2 - 2 years ago. The current version of Invidious does try to minimize API calls which helps a lot. Honestly Google changing API calls/value names and patching the source code is more annoying to deal with than IP bans.
The only way I can see them permanently blocking instances with non-static IPs is if they go down the Twitter route where you can’t even view anything unless you’re logged in.
Is it a public instance or just for you and your fam/comrades? But yeah, mandating a login requirement is what I’ve been afraid of. I would just stop using yt altogether if it came down to that.
It’s a private instance. Maybe I’ll open it up, not sure.
Same. Once they go that far I’ll just
# zfs destroyInvidious and move on to PeerTube. I hope more people will move as well when that happens.