Boof

  • 1 Post
  • 47 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle





  • What we need isn’t browsers. What we need is an universal way to write extensions cross-browser.

    Browsers themselves are easy to make. The problem is convincing extension devs to work with yet another codebase.

    E: Think of it this way. There’s a lot of open source browsers out there.

    Are you using any of them? Probably not.

    Would you use one if it doesn’t have for example Bitwarden, Ublock Origin, Sponsorblock, and such mandatory extensions?

    Users follow extensions and ease of use; not what’s good for them.

    E2: A good project would be a builder extension for VSC for example, which compiles to all supported browsers.

    Browser devs would then contribute to said extension via native-made plugins.

    Cooperation of two fronts.


  • dog@suppo.fiOPtoLinux@lemmy.mlLooking to migrate
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Could you elaborate a bit?

    Isn’t Proxmox etc. “Gpu less”, as they only use tty instead of anything like a WM or DE?

    I’d prefer a “master” / hypervisor running a bunch of VM’s for different purposes.

    Whether they be for gaming, pirating, development, pen testing, home automation, porn, or anything else really.

    'Course I’d only be running gpu passthrough into a single VM at a time, can’t split a single GPU into 50 passthroughs yet.


  • dog@suppo.fiOPtoLinux@lemmy.mlLooking to migrate
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    iGPU shares one monitor with the dGPU, but on different protocol, which from what I read online is supported.

    It only really needs output when I flick it open.

    So maybe it needs a KVM switch instead of trusting the monitors splits.





  • dog@suppo.fiOPtoLinux@lemmy.mlLooking to migrate
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    Scenario 1. X11 “works”, wayland doesn’t. Trying to update NVIDIA drivers leads to boot failure.

    Scenario 2. Wayland works. Only on igpu. Only via HDMI. Only on one monitor.

    Scenario 3. Wayland works on Displayport. Doesn’t even recognize second monitor.

    Scenario 4. Everything seems to work. Trying to do GPU passthrough fails.

    Scenario 5. IGPU is hogging displayport, despite being connected via HDMI, thus preventing the DGPU passthrough on either HDMI or DP.






  • I was thinking it’s only spam servers, but it might actually just be downtime for hetzner or something.

    Instances do not get banned on lemmy. You can run any kind of an instance.

    That said, part of this could be providers pruning “fake customers”, aka spammers, scammers, etc, who “paid” for their servers with stolen CC and SSN.

    Edit: Someone up to making an uptime map for Lemmy, placing servers on a map based on where they report originating at? This could help seeing if a specific datacenter has downtime.



  • Hashing on client side is both more private, and secure. All the user ever submits is a combined hash (auth/pubkey) of their username + password.

    If the server has that hash? Check the DB if it requires 2FA, and if the user sent a challenge response. If not, fail the login.

    Registering is pretty much the same. User submits hash, server checks DB against it, fail if exists.

    Edit: If data is also encrypted properly in the DB, it doesn’t even matter if the entire DB is completely public, leaked, or secured on their own servers.