> ranking is based on favorites/comments rather than a hidden algorithm
But there has to be an algorithm to decide how to rank based on favourites and comments, and I couldn't see that algorithm described anywhere on the site, so I dare say that it's hidden.
Small gripe with the site, it somehow has the "swipe with two fingers sideways to go backward or forward in the browsing history" gesture disabled, which is kinda annoying. (macOS with Firefox)
I'm curious about the legal implications of this. For example:
- In the EU, a consumer has 14 days to withdraw from a contract that you have concluded online, unless the consumer explicitly waives this right during the purchase (so your payment required page will need an explicit statement about this).
- I'm pretty sure in the EU, and probably most countries, you must receive an invoice, even if it's for a 1 cent purchase.
- You might also have to pay VAT on these transactions, which will need to also be included in the invoice. This is especially important for B2B purchases, because companies can claim back VAT.
- What happens if I complete the purchase, but there is an error in the response returned by the website? I.e. between the events of my purchase being confirmed and the server returning the response, the server dies. What recourse do I have?
I found out some years ago that emails that have the fancy features like plane tickets embedded or tracking information are all done with JSON-LD in the emails.
I've got some tests in active code bases that are using the end of 32-bit Unix time as "we'll never get there". That's not because the devs were lazy, these tests date from when that was the best they could possibly do. They're on track to be cycled out well before then (hopefully this year), so, hopefully, they'll be right that their code "won't get there"... but then there's the testing and code that assumes this that I don't know about that may still be a problem.
"End of Unix time" is under 12 years now, so, a bit longer than the time frame of this test, but we're coming up on it.
I seem to recall much smugness on Slashdot around the "idiot winblows users limited by DOS y2k" and how the time_t was "so much better". Even then a few were prophesying that it would come bite us eventually ...
Now I feel bad for using (system foundation timestamp)+100 years as end of "forever" ownership relations in one of my systems. Looking now, it's only 89 years left. I think I should use nulls instead.
https://factorio.com/blog/post/fff-388 - they wanted to use a 64 bit int for the tick count, but Lua doesn't have one; so they used the one available and worked out when it would lose precision.
"More than 2 million years seems to be enough for us to not be around any more when the bug reports start appearing."
I once saw a pop-up in a game saying something along the lines of: wow, it's 10 years later and this game is still being played! Made me laugh out loud, nice little easter egg.
Sadly, I don't recall which game it was. Maybe SpaceChem?
The guy that made that did a writeup on reddit: https://www.reddit.com/r/PixelArt/comments/1v52x96/