amy-petrik-214
Joined 2 years ago
Joined 2 years ago
mito is like <100k bp vs 3000000k bp in human genome (bp = base pair = "character" in a string)
principle derives from the concept of "the selfish gene" or "the red queen" these famous books on the topic. Arms races between X and Y chromosome. Arms race between nucleus and mitochondria, and so on.
or put it this way. why do all animals have sex? because it generates gene sequences that confer fitness more efficiently than self-replication (which is the typical repro method of unix programmers)... .. generates such gene sequences for NUCLEAR DNA that is, mito DNA comes from mom only (the red queen.. .. "mitochondrial eve" ... "y chromosomal adam".. etc). and thus the mito is fundamentally unable to wield the power of evolution, completely evolutionarily outclassed by those nuclear chromosomes. thus exporting all its genes to the nucleus, conferring advantage to all such progeny with their superior power supply
So this means there is common knowledge of some random vector 01101010101 but nature decides the vector randomly, not humans, not communication.
You might get clever and say "aha! if I measured or not can be the communication" and that's true. The way you measure that is to see if your particle is in a superposition state or no. You shoot the entangled photon through a double slit and see if a wave-like pattern occurs, in which case we're still in a superposition and our communicator has not measured, or if it's two lines they have measured. "measured or not" thus is our "bit" that has been communicated instantly.
So the answer is kind of yes and know. At face value instant communication is not possible. Adding a quantum superposition detection device, then yes, such a device's readout may be used for Ender's game style ansible communication.
21%, yes, but what kind of American? Central American, South American?
Conversely a person could start patenting obvious ideas (morse code + cell phone seems like one) and then thousands of people independently arrive at the idea unaware of prior work. So now all that legal paperwork backing meant to fight off the startup type, the dragon, is used on an innocent - he who fights dragons should be careful not to become a dragon himself
IMO the patent system here is transformed into a "first person who calls dibs is the winner!" type free for all, and we get professional dib-callers. And the reason why it happens is the content of the patent, the ideation, execution, is all rote simple and not all that innovative.
It can be a cancer mutating. It can be the cancer not mutating (occurs after drug given) but is mutated (mutation occurred already). We have a population of a billion cancer cells. Treat with drug. 999 million die, 1 million survive because they had that mutation conferring "fitness" i.e. resistance to drug. three months later, we have a billion cancer cells again, descended from the 1 million cells. Now those billion cells also get the next line of therapy. 999 million die, 1 million survive. 3 months later, those 1 million are now a billion again. And so on. Point being, I'd think of it more as a selection mechanism as Darwin taught us, not the cancer automatically generating a resistance mutation - the blind watchmaker. In this case there was probably a mutation changing or downregulating the antibody target, probably HER2 or something related.
I don't know what "rejecting the antibody" means. You would need to look up the ADME to understand physiology and think about how the cancer might modulate that.
All this talk of "oh how do we catch these mutations".. ... ... there are a few dozen companies that will tell you what mutations are there straight up, just from the blood. From the tumor, any hospital can tell you all the mutations. The problem isn't that we don't know. We can tell you the mutations. We can tell you the new mutations. So we find 100 mutations let's say. Okay. Next question, for each of the 100 mutations, does it cause resistance, yes or no? Do two of them together cause resistance? Are they from the same cell, they could be from distinct tumor lineages. You know most of the mutations are what are called "passenger mutations" right? Red herrings.
So this is the pathology of computer scientists. "If only a clever programmer took a crack at this, these biologists what with their humanities style miasmas and rote memorization topical field". Many have in fact... Bioinformatics goes as far back as the 1970s I'd say if not further. And that clever programmer did find all the mutations. Did a great job. Pretty well developed. Then you say "ah let us understand what the mutation does!" Okay. So now you're taking a subset of the broader field of genomic variation and computationally deriving how that variant influences trillions of different cells interacting with an antibody protein with a chemical bound to it. Congrats, if you're such a "clever programmer" than by solving this, you've solved life itself! Basically this notion is "this looks easy, what is this, like the 3-SAT problem, figure if someone was clever enough to take a crack at it then that would solve this whole 3-SAT issue!" completely blind to the fact that it's just as hard (and the same) as proving P=NP. So if you ARE a hardcore clever programmer, then this rabbit hole goes as deep if not deeper than P=NP, and the cancer will humble you, as this is what cancer does, to humble.
That is to say, if we all have a "same browser" then there will be people with "not same", there will be divergences, it will be a mess.
A very simple solution of polymorphic fingerprinting - the fingerprinters will get a fingerprint, a good looking one, just that it will be different each time. Even better to think of when the russians poisoned the ammunition in vietnams with bad bullets. Can't make them all bed or they'll toss the whole batch. I think they arrived at 1:10. The idea is to make fingerprinting as ugly as possible - up to and no further than the point that they are forced to cook up something even more evil.
The other thing cholesterol is used to make, also quite nice to have, is bile. Used for fat digestion and such. A lot of bile. From a lot of cholesterol. Seems like a waste though, to excrete all that finely synthesized bodily chemical. BUt aha, the body realizes this and so resorbs it. THus there is a cycle and recycle of cholesterol and bile. Aha! What if we can trick the body to not resorb it and just release it. Such a drug has been developed. Well, hard to call it a drug. There is no fanciness, no elegant molecular binding to an esoteric receptor, no, nothing of the sort. It's called metamucil, and as the name tells us, it mostly works by being a big chonky mucinous blob of very impressively thick goop. The "magic" of how it works is literally the bile gets trapped in the thick goop and excreted. And thus we've bled off some bile from the cholesterol recycling loop, and thus, cholesterol. And that's why this weird blobby old person fiber supplement is cholesterol magic.
- Find the "bad guy" server onion address "hidden service"
- Run a tor relay. Ideally many. No exit node shenanigans needed - hidden service, not exiting TOR. This is quite nice from a legalistic perspective since you're not on the hook for hacks coming off the exit node.
- Run a bunch of clients. Instruct to connect to "bad guy" onion.
- Gather data over time for correlation attacks. Correlate your client to relay to endpoint server.
- At some point, you'll find one of your relays is the guy connecting directly to said hidden service.
Very simple lesson here. One needs to encrypt the information, yes, but failing to consider packet timing as "information" is the fallacy.
Now I wonder if later Gs have a bit of a decryption loophole for this reason or that, this state actor or that.