Comment

Comment on Why's everyone freaking out about Firefox Terms of Service? Isn't it Open Source?

AlecSadler@sh.itjust.works ⁨3⁩ ⁨days⁩ ago

We’re all keyboard warriors with opinions.

I’ll get downvoted to hell for this, but I honestly feel like right now it is a nothingburger.

Will I continue to keep an eye on the things they do? Yes. Does their CEOs work history bother me? Yes. Will I keep using it and just keep tabs on settings and extensions? Yes.

source

Sort:hotnew top

lordnikon@lemmy.world ⁨3⁩ ⁨days⁩ ago
I agree if it gets bad they will just resurrect Icewessle once again.

source
- mesamunefire@lemmy.world ⁨3⁩ ⁨days⁩ ago
  Librewolf is basically that. It’s pretty good ngl. I don’t have to spend a half hour reconfiguring Firefox like I do in new setups.
  
  source
  - lordnikon@lemmy.world ⁨3⁩ ⁨days⁩ ago
    Yeah unfortunately it’s not in the debian Repo and I don’t like adding in 3rd party repos if I can help it but thanks for the info in case I get desperate
    
    source
    Agility0971@lemmy.world ⁨2⁩ ⁨days⁩ ago
    Its available on flathub, thats arguably better than any repos
    
    source
    -> View More Comments
sxan@midwest.social ⁨3⁩ ⁨days⁩ ago
Maybe. Not everyone is just going to ignore this, though.

I waffle between Firefox and other browsers, depending on how tolerant I’m feeling. Not using Firefox is more work. Sometimes I’ll spend a week or two with Firefox up, but normally, I’m in Luakit.But when I hit that web site that just doesn’t work with WebKit, I hop over to FF for it. Now, with this, I’ll probably start jumping to Nyxt which - while also WebKit - seems for some reason to work with more sites. Nyxt is faster, too; luakit is really slow and has a persistent scrolling bug that drives me nuts. But Nyxt hard-hangs multiple times during each hour of its, requiring a kill -9 and restart, so … Luakit.

Like I said. It’s harder to not use Firefox. But this change in policy is enough to make me change my habits and use something else when I have issues with Luakit. Or surf. Or vimb. Or whatever I’m fancying this month. Problem is, they’re mostly WebKit, and while in grateful for it, it struggles with many web sites - and especially the JS heavy ones.

source
- tomenzgg@midwest.social ⁨1⁩ ⁨day⁩ ago
  I forget why I stopped using Luakit for Qutebrowser…
  
  Maybe I should give it a go, again; or Nyxt. I’m probably more along as a programmer for its setup to be more intuitive.
  
  source
  - sxan@midwest.social ⁨17⁩ ⁨hours⁩ ago
    Luakit has a lot of problems. The biggest one right now is that it has some scrolling bug where it just… won’t. It’s extremely annoying, but it beats having to kill -9 Nyxt multiple times an hour because it hard-freezes.
    
    Why haven’t I tried Qute? Is it keyboard-control oriented?
    
    source
    tomenzgg@midwest.social ⁨15⁩ ⁨hours⁩ ago
    Yeah…; heh, discovered some things this afternoon. Neither browser was able to load Google without crashing the tab (which, I dunno, could – maybe – motivate me to kick the habit?).
    
    Luakit, on my distro, is v2.3.3 and I tried building to v2.4.0 but the built executive kept saying 2.3.3 for its version. I suspect this is probably more my fault, though.
    
    Why haven’t I tried Qute?
    
    I dunno! Heh, I feel like it’s relatively popular but I’ve also been snooping around the minimal browser space since Uzbl so maybe my perception’s off.
    
    The biggest reason you may not have is it is based on Chromium. At the time I discovered it, the dev.'s reason was due to security issues in WebKit, at the time, but that was also 5–9 years ago so that may not be a concern, anymore.
    
    It’s also built with QT; I generally use GTK so it’s my one gripe but I know it doesn’t bother everyone.
    
    And it’s built on Python (I know that bothers some); but those are the only things I can think of.
    
    It uses the same default layout that Uzbl inspired in vimprobable, dwb, jumanji, vimb, and Luakit so that’ll probably be familiar. Vim bindings out of the box (which I feel like Uzbl also inspired in all the aforementioned browsers).
    
    I feel like it’s the most stable of the bunch, for the most part (which is probably why I keep going back to it). It can be resource heavy but the customizability and fairly stable performance is generally pretty good.
    
    And it got support for uBlock Origin (I’m sure there’s a generic name but I’m afraid I don’t know it) style adblock lists recently with the help of Python’s adblock library (I hadn’t realized Luakit and Nyxt had support for that until now and it was always by major con, with Qutebrowser).
    
    Right now, there’s a Wayland display issue in suffering with but that’s QT’s fault and isn’t present on v6.8 (but my distro’s still at 6.7.2…); so that might not even be an issue, for you.
    
    source
    -> View More Comments
- AlecSadler@sh.itjust.works ⁨2⁩ ⁨days⁩ ago
  Hmm, I’ll check these out, thanks!
  
  source
  - sxan@midwest.social ⁨2⁩ ⁨days⁩ ago
    They’re all very niche. Keyboard driven. A fair number of issues; they’re all built on WebKit, with all of the compatability issues that comes with.
    
    I mean, it doesn’t hurt. But it’s like picking up vim: there’s a learning curve. They’re not for everyone, just fair warning.
    
    source
    AlecSadler@sh.itjust.works ⁨2⁩ ⁨days⁩ ago
    Oh haha so this won’t work for…well, work.
    
    source