Your home server might have the required bandwidth but not requisite the infra to support server load (hundreds of parallel connections/downloads).
Bandwidth is only one aspect of the problem.
That solves the media distribution related storage issue, but not the CI/CD pipeline infra issue.
Uninstall OneDrive, problem solved.
Either Connect to VPN > Download the Add-on.
Or, on the GitHub or Gitlab page, provide a copy of extension and the instruction to install it locally.
Wait, I thought they are recipient of Sovereign Tech Fund. Didn’t that help them with their budget?
I’ve Invidious hosted on my Little Raspberry Pi 4, and using it’s WPA app on every device I got.
Zero ad + Decent UI + Access to highest video quality
Could not they just use URL redirection instead?
Your CSS knowledge is still useful to customise other areas of Firefox UI.
Initially I followed this route to avoid Snap version provided by Ubuntu.
Later I just downloaded Tar package from Mozilla, and update it manually.
In short, I just abandoned deb/snap/flatpak altogether.
UX is a very subjective matter.
Bad news is that it is not clear at this point whether Mozilla is going to go forward with the implementation. A post on Reddit by one of the project members suggests that the build is a “rough proof-of-concept”. Some features tested in the build “did not survive”. It is unclear which did not, as they are not mentioned. Mozilla is, however, implementing those that survived the cut into Firefox. Again, the poster does not mention which those are. It is also not verified that the poster is actually a member of the project team, so take this with a grain of salt as well.
All of these are signs of persistent threat actors aka State sponsor hacker. Though the real motive we would never know as it’s now a failed project.
This is exactly what came to my mind while reading through the article.