Monday, September 10, 2018

Digest for comp.lang.c++@googlegroups.com - 13 updates in 4 topics

boltar@cylonHQ.com: Sep 10 08:51AM

On Fri, 07 Sep 2018 18:20:08 -0400
>> else you say is worth a damn.
 
>And how exactly did uuencoded content specify its character set, and type,
>Einstein?
 
*facepalm*
 
Listen, why not go look up how UTF8 works instead of ever increasingly
demonstrating what an utter muppet you are. UTF8 doesn't need to specify a
character set. Thats the WHOLE FECKING POINT OF IT!
 
Jesus christ...
 
>> FFS utf8 is 8 bit, thats binary as far as usenet is concerned.
 
>No, utf8 is not binary. Try again.
 
Yes, it is. Its an 8 bit format, usenet is 7 bit. You work out the rest you
cretin.
boltar@cylonHQ.com: Sep 10 08:53AM

On Fri, 07 Sep 2018 18:23:29 -0400
 
>> Congratulations, you can't spot irony either.
 
>So, your claim of being an uberhacker, and the 2nd coming of Kevin Mitnick,
>is irony?
 
If I didn't read it I wouldn't believe someone who posts to a group like this
could be as gormless as you. Hey ho, takes all sorts I suppose.
 
>> will come as a surprise to precisely no one.
 
>Indeed. You french are world-famous for your sense of humor. You even think
>that Jerry Lewis is funny.
 
I'm not french. Guess again.
boltar@cylonHQ.com: Sep 10 09:23AM

On Fri, 07 Sep 2018 18:20:08 -0400
>> else you say is worth a damn.
 
>And how exactly did uuencoded content specify its character set, and type,
>Einstein?
 
How did any document specify its character set before MIME came along?
 
>> FFS utf8 is 8 bit, thats binary as far as usenet is concerned.
 
>No, utf8 is not binary. Try again.
 
Its 8 bit, usenet is 7 bit only. You work out the rest.
Sam <sam@email-scan.com>: Sep 10 06:52AM -0400

> >Einstein?
 
> *facepalm*
 
> Listen, why not go look up how UTF8 works instead of ever increasingly
 
I know how UTF8 works.
 
> demonstrating what an utter muppet you are. UTF8 doesn't need to specify a
> character set. Thats the WHOLE FECKING POINT OF IT!
 
The whole fecking point is that a random blob of uuencoded content is
completely context-free. There's nothing about it that says "I contain UTF-8
text". For that, you need MIME. That's what MIME is for. It's not a
complicated concept to understand.
 
 
> >> FFS utf8 is 8 bit, thats binary as far as usenet is concerned.
 
> >No, utf8 is not binary. Try again.
 
> Yes, it is.
 
No, it's not.
 
> Its an 8 bit format, usenet is 7 bit.
 
Usenet hasn't been 7 bit for a long long time. If you insist on living in
ancient history, it's your choice alone and you don't get it to impose on
everyone else, just to make it easy for your obsolete message reader.
 
> You work out the rest you cretin.
 
That's Mr. Cretin to you.
Sam <sam@email-scan.com>: Sep 10 06:52AM -0400


> If I didn't read it I wouldn't believe someone who posts to a group like this
> could be as gormless as you. Hey ho, takes all sorts I suppose.
 
That only shows that you don't know everything.
 
 
> >Indeed. You french are world-famous for your sense of humor. You even think
> >that Jerry Lewis is funny.
 
> I'm not french.
 
I'm pretty sure you are.
Sam <sam@email-scan.com>: Sep 10 06:54AM -0400


> >And how exactly did uuencoded content specify its character set, and type,
> >Einstein?
 
> How did any document specify its character set before MIME came along?
 
It didn't. That's the whole point, Einstein.
 
> >> FFS utf8 is 8 bit, thats binary as far as usenet is concerned.
 
> >No, utf8 is not binary. Try again.
 
> Its 8 bit, usenet is 7 bit only. You work out the rest.
 
Insisting that the sky is purple won't really change its color. You can
stomp your little feet, and demand that Usenet must be 7 bits, but all non-
English writer will just laugh and point their finger at you – look,
another one!
boltar@cylonHQ.com: Sep 10 12:13PM

