Vinstaal0 @ Vinstaal0 @feddit.nl

Posts

0

Comments

323

Joined

5 mo. ago

Yeah I know, but it also has a different use case. As far as I know RFC3339 is mostly used for programming while ISO8601 is the standard for international communication and I wish people would use it more. I have processed American invoices in the wrong month because of their date structure. I have no reason to it, but I always write my date ISO 8601 (YYYY-MM-DD)

The omitting of timezones doesn't matter to a vast majority of the world, since most countries only have one time zone so I don't see a reason why that is relevant in most use cases.

ISO is a general standard, it's in the name and the RFC is created for the internet, that is also in the name/description of the RF.

Using 2025-164 can be handy, I actually use the day of the year to check what invoices from previous year are open since those are the invoices that are due 164 days or more.

No I agree, hopefully we can all agree that the MMDDYYYY is the worst date format

it’s crazy to me that for all the ai “advances” in the past few years nobody has thought to improve subtitling.

That's what OP say, I just responded with the reason why that wasn't being done. Aka money

HA! if you even get to be 74!

But in some jobs the year is more important (bookkeeping/accounting) and doing YYYY-MM-DD automatically sorts your dates

I rather have somebody write their invoices at DD-MM-YYYY cause there is a bigger chance it will most likely not be an invoice from a North American company which notriously cannot make proper invoices and most software that actually scans and processes invoices is based on the European standaard DD-MM-YYYY or on ISO8601.

Most people communicate mostly with people in the same timezone's, partially because most countries only have one timezone.

ISO is a wider standard than the RFC standards though which is only for the internet

ISO8601 is YYYY-MM-DD nothing to do with weeks and isn;t the only difference of RFC3339 that you can use a space instead of a T in between the date and time? Also RFC3339 is only an internet standard while ISO is a generally international standard?

Only if you want to say you have the certification for it, you can use it if you want, that is fine

Actually YYYY-MM-DD is better since it can be used basically everywhere and with / it can't be used in filenames

Or just use ISO8601 whi uses hh:mm:ss and well it is an ISO standard, but at least DD:MM:YYYY makes more sense than what Americans are doing.

Also 4th of july ....

iso8601 aka 2025-06-12

Where do you think money for development of new shit comes from? From places where money is made, like TV, movies etc. YouTube doesn't really make more money because the ads are there.

And Twitter hahaha I can only laugh at that

No, but on the fields where there is money to be made for subtitles, like movies and tv shows.

Probably because a lot of countries either dub the content or it is already in their native laguage. You generally see a lot of subtitles on OpenSubtitles of countries like The Netherlands where that doesn't happen

Probably more, some that are mentally challenged awknowledge Trump is terrible, they are just mentally challenged in a nother way.

Not sure where I got it form, but I have a Proton VPN client on Linux. It is pretty barebone, but it works.

Personally I just pay the 12,10$ for Bitwarden and use SimpleLogin aliasses together with that.

I just miss Microsoft Office on Linux, but that has nothing to do with Proton.

They could survive if there was no tax over transactions between states, it wouldn’t make a lot of economic difference.

How do you think something like Lichtenstein exists? Yes they are decently rich, but they just import a lot

I just checked, yes it is every 24 hours, but I have to restart that thing regularly so that it is why it feels quicker I gues