Nirav & Hyelim sit down at Framework HQ SF to talk about all things RISC-V and DeepComputing.
RISC-V Mainboard: https://frame.work/products/deep-computing-risc-v-mainboard
Read the blog post: https://frame.work/blog/introducing-a-new-risc-v-mainboard-from-deepcomputing
---
About Framework
We know consumer electronics can be better for you and for the environment. Unlike most products, ours are open for you to repair and upgrade.
https://frame.work
Follow Us
Instagram: https://www.instagram.com/FrameworkComputer/
Facebook: https://www.facebook.com/FrameworkComputer
Twitter: https://twitter.com/FrameworkPuter
TikTok: https://www.tiktok.com/@frameworkpc
Mastodon: https://fosstodon.org/@frameworkcomputer
Forum: https://community.frame.work
LinkedIn: https://www.linkedin.com/company/frameworkcomputer
502 Bad gateway.
It’s linking to Invidious instances, here’s the YouTube link: https://www.youtube.com/watch?v=iMwepyyaj8I
Thanks. There are many reasons people might want the original YouTube link (e.g. privacy YT apps that intercept YouTube links but not invidious ones).
It’s a farside.link/invidious link. which, instead of sending you directly to Youtube, chooses one of Invidious (privacy frontend for YT) instances to show yoi the video. you probably got redirected to an instance that had issues at that time. Opening the link again should send you to a different instance.
whole privacy frontend movement deserves more attention, so that solutions for issues like this get developed