On Mon, 10 Sep 2018 06:54:25 -0400
>English writer will just laugh and point their finger at you =E2=80=93 lo=
>ok, =20
>another one!
 
Perhaps you'd like to explain to us why your newsreader is base64 encoding
your pgo sig then? Oh, whats that, you've never seen it? Here it is:
 
>--=_monster.email-scan.com-181043-1536576865-0003
>Content-Type: application/pgp-signature
>Content-Transfer-Encoding: 7bit
 
Oh, whats this? ^^^^
 
 
>-----BEGIN PGP SIGNATURE-----
 
>iQIcBAABAgAGBQJblk1hAAoJEGs6Yr4nnb8l9DYQAPYAfnA8Mw+cambFb/J6apOn
>7mwK7QIiOTy6FNTyOb8oKVj0/2jDRuOb5iM+7p49zXr+OgrSIZfExWan0+S9Fz2x
 
etc.
 
Education is very useful. You should try it sometime.
 
>> I'm not french.
 
>I'm pretty sure you are.
 
You seem to think its an insult. If I had to choose between living in france
or the USA it wouldn't be the latter.
boltar@cylonHQ.com: Sep 10 12:14PM

On Mon, 10 Sep 2018 06:54:25 -0400
>English writer will just laugh and point their finger at you =E2=80=93 lo=
>ok, =20
>another one!
 
Perhaps you'd like to explain to us why your newsreader is base64 encoding
your pgo sig then? Pardon, whats that, you've never seen it? Here it is:
 
>--=_monster.email-scan.com-181043-1536576865-0003
>Content-Type: application/pgp-signature
>Content-Transfer-Encoding: 7bit
 
Oh, and whats this? ^^^^
 
 
>-----BEGIN PGP SIGNATURE-----
 
>iQIcBAABAgAGBQJblk1hAAoJEGs6Yr4nnb8l9DYQAPYAfnA8Mw+cambFb/J6apOn
>7mwK7QIiOTy6FNTyOb8oKVj0/2jDRuOb5iM+7p49zXr+OgrSIZfExWan0+S9Fz2x
 
etc.
 
Education is very useful. You should try it sometime.
 
>> I'm not french.
 
>I'm pretty sure you are.
 
You seem to think its an insult. If I had to choose between living in france
or the USA it wouldn't be the latter.
boltar@cylonHQ.com: Sep 10 12:14PM

On Mon, 10 Sep 2018 06:52:02 -0400
>> Listen, why not go look up how UTF8 works instead of ever increasingly
 
>I know how UTF8 works.
 
No, you really don't.
 
>completely context-free. There's nothing about it that says "I contain UTF-8
>text". For that, you need MIME. That's what MIME is for. It's not a
>complicated concept to understand.
 
For the type of content and the code page (or not) there's the usenet header
field "Content-Type" - the clue is in the name. You don't need mime unless you
really need multipart messages. And why would you post those to usenet? Try
learning to use google.
 
>> >No, utf8 is not binary. Try again.
 
>> Yes, it is.
 
>No, it's not.
 
Ok, define binary data for us in the context of NNTP.
Elephant Man <conanospamic@gmail.com>: Sep 09 08:22PM

Article d'annulation posté via Nemo.
boltar@cylonHQ.com: Sep 10 11:13AM +0200

This cancel message has been issued from the web interface for deleting messages
provided by aioe.org (https://news.aioe.org/index.php?id=webcancel) at the request
of IP address 88.151.155.52 for the message identified by the Message-ID <pn5b9t$m0a$1@gioia.aioe.org>
and sent to comp.lang.c++ groups.
 
Please, write to abuse@aioe.org in case of abusive cancels
Horizon68 <horizon@horizon.com>: Sep 09 04:26PM -0700

Hello,
 
 
I am posting just very few posts here on this forum, so don't bother
about it.
 
 
Thank you,
Amine Moulay Ramdane.
Horizon68 <horizon@horizon.com>: Sep 09 04:24PM -0700

Hello,
 
Read this:
 
 
We hear that:
 
CPU rendering is more accurate(and generally assuming raytracing is
involved), so GPU is used for draft that CPU is used for final.
 
So read the following interesting webpage about:
 
What is ray tracing? Everything you need to know about the next big
graphical leap
 
https://www.techradar.com/news/ray-tracing
 
 
Thank you,
Amine Moulay Ramdane.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.

No comments: