I don't live in Hawaii anymore, but when I last did and HELCO was still allowing homeowners to participate their home solar with a grid tie they had the following limitations: no matter what your balance of power production to consumption differential was, there was no discount for a base 'connection fee' - essentially the lease of the meter.

They would sell each household kWh at full price, and 'purchases' daytime production at a wholesale rate derived from a mainland commercial grid interconnect rate, the difference was about one order of magnitude, and their meter had the ability to cap output from the panels, such that no matter what the purchase price of excess power would never exceed the consumed power price, and every month there was at least $80ish in connection fee.

This kept most of my neighbors from either, a) considering solar for the household, or b) deciding to stay disconnected from the grid when the house finished installation.

My friends with new houses being built mauka (up-country) also faced a Many-KiloUSD per pole cost to run lines along the road to new housing areas, and if even you could get everyone on a road to pitch in for a new run it often was more economical for everyone to just DIY their own selection of solar, wind, generator, batteries and it still was less expensive than just running the lines, even before accounting for kWh costs.

Even in towns down closer to the coast, it still made more economic sense to use wind+solar and a batteries with a backup generator than to pay for HELCO's power... which also came in with such erratic voltage and irregular wave profiles that it routinely toasted anything sensitive, from refrigerators, televisions, washing machines, you name it... which careful reading of the manufacturer warranties shows that for most main brands they specifically exclude Hawaii from any guarantee of service or replacement.

Now, HECO services a different island than where I lived, and the situation is widely variable in each of the islands, with completely different rules and operating practices. So that's not to say my observations have any validity outside of Big Island, and some limited observation from friends' ohana in Maui.

When we lived in town, it was necessary to put UPS inline for everything more complicated than a toaster oven, and when we moved way up mauka to our little goat farm, the answer was solar and at first golf cart batteries, then a whole stack of recycled/reconditioned submarine iron core 1.2v cells and some very heavy duty cycle inverters; combined with extremely conservative electricity consumption: about 10~15 kWh per week.

One of the benefits of using all LED red lighting at night, and living at elevation to never need A/C, plus methane digester powered by goat waste for refrigeration and mostly using a rocket stove for cooking with guava wood. and no TV, no tower PC, hand crank wringer for laundry like most mainland peoples great-grandparents and line dry on the patio where the rain cant soak them and the wind might get them dry before too long. Its not an easy or soft way to live, but in many ways my wife and I wish we sere still there.

So, drawing the parallel, 'these are the new garbage' but 'old garbage became acceptable so we should accept the new garbage' as an argument in support of being a meat proxy for Markovian stochastic lossy compression-decompression chatbots is isn't very persuasive, especially among this community with a greater concentration of systems level programmers than the general population.

That being said, i think both chatbots and compilers have a specific level of utility; neither of them should have unrestricted access to production filesystems or networks. That way be dragons.

It seems like implementing a fancontrol tool, and perhaps making a one line edit to /etc/udev/rules.d/60-fan-control.rules so that the tool presets the content as a rule for udevadm to make it controllable for users without sudo.

That seems like it might work for your system, maybe for many laptops with similar firmware.

This 'closure' instead of engaging with the potential solution might not feel fun when you're proposing a band-aid.

However, instead of directing your conversation to the firmware developer, the comment used system76's github repository to directly speak to system76 customers, and try to shame the one developer into 'being motivated'

So, I can see the reasoning behind the closure as it has gone off the topic of reporting a bug, does not add details useful for improving development toward a fix of the bug, and proposes an assumed solution which would potentially add more noise to later responses from other users who attempted that solution whom it didn't help which has the potential to add more noise to the diagnostics process for this particular bug.

As you say, not a firmaware expert, and i understand the frustration at the lack of explanation from system76 in 'Hidden as off-topic' for your comment, but it's not deleted, anyone who want to read it can click the 'expand' button and read it.

Sorry that fan at "0"rpm and the heat spike from that seems to have cooked off your RAM, that really hurts. I would expect that system76 should honor the full extent of the warranty that came with your purchase, if that includes the RAM it would be simply inconvenient, not inconvenient and costly.

