Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #181163 > unrolled thread

E-S

Back to article view | Back to alt.comp.os.windows-10

Contents

  E-S Jim the Geordie <jim@jimXscott.co.uk> - 2025-01-07 12:15 +0000
    Re: E-S Java Jive <java@evij.com.invalid> - 2025-01-07 12:48 +0000
    Re: E-S Newyana2 <newyana@invalid.nospam> - 2025-01-07 08:02 -0500
      Re: E-S "s|b" <me@privacy.invalid> - 2025-01-08 16:27 +0100
        Re: E-S Newyana2 <newyana@invalid.nospam> - 2025-01-08 11:17 -0500
          Re: E-S Chris <ithinkiam@gmail.com> - 2025-01-08 17:38 +0000
            Re: E-S "Alan K." <alan@invalid.com> - 2025-01-08 13:35 -0500
            Re: E-S Paul <nospam@needed.invalid> - 2025-01-08 14:46 -0500
              Re: E-S "s|b" <me@privacy.invalid> - 2025-01-10 20:28 +0100
            Re: E-S Newyana2 <newyana@invalid.nospam> - 2025-01-08 14:52 -0500
          Re: E-S "John C." <r9jmg0@yahoo.com> - 2025-01-09 04:11 -0800
            Re: E-S "Carlos E.R." <robin_listas@es.invalid> - 2025-01-09 14:47 +0100
              Re: E-S Chris <ithinkiam@gmail.com> - 2025-01-09 17:41 +0000
                Re: E-S John <Man@the.keyboard> - 2025-01-10 12:13 +0000
                  Re: E-S John <Man@the.keyboard> - 2025-01-10 12:17 +0000
                  Re: E-S Newyana2 <newyana@invalid.nospam> - 2025-01-10 09:08 -0500
                    Re: E-S Chris <ithinkiam@gmail.com> - 2025-01-10 16:29 +0000
                      Re: E-S Newyana2 <newyana@invalid.nospam> - 2025-01-10 11:58 -0500
                        Re: E-S Chris <ithinkiam@gmail.com> - 2025-01-10 18:34 +0000
                  Re: E-S Frank Slootweg <this@ddress.is.invalid> - 2025-01-10 19:08 +0000
                    Re: E-S Ken Blake <Ken@invalid.news.com> - 2025-01-11 08:57 -0700
                      Re: E-S Frank Slootweg <this@ddress.is.invalid> - 2025-01-11 16:38 +0000
                        Re: E-S Ken Blake <Ken@invalid.news.com> - 2025-01-12 10:45 -0700
                          Re: E-S Paul <nospam@needed.invalid> - 2025-01-12 15:06 -0500
                            Re: E-S Ken Blake <Ken@invalid.news.com> - 2025-01-13 09:39 -0700
                            Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-28 22:34 +1100
                      Re: E-S Paul <nospam@needed.invalid> - 2025-01-11 12:11 -0500
                        Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-30 21:17 +1100
                        Re: E-S Rink <rink.hof.haalditmaarweg@planet.nl> - 2025-04-06 20:23 +0200
                    Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-28 22:21 +1100
                      Re: E-S Frank Slootweg <this@ddress.is.invalid> - 2025-03-28 16:51 +0000
                        Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-30 21:18 +1100
                          Re: E-S Rink <rink.hof.haalditmaarweg@planet.nl> - 2025-04-06 20:07 +0200
                      Re: E-S Mark Lloyd <not.email@all.invalid> - 2025-03-28 21:12 +0000
                  Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-28 22:04 +1100
                    Re: E-S Paul <nospam@needed.invalid> - 2025-03-28 09:24 -0400
                      Re: E-S jerryab <jerryab@juno.com> - 2025-03-28 10:19 -0500
                      Re: E-S Daniel70 <daniel47@eternal-september.org> - 2025-03-30 21:21 +1100
                Re: E-S "Carlos E.R." <robin_listas@es.invalid> - 2025-01-10 14:42 +0100
                Re: E-S "s|b" <me@privacy.invalid> - 2025-01-10 20:29 +0100
              Re: E-S "John C." <r9jmg0@yahoo.com> - 2025-01-11 06:37 -0800
        Re: E-S Lynn McGuire <lynnmcguire5@gmail.com> - 2025-01-08 16:29 -0600
          Re: E-S "s|b" <me@privacy.invalid> - 2025-01-10 20:31 +0100
    Re: E-S Chris <ithinkiam@gmail.com> - 2025-01-07 13:42 +0000
      Re: E-S "Alan K." <alan@invalid.com> - 2025-01-07 08:49 -0500
    Re: E-S "John C." <r9jmg0@yahoo.com> - 2025-01-07 06:08 -0800
      Re: E-S Jim the Geordie <jim@jimXscott.co.uk> - 2025-01-07 14:28 +0000
      Re: E-S Paul <nospam@needed.invalid> - 2025-01-10 10:43 -0500
    Re: E-S "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-01-09 01:24 +0800
      Re: E-S Jim the Geordie <jim@jimXscott.co.uk> - 2025-01-14 13:32 +0000

