2025-10-19 11:46:42
Titan submarine: There were 3 fanless PCs and a switch in there before being imploded!
(Originally saw it on Scott Manley's video about this)
From:
https://data.ntsb.gov/Docket/Document/
Titan submarine: There were 3 fanless PCs and a switch in there before being imploded!
(Originally saw it on Scott Manley's video about this)
From:
https://data.ntsb.gov/Docket/Document/
@borkdude, in your 'scittle with additional libraries' files, you have, for each file in the library, a line
SHADOW_ENV.evalLoad( <filename>, <boolean>, <???>);
where ??? is a string of JS source code with some punctuation replaced by hex codes.
The second last line appears to invoke the file itself (recursively!?!), and the last is always
SHADOW_ENV.evalLoad("shadow.module.<filename>.append.js", false, <???>);
Wha…
⚙️ Print mode runs by default for non-interactive execution, interactive mode enabled via .i. filename marker (task.i.claude .md), _interactive frontmatter key, or -_i CLI flag
🌐 Remote URL imports cached at ~/.mdflow/cache/ with 1-hour TTL, use --no-cache to force fresh fetch, automatic .env file loading from markdown file directory with support for .env.local, .env.development, .env.production
Ok, I’m procrastinating downloading a bunch of vids with yt-dlp and at this point I’m already reaching the tabs limit on this Safari profile
What’d be the best way of downloading a bunch of videos with yt-dlp while still keeping a good control of what failed and what succeeded? (this is basically impossible from its output if you feed it a bunch of links in a single go)
I was wanting a webui I could selfhost and it’d show progress and status for each video it’s downloading (and let me pass custom options to the yt-dlp command, such as filename), but should I just make a script with a for loop for each URL instead?
I do like #NextCloud but sometimes it can drive me crazy. For example, fresh update, hundreds of errors with astoundingly unhelpful messages. Consider:
chmod(): Operation not permitted at /var/www/nextcloud/apps/recognize/lib/Migration/InstallDeps.php#169
ok, so what do we find at line 169? a call to chmod() on presumably a filename, wrapped in an exception Catch.
I realize this is very much non-trivial software with oodles of hours of difficult work by so many kind people, but, really, how much effort would it have been to include the errant target FILENAME in the exception message?
Similarly, a deprecation warning is, by definition, a Warning, not an error.
None of this affects my using Nextcloud, but it does really clutter the log and who knows, maybe some of these Errors are actually important?
@… weird, I had no trouble with GNOME Disks.
What exactly were the symptoms, following the write to the stick?
What's the filename?