Sorry, I can't hear you under my enormous piles of money! π
But yeah. You should do an SSD-only setup if this is within your budget. I assume that for most of us selfhosting is just some soft of hobby. If you're willing to spend money on the latest and cooles tech: do it. If not, then it's fine, too.
If you say "harddrive" ... do you mean actual harddrives or are you using it synonymous with "storage"? If you really talk about actual harddrives, it's hard to even find datacenter/server harddrives below 4 TB. Usually server HDDs start with 8 or 12 TB. You can even find HDDs with 20 TB - Seagate Exos series for example, starting at around 360 Euros (ca. 400 USD).
If you're in for a general storage, preferably SSD, that's another issue. There is the Samsung 870 QVO (8 TB) SSD that is often advertised as "datacenter SSD" (so I assume it would run well in a server that is active 24/7), but it is currently available with a maximum of 8 TB. The 870 QVO is at ca. 70 Euros per terabyte (ca. 77 USD) which, in my experience, is the current price range for SSDs. So it has a high price seen from the outside but it's actually fine. It's also a one-time investment.
For selfhosting I'd go with an SSD-only setup.
do any have particularly good or bad reputation?
From personal experience I'd say, stick with the "larger" brands like Samsung or Seagate.
XUL was HORRIBLE to write, implement, and debug. Been there, done that. It was also 0% portable.
WebExtensions (even if there are some technical limitations and some browser manufacturers decided to intentionally cripple some of the APIs) are in general so much better. You have proper toolchains for development, translations, testing, and publishing. And it is pretty much portable to all browsers. You don't even have to port anything 99% of the time because it's just compatible.
It first checks if ~/.bashrc.d is an existing directory. If this it the case it then iterates over all entries in that directory. In this iteration it checks if the entry is a file and if this is the case it sources that file using the bash-internal shorthand . for source.
So it basically executes all scripts in ~/.bashrc.d. This makes it possible for you to split your bash configuration into multiple files. This quite common and a lot of programs already support it (100% depends on the program, though).
This is absolutely harmless as it is. But: if you or a program places anything in the directory ~/.bashrc.d it WILL be sourced everytime you start a bash.
A slightly better variant would be iterating over ~/.bashrc.d/*.sh instead of just ~/.bashrc.d/* to make sure to only grab files with the .sh suffix (even if suffixes are basically meaningless from a technical point of view) and also test for the file being executable (-x instead of -f).
This would make sure that only files that are ending with .sh and that are executable are sourced. The βattack vectorβ, if you want to call it like that, would then be a bit more narrow than just placing a file in a directory.
As for why itβs there: Did you ever touch your .bashrc? If not, maybe it is there since the beginning because itβs in the so-called skeleton (see /etc/skel/.bashrc) that was used to initialize certain files on user account creation.
Even back in 2023 this was all old stuff β¦ NFT scam was a big thing in 2021 and the crypto hype was a thing around 2013-2018. Itβs both still there, but no-one really cares anymore as far as I can tell.
so Iβm hoping the same holds true when the next AI winter sets in.
They are already sinking millions into the AI hype :(
Make sure that, whatever switch you want to get, the switch supports simulating output (edit simulation/storing) and USB devices. Otherwise every switching action would cause disconnect and connect actions on the hosts.
Any other βgotchasβ that you guys have encountered on mobile FF?
Not specific to Lemmy, but I was ... impressed ... that it is impossible to set a custom homepage in the browser. Something that is possible since 15+ years in every mobile browser I used.
Sorry, I can't hear you under my enormous piles of money! π
But yeah. You should do an SSD-only setup if this is within your budget. I assume that for most of us selfhosting is just some soft of hobby. If you're willing to spend money on the latest and cooles tech: do it. If not, then it's fine, too.