May 2021 - cypherpunks - lists.cpunks.org

*SPAM* false positive.
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: looks like all my messages are being rejected. Begin forwarded message: Date: Thu, 20 May 2021 17:54:12 -0300 From: "Punk-BatSoup-Stasi 2.0" <punks(a)tfwno.gf> To: cypherpunks(a)lists.cpunks.org Subject: *SPAM* Re: Facebook urged to abandon encryption plans after child abuse [...] Content analysis details: (8.0 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: cpunks.org] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [37.120.193.122 listed in list.dnswl.org] -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

2 3

*SPAM* current work [gnuradio]
by Karl 20 May '21

20 May '21

Tagged spam because I'm really confused and not sure what I'm saying. And because I'm still learning about Vikings myself. I have made two gnuradio blocks! I am a tiny hero! https://gitlab.com/xloem/openemissions/-/tree/master/gr-blocks Using gnuradio blocks lets one move towards working with open freedom communities. Gnuradio blocks are all documented at the gnuradio wiki. Everyone's goal of course is a general-purpose workbench, but you have to start somewhere. Pad Crop Block: This is useful for organising wave periods together while adjusting theorised periods. note: there may be helpful blocks under Resamplers to shrink the waves for display if the sample rate is high rescaling could also be added to pad/crop, or sdl video, but gnuradio's way seems to be to use a hier block to move towards user design Connect these: Stream Tag Tools->Stream to Tagged Stream configure this to guess the period of the waveform openemissions->Tagged Stream Pad/Crop Video->Video SDL Sink configure the pad/crop block to output the periods aligned with the video width now any similarities between them are visually clear as vertical bars PiGPIO Sink Block: This is useful for driving hardware based on a time-synchronised signal. In Karl's noiscillate experiment, he has a noise generator connected via a relay to a raspberry pi pin. Connect these: Waveform Generators->Signal Source configure to a square wave with a low frequency openemissions->PiGPIO Sink oscillate power to a device using a relay now the same flowgraph can be used mathematically to compare the signal environment with and without the device powered

1 0

Digest Submission | Bank.org - New York Shelf Charter
by Gunnar Larson 20 May '21

20 May '21