Page 1 of 3  [1] 2 3  Next page →

#181163 — E-S

Anyone seen posts on Eternal-September this morning? 7/1/25
-- 
Jim the Geordie

[toc] | [next] | [standalone]

#181164

On 2025-01-07 12:15, Jim the Geordie wrote:
>
> Anyone seen posts on Eternal-September this morning? 7/1/25

Yes, plenty here in Scotland, UK

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]

#181165

On 1/7/2025 7:15 AM, Jim the Geordie wrote:
> Anyone seen posts on Eternal-September this morning? 7/1/25

I'll let you know in July. :)

[toc] | [prev] | [next] | [standalone]

#181180

On Tue, 7 Jan 2025 08:02:17 -0500, Newyana2 wrote:

> > Anyone seen posts on Eternal-September this morning? 7/1/25
 
> I'll let you know in July. :)

Nobody's laughing.

(-;

-- 
s|b

[toc] | [prev] | [next] | [standalone]

#181181

On 1/8/2025 10:27 AM, s|b wrote:
> On Tue, 7 Jan 2025 08:02:17 -0500, Newyana2 wrote:
> 
>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>   
>> I'll let you know in July. :)
> 
> Nobody's laughing.
> 

   Just a gentle reminder to avoid ambiguous notation in an
international forum. Perhaps Jim didn't realize that M/D/Y
notation and D/M/Y notation are both widely used.

   No date was necessary at all, since newsreaders generally
show the date. Not a big deal, but it is confusing, especially
when the date is 1-12.

[toc] | [prev] | [next] | [standalone]

#181184

Newyana2 <newyana@invalid.nospam> wrote:
> On 1/8/2025 10:27 AM, s|b wrote:
>> On Tue, 7 Jan 2025 08:02:17 -0500, Newyana2 wrote:
>> 
>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>> 
>>> I'll let you know in July. :)
>> 
>> Nobody's laughing.
>> 
> 
>   Just a gentle reminder to avoid ambiguous notation in an
> international forum. Perhaps Jim didn't realize that M/D/Y
> notation and D/M/Y notation are both widely used.

No they aren't. Only the US uses M/D/Y. 
https://commons.m.wikimedia.org/wiki/File%3ADate_format_by_country.svg

>   No date was necessary at all, since newsreaders generally
> show the date. Not a big deal, but it is confusing, especially
> when the date is 1-12.

If nothing else, context should have been enough. 

[toc] | [prev] | [next] | [standalone]

#181185

On 1/8/25 12:38 PM, Chris wrote:
> No they aren't. Only the US uses M/D/Y.
> https://commons.m.wikimedia.org/wiki/File%3ADate_format_by_country.svg
Not 100% right.  I'm not sure why, but some of those 'colors' were marked with both DMY and MDY, 
guess the go both ways depending on territory?  I find it odd though that they aren't consistent.

-- 
Linux Mint 22, Cinnamon 6.2.9,  Kernel 6.8.0-51-generic
Thunderbird 128.5.2esr, Mozilla Firefox 133.0.3
Alan K.

[toc] | [prev] | [next] | [standalone]

#181188

On Wed, 1/8/2025 12:38 PM, Chris wrote:
> Newyana2 <newyana@invalid.nospam> wrote:
>> On 1/8/2025 10:27 AM, s|b wrote:
>>> On Tue, 7 Jan 2025 08:02:17 -0500, Newyana2 wrote:
>>>
>>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>
>>>> I'll let you know in July. :)
>>>
>>> Nobody's laughing.
>>>
>>
>>   Just a gentle reminder to avoid ambiguous notation in an
>> international forum. Perhaps Jim didn't realize that M/D/Y
>> notation and D/M/Y notation are both widely used.
> 
> No they aren't. Only the US uses M/D/Y. 
> https://commons.m.wikimedia.org/wiki/File%3ADate_format_by_country.svg
> 
>>   No date was necessary at all, since newsreaders generally
>> show the date. Not a big deal, but it is confusing, especially
>> when the date is 1-12.
> 
> If nothing else, context should have been enough. 

Date fight!

<gets bag of popcorn, and sits back to watch>

The E-S server is in Finland, and the operator of the
server picks the country, according to the applicable law
of the country. For example, IP reporting requirements
vary from one country to another (how long you have to
keep IP address info).

While in the past, server outages were traceable to DNS changes,
that's not what is going on currently. I've seen no outages to
E-S where I am (Canada), but some other people seem to be seeing
them, and there's no pattern to that (yet).

If you have VPN capability, you could test an exit in another country
and see if it still isn't visible.

   Paul

[toc] | [prev] | [next] | [standalone]

#181247

On Wed, 8 Jan 2025 14:46:42 -0500, Paul wrote:

> Date fight!
> 
> <gets bag of popcorn, and sits back to watch>

<G>

-- 
s|b

[toc] | [prev] | [next] | [standalone]

#181190

On 1/8/2025 12:38 PM, Chris wrote:

>>    Just a gentle reminder to avoid ambiguous notation in an
>> international forum. Perhaps Jim didn't realize that M/D/Y
>> notation and D/M/Y notation are both widely used.
> 
> No they aren't. Only the US uses M/D/Y.

  Yes. Welcome to the outside world.

[toc] | [prev] | [next] | [standalone]

#181193

Newyana2 wrote:
> s|b wrote:
>> Newyana2 wrote:
>>
>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>  
>>> I'll let you know in July. :)
>>
>> Nobody's laughing.
> 
>   Just a gentle reminder to avoid ambiguous notation in an
> international forum. Perhaps Jim didn't realize that M/D/Y
> notation and D/M/Y notation are both widely used.
> 
>   No date was necessary at all, since newsreaders generally
> show the date. Not a big deal, but it is confusing, especially
> when the date is 1-12.

I know that's common usage, but on my system I went to a more logical
way years ago.

YYMMDDHHMMSS

It makes sorting files in File Manager a lot easier. And if I put it at
the start of a file's name, I can easily sort by name. Really helpful
with photos.

-- 
John C.

[toc] | [prev] | [next] | [standalone]

#181195

On 2025-01-09 13:11, John C. wrote:
> Newyana2 wrote:
>> s|b wrote:
>>> Newyana2 wrote:
>>>
>>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>>   
>>>> I'll let you know in July. :)
>>>
>>> Nobody's laughing.
>>
>>    Just a gentle reminder to avoid ambiguous notation in an
>> international forum. Perhaps Jim didn't realize that M/D/Y
>> notation and D/M/Y notation are both widely used.
>>
>>    No date was necessary at all, since newsreaders generally
>> show the date. Not a big deal, but it is confusing, especially
>> when the date is 1-12.
> 
> I know that's common usage, but on my system I went to a more logical
> way years ago.
> 
> YYMMDDHHMMSS
> 
> It makes sorting files in File Manager a lot easier. And if I put it at
> the start of a file's name, I can easily sort by name. Really helpful
> with photos.

Better if you do YYYY. It makes easier for other people to recognize it 
is a year. Once you know the first figure is the year, it is easy to 
guess the rest.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#181197

Carlos E.R. <robin_listas@es.invalid> wrote:
> On 2025-01-09 13:11, John C. wrote:
>> Newyana2 wrote:
>>> s|b wrote:
>>>> Newyana2 wrote:
>>>> 
>>>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>>> 
>>>>> I'll let you know in July. :)
>>>> 
>>>> Nobody's laughing.
>>> 
>>>   Just a gentle reminder to avoid ambiguous notation in an
>>> international forum. Perhaps Jim didn't realize that M/D/Y
>>> notation and D/M/Y notation are both widely used.
>>> 
>>>   No date was necessary at all, since newsreaders generally
>>> show the date. Not a big deal, but it is confusing, especially
>>> when the date is 1-12.
>> 
>> I know that's common usage, but on my system I went to a more logical
>> way years ago.
>> 
>> YYMMDDHHMMSS
>> 
>> It makes sorting files in File Manager a lot easier. And if I put it at
>> the start of a file's name, I can easily sort by name. Really helpful
>> with photos.
> 
> Better if you do YYYY. It makes easier for other people to recognize it 
> is a year. Once you know the first figure is the year, it is easy to 
> guess the rest.

Fortunately there's an ISO standard for all of this: 8601

The valid format is YYYY-MM-DD or, optionally, YYYYMMDD. 

[toc] | [prev] | [next] | [standalone]

#181222

On Thu, 9 Jan 2025 17:41:31 -0000 (UTC), Chris <ithinkiam@gmail.com>
wrote:

>Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 2025-01-09 13:11, John C. wrote:
>>> Newyana2 wrote:
>>>> s|b wrote:
>>>>> Newyana2 wrote:
>>>>> 
>>>>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>>>> 
>>>>>> I'll let you know in July. :)
>>>>> 
>>>>> Nobody's laughing.
>>>> 
>>>>   Just a gentle reminder to avoid ambiguous notation in an
>>>> international forum. Perhaps Jim didn't realize that M/D/Y
>>>> notation and D/M/Y notation are both widely used.
>>>> 
>>>>   No date was necessary at all, since newsreaders generally
>>>> show the date. Not a big deal, but it is confusing, especially
>>>> when the date is 1-12.
>>> 
>>> I know that's common usage, but on my system I went to a more logical
>>> way years ago.
>>> 
>>> YYMMDDHHMMSS
>>> 
>>> It makes sorting files in File Manager a lot easier. And if I put it at
>>> the start of a file's name, I can easily sort by name. Really helpful
>>> with photos.
>> 
>> Better if you do YYYY. It makes easier for other people to recognize it 
>> is a year. Once you know the first figure is the year, it is easy to 
>> guess the rest.
>
>Fortunately there's an ISO standard for all of this: 8601
>
>The valid format is YYYY-MM-DD or, optionally, YYYYMMDD. 


 And, in a couple of years, that is going to be Y2000'ed. 

 "The CHILDREN, THE CHILDREN, Won't *anyone* ever think of THE
*C*H*IIIIIIII*LLLLLLLL*DD*RRRR*EEEEEEEEE*NNNNNNNNNN???!!!!"

                                                         J. 





Addendum: the day after the 31st of December, 9999, in case you're
still coffee deprived.

 I'd give ten minutes of setting-up time for the ability to use
coloured text, bold, italic and marching ants in Usenet. Hysterical
lunacy just ain't as fetching in plain ASCII. :)              J. 

[toc] | [prev] | [next] | [standalone]

#181223

On Fri, 10 Jan 2025 12:13:27 +0000, John <Man@the.keyboard> wrote:

>On Thu, 9 Jan 2025 17:41:31 -0000 (UTC), Chris <ithinkiam@gmail.com>
>wrote:
>
>>Carlos E.R. <robin_listas@es.invalid> wrote:
>>> On 2025-01-09 13:11, John C. wrote:
>>>> Newyana2 wrote:
>>>>> s|b wrote:
>>>>>> Newyana2 wrote:
>>>>>> 
>>>>>>>> Anyone seen posts on Eternal-September this morning? 7/1/25
>>>>>>> 
>>>>>>> I'll let you know in July. :)
>>>>>> 
>>>>>> Nobody's laughing.
>>>>> 
>>>>>   Just a gentle reminder to avoid ambiguous notation in an
>>>>> international forum. Perhaps Jim didn't realize that M/D/Y
>>>>> notation and D/M/Y notation are both widely used.
>>>>> 
>>>>>   No date was necessary at all, since newsreaders generally
>>>>> show the date. Not a big deal, but it is confusing, especially
>>>>> when the date is 1-12.
>>>> 
>>>> I know that's common usage, but on my system I went to a more logical
>>>> way years ago.
>>>> 
>>>> YYMMDDHHMMSS
>>>> 
>>>> It makes sorting files in File Manager a lot easier. And if I put it at
>>>> the start of a file's name, I can easily sort by name. Really helpful
>>>> with photos.
>>> 
>>> Better if you do YYYY. It makes easier for other people to recognize it 
>>> is a year. Once you know the first figure is the year, it is easy to 
>>> guess the rest.
>>
>>Fortunately there's an ISO standard for all of this: 8601
>>
>>The valid format is YYYY-MM-DD or, optionally, YYYYMMDD. 
>
>
> And, in a couple of years, that is going to be Y2000'ed. 

 "We're going to need a bigger standard ..." 

>
> "The CHILDREN, THE CHILDREN, Won't *anyone* ever think of THE
>*C*H*IIIIIIII*LLLLLLLL*DD*RRRR*EEEEEEEEE*NNNNNNNNNN???!!!!"

 And the odds of there actually *being* any are? 

>
>                                                         J. 
>
>
>
>
>
>Addendum: the day after the 31st of December, 9999, in case you're
>still coffee deprived.
>
> I'd give ten minutes of setting-up time for the ability to use
>coloured text, bold, italic and marching ants in Usenet. Hysterical
>lunacy just ain't as fetching in plain ASCII. :)              J. 

 Or maybe not. I always hated those Manglers who spent their days
finding obscure fonts and flashy tools to jazz up the multi-megabyte
email attachments that could have been a few lines of plain,
easy-to-read text. :)

 Happy New Year, everyone. 

                                                        J. 

