Jhsto

Not OP, but what is much simpler is buying a motherboard with IPMI and placing that behind a VPN. If you cannot afford the couple hundred extra bucks for the motherboard, then a USB stick with minimal Linux setup + SSH and then doing a kexec from that is another option.

Nix-based PXE booting. It can boot different images than your NixOS-based system configurations, but the main focus has been to support NixOS. We even have a system which is able to scan your hardware pre-boot, and then launch the initial ramdisk with a kernel which has all the required drivers pre-installed. https://github.com/majbacka-labs/nixos.fi

Another note, NixOS containers with systemd-nspawn cpmpatibility: https://nixos.wiki/wiki/NixOS_Containers

There is a good blog post here about how these work: https://www.tweag.io/blog/2020-07-31-nixos-flakes/

And of course, it is just a tarball, so it works on every systemd based distro.

Photoprism for photos. Plex for music, movies, and series. Invoices I file physically. For messaging I plan to move to Matrix such that my homeserver runs "bridges" for other platforms so that I can later on export and query messages. For emails I use notmuch.

If you want to roll your own there is a mail client I have been using called himalaya which exposes JSON endpoint for mail stuff. It could be used to write a mailing list feature.

I would not underestimate the how shortsighted people are -- most of my peers are PhD students and most of them skip meals. Anecdotally, none of my flatmates eat breakfast, and my office mates often skip lunch and/or dinner because they have a meeting. The food offered at the university is a steal for the price and how convenient it is. These people are not out of money, they are (work) sprinting.

I feel like the best mobile plan insofar for traveling has been Google Fi: $10/GB anywhere in the world, allows you to pause service and pay nothing, works both as a physical and eSIM card.

The downside: only available for purchase in the US.

In a perfect world some of the development could happen in nix-community repos which are usually a bit more topic specific. The packages and modules would "move up" to nixpkgs on tag releases. This is how I initially thought the repos work anyway, but now I see that most of them just live as overlays and never quite sync up with the main repo.

One of the awful things about the subtitles is that series episodes wont be released before the subtitles are done. This might introduce a couple day lag to release window -- and at that time all the discussion online has already happened.

The reason that zkSync and Starknet are targeted is that neither have run an "airdrop" or token distribution scheme, and both are rather well known projects in the scene. It's a bit pity for them.

Ethereum staking (the S in PoS) is similar that Lido has around 33% share: https://dune.com/hildobby/eth2-staking

Of the nodes that have the blockchain (which there are less than 6000) 50% is cloud hosted: https://ethernodes.org/network-types

Hurricane Electric gives out free ipv6 blocks that you can assign however you want.

I get an ipv6 for my phone through Wireguard that way.

It would have to predict the model numbers of the planes though: some newer ones I have been to (A350s) seem to have automagic dimming windows. Getting on flights with such windows is better even if you have to sit in the sun!

Only the combustion of the plant is the problem though - not the addictive parts of it: artificially created nicotine enjoys an open market globally. Tobacco is in a sense demonized due to the direct idea that it’s combusted — nicotine pouches are legal everywhere in the EU but the ones with tobacco are banned sans Sweden.

Nicotine pouches were first sold in year 2008 according to Wikipedia.

> Less familiar with how European sensitive networks are architected.

Some governments have physical tunnel networks to move people who matter around. Computer networks follow pretty much without a loss of generality.

It should be noted that for Europeans other alternatives exist, as you can freely shop any EU country to incorporate a business. Many of my tech friends have set a company in Estonia for tax planning once they have hit a certain revenue (and 0% corporate income tax).

Anecdotally relevant to employees too: sometimes companies (and even public organizations like universities) let you keep the hardware they buy for you after it meets the 3 years depreciation rule.

Sounds like something to try in an internal network where you want to do X11 or Wayland application forwarding!

I recommend checking out your local teletext offerings and seeing if there are any translated into HTML. The teletext format is much more terse, and there is less hubris in general.

> suggests that (my flavor of tinnitus, at least) may be due to physical/muscle related causes

I have explosion-related tinnitus/hearing damage and it also reacts to muscle movements. So, it seems like they are the same.

I personally wen't this route last year and eventually got things working (networking etc. OK with only the kernel). My company then took a direction in which each compute node has its custom kernel, so that we can control the initial stages of boot better (initrd is dynamically downloaded from intranet, given that the network drivers are baked-in) to manage heterogeneous nodes with different "roles" (GPUs, add-on devices, etc.).

Something I have been surprised about is how much functionality exists in the Linux kernel and how much more reliable the modules are compared to many user-space tools (e.g. race-conditions).

