From Newsgroup: comp.misc

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------McartRHxdbwECLYGtyLlROmn
Content-Type: multipart/mixed; boundary="------------Tt8my9EQNXhQlE93lqBKz0mM";
protected-headers="v1"
From: Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Newsgroups: comp.misc,alt.comp
Subject: Better colorscheme than Solarized?

--------------Tt8my9EQNXhQlE93lqBKz0mM
Content-Type: multipart/mixed; boundary="------------mmNZ03EhTrk2EIAXSj0QuBYT"

--------------mmNZ03EhTrk2EIAXSj0QuBYT
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

DQpIZWxsbyENCg0KSSdtIGxvb2tpbmcgZm9yIGEgY29sb3Igc2NoZW1lIHRoYXQncyBiZXR0 ZXIgdGhhbiBTb2xhcml6ZWQuICDigItXaGlsZSBpIA0KZG8gbGlrZSBTb2xhcml6ZWQgKGVz cGVjaWFsbHkgdGhlIDI1Ni1jb2xvciBTb2xhcml6ZWQpLCB0aGVyZSBhcmUgYSBmZXcgDQpw cm9ibGVtcyB0aGF0IGkgaGF2ZSB3aXRoIGl0LCBzdWNoIGFzIHRoZSB3YXkgdGhhdCB0aGUg cGFsZXR0ZSBmYWlscyB0byANCm1hcCB0byB0aGUgdHJhZGl0aW9uYWwgMTYtY29sb3IgcGFs ZXR0ZSBhbmQgdGhlIHNvbWV3aGF0IHN0cmFuZ2UgDQppbWJhbGFuY2VzIGluIHNvbWUgb2Yg dGhlIGNvbG9ycy4gIFNvIHdoYXQgaSdtIGxvb2tpbmcgZm9yIGlzIGEgY29sb3IgDQpzY2hl bWUgbGlrZSB0aGlzOg0KDQotIEFib3V0IHRoZSBzYW1lIGxldmVsIG9mIGNvbnRyYXN0IGFz IFNvbGFyaXplZA0KLSBFYXNpbHkgaW52ZXJ0aWJsZSwgbGlrZSB3aGF0IFNvbGFyaXplZCBk b2VzDQotIE1hcHMgdG8gdGhlIHRyYWRpdGlvbmFsIDE2LWNvbG9yIHBhbGV0dGUgKGkuZS4g aGFzIGJyaWdodCBhbmQgZGFya3Mgb2YgDQp0aGUgcHJpbWFyaWVzLCBzZWNvbmRhcmllcywg YmxhY2ssIGFuZCB3aGl0ZSkNCi0gQ29sb3JzIGFyZSBiYWxhbmNlZCBhbmQgbm90IGJpYXNl ZCB0b3dhcmRzIGFueSBwYXJ0aWN1bGFyIGNvbG9yIChlLmcuIA0Kbm90IHdhcm0tIG9yIGNv b2wtbGVhbmluZykNCi0gRG9lc24ndCBtYWtlIGFzc3VtcHRpb25zIGFib3V0IGhvdyBpdCB3 aWxsIGJlIHVzZWQgKGUuZy4gZG9lc24ndCBnbyANCiJyZWQgc2hvdWxkIGJlIG1vcmUgaW50 ZW5zZSBiZWNhdXNlIGl0J3Mgb2Z0ZW4gdXNlZCBmb3Igd2FybmluZ3MiIG9yIA0Kc29tZSBi dWxsc2hpdCBsaWtlIHRoYXQpDQoNCkRvZXMgYW55b25lIGtub3cgb2Ygc29tZXRoaW5nIHRo YXQgZml0cyB0aGUgYmlsbD8NCg0KLS0gDQovYmx1Lm3Jm2luLmTKsGFrLyB8IHNob3J0ZW5z IHRvICJIYXdrIiB8IGhlL2hpbS9oaXMvaGltc2VsZi9Nci4NCmJsdWVtYW5lZGhhd2suZ2l0 aHViLmlvDQpJIHRoaW5rIG15IFVzZW5ldCBwcm92aWRlciBzdG9yZXMgdGhlaXIgdXNlcnMn IGFjY291bnRzJyBwYXNzd29yZHMgaW4gDQpwbGFpbiB0ZXh0LiAgSWYgaSdtIGFjdGluZyBz dXNwaWNpb3VzbHksIGNoYW5jZXMgYXJlIHRoYXQgdGhhdCBiYWNrZmlyZWQgDQpvbiB0aGVt
Lg0K
--------------mmNZ03EhTrk2EIAXSj0QuBYT
Content-Type: application/pgp-keys; name="OpenPGP_0x0D8C69D9C42BA5C8.asc" Content-Disposition: attachment; filename="OpenPGP_0x0D8C69D9C42BA5C8.asc" Content-Description: OpenPGP public key
Content-Transfer-Encoding: quoted-printable

