Anyone seen posts on Eternal-September this morning? 7/1/25
Anyone seen posts on Eternal-September this morning? 7/1/25
Anyone seen posts on Eternal-September this morning? 7/1/25
Jim the Geordie <jim@jimXscott.co.uk> wrote:
Anyone seen posts on Eternal-September this morning? 7/1/25
Yup, working fine.
Jim the Geordie wrote:
Anyone seen posts on Eternal-September this morning? 7/1/25
Yes, I'm sending you this via their servers now. Usually, the problem
arises when their servers get overloaded. Sometimes this can tell you if that's the problem:
http://www.eternal-september.org/serverstatus.php?language=en
Usually though, just waiting a while until the problem goes away is the
best solution.
Anyone seen posts on Eternal-September this morning? 7/1/25
I'll let you know in July. :)
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.
No they aren't. Only the US uses M/D/Y. https://commons.m.wikimedia.org/wiki/File%3ADate_format_by_country.svgNot 100% right. I'm not sure why, but some of those 'colors' were marked with both DMY and MDY,
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.
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.
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.
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.
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.
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.
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.
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.
Jim the Geordie wrote:
Anyone seen posts on Eternal-September this morning? 7/1/25
Yes, I'm sending you this via their servers now. Usually, the problem
arises when their servers get overloaded. Sometimes this can tell you if that's the problem:
http://www.eternal-september.org/serverstatus.php?language=en
Usually though, just waiting a while until the problem goes away is the
best solution.
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 ;)
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.
Date fight!
<gets bag of popcorn, and sits back to watch>
Nobody's laughing.
(-;
I laughed.
Fortunately there's an ISO standard for all of this: 8601
The valid format is YYYY-MM-DD or, optionally, YYYYMMDD.
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
with photos.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
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.
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!
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
Ken Blake <Ken@invalid.news.com> wrote:
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
Well, my mum lived to 102, so if you manage that, you'll be looking
*back* on 2038.
And what about your (grand)kids, if any?
Anyway, as the smiley indicates, it's a joke, and, like with Y2K, it's
no so much the systems, but the software/programs/applications/
<whatever> running *on* those systems, which are the problem.
BTW, your '1938' typo was quite funny, in this context!
On 11 Jan 2025 16:38:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
Ken Blake <Ken@invalid.news.com> wrote:
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
Well, my mum lived to 102, so if you manage that, you'll be looking
*back* on 2038.
Highly unlikely. I have metastatic prostate cancer.
On Sun, 1/12/2025 12:45 PM, Ken Blake wrote:
On 11 Jan 2025 16:38:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
Ken Blake <Ken@invalid.news.com> wrote:
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
Well, my mum lived to 102, so if you manage that, you'll be looking
*back* on 2038.
Highly unlikely. I have metastatic prostate cancer.
That doesn't sound good.
https://www.hopkinsmedicine.org/health/conditions-and-diseases/prostate-cancer/prostate-cancer-prognosis
And that's why there is an entire wing on the small hospital near
my place, given over to cancer. And nothing for heart disease
(which is downtown). Every hospital seems to have a cancer wing.
On 7/1/2025 8:15 pm, Jim the Geordie wrote:
Anyone seen posts on Eternal-September this morning? 7/1/25
Working fine from Hong Kong as of 08 Jan (HKT) ...
On Thu, 9 Jan 2025 17:41:31 -0000 (UTC), Chris <ithinkiam@gmail.com>
wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
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???!!!!"
Addendum: the day after the 31st of December, 9999, in case you're
still coffee deprived.
On Sun, 1/12/2025 12:45 PM, Ken Blake wrote:
On 11 Jan 2025 16:38:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
Ken Blake <Ken@invalid.news.com> wrote:
On 10 Jan 2025 19:08:56 GMT, Frank Slootweg <this@ddress.is.invalid>
wrote:
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!
I don't know and I don't care. I won't be alive in 1938 or 2486.
Well, my mum lived to 102, so if you manage that, you'll be looking
*back* on 2038.
Highly unlikely. I have metastatic prostate cancer.
That doesn't sound good.
https://www.hopkinsmedicine.org/health/conditions-and-diseases/prostate-cancer/prostate-cancer-prognosis
And that's why there is an entire wing on the small hospital near
my place, given over to cancer. And nothing for heart disease
(which is downtown). Every hospital seems to have a cancer wing.
Paul
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>
On 10/01/2025 11:13 pm, John wrote:
On Thu, 9 Jan 2025 17:41:31 -0000 (UTC), Chris <ithinkiam@gmail.com>
wrote:
Carlos E.R. <robin_listas@es.invalid> wrote:
<Snip>
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???!!!!"
Addendum: the day after the 31st of December, 9999, in case you're
still coffee deprived.
"Y2000'ed" .... "9999"!!
I have sever doubts about YOUR definition of "in a couple of years"!! ;-P
Even Dr.Pepper soda pop beverage does not last that long.
On 11/01/2025 6:08 am, Frank Slootweg wrote:
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>
I might make it to 2038 (only 13 years after all!) .... but 2486 is
probably out of the question.
What's the problem or the root of the problem anticipated in 2486??
'Year 2038 problem' <https://en.wikipedia.org/wiki/Year_2038_problem>I might make it to 2038 (only 13 years after all!) .... but 2486 is
probably out of the question.
What's the problem or the root of the problem anticipated in 2486??
On 29/03/2025 3:51 am, Frank Slootweg wrote:
Daniel70 <daniel47@eternal-september.org> wrote:
On 11/01/2025 6:08 am, Frank Slootweg wrote:
John <Man@the.keyboard> wrote:I might make it to 2038 (only 13 years after all!) .... but 2486 is
[...]
  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>
probably out of the question.
COMPUTERS!! Are they really of assistance to US Humans??
What's the problem or the root of the problem anticipated in 2486??
  The XFS filesystem. See the 'Implemented solutions' section of the
above Wikipedia page for details.
  I failed to notice that the ext4 filesystem problem comes even sooner, >> 2446! And 2106 (OpenVMS and MariaDB) is also right around the corner!
  And watch out for the year 30,828 problem (Windows)! That's the real
killer!
"Prince -- Party Like It's 1999" [Balance still isn't very good, hard to hear vocals clearly]
https://www.youtube.com/watch?v=iI2fRPmEZ6A
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 508 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 217:37:06 |
| Calls: | 9,974 |
| Calls today: | 5 |
| Files: | 13,831 |
| Messages: | 6,358,556 |
