"it was kind of inevitable once Poland stopped being oppressed by its neighbors"
No. Not at all inevitable. Poland might have descended into kleptocracy, e.g. Hungary. That this did not happen is worthy of investigation. I'm not holding my breath however; the findings would probably not be welcome.
"A general lack of ideological 'mind viruses' that seem to plague the western world"
Indeed. Poland frequently disappoints the rest of the EU with its stubborn indifference to obligatory Western moral panics.
Yes, Intel is actually competitive again. Between working backside power, the most advanced chiplet packaging tech going, 18A yields steadily improving, and other good news, Intel is really on plane. Now they've landed both SpaceX and Apple.
It's good to see. Guess they were worth saving. I do hope their abandonment of discrete desktop GPU is temporary.
Agreed. Right now, if I needed "workflow" for a greenfield that could tolerate some risk, I'd look at https://www.restate.dev/ which matches your model of a self contained binary.
There are a small number of such sites in the US. One that fits closely with this description is a legacy of the Manhattan Project: Coldwater Creek, MO. The Mallinckrodt Chemical Works refined a lot of uranium, and waste handling was about what you would expect given the prerogatives of the 1940's and the Cold War. They carried on refining for power plants after WW2.
Obviously, fuel refining hasn't just carried on like that, in the US and Europe at least. But it's one of many handy cudgels to use whenever folks get excited about nuclear.
It carried on until at least 1989, and the effects were present majorly until around 2000, and the superfund site was completed in 2006. So, like, pretty darn recent on the scale of a human lifetime.
Going in the opposite historical direction is the other side of that ledger. The actual plant in question was shut down in 1957. The AEC stepped in years earlier to triage the operation, after actually establishing formal exposure limits in 1950, which didn't exist prior to that point. Before that, the company itself had hired staff to control waste and detect contamination. They had to build their own survey equipment because there were no commercial tools available. The worst of the actual contamination was actually incurred prior to that; 1942-1945, when the gloves were entirely off building bombs.
The lessons have been learned. It's tragic and shameful history, but not terribly relevant to modern practice in nuclear power.
SIM farm is a different scenario and arguably not even illegal. This story is about scammers operating a DIY stingray that broadcasts phishing messages via SMS to nearby devices.
SIM farms are devices with a lot of SIM cards aka numbers used to scam/flood victims numbers after these were acquired through ad companies, purchased these numbers online, etc.
The OP ones are actively scanning the vicinity and acting like BTS to connect to phones automatically, equipped with radio antennas, SDR, etc. to gather the victims numbers in real time and send them spam/phishing while the phones are connected to to these BTS
The real story is the government didn’t really care about users being spammed, you get those all the times and there’s little regulation to protect you (like preventing corporate from selling your number etc.), they cared because with these devices people can and will communicate outside of the approved channels, that also might be encrypted too, so harsh charges and make it as public as possible to deter others from doing the same, even if they were not in it to scam or phish people, and notice on the emphasis on “blocking the 911 calls!!” so jamming charges are there too.
People I know in US telecom are not surprised by these SIM farms. These people are either:
a) Doing some weird grey market VoIP thing. 32-in-1 GSM to SIP gateways have been a thing for a very long time in the developing world. Maybe they think they found some arbitrage route for phone traffic to/from the US PSTN that they can profit from. Anyone who interacts with grey market voip stuff will recognize these things immediately.
b) Using them for something like receiving 2FA authentication codes to create bot/socketpuppet social media accounts. In this sort of scenario they'd have live phone numbers/service and the cheapest possible phone plan, and ability to receive incoming SMS. The accounts then get provided to some other group of people who are doing mass advertising/social media manipulation.
"Authentic" US domestic resident sockpuppets for political or social manipulation. Combined with things like using residential proxies/relays through traffic on compromised routers on top-10 sized US last mile broadband providers such as Comcast, RCN. Google "residential proxies for sale" for some examples.
Plenty of things like the various services run by Meta will treat your content differently if they know you're coming from a Bangladesh phone number and ISP vs. being what appears to be an authentic domestic USA human.
Having live US phone numbers that can receive SMS for "is a live human receiving this code" verification purposes is also useful for many other kinds directly fraudulent activities.
c) grey route outbound sms. Even cheap US plans tend to have 'unlimited' sms, sometimes even to selected foreign destinations. Sometimes carrier billed SMS is cheaper than aggregators (but not too often) or may have better routing to difficult destinations.
Yes, I can definitely see that being plausible, particularly if they've gone to the efforts to make software tooling to spread out the outbound SMS volume around many different SIM and self-rate limit their volume, to avoid getting cut off, rate limited, or account banned.
To point A: I remember a long while ago making a 'free VoIP' call and my call routed into a MetroPCS recording telling me my service was suspended for nonpayment. Hung up, redialed, number shot through another dodgy route.
"Law enforcement shrugs"? The whole focus of the article is about how the secret service confiscated those devices and charged the SIM farm operators with crimes. Which part of that is shrugging?
Espressif themselves do this for their own prerogatives. The ESP32-S3 MCU from this story actually has a small, low power RISC-V core that deals with several things, including "deep sleep" tasks. Many ESP32-S3 users are unaware that their dual core Xtensa device also includes a RISC-V core; it's just there, transparently doing Expressif stuff on a dedicated core, immune to whatever is going on with the fast cores.
> ESP32-S3 may be the worse model to run Rust on due to the XTensa cores that makes the toolchain unnecessarily complicated.
Indeed. ESP32-S31 appears to target exactly this concern in the popular "S3" segment. It's basically a updated S3, with faster and newer wireless and memory, and it adopts a pair of RISC-V cores in place of the Xtensa cores.
My brain broke a little when I read this. Today I learned the C stands for Core, and the S stands for Speed, or Strength, or maybe Superior. My working assumption that C meant RISC-V and S meant Xtensa was incorrect.
That's a widely shared misunderstanding. The letters are market segments.
The "S" segment is really popular. Despite the introduction of many Espressif RISC-V devices, one still sees lots of Xtensa S3 stuff. An excellent example is Unexpected Maker's line of ESP32-S3 boards.
ESP32-S31 is going to be a big hit, and RISC-V is only part of that. More GPIO are very welcome. The CLIC (core local interrupt control) is another subtle win that is lost in mainstream headlines: it provides Cortex NVIC level of interrupt management, enabling awesome things like RTIC work without compromise. I imagine using one of these with core 0 running plain old FreeRTOS handing Wi-Fi/OTA/etc., and core 1 exclusively running a Rust RTIC/SRP application, nailing real time peripheral activity.
The only miss is the lack of 5GHz. Nothing is perfect, and that's not a deal killer in most cases.
This depends on what resources you're counting. If you're counting the developer cycles, it is not.
ESP-IDF+FreeRTOS has great value: it solves a host of mundane problems that need solving in real products. Discarding all of that value is foolish; you should preserve it, and look to keep your work aligned with the recent ESP-IDF and FreeRTOS evolution, so future you can adopt updates and supported tooling in a timely manner.
However, you also need at least some of your work to be hard real time, bare metal code. You do this through hardware peripherals, precision memory management, and tight ISRs that do not contend with whatever FreeRTOS or some Expressif driver is up to. Most of all, you want to never have to rework these parts because something in ESP-IDF and/or FreeRTOS, both rapidly moving targets, has changed.
Dedicating cores (0 for FreeRTOS, 1 for you) provides exactly this, and why ESP-IDF supports this model.
There is an ugly truth here. Ideally, one should not need to resort to such things. If the model and runtime behavior of the vendor's stack were extremely mature and could be relied upon with high confidence, it would not be necessary. However, anyone that has ever actually dealt with real time requirements and/or needed to fully exploit hardware peripheral capabilities in the real world of endlessly changing, incomplete, buggy BSPs/RTOSes/etc., knows that they probably won't live to see that.
No. Not at all inevitable. Poland might have descended into kleptocracy, e.g. Hungary. That this did not happen is worthy of investigation. I'm not holding my breath however; the findings would probably not be welcome.
"A general lack of ideological 'mind viruses' that seem to plague the western world"
Indeed. Poland frequently disappoints the rest of the EU with its stubborn indifference to obligatory Western moral panics.
reply