-----BEGIN PGP PUBLIC KEY BLOCK-----

xjMEYxaDphYJKwYBBAHaRw8BAQdAUe6dogfbVLWO2sZL0eYioBqrlDcMAS2iOPk/ JtAsPn7NKUJsdWUtTWFuZWRfSGF3ayA8Ymx1ZW1hbmVkaGF3a0BnbWFpbC5jb20+ wokEExYIADEWIQRyCHAqodVWYEd5ANANjGnZxCulyAUCYxaDpgIbAwQLCQgHBRUI CQoLBRYCAwEAAAoJEA2MadnEK6XIE3QBAPwF9MRW659ePa7L5sxbsZZOBqRbGXsA XczlrKrxzeSxAQDhFiK3bYSzYLsP7MRuLz7P/DtAe6fzqNZp6ab1yDGrCc44BGMW g6YSCisGAQQBl1UBBQEBB0ArdZWeQkNjCCbAlw5tg4i+zPh9zIzvmDwpHrkgz5XE YQMBCAfCeAQYFggAIBYhBHIIcCqh1VZgR3kA0A2MadnEK6XIBQJjFoOmAhsMAAoJ EA2MadnEK6XIk1MBAPnNFbnBPXCJtWLUZjC/vZo8VPMuXHd5lCp2UeAi3x8xAQCS TqAJETrOQMTOd9dM/AYq3xwYUfDJ5hBSbNEn/lXyDg=3D=3D
=3Dat/d
-----END PGP PUBLIC KEY BLOCK-----

--------------mmNZ03EhTrk2EIAXSj0QuBYT--

--------------Tt8my9EQNXhQlE93lqBKz0mM--

--------------McartRHxdbwECLYGtyLlROmn
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQRyCHAqodVWYEd5ANANjGnZxCulyAUCYzkzfgUDAAAAAAAKCRANjGnZxCulyDYY AQDrekU++BCQHwrOlZTuHQH7H8Oztng6Fc7heYifTPGzWQD8Cm/0bUjAKYyBzyysXRf5K18ftUO1 iycSGyWktd0uVgo=
=7X5A
-----END PGP SIGNATURE-----

--------------McartRHxdbwECLYGtyLlROmn--

--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On 2022-10-02, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

And this is a plain text response, pointing out I couldn't read a word
of your message. But hey.
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

In comp.misc, Retrograde <fungus@amongus.com.invalid> wrote:

On 2022-10-02, Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)

And this is a plain text response, pointing out I couldn't read a word
of your message. But hey.

That's okay. I read his message and I have no idea what he's asking for.
He doesn't mention a program or operating system, and asks for opinions
on color scheme named after a black and white photography process, so
he's likely just going to be sad.

https://en.wikipedia.org/wiki/Solarization_(photography)

Elijah
------
Photoshop has (or had) a Sabattier effect misnamed as "Solarize"
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Eli the Bearded <*@eli.users.panix.com> wrote:

That's okay. I read his message and I have no idea what he's asking
for. He doesn't mention a program or operating system, and asks for
opinions on color scheme named after a black and white photography
process, so he's likely just going to be sad.

https://en.wikipedia.org/wiki/Solarization_(photography)

