If I'm going to be completely honest; I feel like these people in support of such a withdrawal of support (of Israel) are going to have to move the needle A LOT more than a mere 5% to get the attention they want.
Might be acceptable to get a little louder about your issue; and properly educate people about it.
Depending on how Vyvanse is Scheduled; it might be legal to privately make. If it's not scheduled like a standard amphetamine; the DEA is powerless.
I have a sneaking suspicion it's not illegal to compound this stuff. But IANAL; and it doesn't matter if the DEA thinks it is and will hassle anyone trying.
I firmly think this would be a boon for many people; owning one of these is likely a lifeline that even small town physicians could utilize to dispense drugs freely or cheaply to patients in need.
This is something that I think small-town pharmacies could use to create compounds in cases of drug shortages. I think tools and programs and small labs like what are discussed in the article are a positive force for good; and that they should be not only allowed, but encouraged, for many drugs that are expensive, unavailable to someone in need and can be readily synthesized safely with a basic college level of chemistry training by someone in a pharmacy.
I think the potential risks and downsides are small right now; and I think more of it should be encouraged gently so that we can find out quickly what the flaws and limitations are so that we can put regulatory guardrails around it so that people do not harm themselves.
While I wouldn't condone using an AI to create an entire novel, I would be fine with a human using ChatGPT to generate topics, prompts, and check spelling & grammar.
AI is a tool. It can be used for good, and it can be used for bad. Much like a hammer. There are both good and bad ways to use them.
There's no reason for there to be prohibition of AI generation; just prohibition of AI Generation being the only source of text.
It feels like this vulnerability isn't notable for the majority of users who don't typically include "Being compromised by a Nation-State-Level Actor."
That being said; I do hope they get it fixed; and it looks like there's already mitigations in place like protecting the authentication by another factor such as a PIN. That helps; for people who do have the rare threat model issue in play.
The complexity of the attack also seems clearly difficult to achieve in any time frame; and would require likely hundreds of man-hours of work to pull off.
If we assume they're funded enough to park a van of specialty equipment close enough to you; steal your key and clone it; then return it before you notice...nothing you can do can defend against them.
(As if spoken by the King to Simba:)
Rust: Everything from the bottom of this cliff to the acacia tree there is ours. Make sure you ask permission before you take something, take nothing you are not permitted to take. We don't go beyond that tree; and if you even think about the elephant graveyard beyond it; I'll kill you myself.
C: Everything the sun touches is yours. I caution you to not venture into the shadows; but I will not stop you, for you are a king, and nothing a king can do is unnecessary if it is for his people.
I think there's a problem with the 'C only' devs refusing to be accomodating to the Rust developers. Instead of being stubborn; why not provide them what is needed and help the Rust team learn how to maintain what is needed themselves?
None of the reasons I've seen mentioned are legitimate reasons for refusing to at least help them a few times, and helping them to learn how to do the onerous task themselves so they can keep it off the main plate for too long.
C devs do not need to learn Rust to provide critical information; they need only be present and cooperative with Rust devs to help them find, convert, and localize data structures for Rust use. They can stand to sit and pair code with their Rust Dev counterparts long enough to teach a Rust Dev counterpart how and what they need to look for in C code. It's not that big of an ask, and it's not something that really is a large ask. Provide the bindings for a short period of time, and work on training a team of Rust Devs to maintain the bindings.
That way both sides are stepping up to meet the others and the data isn't being sat on by the C-only Devs.
I'm certainly concerned that now that this software has been covered in PopSci; that it will certainly suffer a needless onslaught of DMCA and other lawsuit-related shenanigans. >_>
No; Piracy won't stop.
Analog loopholes still exist; and cannot be eliminated completely from the chain. Enterprising crackers will tinker and find weaknesses in systems. People will find bypasses, workarounds, and straight up just crack whole encryption schemes that were badly implemented.
Encryption was never intended to protect content. It was intended to protect people. In the short term; sure, DRM and encryption can protect profits. In the long term, it provably cannot and does not. Oftentimes it gets cracked or goes offline; and the costs associated with keeping authentication servers up for long enough to keep lawsuits off your back is provably large and difficult to scale. I would even assert that it costs more to run DRM than it saves anyone in 'missed profits'.
Frequently companies also argue that it saves profits by recapturing "lost sales"; but that's provably false. A consumer, deprived of any other viable choice, will in fact, just not buy the thing if they cannot buy it for what they deem as a fair price. It has also been proven; that if they can acquire the content freely; they will oftentimes become far more willing to buy whatever they acquired or even buy future titles. When a customer trusts; they may decide to purchase. But why should a customer trust a company that does not trust them?
While there is no harm; I could easily understand why parents might not want this measure passed. Frequently the costs get passed onto them in a painful way; either at the lunchline every day or indirectly via the taxes they pay and how much the school spends.
I think it could be easier if instead of passing the law for everyone statewide; they just let schools and districts "opt into" this sort of thing by polling parents; and "voluntarily join the study of this subject" rather than being forced into it by state legislature statewide. Then the State can control and gather data in their own ways...and maintains their own control group; which makes a better study. They can't control the quality of the control group when using data borrowed from other states...what they get is what they get.
To be clear; the Nintendo Switch tends to trade fluently in cryptographic certificates.
The MiG Switch has one of these certificates; one it's creators likely copied from a legitimate Nintendo Switch game title. All games have such certificates and they are uniquely serialized; much like a GUID or UUID would be. These certificates are signed by the Game Dev studio, and then Nintendo in a typical certificate signing chain scheme; Nintendo signs the Game Dev Studio cert, which signs the Title certificate, which signs the unique cart or digital copy cert.
This banning is usually achieved by banning either the lowest certificate in the chain or the one directly above it; or even the Dev Cert if it was compromised.
So the MiG Switch carts are likely hardware banned. Your Nintendo Switch probably advertises to Nintendo which cart(s) were inserted into it recently by sharing the fingerprints of the certificates. Then Nintendo can basically kill the certificate assigned to your Switch system and prevent you from connecting online; as your Switch uses it's own system cert to identify itself to Nintendo services.
In all cases this is un-evade-able when connecting to the internet; as Nintendo Switch system certs are burned into a PROM chip on the main board at manufacture. This chip is a WORM chip, which can only be written once and read many billions of times.
A critical part of the way they try and curb cheating in online play is checking the integrity of the runtime environment; which includes checking what titles were launched recently; and if that happens to include a certificate they've banned for being cloned by the MiG Switch; then you'll quickly be banned by their anti-cheating hammer.
Most important is those checks typically don't take place naturally; they only occur when you're connecting to the EShop, or connecting to NN to play multiplayer online. The devil therein unfortunately lies in the details; and if you've ever purchased a Digital Title that means your Switch is regularly connecting to the EShop to renew Digital License Tickets needed. They tend to expire every 72 hours and must be renewed by presenting an expired Ticket, a valid Ticket Granting Ticket (given to your Switch when you buy the title) and contacting "Mommy Nintendo" and asking "Mommy, May I?". Yeah. DRM sucks.
If all goes well; your Switch gets a shiny new set of tickets. Unfortunately Nintendo was paying attention to requests and will issue out regular waves of bans for systems detected cheating. You won't know when this will happen, and it won't prevent Nintendo from letting you play your games; you'll just suddenly find your Switch banned from online play after such ban waves.
I'll just leave this here.
https://youtu.be/9xn0OHEZZ8Q