[toc] | [prev] | [next] | [standalone]

#181228

On 1/10/2025 7:13 AM, John wrote:

>>
>> Fortunately there's an ISO standard for all of this: 8601
>>
> 
> Addendum: the day after the 31st of December, 9999, in case you're
> still coffee deprived.

    By the way, can someone post the ISO standard for brewing
coffee, so that Chris can treat his irritability? Some people just
don't do well without rules.

[toc] | [prev] | [next] | [standalone]

#181233

Newyana2 <newyana@invalid.nospam> wrote:
> On 1/10/2025 7:13 AM, John wrote:
> 
>>> 
>>> Fortunately there's an ISO standard for all of this: 8601
>>> 
>> 
>> Addendum: the day after the 31st of December, 9999, in case you're
>> still coffee deprived.
> 
>    By the way, can someone post the ISO standard for brewing
> coffee, so that Chris can treat his irritability? Some people just
> don't do well without rules.

I don't drink coffee ;)

[toc] | [prev] | [next] | [standalone]

#181236

On 1/10/2025 11:29 AM, Chris wrote:
> Newyana2 <newyana@invalid.nospam> wrote:
>> On 1/10/2025 7:13 AM, John wrote:
>>
>>>>
>>>> Fortunately there's an ISO standard for all of this: 8601
>>>>
>>>
>>> Addendum: the day after the 31st of December, 9999, in case you're
>>> still coffee deprived.
>>
>>     By the way, can someone post the ISO standard for brewing
>> coffee, so that Chris can treat his irritability? Some people just
>> don't do well without rules.
> 
> I don't drink coffee ;)
> 

