#patent

opensciencedaily@diasp.org
ramnath@nerdpol.ch

enter image description here
#Why did a Chinese-born, US Army engineer perfect a nanotechnology to deliver quantum dots in humans? A nanoweapon technology that’s owned by the Chinese military and used in the COVID-19 vaccines.

#KarenKingston

Oct 18. 2022

Quantum dots and other nanotechnologies are foreign terms to most of us. They are alien concepts difficult for many people to comprehend even exist. Although not well-known, nanotechnologies such as quantum dot, hydrogels, graphene oxide, and single wall carbon nanotubes (SWCNT), have been used in consumer electronic devices, healthcare products, foods & beverage, military neuroweapons, and medical device research and applications for over a decade.

If quantum dots seem to be literally everywhere (ubiquitous), why are most Americans unaware of what quantum dots are?

One reason may be because they are invisible. #Quantum #dots are less than 1/100th the size of a micron. (Most viruses are several microns in size).

While quantum dots cannot be seen by the #human #eye, the effects of quantum dots are not ‘invisible’ to our bodies.

The #electromagnetic fields and #frequencies emitted by quantum dots can cause #emotional, #psychological, and #physical #disease and #dysfunction in our bodies. Quantum dots can be used as neuroweapons and can cause severe disruptions to your emotions, energy, phsycical abilities and your ability to think straight ( #brain #fog).

It is evident that the COVID-19 injections contain nanotechnology that can host electromagnetic fields and receive signals. People are magnetic and are suffering from rapid onset of neurological disorders and hallucinations, sometimes resulting in death.

Scientists and researchers have observed the self-assembling nanotechnology by examining the ingredients of the COVID-19 vials under an electron microscope.

Per #MODERNA #Patent US 10703789 B2, which can be found on the MODERNA website, the technology for all #mRNA #COVID-19 vaccines uses lipid nanoparticle (LNP) #technology.

Per sections 219 of MODERNA US 10703789 B2, the lipid nanoparticles (LNPs) are fully programmable self-assembling technologies.

Sections 219 and 220 state that the LNPs can contain gels and hydrogels.

US 0028565 A1 is part of the intellectual property of MODERNA US 10703789 B2 and is for water-dispersible semi-conductive metallic nanoparticles.

US 0028565 A1 patented the functionality of the nanotechnology in the COVID-19 bioweapon injections to ensure rapid, easy, and targeted biodistribution of the nanoparticles throughout the body.

This COVID-19 ‘vaccine’ nanotechnology is quantum dot. I reported on US 0028565 A1 in August of 2021 on Pete Sentilli’s show.

Since publicly reporting on this patent last summer on multiple shows, the US patent office blocked public access to US Patent 0028565 A1.

The patent expired on May 16, 2022 due to nonpayment. Life Technologies is listed as the correspondent contact. The address shown is an address for one of the ThermoFisher Scientific offices in Carlsbad, CA. The original applicants’ names, Edward William Adams and Marcel Pierre Bruschez, Jr., are listed as unavailable.

Per US 0028565 A1, quantum dot’s functionality is based on the quantum mechanics of the Bohr particle. Due to quantum mechanics, quantum dots that have been injected into American and global citizens by means of the the COVID-19 bioweapons can quite literally appear within the human body based on specific electromagnetic frequencies (EMF) or disappear based on specific frequencies.

Per US 0028565 A1, quantum dots respond to high- and short- frequencies that emit blue light. At these higher frequencies, the quantum dots reduce in size enabling them to connect with, receive, and emit frequencies from the quantum field.

Per the 2011 book publication, Quantum Confinement Effect, quantum dots are able to produce electromagnetic labels (i.e. Bluetooth addresses) inside the body and tag organs.

Per Quantum Confinement Effect, extensive animal research has been successfully completed using quantum dots to invade, target. and mark major organs, such as the heart, lungs, kidneys, liver, spleen, and brain.

Per ThermoFisher Scientific’s website, quantum dot (Q-dot labels) can be used to target, track and trace, not only tissues, but even individual cells.

On February 23, 2022, ThermoFisher Scientific announced a 15-year manufacturing deal with Moderna for Moderna’s mRNA COVID-19 vaccines and other experimental mRNA vaccines. ThermoFisher Scientific had previously partnered with Moderna to manufacture their mRNA COVID-19 vaccines in 2021.

WO 148684 A1 is is part of the intellectual property of MODERNA US 10703789 B2 and is for opal hydrogels. Opal hydrogels are part organic and inorganic. This means that they are part biology and technology.

