diff --git a/bin/status2html.sh b/bin/status2html.sh index d9bd53a1c..e25273054 100755 --- a/bin/status2html.sh +++ b/bin/status2html.sh @@ -20,6 +20,8 @@ # # Copyright (c) 2024 by Landon Curt Noll. All Rights Reserved. # +# ... with minor improvements made in June 2024 by Cody Boone Ferguson. +# # Permission to use, copy, modify, and distribute this software and # its documentation for any purpose and without fee is hereby granted, # provided that the above copyright, this permission notice and text @@ -450,17 +452,18 @@ esac ;; closed) echo "# The IOCCC is closed" echo - echo "The IOCCC is **NOT** accepting new submissions at this time. See the" \ + echo "The IOCCC is **NOT** accepting [new submissions](faq.html#submit) at this time. See the" \ "[IOCCC winning entries page](years.html) for the entries that have won the IOCCC." echo - echo "Watch both [the IOCCC status page](status.html) and the" \ + echo "Watch both [this IOCCC status page](status.html) and the" \ "[@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for information about future IOCCC openings." ;; *) echo "# The IOCCC status is unknown" echo echo "The IOCCC status is an unexpected status value: $CONTEST_STATUS" echo - echo "This is a **BUG**, not a feature. Feel free to report it!" + echo "This is a **BUG**, not a feature. Feel free to report it!" 1>&2 + echo "See the [GitHub issues page](https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose}." 1>&2 ;; esac echo diff --git a/news.html b/news.html index 8840f3f4d..a5cbfdf77 100644 --- a/news.html +++ b/news.html @@ -383,20 +383,51 @@

For more news, try mastodon

-

Please follow** the IOCCC on Mastodon

+

Please follow the IOCCC on Mastodon

We use Mastodon to make minor announcements, in addition to announcing major events such as the opening of a new IOCCC, or who won.

See “FAQ 6.12: What is Mastodon and why does IOCCC use it?” for more information on Mastodon.

-

2024-05-30

+

News

+

2024-06-08

+

We continue to make good progress on the +temp-test-ioccc website +via the temp-test-ioccc repo.

+

One of the largest html +files has +been checked for broken links which leaves two longer files to go. These two +files are the bugs.html +file and the FAQ.

+

However, where it was thought that those two files would be looked at before the +other html files, it has been decided that they will be done after the other +files as it is very possible that some things in these two files will have to be +changed or added as the other files are reviewed for broken links.

+

As of today, 08 June 2024, the top level html files are being looked at, with at +least three done already (judges.html, news.html and +status.html). This should not take more than a few days if things +go as planned, as these files are small and should be relatively quick and easy +to check for broken links. Of course, some of these, like the +news.html and possibly status.html will likely have to be +checked again but as for news.html the dates up to and including 08 +June 2024 have been checked for invalid links so that only new news updates +will have to be checked.

+

Once those are done the html files of all the entries will be looked at. As +those are being reviewed it the bugs.html might very well be +updated and the FAQ might be as well. This is why, as noted above, +we have decided to review these files last, in order to save time and effort in +not having to look at them more than once on a whole, other than possible +entries that have to be added at the end, like the example below.

+

Once the submit server server is ready another FAQ will be added and that +entry can be looked at alone.

+

2024-05-30

A number of issues from minor fixes have been applied to the temp-test-ioccc website via the temp-test-ioccc repo.