I believe Solarized is operating system independent,
so technically these are the correct newsgroups?

Solarized is a color scheme for code editors and terminal
emulators created by Ethan Schoonover. The scheme is
available in a Light and a Dark mode. Packages that implement
the color scheme have been published for many major
applications, with some including the scheme pre-installed.
-- https://en.wikipedia.org/wiki/Solarized

Wikipedia's widely inconsistent metrics for software project
notability always baffles me. Solarized is important enough to
merit its own page, however things like rocket.chat aren't?
--
/* * * Otto J. Makela <om@iki.fi> * * * * * * * * * */
/* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
/* Mail: Mechelininkatu 26 B 27, FI-00100 Helsinki */
/* * * Computers Rule 01001111 01001011 * * * * * * */
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------IeZlNQrwtzcdLS05TiXk9TYS
Content-Type: multipart/mixed; boundary="------------el0uOEVT5fXliVXfuOdkiLnC";
protected-headers="v1"
From: Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Newsgroups: comp.misc
Subject: Re: Better colorscheme than Solarized?
References: <thbc1u$1kurt$16@dont-email.me> <egvj1j-rv6.ln1@berry.solani.net> In-Reply-To: <egvj1j-rv6.ln1@berry.solani.net>

--------------el0uOEVT5fXliVXfuOdkiLnC
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

T24gMTAvMTIvMjIgMTk6MzQsIFJldHJvZ3JhZGUgd3JvdGU6DQo+IE9uIDIwMjItMTAtMDIs IEJsdWUtTWFuZWRfSGF3ayA8Ymx1ZW1hbmVkaGF3a0BnbWFpbC5jb20+IHdyb3RlOg0KPj4g VGhpcyBpcyBhbiBPcGVuUEdQL01JTUUgc2lnbmVkIG1lc3NhZ2UgKFJGQyA0ODgwIGFuZCAz MTU2KQ0KPiANCj4gQW5kIHRoaXMgaXMgYSBwbGFpbiB0ZXh0IHJlc3BvbnNlLCBwb2ludGlu ZyBvdXQgSSBjb3VsZG4ndCByZWFkIGEgd29yZA0KPiBvZiB5b3VyIG1lc3NhZ2UuICBCdXQg aGV5Lg0KDQrigItJJ20gc29ycnkuICBJIGRvbid0IGtub3cgd2h5IFRodW5kZXJiaXJkIGlz IG1ha2luZyBteSBtZXNzYWdlcyANCm5vdC1wbGFpbi10ZXh0LCBhbmQgaSBkb24ndCBrbm93 IGhvdyB0byB0dXJuIGl0IG9mZi4NCg0KLS0gDQovYmx1Lm3Jm2luLmTKsGFrLyB8IHNob3J0 ZW5zIHRvICJIYXdrIiB8IGhlL2hpbS9oaXMvaGltc2VsZi9Nci4NCmJsdWVtYW5lZGhhd2su Z2l0aHViLmlvDQpJIHRoaW5rIG15IFVzZW5ldCBwcm92aWRlciBzdG9yZXMgdGhlaXIgdXNl cnMnIGFjY291bnRzJyBwYXNzd29yZHMgaW4gDQpwbGFpbiB0ZXh0LiAgSWYgaSdtIGFjdGlu ZyB1bnVzdWFsbHksIHRoYXQgcHJvYmFibHkgYmFja2ZpcmVkIG9uIHRoZW0uDQoNCg==

--------------el0uOEVT5fXliVXfuOdkiLnC--

--------------IeZlNQrwtzcdLS05TiXk9TYS
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQRyCHAqodVWYEd5ANANjGnZxCulyAUCY0juWgUDAAAAAAAKCRANjGnZxCulyJjx AP9csxwNWfR9YRmhVz66uLiG89JWzXjje389H3E6fCu73gD8DHKFy3bGx+64aAGgSgJ0nz1e0iE0 K43yr/jwxl4VHQ0=
=50f+
-----END PGP SIGNATURE-----

--------------IeZlNQrwtzcdLS05TiXk9TYS--

