or perhaps reprogram your immune system to recognise the transplant as native rather than foreign.
I've heard about this happening; someone's immune system was destroyed for something unrelated. When it was restored, a transplant patients no longer needed immunosupressants. There is some research into doing this specifically to deal with transplants.
A good thing. Great though these drugs are, they cause all sorts of problems, making people more susceptible to sickness (minor ailments can be fatal), and they increase the risk of cancer.
I actually don't get what the fuss is about this. I you want to life in a law less zone that is fine for you.
Just because you live in a zone with fascist anti-Speech laws for protecting a right to be "forgotten" and erase what was publicized about you don't mean the rest of the world does.
Your country might grant you the right to be forgotten by restraining companies' free speech, but your country don't have a right
to restrict what gets stored on and served out to the world by by servers outside your country.
The TLD of the domain generally has nothing to do with the location of the servers.
In fact... this is incorrect. Usually they are directly related. Usually companies place the servers that will ultimately
handle the HTTP request for a given TLD within or near to the geographic area of that TLDS' users.
Yes, some TLDs are (mis)used in different ways, and some smaller companies put all their servers in one country, and still serve
out multiple TLD versions of their website from the same datacenter.
However, for global companies such as Google, they will have datacenters in numerous countries, and the corresponding DNS name TLD
is routed towards the datacenter appropriate for that localization of their website.
In Google's case, when you visit their website, they redirect you to the proper TLD, and they have their systems of answering IP addresses and DNS queries differently (Anycast-based service routing) depending on which country you are located in when you navigate to your local country's version of Google; so the TLD used indicates which country/region's localization of Google you are using.
I've seen this kind of horseshit come up lots of times; in Brocade too long ago. In large corporations,
top management is either drinking the Kool-Aid, Or maybe intentionally coming up with ridiculous bogus assertions that
anyone familiar with technology and a few brain cells could clearly recognize as bogus.
Network neutrality and self-driving cars have nothing to do with each other.
Also, network neutrality is not about "No paid prioritization"; it's about no paid prioritization of different products or services based on throttling or accelerating certain websites on the same internet (that thus exist at the same level of service) based on business reasons behind the scenes -- or other providers' competitive nature or refusal to pay extra eyeball taxes.
Network neutrality don't prevent you from selling an entirely separate network service to consumers AND sharing backbone infrastructure, and providing those separate network systems different priority.
If you access a different TLD, then you are connecting to servers in a different country, therefore the location IS very different.
Shoulder surfers can watch the keyboard, so masking often provides a false sense of security.
It is best for the user to feel "exposed" and take other precautions to prevent people seeing them type, especially for rare operations like setting the password where needing to see potential typos is an issue.
If cryptocurrencies want to go legit as a legal tender, they need to do the same to ransomware addresses.
I guess what needs to be done is introduce trusted "Blacklisting" authorities that all users, and possibly all nodes will honor.
If an address is BLACKLISTED, then all services and bitcoin nodes check the path coins have taken, and the coins that passed through a blacklisted address cannot be spent anywhere further, they are tainted: Both transaction/payment providers/exchanges/retailers or other business running nodes and Miners/Network nodes will consume the blacklist and boycott their requested transactions.
Some centralized agreed-upon "Coin seizure arbitration authority" could be entrusted to sign WHITELISTED addresses, and Blacklisted coins can be spent to a WHITELISTED transaction by the trusted authority and clears the taint.
This would allow criminals to "self-forfeit" their stolen assets in exchange, for, probably some minor consideration such as reduced jail time, or freeing up other tainted coins they own which were not involved in the activity.
All in all, Android is a better experience than the Windows on this particular tablet. I'd put Linux on it, but from what I heard, Linux is pretty bad as touchscreen support. (Disclaimer: I haven't tried. I only *heard* it was sucky. If you have decent suggestions, I'm all ear. I usually only run Linux on laptops and Desktop. This machine is pretty much the exception)
Ethereum has done it before in a previous hacking. They could write a patch, in theory, to do a fork and invalidate all transactions to the Hacker's address.
If that is their intention, they should announce it immediately to help mitigate damage (Make sure the hacker doesn't spend further and leave other people holding the bag).
Hail, bird strikes, random acts of God, manufacturing defects etc etc replacement, plus 20% overhead = less than ideal service life for the panels. The utility companies typically do RTF, or "run to fail" and they need a number that's comfortably below the average design life so that they can budget for the the items listed at the beginning of this post. Any overages in savings go to pay for union worker's raises and benefits.
and no, consolidating our entire solar grid into a single spot wouldn't make much sense from a security standpoint
So instead of having 1 10000 Mi^2 site.... have 10000 1x1 Mi^2 sites....
or better yet 185,853,333 sites that are 1500 Square-Ft of panels each.
Just make sure they are all well-distributed across the grid and hardened, so they are not easily damaged by weather conditions, and not easily harmed by remote electrical attacks.
is an idiot who brought in a device like a wireless router that acted as a DHCP server or similar and kicked a pile of people off a network
That is not the problem. We have a very robust solution to that technical problem that any modern switch OS will support.
Rogue devices on the network can be used to create backdoors, they may be infected or vulnerable to serve as attacker beachheads, or otherwise facilitate malicious activity such as with ARP Poisoning, because Ethernet was not designed for security, it is very susceptible to malicious actors --- Also, because the local network is behind the firewall, you're skipping security barriers, And who's to say that unauthorized device isn't a rogue VPN tunneling through the perimeter to allow outsider access?
"Kill the Wabbit, Kill the Wabbit, Kill the Wabbit!" -- Looney Tunes, "What's Opera Doc?" (1957, Chuck Jones)