Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 28 |
Nodes: | 6 (1 / 5) |
Uptime: | 46:06:02 |
Calls: | 422 |
Calls today: | 1 |
Files: | 1,024 |
Messages: | 90,336 |
Please post your predictions for the GP in United before the start
of P1 on 22/11/2024. Times for various timezones appear below, but
the cutoff is start of practice.
Pole position:
P1:
P2:
P3:
Please post your predictions for the GP in United before the start
of P1 on 22/11/2024. Times for various timezones appear below, but
the cutoff is start of practice.
Pole position:
P1:
P2:
P3:
Track (Last Vegas) 21/11/2024 20:30 PST
I used to update it a few times during the season - fully automated and
taken straight from the F1 web page - but they've made the data _so_
horrible (and change it even mid-season) it's become semi-manual and >long-winded.
All because web designers these days are *so* sloppy, they can't even
get basic validation of data right...and browser companies are complicit
as they have built acceptance of this brokenness into their browsers, so
that they can render even the most broken pages (mostly).
* I'm talking about a level of unmatched and mismatched tags that it
makes validation tools and parsers give up in frustration. Just a
simple example is the 96 violations (24 errors, 4 warnings, 68 info
advisories) that the W3C validator comes up with just on the front
results page:
https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.formula1.com%2Fen%2Fresults%2F2024%2Fraces
On Mon, 4 Nov 2024 13:20:28 -0000 (UTC), Mark <mpconmy@gmail.com>
wrote:
I used to update it a few times during the season - fully automated and
taken straight from the F1 web page - but they've made the data _so_
horrible (and change it even mid-season) it's become semi-manual and
long-winded.
It is one of the reasons I'm a bit slower with results the last couple
of years. For a decade, that was fully automated. A Python script would
parse the F1 website, compile the full set of results and inject them
into the SQL table. Another script would then build the results post.
Please post your predictions for the GP in United before the start
of P1 on 22/11/2024. Times for various timezones appear below, but
the cutoff is start of practice.
It is one of the reasons I'm a bit slower with results the last couple
of years. For a decade, that was fully automated. A Python script would
parse the F1 website, compile the full set of results and inject them
into the SQL table. Another script would then build the results post.
Pole position: VER
P1: VER
P2: NOR
P3: LEC
Please post your predictions for the GP in United before the start
of P1 on 22/11/2024. Times for various timezones appear below, but
the cutoff is start of practice.