--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------EKd7DC0tIxhFP8tnO0KpS7Un
Content-Type: multipart/mixed; boundary="------------0nbGm0fHGFwu4hLYbIPpKaHD";
protected-headers="v1"
From: Blue-Maned_Hawk <bluemanedhawk@gmail.com>
Newsgroups: comp.misc
Subject: Re: Better colorscheme than Solarized?
References: <thbc1u$1kurt$16@dont-email.me> <egvj1j-rv6.ln1@berry.solani.net>
<eli$2210122336@qaz.wtf> <87o7ug9nx6.fsf@tigger.extechop.net>
In-Reply-To: <87o7ug9nx6.fsf@tigger.extechop.net>

--------------0nbGm0fHGFwu4hLYbIPpKaHD
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

T24gMTAvMTMvMjIgMDM6MzUsIE90dG8gSi4gTWFrZWxhIHdyb3RlOg0KPiBFbGkgdGhlIEJl YXJkZWQgPCpAZWxpLnVzZXJzLnBhbml4LmNvbT4gd3JvdGU6DQo+IA0KPiBbc25pcF0NCj4g CQktLSBodHRwczovL2VuLndpa2lwZWRpYS5vcmcvd2lraS9Tb2xhcml6ZWQNCj4gW3NuaXBd DQoNCuKAi1llcywgdGhpcyBpcyB0aGUgY29sb3JzY2hlbWUgaSdtIHJlZmVycmluZyB0bywg YW5kIGkgd2FudCBzb21ldGhpbmcgDQpiZXR0ZXIgdGhhbiBpdC4NCg0KLS0gDQovYmx1Lm3J m2luLmTKsGFrLyB8IHNob3J0ZW5zIHRvICJIYXdrIiB8IGhlL2hpbS9oaXMvaGltc2VsZi9N ci4NCmJsdWVtYW5lZGhhd2suZ2l0aHViLmlvDQpJIHRoaW5rIG15IFVzZW5ldCBwcm92aWRl ciBzdG9yZXMgdGhlaXIgdXNlcnMnIGFjY291bnRzJyBwYXNzd29yZHMgaW4gDQpwbGFpbiB0 ZXh0LiAgSWYgaSdtIGFjdGluZyB1bnVzdWFsbHksIHRoYXQgcHJvYmFibHkgYmFja2ZpcmVk IG9uIHRoZW0uDQoNCg==

--------------0nbGm0fHGFwu4hLYbIPpKaHD--

--------------EKd7DC0tIxhFP8tnO0KpS7Un
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQRyCHAqodVWYEd5ANANjGnZxCulyAUCY0jwDAUDAAAAAAAKCRANjGnZxCulyBOH AQDhdkPemf45vvgE7ETnYNMlPZ0jU3OMwfRcBiqSwO8NLQEAjJ0xxDVEMpKqdoY1L06lM86CQHkA bokqZYwNv8n/7wk=
=lv08
-----END PGP SIGNATURE-----

--------------EKd7DC0tIxhFP8tnO0KpS7Un--

--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

​I'm sorry. I don't know why Thunderbird is making my messages not-plain-text, and i don't know how to turn it off.

There are two things: your signature block contains UTF-8 characters,
and you have PGP signing enabled.

Your message is however properly formed, and Gnus v5.13 is able to
decode it correctly. Apparently slrn/1.0.3 isn't.
--
/* * * Otto J. Makela <om@iki.fi> * * * * * * * * * */
/* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
/* Mail: Mechelininkatu 26 B 27, FI-00100 Helsinki */
/* * * Computers Rule 01001111 01001011 * * * * * * */
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On Fri, 14 Oct 2022 10:16:03 +0300
om@iki.fi (Otto J. Makela) wrote:

Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

I'm sorry. I don't know why Thunderbird is making my messages not-plain-text, and i don't know how to turn it off.

There are two things: your signature block contains UTF-8 characters,
and you have PGP signing enabled.

Your message is however properly formed, and Gnus v5.13 is able to
decode it correctly. Apparently slrn/1.0.3 isn't.

