- Mozilla has launched a paid subscription service called Mozilla Monitor Plus, which monitors and removes personal information from over 190 sites where brokers sell data.
- The service is priced at $8.99 per month and is an extension of the free dark web monitoring service Mozilla Monitor (previously Firefox Monitor).
- Basic Monitor members receive a free scan and one-time removal sweep, while Plus members get continual monthly data broker scans and removal attempts.
Archive link: https://archive.ph/YdY3R



lsblk outputs that my NVMe0n1p1 is mounted at /var/snap/Firefox/common/host-hunspell.
This drive and partition is where my root is.
lsblkis just lacking a lot of information and creating a false impression of what is happening. I did a bind mount to try it out.sudo mount -o ro --bind /var/log /mntThis mounts
/var/logto/mntwithout making any other changes. My root partition is still mounted at/and fully functional. However, all thatlsblkshows under MOUNTPOINTS is/mnt. There is no indication that it’s just/var/logthat is mounted and not the entire root partition. There is also no mention at all of/.findmntshows this correctly. Omitting all irrelevant info, I get:TARGET SOURCE [...] / /dev/dm-0 [...] [...] └─/mnt /dev/dm-0[/var/log] [...]Here you can see that the same device is used for both mountpoints and that it’s just
/var/logthat is mounted at/mnt.Snap is probably doing something similar. It is mounting a specific directory into the directory of the firefox snap. It is not using your entire root partition and it’s not doing something that would break the
/mountpoint. This by itself should cause no issues at all. You can see in the issue you linked as well that the fix to their boot issue was something completely irrelevant.