• 0 Posts
  • 48 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle


  • rekabis@lemmy.catoLinux@lemmy.mlProjects To Watch Out For: Ladybird Browser
    link
    fedilink
    arrow-up
    19
    arrow-down
    6
    ·
    edit-2
    30 days ago

    We don’t have anyone actively working on Windows support, and there are considerable changes required to make it work well outside a Unix-like environment.

    We would like to do Windows eventually, but it’s not a priority at the moment.

    This is how you make “critical mass” adoption that much more difficult.

    As much as I love Linux, if you are creating a program to be used by everyone and anyone, you achieve adoption inertia and public consciousness penetration by focusing on the largest platform first. And at 72% market share, that would be Windows.

    I hope this initiative works. I really do. But intentionally ignoring three-quarters of the market is tantamount to breaking at least one leg before the starting gate even opens. This browser is likely to be relegated to being a highly niche and special-interest-only browser with minuscule adoption numbers, which means it will be virtually ignored by web developers and web policy makers.


  • Any brands protected by American law must be independently-owned, with full transfer of all branding, patents, trade secrets, intellectual assets and physical assets.

    So, for example, for even a single bottle of Perrier to be sold in America, it needs to have been made by a company registered with the brand name of Perrier, with exclusive use of that name within the country, independently owned and under zero control by Nestle, being manufactured using the exact same process with the exact same ingredients, and having control of the exact same patents and American-side infrastructure.

    America is such a large marketplace that it would be impossible to split a company like this. Patents alone would prevent this, forcing Nestle to divest themselves of each individual subsidiary.




  • What makes the built-in database easier to attack than a separate one?

    For performance reasons, early versions weren’t even encrypted, and later versions were encrypted with easily-cracked encryption. Most malware broke the encryption on the password DB using the user’s own hardware resources before it was even uploaded to the mothership. And not everyone has skookum GPUs, so that bit was particularly damning.

    Plus, the built-in password managers operated within the context of the browser to do things like auto-fill, which meant only the browser needed to be compromised in order to expose the password DB.

    Modern password managers like BitWarden can be configured with truly crazy levels of encryption, such that it would be very difficult for even nation-states to break into a backed-up or offline vault.






  • rekabis@lemmy.catoTechnology@lemmy.worldDesk read error occurred.
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    running it in an ssd is it can speed it up

    Let me be absolutely clear: due to the finite write capabilities of solid-state technology, using SpinRite on an SSD is materially harmful to that SSD, and WILL shorten it’s operational lifespan by a non-trivial amount.

    This is why SSDs have wear-levelling technology: to limit the number of writes that any one data cell will receive. By using a program that conducts intensive read/write operations on sectors, you are wearing your SSD out at a much higher rate than normal, dramatically speeding up any failures in the future.



  • rekabis@lemmy.catoTechnology@lemmy.worldDesk read error occurred.
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    3 months ago

    SpinRite is only meant for traditional “spinning-rust” mechanical drives.

    SpinRite IS NOT meant for SSDs. The existence of TRIM makes SpinRite useless on any sort of solid state storage.

    And since almost all laptops sold within the last half a decade use SSDs almost exclusively, it is highly unlikely your advice will be useful.






  • I am also supremely space-constrained, but I also had no need to take my development device away from my desk. So I got a workstation and a KVM to switch between workstations, thereby needing only one keyboard, mouse, and set of monitors for multiple computers.

    I went further than that, because I also needed to keep the desktop largely clear and the floor space used down to an absolute minimum. So I got a 60s “tanker desk”, and put a smaller office table on top of it. the computers all sit on top of the office table, up near the ceiling (and away from a lot of the dust!) and the monitors and KVM dangle down from beneath it. This leaves only the two pedestal legs of that office table and my keyboard and mouse as the only things “on” the top surface of my desk.

    And ignoring the chair, I can have four workstations and six monitors within a 30×60 inch footprint (the tanker desk).