get the sourcecode [of UTF-8]

[A bughunter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

My reply to Doug. Julian , Otto,  Jim and all you attackers.

"focus on the originating question because as you see I was dumped on with over 5 pages of unrelated and offtopic nonsense in reply to my single line question. " ( https://corp.unicode.org/pipermail/unicode/2024-November/011111.html )

" with about 18 pages of replies it is getting hard to track and some mail I couldn't even find before replying, " ( https://corp.unicode.org/pipermail/unicode/2024-November/011139.html )

begun Sat Nov 2 19:42:46 CDT 2024 25 replies from 12 senders. Notice they all instantly pose arguments and personal attacks against me whilst babbling on with conflicting, scattered, and wrong technical jargon. Because these posts betwixt each other contradict and conflict each other you might expect those posters would correct each other but no all 25 mails by 12 guys target the inquirer. 

Here is an example of one all you attackers could have corrected:

@Julian says "There are no codepages in Unicode. (Or I suppose there is exactly
one.)" ( https://corp.unicode.org/pipermail/unicode/2024-November/011116.html )

does conflict with

@Otto says "UTF-8 is one method (of a handfull of standardized methods) to represent Unicode text at the bit level in order to conveniently transfer, or store, it." ( https://corp.unicode.org/pipermail/unicode/2024-November/011132.html )

@Jim says he is putting up a post like a seeing eye dog by pasting from my GitHub ( https://www.github.com/freedom-foundation ) "I summarised what I understand of your project as a courtesy to my fellow unicode-list subscribers. "

I chuse this example because it goes to show that Unicode consortium is disappointed. You will probably read in there somewhere that it intended to solve a problem of many codepages hower you see that it has become something more complicated than the problem it were to simplify to solve.

from A_bughunter at proton.me

Sent with Proton Mail secure email.

On Thursday, November 7th, 2024 at 05:25, Doug Ewell via Unicode <unicode at corp.unicode.org> wrote:

> Many companies, fearful that their employees may click on malicious links in emails and put the business at risk, have begun sending out so-called “phish alert” messages. These are simulated phishing emails that contain many of the tell-tale signs of real attacks, complete with phony links that redirect to the company’s IT department. The object is to see how many, and perhaps which, employees report the email as phishing and how many take the bait and click on the links.
> 
> I feel like we are living inside such an experiment with this thread.
> 
> --
> Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmctlQIJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu
8pkAAOAMAQDOLUYx2VnvbtEIMrHfl0WM1kF1lhvDXQd5Wpob8s6jeAEA9BmR
mLEFEOp6R4/s7o+XQNfaswCmNuI65a6rHEsi0Ao=
=j6r0
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - A_bughunter at proton.me - 0x66540805.asc
Type: application/pgp-keys
Size: 653 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20241108/b65cfce1/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - A_bughunter at proton.me - 0x66540805.asc.sig
Type: application/pgp-signature
Size: 119 bytes
Desc: not available
URL: <https://corp.unicode.org/pipermail/unicode/attachments/20241108/b65cfce1/attachment-0001.sig>