If you don't mind using a gibberish .xyz domain, why not an 1.111B class? ([6-9 digits].xyz for $0.99/year)
Is this just placing them vertically, nothing else?
I currently use the Tree Style Tab extension and really like how it handles sub-tabs and allows collapsing the tree nodes. If I can't have that this is probably not directly useful to me unless extensions can add that functionality.
I guess I'll be watching how this evolves though.
For MIT, why do you care? That's perfectly fine and explicitly allowed by the license. Same for Apache, but with a few extra requirements (like keeping a list of changes in the source code and preserving licensing information etc.).
As for how I know big corporations are using my code: the fact that a prominent project (publicly used by several tech giants) took a dependency on one of my tiny (permissively licensed) library packages is probably a clue.
There was some kind of incident between the artist and a camera woman. The exact details aren't public, AFAIK.
Assuming they went to signed 64-bit time, it should be about 3:28:32 pm UTC on Sunday, December 4, 292277026596. Yes, that last number is a year.
You forgot one:
I believe so, but in addition it is also a "the original meaning of 'barbarian' is non-Greek person" joke.
This War [...]
Unfortunately you'll have to be a bit more specific than that, too many wars going on at the moment...
My family shares a fairly uncommon surname with a professional athlete we are (as far as we can tell) completely unrelated to.
My father always joked that we should answer "we don't discuss that" when asked about it, as if there had been some huge falling-out.
Because you need a way to be reachable over HTTPS for other instances to be able to securely send you updates (new posts/comments/votes etc.), so you need a trusted certificate. While HTTPS does not strictly require a domain name^1^ it vastly simplifies the process.
^1^: It's possible to get a trusted certificate for an IP address, but not nearly as easy as getting one for a domain. And it's probably also more expensive than just getting a domain and using Let's Encrypt to get a certificate.
As of v0.18.2, Lemmy marks the "original URL" as the canonical URL so search engines know which page is the "real" one. Shouldn't that help?
You don't actually have to set all the modification dates to now, you can pick any other timestamp you want. So to preserve the order of the files, you could just have the script sort the list of files by date, then update the modification date of the oldest file to some fixed time ago, the second-oldest to a bit later, and so on.
You could even exclude recently-edited files because the real modification dates are probably more relevant for those. For example, if you only process files older than 3 months, and update those starting from "6 months old"^1^, that just leaves remembering to run that script at least once a year or so. Just pick a date and put a recurring reminder in your calendar.
^1^: I picked 6 months there to leave some slack, in case you procrastinate your next run or it's otherwise delayed because you're out sick or on vacation or something.