My guess is that what's causing problems for some people is that Hawk's posts are BASE64 encoded. I don't know why Thunderbird does that but there do exist news.software.newsreaders and alt.comp.software.newsreaders for such questions.
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Spiros Bousbouras <spibou@gmail.com> wrote:

On Fri, 14 Oct 2022 10:16:03 +0300
om@iki.fi (Otto J. Makela) wrote:

Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

I'm sorry. I don't know why Thunderbird is making my messages
not-plain-text, and i don't know how to turn it off.

There are two things: your signature block contains UTF-8 characters,
and you have PGP signing enabled.

Your message is however properly formed, and Gnus v5.13 is able to
decode it correctly. Apparently slrn/1.0.3 isn't.

My guess is that what's causing problems for some people is that
Hawk's posts are BASE64 encoded. I don't know why Thunderbird does
that but there do exist news.software.newsreaders and alt.comp.software.newsreaders for such questions.

Indeed; I took it as implied that UTF-8 characters in the signature
block causes this need for encoding, and for some reason base64 gets
selected, instead of the (in this case) more frugal quoted-printable.

Followup-to: alt.comp.software.thunderbird,news.software.newsreaders,alt.comp.software.newsreaders
--
/* * * Otto J. Makela <om@iki.fi> * * * * * * * * * */
/* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
/* Mail: Mechelininkatu 26 B 27, FI-00100 Helsinki */
/* * * Computers Rule 01001111 01001011 * * * * * * */
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On 2022-10-14, Otto J. Makela <om@iki.fi> wrote:

There are two things: your signature block contains UTF-8 characters,
and you have PGP signing enabled.

Your message is however properly formed, and Gnus v5.13 is able to
decode it correctly. Apparently slrn/1.0.3 isn't.

Interesting observation, so I tested, and you are right. Emacs
26.3/gnus 5.13 handles it effortlessly, while slrn does not.
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On Fri, 14 Oct 2022 15:18:36 +0300
om@iki.fi (Otto J. Makela) wrote:

Spiros Bousbouras <spibou@gmail.com> wrote:

My guess is that what's causing problems for some people is that
Hawk's posts are BASE64 encoded. I don't know why Thunderbird does
that but there do exist news.software.newsreaders and alt.comp.software.newsreaders for such questions.

Indeed; I took it as implied that UTF-8 characters in the signature
block causes this need for encoding, and for some reason base64 gets selected, instead of the (in this case) more frugal quoted-printable.

But , as the recent thread (on comp.misc) "in praise of text files" showed , 8 bit characters go through just fine with no need for encoding. It may be
that thunderbird decided to use BASE64 because Hawk's post contains some
octets with value > 127 but there was no need for the programme to do any encoding.

If one does decide to use encoding , on usenet quoted-printable seems safer than BASE64. I've never seen complaints about quoted-printable posts but
I've seen complaints by people whose newsreaders apparently don't decode
BASE64 posts. Also the news2.informatik.uni-stuttgart.de newsserver often drops BASE64 encoded posts. For example thbc1u$1kurt$16@dont-email.me (the opening post of this thread) does not appear at all on that server although posts from earlier dates do.

Followup-to: alt.comp.software.thunderbird,news.software.newsreaders,alt.comp.software.newsreaders

By the way , the post I'm responding to does not appear on news.aioe.org presumably because you have crossposted to too many newsgroups.
--
Visceral importance and interpretative subtlety are, sadly, inversely proportional.
That, of course, is the great frustration of history as an intellectual pursuit: the
further the event recedes and fades, the more refined our understanding, the less
anyone cares.
Peter Baldwin
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Spiros Bousbouras wrote:

On Fri, 14 Oct 2022 15:18:36 +0300 om@iki.fi (Otto J. Makela) wrote:

[...]
Followup-to: alt.comp.software.thunderbird,news.software.newsreaders,alt.comp.software.newsreaders

By the way , the post I'm responding to does not appear on news.aioe.org presumably because you have crossposted to too many newsgroups.

