dx1

Turns out "move fast and break things" doesn't work that well in the auto industry

I meant something a little more peer-to-peer than lemmy/mastodon actually. Each person self-hosting their own.

So in other words this is a tech issue.

As someone who's written in-browser player and transcoding/server code...the lemmy/mastodon etc. version of this can work, especially if flexible bitrate handling is baked into it (i.e., bitrate offer/acceptance matching over a protocol). You can get this down to YouTube interface + install some software + open a port on your firewall.

Did we not abolish the TSA yet? Funny how we're always losing ground on everything.

Like "AOC" didn't spend the last year talking out both sides of her mouth about a genocide, including endorsing one of its perpetrators. AOC isn't a "progressive", she's the epitome of the Democratic party, all appearance and no justice, "where protest movements go to die".

Activists have already moved on from her, what is taking the rest of you so long?

"Fanatical" would be a word to use there maybe.

Years

YYYY

±YYYYY

ISO 8601 prescribes, as a minimum, a four-digit year [YYYY] to avoid the year 2000 problem. It therefore represents years from 0000 to 9999, year 0000 being equal to 1 BC and all others AD, similar to astronomical year numbering. However, years before 1583 (the first full year following the introduction of the Gregorian calendar) are not automatically allowed by the standard. Instead, the standard states that "values in the range [0000] through [1582] shall only be used by mutual agreement of the partners in information interchange".[20]

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[21] An expanded year representation [±YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign[22] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on.[23]

If you're being handed a string 2022424-12-19T14:44:39Z, and told it's ISO-8601, you should be able to figure it out. Really, a decent parser should be able to recognize that on its own (just use {4,} instead of {4} in regex). It does mean that non-hyphenated YYYYMMDD shouldn't be used (I typically never see them encoded that way) - but even if you did, you'd just do (\d{4,})(\d{2})(\d(2}).

Planes crashing out of the sky wouldn't have been inconceivable. Say you have two air traffic control systems that are synchronizing - one handles dates with a modulo 100 (00-99, i.e. 1900-1999), another handles them in epoch time. All of a sudden the two reported time + positions of two different planes don't match up by a century, and collision projection software doesn't work right. I've seen nastier bugs than that, in terms of conceptual failure.

At no point is that a theory about a "conspiracy" either, IDK why you're bandying that term around.

...

Yeah, that and the racist depictions of Babu, the Chinese postman and restaurant staff, the inexplicably Middle Eastern "Soup Nazi"...the fact that the only time black people ever appear on the show is to tokenize them and make an issue out of their identity...same with the association of Hispanic people with criminality (i.e. the two Puerto Rican guys with the armoir)...that is just off the top of my head...

I suspect you have better answers to that question than I do. Though the more pertinent question would probably be the reparations they're owed from the genocide perpetrated against them by the U.S.

The pay is low because bonuses make up for it (supposedly).

Business lesson #1: a promise in writing is the only kind that has value. At least in this godforsaken civilization.

IDK why the second pic says "same capacity" when...you can see they don't have the same capacity.