With those specs nothing will be fast. Except Lynx or w3m - which are not really usefull for modern browsing.

If you can, at least upgrade your memory and disk to ssd. You cam get second hand stuff for pretty cheap. However if you cannot do that I would first make sure you get your OS as lightweight as possible to free as much of your resources for browsing. Arch is a good choice. I would also use LXCE for your desktop environment. Or even no desktop environment at all and just boot to browser.

Then you should use modern browser with as little bloat as possible. You have two realistic choices: chromium fork (like brave) or firefox fork (like librewolf or mull browser). Make sure you open setting and disable all the things you do not need. You shluld also google what are some more advanced things you could disable. Make sure you install ublock origin extention and open its setting and set it to block everything that sites do not need to run (like ads etc...)

I think noscript or umatrix extention would also improve your experience. Since lots of websites do not need to run code in background.

Make sure you do not install extentions you do not need.

If for some reason you can afford to own raspberry pi or non-provider router while you can afford to buy some extra ram: Offload blocking to your router or pihole. Maybe you will have to upgrade your router to openwrt if it is supported. If your internet speed is also slow: Setup a proxy that would cache all websites you visit. So they will load faster the next time.

You can also browse some stuff offline. Wikipedia can be downloaded and browsed locally. There are apps for that. Apps that are way more lightweight than a browser.

I hope all this helps you somehow.

  • source
  • [–] 2 points 6 months ago

    That's not a kernel notification, that's a program you have installed setup to monitor for oom kernel notifications then to kill the offending process before it causes system issues. I installed one ages ago as I hit oom quite a bit with some of the data analysis I do in python.

  • source
  • [–] 4 points 6 months ago (2 children)

    I can't tell where you're getting this message from, but kernel logs would mention "OOMKill", so I'm assuming this isn't from the kernel itself, but another monitor logging it and reporting on it perhaps.

    Create extra swap and that will help prevent this.

  • source
  • It's a simple systemd service that builds your mirrorlist based on its config, which has the same options as the online mirrorlist creator.

    I set it up to run once a week and I never ran into any trouble. Worst case you'd have to overwrite the mirrorlist by hand, which is what you already do periodically.

  • source
  • parent
  • context
  • [–] 0 points 6 months ago (1 child)

    Þat's one þing I'm never sure about wiþ Arch: some stuff is safely automate-able, and some isn't, and it's not clear to me which is which. I need to build a cheat-sheet one of þese days.

  • source
  • parent
  • context
  • [–] 2 points 6 months ago

    make everyone to use signal by any means and sudo pacman -S signal-desktop /s

    as an answer for your question , I actually stopped using whatsapp altogether just because of this, anyway signal is good only problem is you have to get everyone to text you on signal.

  • source
  • [–] [S] 1 point 6 months ago* (last edited 6 months ago)

    It's that time again!

    Firefox ESR 140.10.0

    Firefox RR 150.0

    Relevant for AUR users this time, there is a regression with rustc 1.95^1^ affecting both releases. So those building from source will need to either:

    • Ensure they compile with compatible rust version (1.94)
    • Apply fix for Bug 2033279
    • Use PKGBUILD that sorts it out. firefox and konform-browser^2^ have upstream patch ported for RR and ESR, respectively.

    Removing ac_add_options --enable-rust-simd from mozconfig might also be a workaround.

    ^1^: Which is what Arch currently ships.

    ^2^: Only fork delivering the security fixes from this monthly security release as of writing.

  • source
  • [–] 1 point 7 months ago

    I have noticed a greater number of IT infrastructure attacks after the European(-adjacent) wars started in 2022. Even where I live, which isn't particularly close to where the action is happening.

    As for browser themselves, take a closer look at release notes and changelogs (for forks, go to upstream). Note the number and severity of addressed issues and update frequency.

    This is to what I was mostly referring. I don't really care to look at Chromium's release notes anymore since 2018 when I switched back to Firefox, so I'm probably missing a lot there. But I read every release notes from Firefox, and I haven't seen much uptick in severity or number of addressed issues there. Maybe I'm not paying enough attention there either, or maybe they don't have enough manpower or interest to fix/find severity issues. Or maybe they just don't have them. πŸ™ƒ

    But either way, it's definitely a good idea to keep updated, on all your software packages! πŸ™‚πŸ‘

  • source
  • parent
  • context
  • [–] 1 point 7 months ago

    That's a lot of cruft to sift through, honestly. I scrolled for a couple of minutes each on a few of those blogs and couldn't find a single direct vulnerability within a browser. Do you have a link, perhaps? Most I saw was shit surrounding the ecosystem. Supply chain attacks, attacks on routers, vulnerable extensions, etc.

    πŸ€·β€β™‚οΈ

  • source
  • parent
  • context
  • [–] [S] 1 point 7 months ago* (last edited 7 months ago) (1 child)

    This comment and its support is baffling to me. How is this not obvious to professionals?

    haven’t seen any uptick in issues lately that makes me more worried about browser updates than like 5 years ago.

    Then you have not been paying attention and I urge you to start doing so!

    Blogs:

    https://socket.dev/blog

    https://krebsonsecurity.com/

    https://www.malwarebytes.com/blog

    https://johnhammond.beehiiv.com/archive

    https://www.bleepingcomputer.com/author/bill-toulas/

  • source
  • parent
  • context
  • view more: β€Ή prev next β€Ί