It seems that some of the groups does not exist, e.g. "news.software.newsreaders" and "alt.comp.software.newsreaders".

But the group "news.software.readers" exists
(<news:news.software.readers>, if your newsreader supports URIs).


[Xpost reduced]
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Michael Bäuerle <michael.baeuerle@stz-e.de> wrote:

But the group "news.software.readers" exists

Confirmed: I have lurked there since before Blinky died.
To get attention in that group put [your newseader]
including the square brackets in the Subject line;
otherwise you are likely to be ignored.
--
^Ï^. My pet rock Gordon just is.

~ Slava Ukraini ~
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Blue-Maned_Hawk <bluemanedhawk@gmail.com> writes:

On 10/13/22 03:35, Otto J. Makela wrote:

Eli the Bearded <*@eli.users.panix.com> wrote:
[snip]
-- https://en.wikipedia.org/wiki/Solarized
[snip]

​Yes, this is the colorscheme i'm referring to, and i want something
better than it.

I've been using the Modus themes for Emacs and I nicked the color pallete for that and use that for my Xresources file. I'm not particularly picky when it comes to how my desktop looks. I'd rather
have it readable than fancy.

You said you'd like to have a scheme with more constrast so maybe you
can look into that.

Cheers,
--
Pointless meanderings in a bleak and lonely world.
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

In article <Z2xjxj6GLU0cTiaJR@bongo-ra.co>,
Spiros Bousbouras <spibou@gmail.com> wrote:

On Fri, 14 Oct 2022 10:16:03 +0300
om@iki.fi (Otto J. Makela) wrote:

Blue-Maned_Hawk <bluemanedhawk@gmail.com> wrote:

I'm sorry. I don't know why Thunderbird is making my messages
not-plain-text, and i don't know how to turn it off.

There are two things: your signature block contains UTF-8 characters,
and you have PGP signing enabled.

Your message is however properly formed, and Gnus v5.13 is able to
decode it correctly. Apparently slrn/1.0.3 isn't.

My guess is that what's causing problems for some people is that Hawk's posts >are BASE64 encoded. I don't know why Thunderbird does that but there do exist >news.software.newsreaders and alt.comp.software.newsreaders for such >questions.

They are BASE64 encoded because they are MIME-packed. They are MIME-packed
for the reasons mentioned above, that the signature contains high bit chars
and PGP signing is enabled. When you turn PGP signing on, the signature is
not just appended to the file but sent as a MIME enclosure. Because there
are high bit chars, that MIME enclosure gets BASE64ed.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

kludge@panix.com (Scott Dorsey) writes:

They are BASE64 encoded because they are MIME-packed. They are MIME-packed for the reasons mentioned above, that the signature contains high bit chars and PGP signing is enabled. When you turn PGP signing on, the signature is not just appended to the file but sent as a MIME enclosure. Because there are high bit chars, that MIME enclosure gets BASE64ed.

MIME doesn’t enforce base64. quoted-printable is an option too, and a
more appropriate one for Usenet where half the clients don’t seem to
have been updated since 1995.
--
http://www.greenend.org.uk/rjk/
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Richard Kettlewell <invalid@invalid.invalid> wrote:

kludge@panix.com (Scott Dorsey) writes:

They are BASE64 encoded because they are MIME-packed. They are MIME-packed >> for the reasons mentioned above, that the signature contains high bit chars >> and PGP signing is enabled. When you turn PGP signing on, the signature is >> not just appended to the file but sent as a MIME enclosure. Because there >> are high bit chars, that MIME enclosure gets BASE64ed.

MIME doesn't enforce base64. quoted-printable is an option too, and a
more appropriate one for Usenet where half the clients don't seem to
have been updated since 1995.

This is true, but sadly not all applications developers think this way.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On 16 Oct 2022 13:18:25 -0000
kludge@panix.com (Scott Dorsey) wrote:

In article <Z2xjxj6GLU0cTiaJR@bongo-ra.co>,
Spiros Bousbouras <spibou@gmail.com> wrote:

