Some parts of the website are explicitly login-only, yes. I sometimes tend to follow link to gh from my mail on phone where I'm not logged in and found that e.g. you can't see any CI results without logging in.
I was going to say that this is an unfortunate side-effect of how electricity is being priced in the market but I learned today that Iberian is not participating in the nordpool. Nordpool has this weird pricing model that pays every generator the price of the most expensive one that supplies the last watt of demand.
Regardless and despite this nordpool weirdness; with some rooftop & batteries I haven't been paying a cent for electricity outside of January so I don't need to care about prices in the market much at all.
I make a point to have my direct energy use be electric (e.g. for driving) so the recent jump in the pricing of molecules affects me relatively little. Unfortunately I don't have much say in indirect energy use (as used for food production) but I believe that people are rational and will figure they can do what I did sooner or later.
Senn HD 490 PRO is an amazing and extremely comfortable headphone that has very affordable 1st party replacement parts (pads, cables) to boot. These are the first ones I've been happy with from day one. But they are wired & open back.
The humanity has all the knowledge and tools it needs at this point to have anybody: individual persons, counties, countries, continents be much more self-sufficient in energy, in a way that makes economic (and all sorts of other) sense.
I am glad to personally be largely independent of molecule-sourced energy March to October. Hoping that the countries affected by oil instability take this as an opportunity to learn this lesson as well.
I got one from work that I don't use much outside of travel and haven't changed in any way past initial setup. It stays connected to WiFi and continuously broadcasts various discovery packets for the past month and a half since I last opened it up.
Its weird to read about Schneider Electric not bothering with brand awareness. They aren't a household brand, sure, but they are well up there with Siemens and the like in industrial/b2b sector and their marketing budget is allocated accordingly.
This superloop pattern can also appear in more abstract scenarios as well.
The wildly popular ESPHome is also driven by a superloop. On every iteration the main loop will call an update handler for each component which then is supposed to check if the timers have elapsed, if there is some data coming from a sensor, etc before doing actual work.
This pattern brings with it loads of pitfalls. No component ought to do more than a "tick" worth of work or they can start interfering with other components who expect to be updated at some baseline frequency. Taking too long in any one component can result in serial buffers overrunning in another component, for example.
In my homelab I've been using very barebones options (the one built into systemd-networkd as well as the dhcp server built into RouterOS) and never found myself needing a web interface, a database or anything… really. It has been sufficient to add the couple dozen static allocations to the configuration files and forget DHCP exists. Even HA is not something I found myself wanting as nodes will retain their lease well over the period of downtime incurred during botched upgrades.
How fancy does a network needs to be before this starts making sense? Who are the target audience for this project?
The title qualifies "Android TV" with a "Streaming Box" right after. Lots of service providers supply such a box to subscribers (similarly to how ISPs provide all-in-one firewall-router-modems.) Even then these are extremely cheaply made, underpowered and largely unmaintained internet connected devices. And indeed you can purchase one such box yourself (including with piracy features as described here,) but I'd be surprised if the vast majority of these devices aren't supplied by the service providers.
I would say that npm likely has easier solutions here compared to Cargo.
Well before the npm attacks were a thing, we within the Rust project, have discussed a lot of using wasm sandboxing for build-time code execution (and also precompiled wasm for procedural macros, but that's its own thing.) However the way build scripts are used in the Rust ecosystem makes it quite difficult enforce sandbox while also enabling packages to build foreign code (C, C++ invoke make, cmake, etc.) The sandbox could still expose methods to e.g. "run the C compiler" to the build scripts, but once that's done they have an arbitrary access to a very non-trivial piece of code running in a privileged environment.
Whereas for Javascript rarely does a package invoke anything but other javascript code during the build time. Introduce a stringent sandbox for that code (kinda deno style perhaps?) and a large majority of the packages are suddenly safe by default.
The options in the '70s were much different from those of today. And for France specifically what they have underground (lots of uranium, no oil, no gas & no coal) strongly suggested exactly one way forward.
Back when I had my own Xmonad config – during student years with too much time than I knew what to do with – the biggest benefit to Xmonad being a haskell program that I myself wrote was that it was a program that I myself wrote.
This meant that instead of e.g. spawning some utility on a media key input, the compositor could directly stay connected to the dbus and control mpdris clients directly.
The way I see xmonad in retrospective today is that it is/was a "make your own compositor" library much like wlroots, smithay, etc, but it came with enough of the batteries included in the package that spinning up a nice and productive environment took barely any code. Something you can't really do with wlroots or similar.
They already charge that and more if you have to check-in at the airport for any reason. And you cannot check-in online without making an account with them. Ryanair is grift squared.
That said I never had problems boarding with a PDF displayed on the phone screen. Unfortunate that they're going away.