A literalist to the end. How poetic.

[toc] | [prev] | [next] | [standalone]

#181242

Newyana2 <newyana@invalid.nospam> wrote:
> On 1/10/2025 11:29 AM, Chris wrote:
>> Newyana2 <newyana@invalid.nospam> wrote:
>>> On 1/10/2025 7:13 AM, John wrote:
>>> 
>>>>> 
>>>>> Fortunately there's an ISO standard for all of this: 8601
>>>>> 
>>>> 
>>>> Addendum: the day after the 31st of December, 9999, in case you're
>>>> still coffee deprived.
>>> 
>>> By the way, can someone post the ISO standard for brewing
>>> coffee, so that Chris can treat his irritability? Some people just
>>> don't do well without rules.
>> 
>> I don't drink coffee ;)
>> 
> 
> A literalist to the end. How poetic.
> 

It's a joke. ffs. 

[toc] | [prev] | [next] | [standalone]

#181245

John <Man@the.keyboard> wrote:
[...]

>  And, in a couple of years, that is going to be Y2000'ed. 
> 
>  "The CHILDREN, THE CHILDREN, Won't *anyone* ever think of THE
> *C*H*IIIIIIII*LLLLLLLL*DD*RRRR*EEEEEEEEE*NNNNNNNNNN???!!!!"
> 
> Addendum: the day after the 31st of December, 9999, in case you're
> still coffee deprived.

  Isn't the Internet, etc. supposed to die first, because of all the
Unix servers going down, on January 19, 2038!? :-) And the *next*
disaster in 2486!

'Year 2038 problem'
<https://en.wikipedia.org/wiki/Year_2038_problem>

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | alt.comp.os.windows-10

csiph-web