My guess is that what's causing problems for some people is that Hawk's posts
are BASE64 encoded. I don't know why Thunderbird does that but there do exist
news.software.newsreaders and alt.comp.software.newsreaders for such >questions.

They are BASE64 encoded because they are MIME-packed. They are MIME-packed for the reasons mentioned above, that the signature contains high bit chars and PGP signing is enabled. When you turn PGP signing on, the signature is not just appended to the file but sent as a MIME enclosure. Because there are high bit chars, that MIME enclosure gets BASE64ed.

Is there some RFC which says that it has to be encoded ? In other words , if <thbc1u$1kurt$16@dont-email.me> had

[...]
--------------Tt8my9EQNXhQlE93lqBKz0mM
Content-Type: multipart/mixed; boundary="------------mmNZ03EhTrk2EIAXSj0QuBYT"

--------------mmNZ03EhTrk2EIAXSj0QuBYT
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hello!

I'm looking for a color scheme that's better than Solarized. While i
[...]
/blu.mɛin.dʰak/ | shortens to "Hawk" | he/him/his/himself/Mr.
[...]
--------------mmNZ03EhTrk2EIAXSj0QuBYT
Content-Type: application/pgp-keys; name="OpenPGP_0x0D8C69D9C42BA5C8.asc" Content-Disposition: attachment; filename="OpenPGP_0x0D8C69D9C42BA5C8.asc" Content-Description: OpenPGP public key
Content-Transfer-Encoding: quoted-printable
[...]

, would it violate any RFC ?
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

On Sun, 16 Oct 2022 18:00:28 +0100
Richard Kettlewell <invalid@invalid.invalid> wrote:

kludge@panix.com (Scott Dorsey) writes:

They are BASE64 encoded because they are MIME-packed. They are MIME-packed for the reasons mentioned above, that the signature contains high bit chars and PGP signing is enabled. When you turn PGP signing on, the signature is not just appended to the file but sent as a MIME enclosure. Because there are high bit chars, that MIME enclosure gets BASE64ed.

MIME doesn’t enforce base64. quoted-printable is an option too, and a
more appropriate one for Usenet where half the clients don’t seem to
have been updated since 1995.

If they can otherwise parse the MIME parts correctly , doing BASE64 decoding
is only a few lines of C code. In some languages it would be just calling a function , possibly after importing a package.
--- Synchronet 3.19c-Linux NewsLink 1.113

From Newsgroup: comp.misc

Blue-Maned_Hawk:

I'm looking for a color scheme that's better than
Solarized. While i do like Solarized (especially
the 256-color Solarized), there are a few problems
that i have with it, such as the way that the
palette fails to map to the traditional 16-color
palette and the somewhat strange imbalances in
some of the colors.

I have never seen a 256-color version, nor am inter-
ested in it. The one I know is 16-color:

https://github.com/altercation/solarized

And I don't think it is as good as advertised:

1. Some colors are too similar (red and orange).

2. The light version has perceptually less contrast
than the dark one.

3. The brighnesses are overequalised, whereas some
variation is desirable.

4. The hues and saturations are chosed using the LAB
color model, which, although perceptive, has its
imperfections. The human is the ultimate judge.

So what i'm looking for is a color scheme like
this:

-- About the same level of contrast as Solarized

-- Easily invertible, like what Solarized does

-- Maps to the traditional 16-color palette (i.e.
has bright and darks of the primaries, secon-
daries, black, and white)

-- Colors are balanced and not biased towards any
particular color (e.g. not warm- or cool-lean-
ing)

-- Doesn't make assumptions about how it will be
used (e.g. doesn't go "red should be more in-
tense because it's often used for warnings" or
some bullshit like that)

Does anyone know of something that fits the bill?

No, and I checked lots of ANSI-compatible palettes.
Very manage so much as barely to work in Far, Nor-
ton, and Midnight Commander. I am currenly working
on a improved version of the standard eye-piercing
ANSI palatte with most of your goals except in-
versibility.

P.S.: I can read your articles in Sylpheed, but dis-
approve of their format.
--
() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments
--- Synchronet 3.20a-Linux NewsLink 1.113