That has happened to me, not from this kind of firmware driven failure, but lots of time pushing systems to the limit of design has given me maybe too much experience with 'little puffs of blue smoke.'

If it's of any relevance, my experience going back 20+ years at this point makes me almost exclusively purchase Kingston RAM. Simply because I have had them honor a no-questions lifetime warranty for sticks of RAM. Even recovered from eWaste, physically damaged, off the floor. If it has the KVM number legible, I've had replacement sticks shipped to me for the cost of postage. Once even had them offer an option to upgrade from DDR to DDR2 as they didn't actually have much DDR "1" in stock, and it was better for me also at the time.

It makes me purchase new systems with a minimum of RAM installed, and then swap whatever brand it comes with for matched sets of Kingston after a basic functionality test on arrival.

I keep the original as fail-back for warranty / service.

Hope your new RAM is performant, and hope the udev solves the issue until the firmware gets fixed.

Have you identified the code changes which effect the solution?

Are those able to be integrated back with the firmware via a PR?

IFF those are possible, it would be most interesting to see what the maintainer(s) [Tim Ziegler (@tizcza), Jeremy Soller (@jackpot51)] responses are to a PR for fixing this.

Without trying to solve it via those channels, one probably cannot say whether this specific "snarky" post being hidden constitutes bad faith on the part of the company.

Thanks for the highlight, I read Okazaki's the first time about 2014/15 IIRC.

Another great read is "A Theory of Regularity Structures" - https://arxiv.org/pdf/1303.5113. by Martin Hairer.