Dear Cypherpunks: I would like to submit the "Bank.org - NEW YORK Shelf Charter" memo for digest consideration. - Below the signature of this message, please find the the memo's text - You may access a link to the memo here: https://docs.google.com/document/d/1GKHZPmNa1FbFImTzIdSaKCpJXRZivvQYKXIBdQA… - The memo was originally published on March 14: https://thecapital.io/article/bankorg--new-york-shelf-charter--MVkuUJjbXVEw… Please let me know if the memo is something you think would be suitable for a Digest submission. Sending you warm regards. Thank you, Gunnar -- *Gunnar Larson - xNY.io <http://www.xNY.io> | Bank.org <http://Bank.org>* MSc <https://www.unic.ac.cy/blockchain/msc-digital-currency/?utm_source=Google&u…> - Digital Currency MBA <https://www.unic.ac.cy/business-administration-entrepreneurship-and-innovat…> - Entrepreneurship and Innovation (ip) G(a)xNY.io +1-646-454-9107 New York, New York 10001 ---------------------------------------------------------------- March 13, 2021 BY ELECTRONIC MAIL New York State Department of Financial Services Honorable Superintendent Ms. Linda Lacewell Innovation(a)dfs.ny.gov Re: Bank.org <http://www.bank.org> Shelf Charter Dear Madam Superintendent: xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> must innovate beyond market manipulation and cross-border computer crimes that present serious risks, both to consumers and to the safety and soundness of financial services institutions. As the cryptocurrency markets continue to evolve, the New York Department of Financial Services (NY-DFS) has directed virtual currency companies like xNY.io <https://xny.io/> to take the necessary steps to guard against fraud and to be extra vigilant about manipulation. Today’s memo aims to innovate the market and can only evolve with your strong regulatory supervision. xNY.io <https://xny.io/>’s recent Tech Sprint Submission <https://thecapital.io/article/computer-crimes-and-the-bitlicense-nydfs-MUoH…>, “A Design Mechanism to Report Digital Regulatory Computer Crimes,” was filed with your esteemed office on March 2, 2021. xNY.io <https://xny.io/> has discussed the matter of marketplace manipulation with the NY-DFS innovation team. We have both agreed marketplace manipulation is an issue and specifically affects xNY.io <https://xny.io/> and Bank.org’ <http://www.bank.org/>s bottom line. Our mutual moods seemed aligned on innovation. However, there is an air of dienfranchiemt. Madam Superintendent, recently I published an Open Letter to Bloomberg on Modern BitLicense Logic <https://thecapital.io/article/an-open-letter-to-bloomberg-on-modern-bitlice…>. Some BitLicensees candidly offer feedback regarding New York State borders. There seems to be some confusion concerning the BitLicense’s jurisdictional reach and given that xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/>’s business falls under DFS surveillance and the USA PATRIOT Act, Congress amended the definition of “protected computer” to make clear that this term includes computers outside of the United States so long as they affect “interstate or foreign commerce or communication of the United States.” 18 U.S.C. § 1030(e)(2)(B) (2001). This change addresses situations where an attacker within the United States attacks a computer system located abroad and situations in which individuals in foreign countries route communications through the United States as they hack from one foreign country to another. Both situations can therefore be violations of section 1030. As such, it would seem that BitLicensees are subject to New York Law while operating outside of New York (including Human Rights Law <https://dhr.ny.gov/law>). The utility of virtual currency is cross-border. New York is not a walled garden for bad actors to camp while profiting off of the back of xNY.io <https://xny.io/> and Bank.org <https://docs.google.com/document/u/0/d/1dTMICjsRVXmYojTm0Kavl-5UDdh6nosviJB…> wrongfully across global markets. The textbook definition of marketplace manipulation has been discussed with the patient Ms. Seema Shah, a DFS innovation leader whom we look forward to consulting with over days and weeks to come. Meanwhile, it is our observation that the Bitcoin Blockchain has been targeted by New York firms licenced by your office, such as Ripple and Goldman Sachs. In Africa, we experienced how these various actions affected the integrity of our global enterprise. - The Supreme Court placed emphasis on the central role of deception to the concept of fraud—“the words ‘to defraud’ . . . primarily mean to cheat, . . . usually signify the deprivation of something of value by trick, deceit, chicane, or overreaching, and . . . do not extend to theft by violence, or to robbery or burglary.” Id. at 627 (construing Hammerschmidt v. United States. 265 U.S. 182 (1924)). - xNY.io <https://xny.io/>- CryptoBank is painfully aware of a “Crypto Bank” loophole between New York, Europe and Africa. We submitted a Declaration for the Superintendent's review on the matter <https://thecapital.io/article/universal-bitlicense-declaration-on-virtual-c…> of this loophole as it relates to Human Rights from our graduate research as a New Yorker traveling abroad. New York banks are not immune to Civil and Human Rights abroad, specifically if these violations are using computers against other New Yorkers’ enterprises (aka the aforementioned xNY.io - CryptoBank loophole concern). xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> followed DFS direction: 1. Immediately upon discovering any wrongdoing, a virtual currency entity must submit to DFS a report stating all pertinent details known at the time of the report. Virtual currency entities must also submit to DFS, as soon as practicable, a further report or reports of any material developments relating to the originally reported events, along with (we have been actively reporting the matter to DFS, only greeted with silence and Tech Sprint denial…) 2. A statement of the actions taken or proposed to be taken with respect to such developments, and 3. A statement of changes, if any, in the virtual currency entity’s operations that have been put in place or are planned in order to avoid repetition of being affected by similar circumstances. Specific to points two and three above: This memorandum is to properly disclose xNY.io’s agreement and purchase of Bank.org <http://www.bank.org> with further intent to seek Shelf Charter approval from your office. Bank.org <http://www.bank.org/> - Shelf Charter Poverty has no borders, and neither does excellence. xNY.io’s campaign for “Modern BitLicense Logic <https://thecapital.io/article/an-open-letter-to-bloomberg-on-modern-bitlice…>” will forever be grateful for the borders of New York State. Meanwhile, Bank.org’s Shelf Charter is a global concern and DFS should understand our modern, logical international intentions: - The purpose of the Department of Financial Services Shelf Charter is to enable parties that currently do not have a bank charter to participate in bidding for failed or failing banks that are being sold by the FDIC. - Prior to the preparation of a formal application, an outline of the proposed business plan should be submitted to the Department of Financial Services. At minimum, the outline should include the rationale for organizing the proposed institution. Bank fraud is a serious problem for such a developed country as the United States, whose bank regulators have drawn attention to the increase of these crimes. Having discovered that an unregulated virtual currency sphere (such as in Africa, or other developing markets) is very popular among virtual currency fraudsters <https://www.americanbanker.com/news/jpmorgan-chase-warns-of-upcoming-fine-o…>, the New York State Department of Financial Services concluded that this kind of regulatory fraud was threatening US national security. xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> are interdependent solutions of cutting edge innovation, and we seek to begin dialogue with your office for hopeful 2021 Shelf Carter approval. Our goal was to work through Market Manipulation during the Tech Sprint, however, we were denied participation. - The basic problem with New York Bank Innovation is monopoly power <https://thecapital.io/article/universal-bitlicense-declaration-on-virtual-c…>, and policy should address that issue directly. If the problem is a lack of transparency and accountability in government activities, one should find ways to open up the public sector to oversight from outsiders. If the problem is an opaque and confusing regulatory structure, rules should be simplified and clarified. - As elegantly as possible, xNY.io <http://xny.io/> and Bank.org must strive to innovate beyond a Laissez-faire attitude concerning the systems and processes in which transactions between our peers are now free from (or, almost free from) any form of economic/regulatory interventions such as the BitLicense lacking cross-border regulatory logic concern. - Madam Superintendent, bank innovation from the great state of New York touches people on all continents on Earth, and it seems that if given the opportunity, DFS would want to solve any market manipulation matters through technology. - xNY.io <http://xny.io/> underscores the need for reporting innovation specific to virtual currency marketplace manipulation and/or other crypto cross-border regulatory arbitrage frameworks directed out of New York, affecting over 1 billion people. - Bank of New York’s (BNY Mellon) controversies and legal issues history <https://en.wikipedia.org/wiki/BNY_Mellon#Controversies_and_legal_issues> should not be confused with xNY.io <https://xny.io/>’s future, or even in competition with our marketplace entrance. - Libra/Diem/Robinhood/XRP all fail to match xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> global innovation, considering the firms’ historical relationships with computer crimes (cross-border). - xNY.io <https://xny.io/> intends to offer several products and services, including: a tokenized, programmable virtual currencies called xNY, xBB and xLG; Bank.org’s hopeful charter will provide global custody services for assets; API-based online banking services where customer deposits must be 100% backed by reserves; and prime services for digital assets. xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> will operate under the themes of a Universal Declaration on Virtual Currency and Human Rights <https://thecapital.io/article/universal-bitlicense-declaration-on-virtual-c…> . Innovating rather than litigating, we hope to begin immediate discussion on Bank.org <http://www.bank.org/>’s earning your Shelf Charter approval as the most sophisticated solution to innovate and dawn a new legacy of the modern version of the World’s Best Bank. Personally, I am concerned that DFS has potentially ignored xNY.io <https://xny.io/>’s interests ensured through interpretations of specific provisions in the existing national and supra-national legal framework (civil law, securities law, bankruptcy law, international human rights law and civil rights law). As Bank.org <http://www.bank.org/> begins to be re-developed for launch as an international bank, Madam Superintendent it is our business to now lead New York in the global virtual currency industry with xNY.io <https://xny.io/> and to further clarify the rights of the public and obligations of Bank.org’s future customers across global economies and corresponding currencies. xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> choose to register corresponding operations out of New York State rather than Delaware or elsewhere out of passion for this great State and desire to contribute meaningfully to State tax revenue(s). This can be achieved through subtle action on “conditional approvals” that are well earned from DFS review, demonstrating historic cross border innovation and a new, pure DFS association. As a matter of New York Civil and Human Rights <https://thecapital.io/article/universal-bitlicense-declaration-on-virtual-c…> regulation we hope you share our enthusiasm for xNY.io and Bank.org pioneering and preserving a technology-neutral, principle-based, non-discriminatory framework for the next generation of modern New York virtual currency public policy, naturally supporting innovation within the limits imposed by overriding international public interests. - Kindly note that we have a pending Freedom of Information Law (FOIL) request due response related to xNY.io <https://xny.io/>’s Tech Sprint submission covering COMPUTER CRIMES and the BitLicense. - It was upsetting to be denied participation due to other firms’ felony association(s) and wrongdoing to settle criminal and civil investigations with the Justice Department. - Bank.org’s <http://www.bank.org/> Shelf Charter helps push the arch of innovation forward as an example of best practices, unlike Wells Fargo who was admitted to the Tech Sprint at the denial and will concerning xNY.io <https://xny.io/>’s purity. - The two week sprint, from our clearly communicated perspective was to foster community building and relationships with our peers, and denied for unjust cause. - Madam Superintendent, I am sensitive about the Tech Sprint and treatment by DFS thinking millions of our customers globally… - I can wear these shoes as a ethnic minority scholar living in Chelsea, Manhattan, 2020-2021 affording being grateful for New York State’s Pandemic Unemployment Insurance and SNAP benefits. - DFS surveillance must provide the Superintendent’s office outline of clear examples of my personal banking relationships at Wesern Union? Young people around the world experience daily what I have been so fortunate to experience and overcome under the great leadership of the DFS Superintendent. xNY.io <https://xny.io/> and Bank.org <http://www.bank.org/> innovation intentions use our example as a matter of poverty transformed into a modern global Banking enterprise through agile innovation (and, only possible by partnership with your office). xNY.io and Bank.org expect to be a New York success story, at the very least, if not one of the World’s Best Banks. Madam Superintendent, raising capital to fund this historic, innovative operation is of no serious concern. Rather, the key to success isDFS approval and collaboration concerning agile innovation. The Shelf Charter’s utility overwhelmingly fits Bank.org’s case. - Let’s be honest with each other: All the money in the world will not solve anything without DFS collaboration concerning radical innovation. -------- For the reasons above and known generally, xNY.io and Bank.org are now seeking DFS’ ACCELERATED review and collaboration for Shelf Charter status. We hope you share our enthusiasm and willingness of granting 2021 Shelf Charter approval, for all people everywhere. -------- We look forward to our long term innovation relationship under your historic regulatory oversight. Respectfully yours with anticipation, Gunnar Larson - xNY.io <http://www.xny.io> | Bank.org <http://bank.org>MSc <https://www.unic.ac.cy/blockchain/msc-digital-currency/?utm_source=Google&u…> - Digital Currency MBA <https://www.unic.ac.cy/business-administration-entrepreneurship-and-innovat…> - Entrepreneurship and Innovation (ip) G(a)xNY.io +1-646-454-9107

