• 0 Posts
  • 31 Comments
Joined 2 years ago
cake
Cake day: July 24th, 2023

help-circle











  • The ultimate in privacy for YouTube is Invidious https://invidious.io/, which fully proxies your videos from YouTube through an Invidious server. Every once in a while YouTube will get the upper hand and figure out how to fingerprint and block the servers, but so far the community has always figured out how to circumvent it. One advantage is that you can feasibly use a VPN with Invidious; without it, you have to keep hopping from VPN server to VPN server until you find one YouTube hasn’t already blocked, especially on a large public VPN like ProtonVPN. This applies to NewPipe as well, since NewPipe still tries to talk to YouTube directly as far as I understand. On Android I use Clipious as the app to access the Invidious servers.


  • So many people say to isolate google play services in another profile, but I have not seen anything quantifying the amount of attack surface reduction or what benefit this gives in terms of anonymity or security. Google play services includes Firebase Cloud Messaging (FCM) which is what enables most apps to give timely notifications. There are alternatives like ntfy, but they require some understanding of how to set them up, and tinkering.

    Finally, multiple profiles is useful for the most security conscious but for the typical user I do not believe its very useful. One thing I noticed is notifications are not consisently reliable, so setting up a “Facebook” profile does isolate you from the app but then you may miss notifications. You also have to type your password for every profile switch.


  • NVIDIA definitely has stability issues, newest drivers still kernel panic on resume from suspend. Only thing more you can do is try to capture debug logs with nvidia-bug-report.sh (I go in during a crash via SSH, usually the system is still responsive for a little while after), and post it to the NVIDIA Linux forums. They do actually seem to use the feedback there, NVIDIA reps respond from time to time and say they’ve submitted bug reports from the feedback. Otherwise, after that yeah you just do what you have to do for a usable system and wait…






  • If it works on chromium I’d consider that even if it is a quirk on the bank website, chromium is handling it cleanly and allowing you to use the site. That’s something we probably want incorporated in Firefox. I’d encourage submitting the bug report to Mozilla, and don’t assume too much about what they can/cannot do!


  • I think the key part here is that it’s a guess on your part whether using Firefox is the cause. Do you get any specific error when using the website? Or does something just “not work”, such as you click a button and it does nothing?

    Also, I’ve run into stuff like this before, and my best bet has been to be flexible about using other browsers to work around issues. I would suggest testing the banking website with Chromium (or even Chrome). If it works, file a bug with Mozilla (https://support.mozilla.org/en-US/kb/file-bug-report-or-feature-request-mozilla) and just use Chromium/Chrome for only that website until the bug is fixed.

    This will allow you to still do business, while still participating in open source via a helpful bug report that could end up benefitting others as well.