I miss when packages took like a week to arrive and there was no overnight postage nonsense (unless you paid a lot for it). Now it is industry standard and I need to be ready to get my package the next day, like...I need at least few buffer days to prepare emotionally.
Also the tracking system is not great and telling me it can come between 8-16 is NOT HELPFUL.
I an up at 8 only in case it arrives now.
Madness, I tell ya.
@Firlefanz Our drop boxes send you a code via text, which you then use the boxes. No extra app.
But mailing system has an app that tracks the delivery ("tracks"), and has some other objectives like "see your bills, which we dont send as a paper version anymore, or straight to your bank for some reason, so you need this app" and "offical papers also come here so you clutter both your hone with them and this damn app". Not a big fan...
@heaths Communities should have “spring cleaning” events. Where authors put their packages up to either be maintained by others, mark them as “done”, or archive them away and out of package registries.
@ErHaWeb That makes you responsible to monitor the bundled dependencies and provide updates to TER if any of them receives an security update.
A general issue of delivering bundled software. Using composer moves that responsibility to the consumer.
Which also enables consumers to update instead of waiting for publishers to catch up.
@danielsiepmann@ErHaWeb We had some TYPO3 Extension Security Bulletins in the past, which focused on vulnerabilities in bundled 3rd party libraries, which were exploitable through the extension.
So bundeling 3rd party dependencies in an extension does always move the responsibility to update those components to the extension maintainer. This is basically the same with TYPO3 core, where 3rd party dependencies must be updated, if known security vulnerabilties exist.
I've placed half a dozen orders in the last month and a bit, and it seems that every single one hasn't even #shipped for 2 or 3 days after I place the order. Everything I've ordered was in #stock (and not marginally; "27,563 in stock" type of thing).
Well, my "insider" works in catalogue department, so may not have any information.
Aha! but I was wrong. A month ago they moved to a new facility, which is much more automated. And there have been issues, both with the new custom-designed system and with the learning curve. Supposedly last week they were almost back to normal output speed, but of course they have backlog to catch up on.
@amadeus Ha! Oh goodness me no no nooooooooooo. I know next to nothing 👍. But i do know how to use a search engine, & i like to learn some cool tricks that way from peeps who actually do know stuff!
That script simply combines a couple of things i have progressively "acquired" from others over past years in this wunnerful :linux: journey, eg;
aliases [in this case, archlinux[~] 13:08:37 Sat Nov 04 $> alias chkalias chk='checkupdates' ]
tldr while [i learned of the former from a Chris Titus video, & the latter from some random internet browsing years ago iirc]
@AngryAnt@adingbatponder this isn’t quite true, actually. There are derivations besides nixpkgs, and you can import them as either a flake or a channel. (Flakes are much easier to write and publish.) But anything not in nixpkgs is harder to discover, which is why there are flake registries being created.