Rose here. Also @umbraroze for non-kbin stuff.

  • 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • My theoretical answer is this: in an ideal world, there would be no copyright at all. This is an artificial contrivance that was once dreamed up to serve physical-copy economy, and it was rendered obsolete by the digital age. Shit would be so much easier when we got rid of this shit and everyone could share everything by default without any profit motive. (Caveat: This will not work unless literally every jurisdiction on the planet gets rid of copyright laws all at once, otherwise this is way too exploitable due to power imbalance. So I don’t think this is a practical proposition. *cough* unless we all decide Anarchism is a good idea after all *cough*)

    My practical answer is this: Welllllll we’re kinda damned if we do and we’re damned if we don’t. My personal feeling is that AI creations aren’t really copyrightable, and even suggesting they are copyrightable is kind of opening a huge can of worms regarding what exactly counts as “creativity” in the first place. The best we can do under current copyright regime is to regulate how the AI datasets are curated, because goodness knows the current datasets weren’t exactly ethically obtained.





  • Funny thing, in ISO 8601 date isn’t separated by colon. The format is “YYYY-MM-DDTHH:MM:SS+hh:mm”. Date is separated by “-”, time is separated by “:”, date and time are separated by “T” (which is the bit that a lot of people miss). Time zone indicator can also be just “Z” for UTC. Many of these can be omitted if dealing with lesser precision (e.g. HH:MM is a valid timestamp, YYYY-MM is a valid datestamp if referring to just a month). (OK so apparently if you really want to split hairs, timestamps are supposed to be THH:MM etc. Now that’s a thing I’ve never seen anyone use.) Separators can also be omitted though that’s apparently not recommended if quick human legibility is of concern. There’s also YYYY-Wxx for week numbers.





  • Technically, SQL is case-insensitive.

    Practically, you want to capitalise the commands anyway.

    It gives your code some gravitas. Always remember that when you’re writing SQL statements you’re speaking Ancient Words of Power.

    Does that JavaScript framework that got invented 2 weeks ago by some snot-nosed kid need Words of Power? No. Does the database that has been chugging on for decades upon decades need Words of Power? Yes. Words of Power and all the due respect.




  • Well, Google Photos shouldn’t be considered a “backup” solution to begin with. Never mind that both Google and Apple scan the content in their respective services, but there’s just no guarantee that they don’t modify the data on cloud. “Oooh guys, we just invented a revolutionary new photo compression algorithm! Also hosting data is kinda expensive! So pay up if you want your originals.” …and there’s occasional reports that these services just straight up corrupted some old files while no one was looking at them. Good going.

    I just treat my Android phone like any other camera I own and use. Copy the files from phone to PC and from there to my NAS, and I use ACDSee’s DAM functionality.




  • Scrivener is still the absolute best word processor for ginormous writing projects. There are FOSS projects that do some parts of it right, but fall far behind in the others. It’s particularly frustrating because my usual FOSS approach would be to use other tools that make up for the inadequacies, but Scrivener pretty much nails the “what to include and what to leave out” equation. It’s a great combo of a word processor, project management tool and a research/notes tool, all rolled into one.