This hybrid biosynthetic technology species is Inorganic-Organic Hydrogels (IOHs). Quantum dots are part of the technology part of the IOH hydrogels and emit vibrant colors. Quantum dots are also what give LED television screens their bright colors.

Quantum dots need to be encapsulated in single wall carbon nanotubes (SWCNT) within the mRNA lipid nanoparticle (LNP) technology to be delivered into the human body.

Patent US 02510618 A1 is part of the intellectual property of MODERNA US 10703789 B2 and is the patent for the SWCNT. US 02510618 A1 COVID-19 technology vaccine patent is also the intellectual property of the Chinese military.

Per a Breaking Defense January 2020 article, ‘Carbon Nanotubes & Quantum Dots: Army Thinks VERY Small,’ Joe Qui, a Chinese-born, US-trained physicist-turned-engineer-turned-Army program manager, who oversaw the research, development and utilization of nanotechnologies and quantum dot with 5G on US military bases, further developed SWCNT technology for military purposes.

Full article: https://karenkingston.substack.com/

https://karenkingston.substack.com/p/part-5-dismantling-the-covid-19-deceptions

christophs@diaspora.glasswings.com

The mRNA Vaccine Patent Fight Expands | Science | AAAS

So Moderna has announced that they are filing patent infringement suit in the US and in Germany against Pfizer and BioNTech over mRNA vaccine intellectual property. This is not completely unexpected - and by that I don’t mean to imply that Moderna necessarily has a case, because I’m not sure if they do or not. It’s just that there is almost never an example of a breakthrough biopharma technology that does not end up setting off a flurry of patent lawsuits. For better or worse, this is the norm.

#moderna #patent

https://www.science.org/content/blog-post/mrna-vaccine-patent-fight-expands

deutschewelle@squeet.me
canoodle@nerdpol.ch
canoodle@nerdpol.ch

Rst vs Go - Open Source is about enabling users - Rust lang will complement C around the GNU Linux Kernel (for better safety) "Amazon, Microsoft, Google" and the White House, want to make Open Source more secure

Open Source is about enabling users

“Amazon, Microsoft, Google” and the White House, want to help make Open Source more secure…

https://www.youtube.com/watch?v=U-8KopUKMzA

https://www.youtube.com/watch?v=U-8KopUKMzA

so far so good eh?

How will this exactly play out? What will be the “modi operandi”? (Pentagon & JP Morgan Bank, are interested in making the software supply chain more secure, as the IT of banks (!!!) not very good (say the banks THEMSELVES (that fired a lot of IT staff to save on money))

Just an idea for the govs & big corps with the money:

  • put up a “Open Source” “kickstarter” like website
    • where companies & gov can put up their requirements
    • Open Source developers either accept to tackle those requirements
    • or:
      • post their own projects & investors can allocate their resorces to Open Source
      • ABSOLUTE transparency is critical here, not a “pay to play” “taking power” “taking over” “Open Source” “influencing” sealing deals behind closed doors.

https://en.wikipedia.org/wiki/Star_Trek:_First_Contact

https://en.wikipedia.org/wiki/Star_Trek:_First_Contact

long version:

https://peertube.co.uk/w/jKvQozs7xDqpQvbwQFdKbF

The Star Trek economy: will it ever exist?

Afaik Dutch historian Rutger Bregman confirms in his book “Humankind: A Hopeful History” (BE WARNED: it is a realist’s thriller!), that “the nature” of humans (also under constant development), is as such, that only a small percentage are reckless “psychopaths”,

the majority of mankind rather wants to help each other, than shoot each other.

Rust “second in command” around the GNU Linux Kernel

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://en.wikipedia.org/wiki/Rust_(programming_language)

https://foundation.rust-lang.org/

https://foundation.rust-lang.org/

Because Rust lang promises improvements around cyber/itsecurity (no more buffer over/underruns), it might become “second in command” around the Kernel.

The cons: Rust is more C++ than C, which might be a problem for the (long term) C nerds.

Unless (Linus?) & Greg (or someone else) wants to develop a brand new “C” “2.0” lang + compiler designed around security…

Unless Google wants to change it’s Go lang licence…

…Rust it is.

Is Go (a more C like) alternative?

https://en.wikipedia.org/wiki/Go_(programming_language)

https://en.wikipedia.org/wiki/Go_(programming_language)

(2018: developer Voit wrote a Network driver (GNU Linux kernel module) in Go)

https://www.net.in.tum.de/fileadmin/bibtex/publications/theses/2018-ixy-go.pdf

C ixy vs Go ixy: performance (only) “10% slower then the C implementation under optimal circumstance” (optimal meaning: system’s CPU needs fast single threading)

“One of the biggest problem during development was low-level memory management.”

“Specifically register access has proven itself to be difficult in Go

“On the other hand we were surprised about the garbage collection.”

“Originally named as the reason why Go is nor suited for systems programming, our analysis has proven otherwise”

“easier to read and does not require much understanding of the language itself in order to understand the code, especially compared to some C constructs like function pointer, pointer casting and other more intricate operations” (src)

the Go lang licencing MumboJumbo:

“Copyright (c) 2009 The Go Authors. All rights reserved.”

“Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

“AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE

OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.”

that’s not all… there is more licencing mumbojumbo for all those Free Software Foundation & lawyerzzz:

‘Additional IP Rights Grant (Patents)’

‘”This implementation” means the copyrightable works distributed by Google as part of the Go project.

Google hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section)