1 0

*SPAM* Re: COVID-19 Fake Vaccine Causing Magnitism
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Sat, 15 May 2021 12:42:32 -0400 Karl <gmkarl(a)gmail.com> wrote: > - I received the Pfizer vaccine. It included misleading marketing showing > the corporation was valuing profit over public health. how is that misleading? Of course they value profit over 'public health' whatever you think 'public health' is. Content analysis details: (5.3 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: tfwno.gf] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header

2 1

*SPAM* yet another false positive
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Begin forwarded message: Date: Thu, 20 May 2021 17:41:09 -0300 From: "Punk-BatSoup-Stasi 2.0" <punks(a)tfwno.gf> To: cypherpunks(a)lists.cpunks.org Subject: *SPAM* Re: COVID-19 Fake Vaccine Causing Magnitism Content analysis details: (8.0 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: spamhaus.org] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [37.120.193.122 listed in list.dnswl.org] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

*SPAM* another false positive
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Begin forwarded message: Date: Wed, 19 May 2021 22:03:13 -0300 From: "Punk-BatSoup-Stasi 2.0" <punks(a)tfwno.gf> To: cypherpunks(a)lists.cpunks.org Subject: *SPAM* Re: *SPAM* RE: DAN KAMINSKY DIES FROM VACCINE Content analysis details: (8.0 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: dnswl.org] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [37.120.193.122 listed in list.dnswl.org] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

