They need to train an LLM with the windows source code and ask it to write an windows clone.
Apparently copyright law only applies for humans, generative AI gets away with stealing because there is too much monetary interest involved in looking the other way.
I've been mounting my 3.5" hard drives on those "fad" rubber band 5.25" drive bay adapters for decades and have not noticed any increased failure rate at all. Sure, seek time may be worse, but the reduced noise has been worth it for me.
The problem isn't just slower seeks; it's when vibration causes the head to go off-track and write data where it shouldn't, faster than the servo can correct. Track pitch in modern hard drives is only a few dozen nanometers.
Not OP, but I installed a "Balcony solar" 1.4kWp panels 2.4kWh battery system on my parents garage. The only subsidy was the tax free purchase of the components (we did file for an additional tax break with the city, but they had already run out of funds for that because it is so popular). You also save a lot of money on installation costs.
Cost breakdown:
- 400 EUR 2.4kWh 48V battery
- 320 EUR 4x 360W solar panels
- 200 EUR 800W microinverter
- ~200 EUR for helping hands when getting the panels onto the flat roof
- 160 EUR flat roof mounting equipment
- 153 EUR solar cable, connectors and crimping tool
- 115 EUR MPPT charge controller and cables
- 95 EUR electrics (e.g. fuses, dc/dc converter for OpenDTU)
- 50 EUR other assorted costs
So about 1693 EUR in total.
Total yield after 1.3 years: 1715 kWh (including power fed back into the grid)
Of that, discharged from battery: 488 kWh (battery already paid back ~146 EUR)
At the current energy costs, 1715 kWh would be ~514 EUR imported from grid
> you are recommended to get the shingles vaccine instead of the chickenpox vaccine since the way the disease presents and how the body reacts to it changes with age (technically shingles can happen at any age but generally herpes zoster presents as shingles instead of chickenpox the older you get).
If the underlying virus is the same, what is different between the vaccines? How it presents shouldn't matter as much?
The shingles vaccine is a larger/more aggressive dose than the chickenpox vaccine.
And nowadays chickenpox vaccine uses live attenuated viruses (i.e. modified to be non-infectious but still look the same) whereas the shingles vaccine uses recombinant proteins. This allows the shingles vaccine to deliver the higher viral load that they want for inoculating against shingles without putting a bunch of live viruses into the body.
It's also worth noting that the recombinant vaccine is more effective for shingles compared to the equivalent viral load live vaccine by a significant margin. It's something like 90% reduction in incidence vs 50%.
----------
> How it presents shouldn't matter as much?
It's not an all or nothing thing but it's a matter of percentages.
And the big reason why they present differently is that chickenpox kind of attacks every part of the body since it's new. It of course does best at infecting the skin and nerves but it mildly affects every part of the body. But then it goes dormant in the nerves because that's where it's most "compatible" and the body is the worst at fighting it.
So then with shingles your body still has the immunity but the reactivated virus is able to out-compete your immunity in the nerves and it wakes up in whatever specific nerve and spreads along that nerve. This is why shingles generally presents in a band on the body. It's spreading along a specific nerve "line" rather than spreading throughout the whole body, blood, and all.
And so the because the infection can't spread broadly throughout your body it ends up concentrated in that location and presumably the higher viral load combined with focusing on the specific proteins rather than the whole virus increases the body's sensitivity to these flair ups, catching them before they can reach momentum. And then that focused immune training sits on top of the body's existing immunity for the initial "whole body" presentation of the virus.
BTW looking at the 8051 patch bytes, they look like 8051 code to me. 0x02 is the ljmp opcode, so this is a jump table: 0x02, 0x40, 0x58, 0x02, 0x40, 0x4e, 0x02, 0x44, 0x00, 0x02, 0x42, 0x2b, 0x02, 0x41, 0x82
I poked at a vsc73xx-based switch in the past and wrote my own test firmware, but had problems with packet loss since I didn't do all the necessary phy initializations I guess, in case this might be of interest:
https://github.com/ranma/openvsc73xx/blob/master/example/pay...
Also on the device I had the EEPROM was tiny and the code is loaded from EEPROM into RAM, you were pretty much stuck with 8051 assembly that had to fit into the 8KiB of onchip RAM :)
Those addresses all make sense, as 0x4000 - 4fff appears to be where the 8051 has its RAM mapped (all of the peek/poke addresses used for accessing serdes fields are on the high end)
I have the ST one (X-NUCLEO-LPM01A), but its range is actually not enough for something like an ESP32, it goes into "overload" as the max current is 50mA for dynamic (100kHz bandwith) and 200mA for "static" measurements.
The partition table listing from the microSD card shown in the video (before installing a custom u-boot/Linux) shows partitions marked as the Linux partition type at least.
The amount of power you can dump for balancing is just a fraction of the charge/discharge power (because it only needs to offset differences in self-discharge rate). So you still need a proper dummy load when you want to dump more.
Similarly, the heatsinking capacity of the battery is designed for charging/discharging losses (say 5% of charge/discharge power).
> Since there's no point in generating keys for a device which will not be used in Japan, non-Japan SKUs don't have Osaifu-Keitai functionality. So even if you rooted your phone and had full access to the secure element, if your phone's secure element doesn't have the key, you can't use it as an IC card.
At least in some cases it is sufficient to change the phone SKU id (which requires temporary rooting) to the Japan SKU id to unlock the Osaifu-Keitai functionality on a non-Japan phone. I'm not sure if this means that the secure element had the necessary keys provisioned all along, or just that the Osaifu-Keitai app then provisions it on first use.
I believe it is the case that US (at least) iPhones work as IC cards in Japan
Source - I’m sitting in Kyoto right now having travelled all over Tokyo and then on to Kyoto using only my phone to interact with Japan Rail. Verified with two 16Es and a 12. In fact we were able to add the Suica cards to our phones and charge them fromApplePay while still stateside. That let us skip the Welcome Suica line at Haneda and go straight to the monorail. Highly recommended
A broadly supported tap-to-pay fare system is such an underrated accessibility win for public transit when traveling.
Many tourists already get intimidated by language barriers and inscrutable timetables and transit routes; add tariff complexity (and the chance of getting charged with fare evasion!), and many just end up taking a taxi.
With these stored-value systems, you pretty much don't have to ever worry about doing anything wrong as long as you properly tapped in (and have the necessary cash to top up the card at the exit turnstile if you ended up "overdrafting" your card).
Now the remaining complexity is learning about and getting the card in the first place, and Apple Wallet really does an amazing job there in Japan. Not even having to install an app or create any account is absolutely amazing.
Not sure if it's still the case, but last year I could only top up with my AmericanExpress in Apple Wallet. Neither Visa nor MasterCard worked. This was a widespread issue at the time.
Yes, all iPhones and Apple Watches carry the functionality regardless of where you buy them, which has been wonderful for me. The fact that the iOS Wallet app can generate these cards as needed and reload them without a third party app is a cherry on top — so nice to for once get a standardized UI instead of having to deal with some half baked transit service app.
I believe Google is trying to do that with their Wallet/Pay/Wallet app, but I guess it doesn’t support FeliCa yet? They do support some weird card formats, so I guess they have at least some flexibility there – no idea why they can’t add it, too.