patent license to make, have made, use, offer to sell, sell, import, transfer and otherwise run, modify and propagate

the contents of this implementation of Go,

where such license applies only to those patent claims,

both currently owned or controlled by Google and acquired in the future,

licensable by Google that are necessarily infringed by this implementation of Go.

This grant does not include claims that would be infringed only as a consequence of further modification of this implementation.

If you or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that this implementation of Go or any code incorporated within this implementation of Go constitutes direct or contributory patent infringement,

or inducement of patent infringement, then any patent rights granted to you under this License for this implementation of Go shall terminate as of the date such litigation is filed.’

src: https://raw.githubusercontent.com/golang/go/master/PATENTS

While the sources of the Go lang are indeed accessible via github, it’s licence is neither GPL 2.0 nor GPL 3.0 nor Apache licence nor MIT licence and thus questionable if:

  1. Google can be trusted (?)
  2. the Go lang licence is “compact” but (currently) not at all Open Source compatible (not a word about if modifcations are allowed)
  3. why did Google not simply pick a “well known” Open source licence? https://opensource.org/licenses

One fine day, Google might to decide, to change the licence, and from this to:

Next problem: Rust (src here) was started by Mozilla, is used by Mozilla for Firefox, but Mozilla has build up financial dependencies to Google.

(Rust in contrast is licenced under MIT & Apache licence https://www.rust-lang.org/policies/licenses)

While this is all not really: K.I.S.S (the UNIX philosophy of Keep it Super Simple)

No dispair, just do your best.

Sticking to the default?

The problem is that systems designed & “Made in the 1970s” (C compiler, Phones, Mail), were not designed around security (because it was not really a problem in those days).

So…

  • unless Google won’t change the Go lang licence to something Open Source compatible
  • unless Linus & Greg or someone else wants to build a C 2.0 around security, Rust is it.

The Go lang licencing problem is the ZFS Oracle licencing problematic all over again:

https://dwaves.de/2022/01/20/the-most-controversial-filesytem-in-the-known-universe-zfs-so-ext4-is-faster-on-single-disk-systems-btrfs-with-snapshots-but-without-the-zfs-licensing-problems/

In other words: Licences (money) have more than once, instead of enabling developers & users, have hindered developers & users.

Another company that M$ successfully killed by buying it…

Another example how Microsoft successfully made this planet worse:

Ever heared of Video2Brain?

IT WAS AN EXCELLENT learning platform, with high quality video learning courses with…

  • 2000 courses in German
  • 1200 courses in Spanish
  • 1300 courses in French
  • 500 courses in Japanese (as of September 2017)
  • 0 in English? (a bit strange, but this company was from Austria and has focused on the EU market, that might be one reason)

Microsoft bought it up… now it is… dead? MS killed it. #wtf?

Now a high quality Video2Brain Rust videos would be needed (luckily – again – Youtube volunteers are chipping in THANKS! (MS maybe transfer some money to them? eh? thanks!))

PS: so that’s my take, could not ask that question via…

stackoverflow.com and serverfault.com suck and DESPERATELY needs competition

stackoverflow.com and serverfault.com suck and DESPERATELY needs competition

#linux #gnu #gnulinux #opensource #administration #sysops #dev #c #development #rust #go #google #security #itsec #cybersec #cybersecurity #kernel #linus #torvalds #mozilla #licence #licencing #patents #patent

Originally posted at: https://dwaves.de/2022/05/16/rst-vs-go-open-source-is-about-enabling-users-rust-lang-will-complement-c-around-the-gnu-linux-kernel-for-better-safety-amazon-microsoft-google-and-the-white-house-want-to-make-open-sourc/