*SPAM* Re: The Register: Kiss goodbye to privacy forever
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Wed, 19 May 2021 06:44:38 +0000 (UTC) jim bell <jdb10987(a)yahoo.com> wrote: > The Register: Kiss goodbye to privacy forever when brain-implanted comms gear becomes the norm â guru Whit Diffie. > https://go.theregister.com/feed/www.theregister.com/2021/05/17/rsa_cryptogr… [...] Content analysis details: (5.3 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: tfwno.gf] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [37.120.193.122 listed in list.dnswl.org] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header

1 0

*SPAM* Re: Facebook urged to abandon encryption plans after child abuse reports halve
by Punk-BatSoup-Stasi 2.0 20 May '21

20 May '21

Spam detection software, running on the system "mail.pglaf.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Sun, 16 May 2021 16:15:41 -0400 Karl <gmkarl(a)gmail.com> wrote: > On 5/16/21, jim bell <jdb10987(a)yahoo.com> wrote: > > https://news.yahoo.com/facebook-urged-abandon-encryption-plans-070553456.ht… > > > > Facebook has been urged to halt its encryption plans after [...] Content analysis details: (5.3 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [37.120.193.122 listed in zen.spamhaus.org] 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <https://www.spamcop.net/bl.shtml?37.120.193.122>] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: tfwno.gf] 1.3 RCVD_IN_VALIDITY_RPBL RBL: Relay in Validity RPBL, https://senderscore.org/blocklistlookup/ [37.120.193.122 listed in bl.score.senderscore.com] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [37.120.193.122 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS 0.5 MISSING_MID Missing Message-Id: header

