• 0 Posts
  • 53 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle






  • I prefer Calyx on my phone, for the sake of the extra privacy of Micro-G vs sandboxed Google Play Services.

    You should give DivestOS a try tbh if you prefer microG to Sandboxed Play Services, since Divest’s implementation of microG is sandboxed/unprivileged unlike Calyx’s, which is a massive privacy and security benefit. Divest in general is a lot more private and secure then stock or Calyx, since it includes a lot of hardening and patches from Graphene, so I’d recommend it as the second best option to Graphene in general, and definitely by far the best option for using microG. Divest also covers most of the same phones Calyx and Graphene do, unfortunately no Pixel Tablet support though.

    (I’m not trying to shill Divest or anything btw lol, I just think its a great underrated project that deserves a lot more recognition and support than it has, and seems to fit your use case)





  • Not all of it is carrier related. I had an S21 unlocked (from US) and it still included Facebook and their garbage services, Netflix, OneDrive, etc. Also all of Samsung’s first party bloatware and nonsense is prevalent regardless. Not to mention Samsung selling data and their tracking, crippling your phone if you root it or install a custom OS (and in the US outright preventing it entirely), etc. Can’t recommend them or their phones at all, but its unfortunate because they have great hardware, just terrible software.






  • Yeah, that’s what bothers me. Feels like people romanticize pre-Musk Twitter, when in reality, its always just been complete garbage. Musk’s Twitter is certainly worse in some ways, though that isn’t saying a lot.

    Overall, Twitter just sucks. Use other platforms where possible.


  • I’m not sure if it could be done without at least compromising security to some extent (at least in Android’s current state, but maybe that could be changed or worked around in the future), but yeah, overall I do agree, that’s what I was trying to get at. I definitely support there being an official and easier method to root on Android, as long as it isn’t the default, and as long as the risks are clearly explained. People should certainly be able to do whatever they want with their own devices, it is unfortunate, and definitely an overstep from Google and OEMs.


  • Not having root is done on Android for some very good security reasons to be fair, it opens up a giant attack surface and risk for all kinds of malware and nasty stuff to take advantage of. I don’t think it’s done completely in malice as you think. Its a very important part of the app sandbox and Android’s security model at large.

    With that said, I do think that people should have the option to root if they want to, I’m not a fan of OEMs like Samsung and whoever else purposely preventing people from rooting at all costs. I think people should be able to do whatever they want with their own device, root just certainly shouldn’t be the default, and users should be aware of the risks if they choose to use it. But I do think it should be a possibility for those who really do wish to do so.

    With Android, it all just comes down to the OEM and variant of it that you’re stuck with. As a whole, I think its an amazing project and OS, though unfortunately Google, and especially OEMs, tend to make a lot of bad choices. It’s similar to Linux as a whole in that aspect. You’ve got options like ChromeOS which are a nightmare for privacy and user freedom any way you look at them, but then you’ve got your traditional distros like Debian, Arch, Fedora, etc, which are the exact opposite. Its an important distinction.


  • Why not get the flatpak?

    Security concerns. There’s a lot of debate over it, but from the research I’ve done, I believe the Flatpak of Firefox is less secure, since it seems to remove part of Firefox’s internal sandboxing, and relies heavily on Flatpak’s sandboxing.

    Basically makes it easier to compromise your data within the browser (like cookies, site data, passwords, etc), but maybe harder to get to the rest of your OS.

    I just prefer using the rpm of Firefox with Firejail, as that keeps Firefox’s built-in sandboxing intact, while adding an extra layer similar to Flatpak to restrict it further. Best of both worlds.


  • Skimmer@lemmy.ziptoFirefox@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    24
    ·
    edit-2
    1 year ago

    Its great and has a lot of potential, I like a lot of what it does. I just wish they had packaging easily available for Fedora/RHEL through a COPR or the like. Also would’ve preferred if they used a stable release vs. the ESR of Firefox as the base, but I can understand why.

    with hardening out of the box

    Floorp definitely isn’t hardened out of the box in my testing. Only thing it does is seems to disable Firefox’s telemetry, which is nice, but more hardening is certainly needed through other projects like Arkenfox (which work here on Floorp too). Also looks like Floorp makes it easier to toggle some privacy settings that you’d usually have to tweak the about:config for, and comes pre-installed with uBlock Origin, which is great.

    I think overall my only concern with Floorp will be how well and quickly the developer can keep up with updates. The track record for now looks good, but only time will tell. Besides that, this is a good and very promising project, will definitely keep an eye on it.