A dual 3090 system shouldn't go above 600W wall power while running inference, even less with some weights in RAM as you need to do with "only" 48GB VRAM and this model. Unless you are running water cooling, the cards are likely sitting at 200-250W power limit each anyway so they don't run too hot. This is considering a consumer tier CPU and mainboard with about 90W TDP, not a dual CPU or something like a threadripper that can easily push the power draw to 1kw if it runs the calculations on the RAM weights. My dual 3090 setup usually drew about 200W-300W average with LLM workloads according to my HA historical data.
I have a "Homatics Box R 4K Plus" with CoreELEC/Kodi installed. The UX is then determined by your Kodi skin or apps. I wouldn't exactly recommend that box for ease of installation, but it works. It only needed to boot once into Android, annoyingly requiring an internet connection for setup. Since then it only runs CoreELEC. Works via HDMI CEC via the TV remote, which is still a bit annoying, because they had space for a dozen branded streaming provider buttons, but pause/forward etc. are on a mode switch button that overloads the navigation buttons.
Overall I am pretty happy with Kodi on my Android box. 90% of the content is streamed from a local Jellyfin server, so I can't comment on how well it works with DRM media. It occasionally [1] seems to hang, requiring a power reset. The next time it does, I will hook it up to a smart plug to simplify that as well. If you are into tinkering, CoreELEC is based on Linux and you have some basic tools already installed with more available from the addon repos. I have SSHed into LibreELEC to debug network issues with iperf and on a previous iteration to kick over Kodi with systemctl restart.
[1] gonna say less than once a month, I don't remember when it last happened
I intentionally avoid this, especially if I am not the only one connecting to a server. I see potentially breaking others' expectations for my convenience as a clear downside. Plus there is a level of paranoia there, I might have unintentionally included a credential in some config that gets copied over. That potentially increases the blast radius of a server compromise beyond what is strictly required for that specific server. I might copy over some scripts into a directory not in $PATH, easy enough to add it to my shell session if needed, CTRL+R helps as well.
...why are you sharing user accounts in this day and age? Yes, absolutely, don't mess up the shared space everyone uses, but why are you sharing that space in the first place?
Chris just has some fun projects. Sandsifter was pretty well known back then due to finding that VIA x86 opcode, the movfuscator is just an amazing piece of mostly useless engineering and the fun reverse engineering psychological warfare was my first contact with his projects. I guess someone stumbled on one of his projects and others clicked through to his other projects. Many of them are a perfect fit for HN, no wonder they got posted.
I get that argument, but I don't think it is that bad. Open weights that are out of reach for local use are still within reach for groups of people or small to medium companies. Even if you only rent enough cloud GPUs to run the weights for a few hours, you still get to do anything you want with it.
Worst case you can still archive the weights and hope for capable hardware to get affordable. At the same time this archive is the base line for a new frontier lab to start over if required. I see open weights as a pure upside even though I can't run the bigger models in my home lab.
Article is missing a note on the existence of MX records for the domains. Sure, you can easily have a send-only domain without an MX record, but the common case is likely to setup both send and receive capability. It would be interesting to have that number included as domains without MX and DMARC might just not be configured for email at all. Worst case the 45% of domains without DMARC are simply not relevant for email and thus not configured at all. I would find "x% of domains with configured email don't enforce DMARC" more interesting.