I noticed requests that were exploiting the vulnerability were turning into timeouts pretty much immediately after rolling out the patch. I’m surprised it took so long for it to be announced.
I’ve also done a noctua fan replacement on my ups. My worry is that they are rated for lower airflow than the original fans they replaced. Have you checked whether it stays cool when running on battery?
It's a permanent double conversion UPS; it's always inverting. You could activate the "high efficiency" bypass mode to directly connect the input to the output in the presence of mains AC input, but this would also pass through disturbances like fluctuations, harmonics, and surges, so I don't have it enabled. This wastes about 80W in my setup but whatever. I'm not worried about the inverter temperature is the point I'm trying to make; but I was considering this when I did it, which is why they're wired to run at full speed all the time.
I had the same thought, and looked specifically for this in the paper. They do have a section where they talk about fine tuning with “cold” versions of the responses and comparing it with the fine tuned “warm” versions. They found that the “cold” fine tune performed as good or better than the base model, while the warm version performed worse.
But the author doesn’t give a single example, and so there’s nothing someone else can do to explain why or continue the conversation. The best we got use that he has a vague sense of unease, which I don’t think is very useful.
I think the facilities for building larger applications are lacking in APL. It would be great as something embedded into other languages. Consider something like numpy’s einsum, but using apl expressions instead. Use APL to express what it’s good at, and use the facilities of the host language to put together bigger systems.
Large parts of Sweden's health system run on APL; Deutsche Bank also uses lots of APL; Denkmark has an appreciable number of companies using APL. IMHO, the problem isn't the scalability of APL (Dyalog, specifically) but more that good, maintainable, solid APL violates what the industry holds up as Best Practices etc. Trying to apply typical software architecture methodologies to APL definitely evokes the feeling you describe.
However, APL in my experience enables radical simplicity for building large applications. Learning to leverage that means that you need to first unlearn lots of ingrained problem-solving habits and ways of thinking as a software engineer. It's admittedly a steep hill to climb.
I bought one of these to play with xcp-ng, but I didn’t do enough research or I’d have known that there’s problems with jasper lake, and they won’t have a working release till end of year.
This is neat. I had a similar idea of tracking what we read online in the browser. In addition to just recording time spent and links followed, I would also archive every article read to automatically build up a personal library of the articles themselves. Additionally, light weight note taking on the articles themselves ala hypothe.is
Unfortunately a new baby has drained all my time for such pursuits.
So right now, the Chrome Extension tracks all link clicks as well so the visualisation actually builds relationships between articles/ blogs/ anything else you read on the internet.
I also had another idea that once we build our Knowledge Maps, we should be able to compare and share it will one another.
For instance, I'd love to see what our software engineers around my age/ experience are reading and the insights they are drawing from articles.
Obviously some sort of security/ privacy mechanism will need to be implemented as well.