It builds on his thesis, Comportement Asymptotique d’ ´Equations `a D´eriv´ees Partielles Stochastiques. - https://www.hairer.org/papers/these.pdf

The English language preprint from just prior to the French is at https://arxiv.org/pdf/math/0109115 "Exponential Mixing Properties of Stochastic PDEs Through Asymptotic Coupling" great, but I read them in revers order from publication and kind of prefer them in that order.

I cant disagree with the premise of the OC, however, there's a feel to Hairer's and Okasaki's insights and presentation that simply is not going to be reached via the lossy compression that is at the heart of LLM.

If that sets a high bar for who gets a PhD going forward, this would be a good thing.

You are right. It was Nokia buying Trolltech and getting the seats on the board of the KDE Free Qt Foundation in 2008 that I was not recalling properly. It's been a minute.

Thanks for catching my miss.

We can all continue to rely on the freedom aspect of Qt and KDE, the Foundation was ahead of the pack in protecting the openness through the risks of privatization.

TLDR; Its complicated. Open source communities have learned they need Institution/Foundation grade protection to keep IP from becoming commercial property in some cases. KVM won by having that realization earlier than most. There are very functional Enterprise tools for Xen which are AGPL but are behind a paid pre-compiled binary which discourages free-as-in-beer AND free-as-in-speech adoption. For anyone is willing to modify source and compile for themselves the tools are both kinds of free.

For the more 'all over the place version' here goes nothing:

I was in the thick of it over two decades ago. Avi (KVM's original coder) had very good insights and organizational wisdom. He started development when the virtualization hardware for intel/amd was already invented and that made virtualization possible as a normal linux kernel process. This is distinct from the Xen point-of-view which is about using the microkernel's abstraction as a separation of concerns, for several reasons including a basic security posture.

The 'sentiment' in regards to the risk of corporate vs true opensource was perhaps within the smaller community at the time and not highly visible outside of that community. It did however exist and later the changes in licensing for XenServer ultimately led to the fork of XCP-ng.

Other acquisitions about the same time which led to similar sentiment include:

Android's acquisition by Google just prior to the Citrix and Xen point in time, shortly after that MySQL was aquired by Sun which then got acquired by Oracle, leading to MariaDB.

The Qt framework acquired by Nokia, and mismanagement thereafter leading to the KDE Free Qt Foundation's origin.

Java/OpenJDK also went through the Sun to Oracle path which resulted in IP lawsuits against Google by Oracle for Java use on/in Android.

Another software suite which had been sponsored in a very cooperative way by Sun was OpenOffice.

Following the Oracle acquisition and on the heels of the aggressive licensing stance by Oracle in other software stacks motivated OpenOffice original core of developers to create TheDocumentFoundation and the libre-office fork to keep the development out from under Oracle's / Larry's corporate thumb.

Sun all but admitted that they had lost the necessary developer participation and market inertia by 'donating' (dumping) OpenOffice on the Apache Foundation.

We can perhaps agree that the donation didn't really get the community back together and reunite libre-office and OpenOffice in any meaningful way as the move put OO under the commercialize as you please Apache License vs LGPL/MPL,

So; this all establishes a theme of concern and developer communities tendency to a reaction to those concerns in the open source world in the 'several decades ago' time. Citrix as corporate owner of a significant part of the Xen ecosystem versus Red Hat's stewardship of KVM was part of the motive for decisions way back then, by my best recollection of the time.

The current AWS (arguably useful as a surrogate for the broader hyperscaler use case) approach is Nitro, which is KVM adjacent so for the sake of KVM vs Xen, and although AWS did stay in the Xen camp for quite a while (still offers Xen-on-Nitro for those who need it) I expect that the same reason applies - standard tooling and mainline support. Although Nitro does require some Amazon proprietary hardware to function.

I remember thinking at the time that if Xen had better stewardship it could have been a better contender for main kernel support, not instead of KVM, but as an also option. But the virtualization hardware was a big win for KVM and it took Xen a little bit to catch up with the PVH option.

Xen has remained solidly useful for virtualization in many places, including non-hyperscaler type use.

Xen Orchestra supports both XenServer or XCP-ng backends. While being technically open source it does have a a few features including backups which are paywalled in the precompiled binaries with a feature flag which prohibits free license users from accessing those functionalities.

The reluctance of users / enterprise customers to edit the source code to disable the 'check for paid/free license' and compiling clean binary appliance, and to do that for every update of the original source is their 'moat'.

While they are fully compliant with the AGPLv3 and can say "our stuff is open source", this satisfies only the strictest sense of the license. It doesn't supporting integration with most distributions' repositories. This ends up looking like a commercial product to most users look for personal to enterprise scale management front ends.

This 'moat' might not be expected to last with the arrival of code-monkey via agent. Enterprises previously opting not to maintain in-house code repos for management tools like this and just pay the 2k to 4k USD minimum entry cost for Xen Orchestra or similar are already starting to look at multiples of that in token subscription fees. As in-house code repositories become standard practice, why pay for both if the one will get you the other for the asking.

/thank_you_for_reading_my_TED-of-the-day

If that location is still not the US, then they also have no authority to enforce US regulations in that place... "you cannot have your cake and eat it" is the applicable condition.

If those officers seized devices in order to search them, the owner is under no obligation to facilitate a warrantless search, no matter how fervently the department promotes it's self serving rearrangement of the Constitution.

If the owner of the phone had wiped the device, on the plane or before takeoff would there be any presumption of guilt? No. And there is still no presumption of guilt.

One cannot be charged with destruction of evidence if there is no evidence that the evidence existed, and there is no basis for the current 'habit' or 'policy' of searching any device that they decide to because they have wished this to be legal.

If the person is a foreign national requesting permission for entry, there may be a basis for 'allow us or we don't have to let you in', but in the case of a US citizen, to be refused the right of free travel within the US, is simply wrong.

Shrieking "Think of the Childern" or any other vilification doesn't change what is right.

That being said; since the ones at the border aren't currently accountable to anyone but themselves, the solution is to wipe everything before transit, and reinstall and restore the data on the other side.

Barn Swallow (Hirundo rustica): Migrates and breeds across all EU territories from Southern to Northern Europe.

White Stork (Ciconia ciconia): Uses major European flyways crossing through virtually all EU nations during spring and autumn migration.

European Robin (Erithacus rubecula): Widespread resident and migrant present in every EU country.

Common Quail (Coturnix coturnix): A highly migratory ground bird breeding regularly in all EU member states.

Eurasian Blackcap (Sylvia atricapilla): A remarkably adaptable migratory songbird found traversing or breeding in every EU country.

Additional Widespread European Migrants:

Common Swift (Apus apus): Spends summers breeding in all EU nations before migrating to Sub-Saharan Africa.

Common Cuckoo (Cuculus canorus): A widespread brood parasite present across every EU country during the spring breeding season. <~ probably not the image one would want on a 5 Euro note.

Eurasian Skylark (Alauda arvensis): Moves dynamically across all EU borders, adapting via partial migration.

Song Thrush (Turdus philomelos): A migratory and resident songbird found throughout the entire European Union. <~ due to homonym in English for a medical condition. probably not the right image either.

Common Chiffchaff (Phylloscopus collybita): A highly migratory leaf warbler that breeds or passes through every EU state.

Many species of birds are HIGHLY migratory, spend some part of every year chasing weather that supports and provides food for them.

Some of these make round trips from the sub-Arctic to sub-Saharan climates every year. So a list of birds that is acceptable and not 'favoring' any one nation is an easy move. Choosing birds that actually are found in all 27 member nations is a great idea.

Even Malta and Cyprus see all ten of these species as they provide important migration stopovers in the Mediterranean during migration and a few of these species, the Quail even manages to have historically had breeding populations in both, as well as using the islands as key migratory stopovers.

Using birds on an Euro note can help draw public awareness to the ongoing need for cooperation among nations in the protections of a shared symbol of natural freedom, which migratory birds embody.

> XenSource got acquired by Citrix, who closely aligned with Microsoft in order to leverage the Xen commercialization against VMware ~ and the opensource community is hyper-aware of the long term damaging outcomes of these types of alliances with Redmond's powers for FUD.

> KVM's parent org. got acquired by Red Hat and that makes it more palatable for those same reasons.

> Hyperscalers who use KVM to manage multiple client VM instances on the same hardware via over-provisioning get to have kernel level insight into the KVM instances behavior via native, low-latency access to the hardware and direct integration with the Linux kernel's performance framework (perf) - this makes the noisy neighbor problem easier to mitigate than the same task on Xen which requires another layer of abstraction and has less out of the box native support choice of tools.

> KVM is/became a kernel module, and its development is now 'in-tree' for mainline kernel which also meant the kernel can perform the type-1 hypervisor activities using the standard Linux memory and hardware management toolkit. i.e. less maintenance

> there are more reasons, having to do with Xen pre-existing from the days when hardware didn't natively support virtualization and thus the need to modify the VM kernels to be PV (paravirtualized) - but putting KVM into mainline made the vanilla kernel hypervisor-aware as both host and guest

but mostly it's the first reason, and the rest sort of cascade from that one - the 'lack of support' from the standard tools developing opensource community is probably the largest reason.

Try: Ten year-old reproduces Georgetown University professors moth experiment in butterflies under remote instruction and parental supervision. Results demonstrate persistence of trained behaviour across generations, does not explore method of transmission.

Writes a long report and gets invited to entomology conference. The professor gets university support for attending international conference and follow up blog interviews.

Ten year old declines to pretend to want to become an entomologist. States a more financial minded goal of Veterinarian, instead.

TLDR; Science is Complicated, statistics are confusing, some publications that look like science have been paid for by the petrochemical industry to mislead the gullible, and climate instability has many reasons of which human activity is a significant contributor.

Here goes the long version :

There are many, many... very many regions in scientific understanding where one cannot simply 'run fully controlled laboratory experiments with only a single variable.'

These all require many minds working together to find the most probable cause-and-effect relationships, which may have a large number of co-related and unrelated contributory causes.

Most of applied medicine, materials science, ecosystems biology, sociology, ... the list really does go on to include just about every field that is not either very elementary kinetics or basic chemistry.

For example: The primary reason for most of the efforts in low temperature quantum computing is about removing as many exterior effects (thermodynamic chaos) on the very specific material interactions that are being used.

The application of a prismatic view: "we don't have a single-variable laboratory equivalent" to the realm of attempted scientific comprehension, can make it necessary to stop learning at about a 5th grade basic science level, and then set a worldview accordingly.

It might be inferred from the tone and content of linked interaction, not with a frontier-capability LLM model, but with the 'explain-a-thon two-thousand' which has been shimmed into the google search page, perhaps this is the worldview-building approach in use, and this post is seeking validation of that worldview in this forum.

This interaction does not in-fact demonstrate that an understanding of the scientific process has 'defeated' a weak-tea model's training data, nor does it demonstrate that there should be any significant measure of doubt that anthropogenic effect on climate instability exists.

Take strict note of the "significant measure of doubt" phrase, it is load bearing in all of science. If any reliable dataset introduces significant doubt into the scientific consensus, the scientific community (a.k.a the consensus) does reliably investigate and then shift toward explanations of observations which reduces the "significant measure of doubt."

That is the exact process which has been followed, and continues to be followed, to reach current scientific community's consensus in every field, including global climate instability, which was simplified in the press to read as "Global Warming."

Where reliable data is insufficient or false some corner cases appear in headlines about "reproduce-ability failure" and "ethical misconduct" in scientific publications. This is an outcome of many effects, many of which may be attributed to misalignment within institutional science resulting from 'publish-or-perish' stressors on research.

Another effect on the body of climate science publishing has been and continues to be been directed, unethical publications of disinformation funded by the groups who are financially incentivized to continue the mass consumption of petrochemical assets. These publications and the alleged scientists producing them are generally viewed as unprincipled when the financial mechanisms funding the unreliable research and those publications are exposed to public view.

This is similar to situations when tobacco companies contracted the creation of pseudo-science which presented as true various viewpoint from 'smoking is good for you', to 'smoking treats cancer' and later 'smoking doesn't increase your chances of being diagnosed with cancer.' These were conclusively debunked and some of the offending parties held accountable in various courts of law.

The petrochemical industry is in the nascent stages of this same route to accountability.

So, yes, "Science is Complicated" but there is not any significant doubt in the scientific communities' that increasing frequency and severity of weather instability in general and wildfires in particular are one outcome of conditions which have been impacted in a measurable quantity by human actions.

Anyone who is publishing to the contrary is very likely to be perpetuating a worldview that may be easier to understand, but that worldview is less likely to be accurate than the probability of finding several grand prize LOTTO tickets on the ground.

Might as well lean hard into the sub decimal percent market, while developing obvious defense sector flight control software.

The scene was Tokyo Disneyland at the time of the 2011 Tohoku earthquake. Shelter in place was a requirements, and there were school age and younger children who took refuge in a gift shop. As a help to keep the youngest children comforted through a scary time, the staff there took the initiative and let the children hold stuffed anials from the gift shop inventory.

Now, think about this from the US Disney Corp. viewpoint. They did what?? They gave away what amounted to pretty much the entire inventory of stuffed characters?

How fast would the manager taking that action be 'unhired' at L.A. or Florida?

But, this was Japan and things are different.

The managers have a cultural standard of hospitality and responsibility of care, even though this is a Retail Location, these children and parents are still guests in the venue.

The children and their parents also knew that these weren't "gifts" from Disney, but, without getting explicit or formal assent at the time of handing them out, everyone just understood that when the shelter in place period ended, the stuffed characters were to be returned.

Staff didn't even have to ask for them back, and the parents had managed childrens' expectations to prevent meltdowns when that happened.

All the children who needed some extra comforting in a stressful situation had a favorite character, and the Retail Location lost exactly zero product.

I could go on with many other intrinsic differences, but this one is a pretty clear example.

So, the US business realities neither were necessary nor appropriate in that situation.