• 0 Posts
  • 25 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
    3 months 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.




  • His router is tri-band though meaning it has 2 5ghz transceivers.

    Unfortunately, for many models - like the Linksys WRT 3200ACM - that second antenna (technically the third one if you include the 2.4Ghz one) doesn’t function at all without the manufacturer’s firmware. It’s a dead stick with any third-party firmware, and is 100% software-enabled.

    I have found this fact to be reliable whether it is DD-WRT or OpenWRT, and across several different manufacturers including Asus and D-Link.


  • The hardware to read the tapes are calibrated to the maximum size they are configured to accept. So when you hit up eBay, you will need to know the maximum amount of data you will need, and either the size of the largest tape drive to hold all that - if you are not getting a machine with an auto-loader - or the maximum number of drives that the machine’s autoloader can take, so you can size the tapes properly for the data.

    Say you need to back up 25Tb. You are unlikely to ever need more backup than that. So you either look for a machine that takes 25Tb tapes, or you get a machine that can take max. 5Tb tapes, but has an autoloader that can hold at least 4 additional tapes (in addition to the one in the drive) such that all five will automagically cycle through the backup process. That way, all 25Tb will be backed up in either case without your direct and immediate involvement, all you have to do is rotate the tapes off-site after the backups are done, and slot the next ones in for the next backup run.

    Obviously, incremental backups are a no-go, as backups are stored off-site. So it’s an all-or-nothing process. And as such, this is usually done both on your entire primary data set (for fast total-disaster restores) once in a while, with a different set of tapes focusing on your local/on-site warm backups and backing up only the atomic/incremental locally-stored backups for the day/week/month.


  • If you want longevity and shelf stability, tape drives are the way to go. You can get them in very large capacities, even into the hundreds of TB.

    Their benefit is that they have no internal motorized components, they are a lot like VHS videocassettes - two spools with tape. This makes them very shelf-stable, unlike hard drives which can have their spindles seize up over time.

    They also have absolutely epic data densities. You could store on one tape the contents of dozens of the largest hard drives currently available.

    Their downside is that you need highly specialized hardware to read and record them. And this makes the hardware quite expensive.

    So why don’t we use tape drives to store data? Because they store said data linearly - great for writing once, terrible for finding or updating said data - and because they are slow. You want to get to a file 20Tb in? Enjoy scrolling past every single byte up until that point.

    But for cold backups, there ain’t nothing better.


  • Our civilization demands that I be profitable to a parasite who leeches a majority of my labour’s value in order to accumulate obscene levels of wealth.

    Without exorbitant amounts of time spent maintaining that profitability, I will end up poor, homeless, and eventually dead from exposure. This leaves vanishingly little time to spend on open source work, regardless of how intellectually and ethically attractive it may be.


  • 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).


  • If you are looking for Bar, it is highly likely that you are already looking specifically for a particular functionality - say, the action - for Bar. As such, it is irrelevant which method you use, both will get you to the function you need.

    Conversely, while it is likely you will want to look up all items that implement a particular functionality, it is much less likely you are going to ever need a complete listing of all functionality that an item employs; you will be targeting only one functionality for that item and will have that one functionality as the primary and concrete focus. Ergo, functionality comes first, followed by what item has that functionality.







  • Fail2ban bans after 1 attempt for a year.

    Fail2ban yes; one year, however, is IMO a bit excessive.

    Most ISP IP assignments do tend to linger - even with DHCP the same IP will be re-assigned to the same gateway router for quite a number of sequential times - but most IPs do eventually change within a few months. I personally use 3 months as a happy medium for any blacklist I run. Most dynamic IPs don’t last this long, almost all attackers will rotate through IPs pretty quickly anyhow, and if you run a public service (website, etc.), blocking for an entire year may inadvertently catch legitimate visitors.

    Plus, you also have to consider the load such a large blocklist will have on your system, if most entries no longer represent legitimate threat actors, you’ll only bog down your system by keeping them in there.

    Fail2ban can be configured to allow initial issues to cycle back out quicker, while blocking known repeat offenders for a much longer time period. This is useful in keeping block lists shorter and less resource-intensive to parse.




  • A strangely effective option for young whippersnappers who want to maximize employability and income stream in “boring” tech. You’re not gonna be standing up many greenfield projects using that language - and likely speaking, you might go an entire career without ever touching a codebase younger than you are - but if your passions run towards Janitorial/Plumbing work with regards to code, it might be right up your alley.


  • DotNet is closest to Java, but hang on to your hat: the state of C# is at least half a decade ahead of Java, if not a full decade. It’s sophistication will make Java use feel like banging rocks together. DotNet Core can now run on all three primary platforms, and with some careful work, you can write a single program that can compile down to each platform and carry along its own required binaries, no pre-install of any framework needed.

    My second recommendation would be Rust. Stupidly steep learning curve, but an absolutely game-changing one where safety and security is concerned. It’s my next objective, personally speaking.

    Any other language I could recommend starts getting into speciality purposes, which makes general use more difficult or even wholly inappropriate.

    For example, if you are dropping into DotNet for business applications, I would also recommend diving into F# for that functional goodness for building complex business rules and data handling. But building an entire app in F# can be jamming a round peg into a square hole under many circumstances, it’s appropriateness envelope does not cover as many cases as C# does. You want to use C# for boilerplate/frameworks, F# for the core bits where it is going to shine.