@MSGID: 2:221/1.59 65dffe95
@REPLY: 1:153/7001.2989 65dfcb37
@TZUTC: -0500
@CHRS: CP437
On 29 Feb. 2024 00:09, you wrote to August:

MK> More reason NOT to let developers lead the standardization process,
 MK> nevermind the users of their apps.  There is definetly a confict of
 MK> interest, nevermind the ones who are clueless as to how things REALLY
 MK> work.

 Are you familiar with the UTF-8 echo? Perhaps it was set up to
help promote utf-8 inclusion and use. But the chars get little to low
use overall - that is why I`m surprised that utf-8 was included in a
standard. 

 Yeah.. double-standards and inconsistency never seems to escape the
ones wearing the hats. :D
--- AfterShock/Android 1.7.5
 * Origin: Mobile Pixel 3aXL (2:221/1.59)
SEEN-BY: 1/120 18/0 50/109 103/705 120/616 123/0
10 25 126 180 200 755 3001
SEEN-BY: 124/5016 135/115 153/757 7001 7715 154/10
30 40 50 700 203/0 220/90
SEEN-BY: 221/1 6 360 222/2 226/18 70 240/1120
1120 5832 250/1 280/464 5003
SEEN-BY: 292/8125 299/6 301/1 310/31 320/219 341/66
234 396/45 423/81 460/58
SEEN-BY: 467/888 633/280 712/848 1321 770/1
2320/105 3634/0 12 27 56 57 119
SEEN-BY: 4500/1 5001/100 5005/49 5019/40 5020/400
715 848 1042 4441 12000
SEEN-BY: 5030/49 1081 5054/8 5061/133 5075/128
5090/958
@PATH: 221/1 280/464 154/10 3634/12 5020/1042
4441