1 0

COVID-19 Fake Vaccine Causing Magnitism
by Se7en 20 May '21

20 May '21

Today, after hearing the comments on COVID-19 "Vax" leading to odd reports of magnitism and hightened EMF Radiation, I tested my grandfather's arm using refrigerator magnets. He has had "both" jabs, in the same general area (his upper-right arm). I can confirm that his arm is magnitized, and the multiple magnets I used to test the alligations all stuck to his arm using the magnetic force. I do not have the ability to test for EMF. Video regarding Magnitism from COVID-19 Vax: https://banned.video/watch?id=609d47912fabdb2756bbbb5f -- |-----/ | Se7en / The One and Only! | se7en(a)cock.email / | 0x0F83F93882CF6116 / | https://se7en-site.neocities.org

6 21

Ticket Racket: Global Govts Road Pirates Loot and Steal, Monetizing Your Slavery
by grarpamp 20 May '21

20 May '21

No injuries, no crashes... nothing at all, literally no crime, no harm, no tort, no fraud... nothing... except the criminal theft of your money by Governments, and permanent spyveillance tracking of your travels, and biometric invasion, by the control State. Literally as ridiculous as the laughable idea that you need a "license" to drive and conduct yourself from one place to another. The amount of buggery you sheeple apparently enjoy taking from them... appears quite endless and deep indeed. Shame on you. https://www.aier.org/article/governing-as-looting-in-washington-and-beyond/ https://mises.org/wire/dystopian-future-which-almost-no-one-owns-car "Governing As Looting" In Washington & Beyond Authored by James Bovard via The American Institute for Economic Research, A single camera in D.C. generated more than a hundred thousand tickets and $11 million in fines. At what point does a democracy become a kleptocracy? That type of degeneration routinely happens in Third World regimes but the same blight can occur in the United States. Few things epitomize “governing as looting” like the automated traffic ticket cameras that hundreds of local governments have inflicted on drivers across the nation. In 2015, the Missouri Supreme Court struck down St. Louis’s red light camera ticket regime for violating the U.S. Constitution because drivers were forced to prove they were innocent. But elsewhere, mayors and bureaucrats have not permitted constitutional rights to impede their fervent pursuit of revenue. Some of the most brazen abuses occur in the District of Columbia, which issues almost a million speed camera tickets each year. The American Automobile Association (AAA) denounced one D.C. speed camera near the Maryland border as “an old-fashioned, money-making, motorist rip-off speed trap right out of the ‘Dukes of Hazzard.” A single camera in D.C. generated more than a hundred thousand tickets and $11 million in fines. The combinations of speed cameras and shameless bureaucrats can cast citizens into a Kafkaesque hell. Last November 2, Doug Nelson, a 73-year-old Postal Service employee and Vietnam veteran, was carjacked as he returned home from a late shift. Nelson quickly surrendered his vehicle to the pistol-wielding assailants. He filed a police report and his car was eventually recovered but the license plates were stolen by the thieves. In the following weeks, Nelson was stunned to receive thousands of dollars in tickets for speed camera violations spurred by the thieves who stole his car. Nelson and his wife repeatedly notified the D.C. government of the unjust fines but their complaints were ignored. Because of the fines, they were prohibited from getting a new license plate and thus banned from driving their only vehicle. They were told they would have to pay the entire fine – which quickly rose to $5,000 – before they were permitted to formally challenge the penalties. Nelson’s experience exemplifies how “due process” nowadays means any damn process government does. The District has a Ticket Adjudication Ombudsman to deal with cases of gross injustice. But because Nelson failed to speedily file a “Reconsideration or a Motion to Vacate,” he was prohibited from any relief. A local television station put its “I-Team” on the case but D.C. government officials refused to sit down for a televised interview. But the embarrassing publicity finally spurred the city to finally cancel the fines. As Hannah Cox of the Foundation for Economic Education observed, “The District of Columbia unjustly deprived the Nelsons of the use of their car for far longer than the carjackers did.” The District is one of the more than 400 municipalities, including most of the nation’s largest cities, that have imposed red light cameras on their streets in recent decades. Red light cameras are notorious for increasing traffic collisions because they spur drivers to seek to stop suddenly to avoid being fined. In 2005, six years after the District of Columbia set up a red light regime that generated more than 500,000 tickets, a Washington Post analysis revealed that “the number of crashes at locations with cameras more than doubled.” The Florida Department of Highway Safety and Motor Vehicles analyzed traffic crash data and reported in 2016 that “fatalities from accidents doubled” at intersections with red-light cameras. A Virginia Department of Transportation study concluded that cameras were associated with a 29% “increase in total crashes.” But policies that needlessly kill some citizens are worthwhile if they boost government revenue, at least according to the political morality prevailing in many cities. Numerous federal studies have shown that the most effective step to reduce collisions at traffic lights is to lengthen the time of the yellow light to allow drivers more time to stop. A Federal Highway Administration report concluded that “a one second increase in yellow time results in 40 percent decrease in severe red light related crashes.” But in 2015, the District shortened the yellow lights at many intersections and the number of red light tickets skyrocketed. Some of the private companies that install and maintain red light cameras have contract provisions prohibiting cities from extending yellow lights because it would hurt their profits. The vast majority of red light tickets are slapped on drivers who make right turns on red without coming to a dead stop. The National Highway Traffic Safety Administration concluded that zero fatalities occurred nationwide in 1998 “from an accident resulting from a right hand turn on red when the driver yielded to oncoming traffic.” AAA spokesman John Townsend labeled right-turn-on-red cameras as “the biggest scandal in automated traffic enforcement.” Despite a blizzard of automated penalties, traffic fatalities sharply increased in D.C. in recent years. So the mayor and City Council last year voted to triple the number of red light cameras and slashed the speed limit on most city streets to 20 miles per hour, creating new Yukon Territories for speed cameras. Mayor Muriel Bowser is a zealous champion of “Vision Zero” policies and she proclaimed a goal of zero traffic fatalities by 2024. That will never happen but her bogus idealism sanctifies tyrannizing drivers regardless. Foul play is fair play as long as government profits. In 2018, the City Council enacted the Clean Hands Law, which prohibited driver license renewals for anyone with more than $100 in debt to the D.C. government. But local officials are not required to have “Clean Hands.” The D.C. Inspector General found that the automated ticketing system was so out of control that “drivers get speeding tickets for violations they don’t commit and for vehicles they’ve never owned.” The IG slammed the government for issuing tickets “without conclusive identification of the violating vehicle.” City bureaucrats were proud of how the ticketing system was rigged. A senior D.C. government official declared, “You are guilty until you have proven yourself innocent… That has worked well for us.” D.C. police and transportation officials responded with a statement scoffing that complaints “generally come from those relatively few people who feel entitled to speed on District streets or run red lights.” But hundreds of thousands of drivers have been nailed by a regime that is intentionally reckless and unjust. Mayor Bowser is a proud champion of social justice and last year renamed a street in front of the White House as “Black Lives Matter Plaza” and painted that slogan on the asphalt in giant yellow letters. But Bowser, like other D.C. politicians, ignores how their ticketing racketeering punishes the city’s neediest residents. According to a 2018 report by D.C. Policy Center, a think tank, “Neighborhoods where 80 percent or more of residents are black on average paid $322 per capita in automated traffic tickets compared to just $20 per capita in 80 percent white neighborhoods. Residents in black neighborhoods were 17 times more likely to receive a photo ticket.” But black neighborhoods did not have a higher rate of auto crashes than other neighborhoods. Unnecessary and unjust tickets disrupt lives and destroy people’s ability to feed their families. A 2019 study by the Federal Reserve concluded that almost half of Americans “could not afford an unexpected expense of $400 or more.” The National Motorist Association warned, “The practical results for many poor people may be a lot like putting them in debtor prisons, unable to legally drive to work.” In 2018, the D.C. government created a “community service option” where low-income traffic violators could pay off tickets by working unpaid for the city at the minimum wage rate. At least the city has not yet created chain gangs sweating to pay their speed cameras debts. The depredations of automatic ticket enforcement presume that government revenue is a magic wand that solves all problems. But surging revenue has done nothing to prevent the D.C. government from dismally failing its residents. The murder rate is soaring and the schools were dismally failing to educate low-income students even before the pandemic. The city would have collapsed to Baltimorean-levels of debility if not for the endless revenue streams from the federal government and its accompanying graft. Ticket cameras epitomize how democracy provides no protection against politicians willing to force citizens to pay any price to boost government revenue. The Berkeley Journal of Criminal Law noted last month, “Automated enforcement has also failed at the ballot box; red light and/or speed cameras were voted down in 39 of 43 local elections where the initiative appeared as a referendum.” But local politicians insulate themselves, buying support from other groups and blocking citizens from having a chance to pass judgment on at the polling booths. Automatic ticket regimes have turbocharged many politicians’ lifestyles. Bribery scandals have enveloped automated ticketing regimes in Texas, Arizona, Ohio, Illinois, and elsewhere. The former top salesman for Redflex, one of the largest providers of red light cameras, testified that his company had “sent gifts and bribes to officials in at least 14 states.” (Redflex denied the allegation.) Last year, Illinois Comptroller Susana Mendoza condemned red light ticket regimes as “a program that’s broken and morally corrupt” and recommended ending them across the state. Automatic ticketing regimes provide a stark refutation to the illusion that governments automatically serve the people. Especially for policies shrouded in sanctimony, government agencies are almost always more wasteful or oppressive than the media portrays. How much longer will local politicians be permitted to plunder drivers and subvert safety with impunity?

1 0