15:30:19 <danmcd> @Dixie_F you should ask this question on illumos (and PI stamp is recent enough to just say, "current illumos-gate"), but I think our xhci itself could use a little more love in this regard.  We don't, to my knowledge, device-specific-tune anything.
15:34:06 <Dixie_F> @damncd I don't see a #illumos.  I looked previously.  There is #illumos-rust (and -de and -go) but each has less than 20 users
15:42:31 <jbk> it's +s for some reason, but you should still be able to join
15:42:47 <jbk> maybe a past issue with annoying bots joining
16:23:38 <gemelen> I've noticed "rsync updated to 3.4.3. (OS-8734)" in release notes for the latest image and got to think: is there any (implicit or not) agreement on what to do with such tools and utils when they accomodate too much slop and thus bugs? rsync after 3.4.1 shows a significant degradation of quality on mainstream platforms already (where even old Linuxes are left out of QA)
16:29:26 <pjustice> one specific case: https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390
16:35:00 <jbk> heh.. a friend of mine was just talking about the performance issues (that seem to be AI related) with the latest rsync version...
16:39:16 <gemelen> last 6 or so months I encounter it here and there, where previously stable projects (big and small, active or not) went into frenzy about spitting out barely working things
17:41:56 <danmcd> The rsync 3.4.3 update was to plug more than a few things in 3.4.1.  Security patches are the primary motivator for such bumps in illumos-extra tools.  Backporting them is more work than taking the latest version(s).
17:43:30 <danmcd> I see what you mean though:  https://infosec.exchange/@0xabad1dea/116659021592304179
22:02:32 <MelanieUrsidino> should it be handled like xz?