The server space is quite nice with the ASRock Rack models: last month, I bought ROMED8-2T and got double 10G NIC and EPYC compatibility in ATX form factor. I also paid $100 extra for Intel NICs plus an USBC port. The motherboard cost 920 dollars though.

To accompany the other comment, your Nix cache can be hosted by setting `services.nix-serve.enable = true`: https://nixos.wiki/wiki/Binary_Cache

You do not necessarily need nginx.

This is actually quite common in Finnish, since there is no strict word ordering. Once you have figured out all the words and their agglutinations, you can put them in any order. Many phrases don't parse until you heard all of it.

Any idea when you could do an Intel or AMD device with coreboot?

One month was the worst point. It gets better from there until it's unnoticeable unless in a silent room. You will be surprised how the brain is able to both cancel out and then rebalance the sound input to normal (should your tinnitus be one-sided). Same goes for "cracks" that you might hear if the sounds are too loud -- they also go away in time.

I might as well note that anecdotally, barotrauma makes the tinnitus better temporarily. Maybe there is an explanation -- traumatic tinnitus can be at least alleviated by going into an overpressurization chamber immediately after the traumatic event. It seems like even after the fact, a pressure difference has temporary effect. For example, my tinnitus feels better after ascend on flights, even though in this case it's underpressure.

The best motivational video that I still think of after 10 years is this: https://youtu.be/eOU0JhkHY3w

GPU applications are often less buggy on LTS (kernel, but also package sets)

This seems like very useful for browsing NFS shares. Has networked filesystems been a part of the initial motivation?

Couple of thoughts:

> I've been thinking: would it be helpful if the care and maintenance of these compute environments wasn't left to each scientist but was instead aggregated (perhaps per-class or per-university)?

This is definitely something that Nix can abstract quite well. In my company we have [an infrastructure of computers](https://github.com/ponkila/homestaking-infra) that we manage with NixOS. We have gone over the system such that `cd` into a directory "conjures" the environment using devenv or direnv. We don't do anything too fancy yet, but we have a project commencing next month in which we start to also manage routers this way. We speculate that this will help us to do things such as follows: register new node, and it gets automatically imported by the router which establishes DNS entries and SSH keys for each user. The idea is that we could have different "views" of the infrastructure depending on the user which the router could control. For administrators, we have a separate UI created with React that pulls NixOS configuration declarations from a git repository (note: these don't have to be public) and shows how the nodes connect with each other. The UI is still under construction, but imagine this but now with more nodes: https://imgur.com/a/obBfRk0. We have this set up at https://homestakeros.com.

Depending on a project you are working on, you could then have a subset of the infrastructure be shown to the user and have things such as SSH aliases and other niceties set up on `cd` in. When you `cd` out, then your view is destroyed.

We have quite overengineered this approach -- we run the nodes from RAM. NixOS has the idea of "delete your darlings" which is having a temporary rootfs. We have gone the extra mile that we don't even store the OS on the computer, the computers boot via PXE and load the latest image from the router (though any HTTP server will do, I boot some from CloudFlare). We do this because it also forces the administrators to document changes that they do -- there is nothing worse than starting to call up people when theres is downtime and try to figure your way back up from what the mutations are. PXE booting establishes a working initial state for each node -- you just reboot the computer, and you are guaranteed to get into a working initial state. I'm personally big on this -- all my servers and even my laptop works like this. We upgrade servers by using kexec -- the NixOS configurations produce self-contained kexec scripts and ISO images for hypervisors (some stakeholders insist on running on Proxmox). I've suggested some kernel changes to NixOS which would allow boostrapping arbitrary size initial ramdisks, because otherwise you are limited to 2GB file size.

> We're setting these chemists up with conda in Ubuntu in WSL in a terminal whose startup command activates the conda environment. Not exactly setting them up for reproducibility if they ever move to a different laptop.

Python in specific is a PITA to setup with Nix, dream2nix etc., might help but it's definitely the hardest environment to set up of all languages I've tried -- even GPGPU environments are easier. Oftentimes, the only problem is not the packaging, but also the infrastructure used. For that, you could also publish the NixOS configurations and maybe distribute the kexec or ISO images.

A notable thing is that devenv also allows creation of containers from the devShell environment, which may further help your case. Researchers could reference docker images instead of insisting on everyone to use Nix.

In any case, I put some emails on my HN profile so we can also take the discussion off platform -- we are looking for test users for the holistic approach using PXE, and we are currently funded until Q3 next year.

A fair comment, I do not disagree. I do plan to one day do an `ls` command on the root Nix file so that the manual update to the root flake for both the inputs and the RSS feed would be redundant.