ohshit604

u/ohshit604@lemmy.halstead.host
0 posts · 67 comments

Recent posts

No posts.

Recent comments

I remember Quebec trying to do the same thing back In 2007, they wanted their own identity and sovereignty and the rest of Canada shamed them for it, eventually the federal government gave in to their demands and here we are today.

Alberta wants to separate, the rest of Canada is shaming them, they’ll whine and complain until the federal government caves, which is what they’re doing with the pipeline deal.

Would be nice to see this community take on the same rule that /c/selfhosted@lemmy.world did regarding Ai and non-Ai posts.

Also, first commit was 3 months ago yet this repo has over 1k stars. Prove to me that this isn’t a rug pull waiting to happen.

I would hate that for whatever service that is for,

It’s the provincial governments authentication service for Canadians, if you ever used GCKey it’s essentially the same thing but provincial opposed to federal.

It allows ease of access to things like medical records, tax records, license renewals and such.

Alberta has their own system similar to this.


the only Google service I knowingly use is Youtube

Might I suggest Invidious as an alternative, you can host your own that way only 1 device on your network needs to contact YouTube directly or you can use one that is public.

Mine is accessible to Canadians at https://inv.halstead.host/, prohibited to the rest of the world so rate limiting isn’t a huge issue for me.

I also know there is a script you can set up which will handle the initial contact to federate automatically.

I tried finding such a script but had no luck. I was able to export my subscription list from sh.itjust.works and imported it on my instance.

I had to unsubscribe and resubscribe to the communities I follow as I was experiencing the ‘Subscribe Pending’ issue but after a little while things seemed to start evening out and becoming a bit more stable.

My instance has been online for about a month, the supplied docker-compose.yaml was quite straightforward, had a little headache with Nginx but nothing overly complicated.

The long-con so to speak is federation, you have to subscribe to each community manually to begin federating with them, i have noticed timing issues with other instances such as Lemmy.world and have not been able to resolve them.

Chiming back in 3 hours later, just downloaded the latest release from Freetubes website, i can confirm that with my invidious instance that everything seems to be working fine. While my invidious instance is a private one, ill share it with you in the meantime until your normal setup gets back in order, shoot me a DM.

I’m not home to verify my Freetube however, I just checked my invidious instance and can confirm that the first video I attempted to play errored.

I am updating my Invidious instance to see if it still persists, perhaps the instances you’re using are out of date, I know invidious updates quite frequently to stay on-top of YouTube changes.

Edit; Updating invidious appeared to resolve my errors, I can only assume the instances you’re using are out of date. I’ll check Freetube when I get home.

Depends on the instance, some can say “hey don’t index us” whereas others can say “hey index us so we grow”, each instance admin has that decision however search engines can ignore the request to not index and do it anyways.