437 commits have been applied since 2024-04-20, bringing the total number to 5260 commits to date. The temp-test-ioccc -repo is now 5159 commits ahead of the [IOCCC -winner[(https://github.com/ioccc-src/winner) repo.

+repo is now 5159 commits ahead of the IOCCC +winner repo.

Multiple ((top priority)) issues have been resolved or completed. Only one ((top priority)) issue, issue 2006 @@ -409,7 +440,7 @@ there are two more before we can look at the other files.

The issue 2239 TODO list has 10 out of 51 sub-tasks completed. That might not seem like much progress, but keep in mind that some of those 10 -tasks look many months and thousands of commits to complete. +tasks took many months and thousands of commits to complete. Moreover, most of the remaining 41 TODO items are short “checkbox” tasks. The final 31 TODO items are planned to be completed in about a single day.

@@ -423,7 +454,7 @@ ask for beta testing of the new IOCCC registration process and This will speed up the start date of IOCCC28.

It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the IOCCC.

-

2024-04-30

+

2024-04-30

The website now is viewing by mobile devices such as cell phones and tablets. Devices with a screen resolution 1024 pixels and narrower are given a hamburger-style menu icon in place of @@ -445,7 +476,7 @@ files that are static (not generated bin tools) report no warnings, nor info** messages, changes involving fixing invalid links to local files have been corrected, and changes involving the topbar are now HTML 5 conforming.

-

2024-04-20

+

2024-04-20

Nearly all of the temp-test-ioccc website website has undergone editorial review. Nearly all IOCCC winning entries compile on modern systems and many have try.sh scripts to help you run them. @@ -463,10 +494,10 @@ glaring “dancing bears” and other frivolous web features.

where the contents of the temp-test-ioccc website will be merged into the Official IOCCC website.

Stay tuned!

-

2024-02-29

+

2024-02-29

We continue to make good progress on website. In the temp-test-ioccc GitHub repo we have made nearly 4600 changes to date!

All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the bin directory.

-

2023-05-22

+

2023-05-22

We have been busy preparing for an important / significant update to this website. In the temp-test-ioccc GitHub repo we have made nearly 2645 changes to date.

While you are free to look at the temp-test-ioccc GitHub repo, please do not link to it as this repo and related website will disappear once the main @@ -522,7 +553,7 @@ that needs urgent fixing. The IOCCCMOCK will us to beta-test the new IOCCC process without putting the hard work of those who submit real IOCCC entries at risk.

Stay tuned!

-

2023-01-30

+

2023-01-30

We added to the status.json page, a “status_date” JSON member whose value is the date @@ -534,11 +565,11 @@ a “latest_news” JSON member whose value is the date of the most recent news item.

    "status_date" : "Mon Jan 30 02:28:44 PST 2023",
     "latest_news" : "Mon Jan 30 02:28:44 PST 2023"
-

2022-12-18

-

As per the suggestion of Toni Mikkola -(_@Virtaava@home.social_) we now maintain a -status.json page on this website.

-

In addition to the IOCCC-style easter egg, you may count on +

2022-12-18

+

As per the suggestion of Toni Mikkola +(@Virtaava@home.social) +we now maintain a status.json page on this website.

+

In addition to the IOCCC-style Easter egg, you may count on the JSON status page having a JSON member with name of “contest” that will have a value of either “closed” or “open”. When a future IOCCC is announced or the IOCCC is currently open, @@ -552,8 +583,8 @@ The details of such additional JSON members are TBD.

Instead you will have to rely on the additional JSON information and/or read the IOCCC news, and/or follow us on Mastodon via @ioccc@fosstodon.org.

-

2022-11-29

-

We are plan to abandon our +

2022-11-29

+

We are planning to abandon our IOCCC Twitter feed in favor of our new IOCCC Mastodon feed.

Our Mastodon username is: @ioccc@fosstodon.org.

@@ -577,7 +608,7 @@ Proving a Mastodon username will be entirely optional.

If you do not yet have a Mastodon account, you may obtain a free mastodon account via: joinmastodon.org.

If you do have / obtain a Mastodon account, please do us a favor and follow the IOCCC at:

-
    **@ioccc@fosstodon.org**
+
    @ioccc@fosstodon.org

The IOCCC wishes to thank the good folk running the fosstodon.org Mastodon hub. @@ -587,7 +618,7 @@ is made possible by volunteers, and those who voluntarily support the cost of their server.

Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!

-

2022-11-19

+

2022-11-19

Source code has been released for version 0.8.1 2022-11-19 of the mkiocccentry repo, a GitHub repo that includes the official iocccsize tool, @@ -599,13 +630,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co judges will go through the motions (without judging the content) of an IOCCC: testing the above mentioned tools and testing the submit server.

We are working on complete rebuild of this website as well.

-

2022-01-15

+

2022-01-15

Source code has been released for version 0.24 2022-01-15 of the mkiocccentry tool, a tool that is based on, and is containing, the official iocccsize tool, will form a compressed tarball that a registered IOCCC contestant will upload to the submit server (when the contest is open of course).

-

2021-12-27

+

2021-12-27

The Judges are continuing to work on re-tooling how we run the IOCCC. We are writing tools under various repositories our @@ -614,7 +645,7 @@ We are writing tools under various repositories our Sorry for the delay, but we think you will appreciate the re-tooling when it is completed. Stay tuned!

-

2021-10-21

+

2021-10-21

The Judges are re-tooling how we run the IOCCC. Our goal is to build a smoother, more rapid process centered around diff --git a/news.md b/news.md index 91c5efbc9..7bac1cd68 100644 --- a/news.md +++ b/news.md @@ -1,6 +1,6 @@ # For more news, try mastodon -### Please follow** the [IOCCC on Mastodon](https://fosstodon.org/@ioccc) +### Please follow the [IOCCC on Mastodon](https://fosstodon.org/@ioccc) We use Mastodon to make minor announcements, in addition to announcing major events such as the opening of a new IOCCC, or who won. @@ -8,6 +8,47 @@ major events such as the opening of a new IOCCC, or who won. See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastodon)" for more information on Mastodon. +

+# News +
+ +## 2024-06-08 + +We continue to make good progress on the +[temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/) +via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo. + +One of the [largest html +files](thanks-for-help.html) has +been checked for broken links which leaves two longer files to go. These two +files are the [bugs.html](bugs.html) +file and the [FAQ](faq.html). + +However, where it was thought that those two files would be looked at before the +other html files, it has been decided that they will be done after the other +files as it is very possible that some things in these two files will have to be +changed or added as the other files are reviewed for broken links. + +As of today, 08 June 2024, the top level html files are being looked at, with at +least three done already ([judges.html](judges.html), [news.html](news.html) and +[status.html](status.html)). This should not take more than a few days if things +go as planned, as these files are small and should be relatively quick and easy +to check for broken links. Of course, some of these, like the +[news.html](news.html) and possibly [status.html](status.html) will likely have to be +checked again but as for [news.html](news.html) the dates up to and including _08 +June 2024_ have been checked for invalid links so that only new news updates +will have to be checked. + +Once those are done the html files of all the entries will be looked at. As +those are being reviewed it the [bugs.html](bugs.html) might very well be +updated and the [FAQ](faq.html) might be as well. This is why, as noted above, +we have decided to review these files last, in order to save time and effort in +not having to look at them more than once on a whole, other than possible +entries that have to be added at the end, like the example below. + +Once the _submit server_ server is ready another FAQ will be added and that +entry can be looked at alone. + ## 2024-05-30 @@ -19,7 +60,7 @@ via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo. number to 5260 commits to date. The [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo is now 5159 commits ahead of the [IOCCC -winner[(https://github.com/ioccc-src/winner) repo. +winner](https://github.com/ioccc-src/winner) repo. Multiple **((top priority))** issues have been resolved or completed. Only one **((top priority))** issue, [issue @@ -34,7 +75,7 @@ there are two more before we can look at the other files. The [issue 2239](https://github.com/ioccc-src/temp-test-ioccc/issues/2239) TODO list has 10 out of 51 sub-tasks completed. That might not seem like much progress, but keep in mind that some of those 10 -tasks look many months and thousands of commits to complete. +tasks took many months and thousands of commits to complete. Moreover, most of the remaining 41 TODO items are short "checkbox" tasks. The final 31 TODO items are planned to be completed in about a single day. @@ -205,11 +246,11 @@ of the most recent news item. ## 2022-12-18 -As per the suggestion of [Toni Mikkola](https://fosstodon.org/@Virtaava@home.social) -(_@Virtaava@home.social_) we now maintain a -[status.json](status.json) page on this website. +As per the suggestion of [Toni Mikkola +(@Virtaava@home.social)](https://fosstodon.org/@Virtaava@home.social) +we now maintain a [status.json](status.json) page on this website. -In addition to the IOCCC-style _easter egg_, you may count on +In addition to the IOCCC-style _Easter egg_, you may count on the JSON status page having a JSON member with name of **"contest"** that will have a value of either **"closed"** or **"open"**. When a future **IOCCC** is announced or the IOCCC is currently open, @@ -229,7 +270,7 @@ and/or follow us on Mastodon via **@ioccc@fosstodon.org**. ## 2022-11-29 -We are plan to abandon our +We are planning to abandon our [IOCCC Twitter feed](https://twitter.com/ioccc) in favor of our new [IOCCC Mastodon](https://fosstodon.org/@ioccc) feed. @@ -263,7 +304,7 @@ If you do not yet have a Mastodon account, you may obtain a **free mastodon acco If you do have / obtain a Mastodon account, **please do us a favor and follow the IOCCC at**: ``` - **@ioccc@fosstodon.org** + @ioccc@fosstodon.org ``` The IOCCC wishes to thank the good folk running the diff --git a/status.html b/status.html index 3eb63c281..c2917f3f3 100644 --- a/status.html +++ b/status.html @@ -384,14 +384,14 @@

The IOCCC is closed

-

The IOCCC is NOT accepting new submissions at this time. See the IOCCC winning entries page for the entries that have won the IOCCC.

-

Watch both the IOCCC status page and the @IOCCC mastodon feed for information about future IOCCC openings.

+

The IOCCC is NOT accepting new submissions at this time. See the IOCCC winning entries page for the entries that have won the IOCCC.

+

Watch both this IOCCC status page and the @IOCCC mastodon feed for information about future IOCCC openings.

status.json

    {
         "no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
         "IOCCC_status_version" : "1.0 2024-03-09",
         "contest_status" : "closed",
-        "news_update" : "2024-05-31T22:33:29+00:00",
+        "news_update" : "2024-06-08T16:23:00+00:00",
         "status_update" : "2024-04-30T22:51:32+00:00"
     }
@@ -402,73 +402,80 @@

format

-

The following JSON members are required to be present status.json.

+

The following JSON members are required to be present status.json.

no_comment

This is a mandatory comment for which we offer no comment other than this comment. :-)

-

The JSON member value must be the following JSON quoted string:

+

The JSON member value must be the following JSON quoted string:

    "mandatory comment: because comments were removed from the original JSON spec"
+

IOCCC_status_version

+

This is the version of format of the status.json file.

-

The JSON member value of is a JSON quoted string the form “version YYYY-MM-DD”.

+

The JSON member value of is a JSON quoted string the form “version YYYY-MM-DD”.

This document describes version “1.0 2024-03-09”.

contest_status

-

The current status of the IOCCC.

-

The following JSON member value string may be one of the following JSON quoted strings:

+

The current status of the IOCCC.

+

The following JSON member value string may be one of the following JSON quoted strings:

“pending”

-

The IOCCC is not yet open, however there is a tentative scheduled -date and time by which the IOCCC will open for submissions.

-

A preliminary IOCCC rules, guidelines, and tools have been posted. +

The IOCCC is not yet open, however there is a tentative scheduled +date and time by which the IOCCC will open for submissions.

+

A preliminary IOCCC rules, guidelines, and tools have been posted. Comments and suggestions on these preliminary items are welcome. See the IOCCC news for details including the tentative scheduled opening date.

“open”

-

The IOCCC is open for submissions.

+

The IOCCC is open for submissions.

See the IOCCC news page for details on rules, guidelines, tools and deadlines.

-

Be sure to review the official IOCCC rules, guidelines, and tools -for any changes that may have been made while the IOCCC was “pending”.

+

Be sure to review the official IOCCC rules, guidelines, and tools +for any changes that may have been made while the IOCCC was “pending”.

“judging”

-

The IOCCC is closed to new submissions. The IOCCC judges -are in the process of judging the submissions they received while -the IOCCC was open.

+

The IOCCC is closed to new submissions. The IOCCC judges +are in the process of judging the submissions they received while +the IOCCC was open.

Watch the @IOCCC mastodon feed for updates.

-

Once the IOCCC closes, the judges will:

+

Once the IOCCC closes, the judges will:

“closed”

-

The IOCCC is closed and is NOT accepting new submissions.

-

See the IOCCC winning entries page for the entries that have won the IOCCC.

-

NOTE: From time to time, winning IOCCC entries may have their write-ups updated, -Makefiles improved and source code fixed. See IOCCC news for details.

-

Watch both the IOCCC status page and @IOCCC -mastodon feed for information about future IOCCC openings.

+

The IOCCC is closed and is NOT accepting new +submissions.

+

See the IOCCC winning entries page for the entries that have won +the IOCCC.

+

NOTE: From time to time, winning IOCCC entries may have their write-ups updated, +Makefiles improved, source code fixed etc. See IOCCC news for details.

+

Watch both this IOCCC status page and the @IOCCC +mastodon feed for information about future +IOCCC openings.

news_update

This shows the latest modification date for the IOCCC news page.

-

The JSON member value is a JSON quoted string obtained from the date field +

The JSON member value is a JSON quoted string obtained from the date field of the following ls(1) command:

    TZ=UTC ls -D '%FT%T+00:00' -ld news.html

NOTE: The date and time are given with respect to UTC timezone.

-

Sorry: It is possible that for some reason, the IOCCC news page +

NOTE: It is possible that for some reason, the IOCCC news page was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does.

status_update

-

This shows the latest modification date status.json file.

-

The JSON member value is a JSON quoted string obtained from the date field +

This shows the latest modification date of status.json file.

+

The JSON member value is a JSON quoted string obtained from the date field of the following ls(1) command:

    TZ=UTC ls -D '%FT%T+00:00' -ld status.json

NOTE: The date and time are given with respect to UTC timezone.

-

Sorry: It is possible that for some reason, the status.json file +

NOTE: It is possible that for some reason, the status.json file was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does.


diff --git a/status.json b/status.json index e422abd71..b10ea8928 100644 --- a/status.json +++ b/status.json @@ -2,6 +2,6 @@ "no_comment" : "mandatory comment: because comments were removed from the original JSON spec", "IOCCC_status_version" : "1.0 2024-03-09", "contest_status" : "closed", - "news_update" : "2024-05-31T22:33:29+00:00", + "news_update" : "2024-06-08T16:23:00+00:00", "status_update" : "2024-04-30T22:51:32+00:00" } diff --git a/status.md b/status.md index afea125e0..ecff5017d 100644 --- a/status.md +++ b/status.md @@ -1,80 +1,93 @@ # format -The following JSON members are required to be present [status.json](status.json). +The following **JSON** members are required to be present [status.json](status.json). +
## no_comment +
This is a **mandatory** comment for which we offer no comment other than this comment. :-) -The JSON member value must be the following JSON quoted string: +The **JSON** member value must be the following **JSON** quoted string: ``` "mandatory comment: because comments were removed from the original JSON spec" ``` +
## IOCCC_status_version +
This is the version of format of the [status.json](status.json) file. -The JSON member value of is a JSON quoted string the form "_version YYYY-MM-DD_". +The **JSON** member value of is a **JSON** quoted string the form "_version YYYY-MM-DD_". This document describes version "**1.0 2024-03-09**". +
## contest_status +
-The current status of the IOCCC. +The current status of the [IOCCC](index.html). -The following JSON member value string may be one of the following JSON quoted strings: +The following **JSON** member value string may be one of the following **JSON** quoted strings: +
#### "**pending**" +
-The IOCCC is not yet open, however there is a tentative scheduled -date and time by which the IOCCC will open for submissions. +The [IOCCC](index.html) is not yet [open](#open), however there is a tentative scheduled +date and time by which the [IOCCC](index.html) will open for submissions. -A preliminary IOCCC rules, guidelines, and tools have been posted. +A preliminary [IOCCC](index.html) rules, guidelines, and tools have been posted. Comments and suggestions on these preliminary items are welcome. See the [IOCCC news](news.html) for details including the tentative scheduled opening date. +
#### "**open**" +
-The IOCCC is open for submissions. +The [IOCCC](index.html) is [open](#open) for [submissions](faq.html#submit). See the [IOCCC news](news.html) page for details on rules, guidelines, tools and deadlines. -Be sure to review the official IOCCC rules, guidelines, and tools -for any changes that may have been made while the IOCCC was "**pending**". - +Be sure to review the official [IOCCC](index.html) rules, guidelines, and tools +for any changes that may have been made while the [IOCCC](index.html) was "**pending**". +
#### "**judging**" +
-The IOCCC is closed to new submissions. The [IOCCC judges](judges.html) -are in the process of judging the submissions they received while -the IOCCC was open. +The [IOCCC](index.html) is [closed](#closed) to new submissions. The [IOCCC judges](judges.html) +are in the process of judging the [submissions](faq.html#faq2_0) they received while +the [IOCCC](index.html) was open. Watch the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for updates. -Once the [IOCCC](index.html) closes, the judges will: +Once the [IOCCC](index.html) [closes](#closed), the judges will: -* Select the [winning entries](years.html) announce them on the [@IOCCC +* Select the [winning entries](years.html) and announce them on the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc). -* Notify the authors of entries that won the IOCCC via email using their previously -registered email address. +* Notify the [authors](authors.html) of entries that won the [IOCCC](index.html) +via email using their registered email address. -* Announce who are authors of this year's winning IOCCC entries via the [@IOCCC mastodon +* Announce who the [authors](authors.html) are of this year's [winning IOCCC +entries](years.html) via the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc). -* Upload the winning code to the [Official IOCCC winner repo](https://github.com/ioccc-src/winner) +* Upload the winning code to the [Official IOCCC winner +repo](https://github.com/ioccc-src/winner). * Update the [Official IOCCC website](index.html), and in particular -display this year's winning IOCCC entries at the top of the [IOCCC +display this year's [winning IOCCC entries](years.html) at the top of the [IOCCC winning entries page](years.html). * Update the [IOCCC news](news.html) page. @@ -82,22 +95,27 @@ winning entries page](years.html). #### "**closed**" -The IOCCC is closed and is **NOT** accepting new submissions. +The [IOCCC](index.html) is closed and is **NOT** accepting [new +submissions](faq.html#submit). -See the [IOCCC winning entries page](years.html) for the entries that have won the IOCCC. +See the [IOCCC winning entries page](years.html) for the entries that have won +the [IOCCC](index.html). -**NOTE**: From time to time, winning IOCCC entries may have their write-ups updated, -Makefiles improved and source code fixed. See [IOCCC news](news.html) for details. +**NOTE**: From time to time, [winning IOCCC entries](years.html) may have their write-ups updated, +`Makefiles` improved, source code fixed etc. See [IOCCC news](news.html) for details. -Watch both [the IOCCC status page](status.html) and [@IOCCC -mastodon feed](https://fosstodon.org/@ioccc) for information about future IOCCC openings. +Watch both [this IOCCC status page](status.html) and the [@IOCCC +mastodon feed](https://fosstodon.org/@ioccc) for information about future +[IOCCC](index.html) [openings](#open). +
## news_update +
This shows the latest modification date for the [IOCCC news](news.html) page. -The JSON member value is a JSON quoted string obtained from the date field +The **JSON** member value is a **JSON** quoted string obtained from the date field of the following `ls(1)` command: ``` @@ -106,16 +124,18 @@ of the following `ls(1)` command: **NOTE**: The date and time are given with respect to **UTC** timezone. -**Sorry**: It is possible that for some reason, the [IOCCC news](news.html) page +**NOTE**: It is possible that for some reason, the [IOCCC news](news.html) page was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does. +
## status_update +
-This shows the latest modification date [status.json](status.json) file. +This shows the latest modification date of [status.json](status.json) file. -The JSON member value is a JSON quoted string obtained from the date field +The **JSON** member value is a **JSON** quoted string obtained from the date field of the following `ls(1)` command: ``` @@ -124,7 +144,7 @@ of the following `ls(1)` command: **NOTE**: The date and time are given with respect to **UTC** timezone. -**Sorry**: It is possible that for some reason, the [status.json](status.json) file +**NOTE**: It is possible that for some reason, the [status.json](status.json) file was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does.