running this the other direction it seems a touch odd to suggest my own instance's 6969 character limit is capable of conferring some amount of authority, but hey i'll take it
unless i misunderstand the implication as to their behavior on touchscreenful computers, this would seem to poorly address the concern upthread of explicitly expecting the touchscreen hardware, and thus the concomitant…
railway guns go all the way back to the us civil war, but i suppose we can still quibble on locomotive there.
sure, i'm happy to recant my rather tepid defense of chainguard in the case that what was said upthread was a blatant fabrication. i'm even open to being convinced that it was. as it stands though, what i replied to…
what exactly is the point of maintaining coordinated disclosure even if one believes in it wholeheartedly in the case where the thing in question is under active exploitation already and there is no longer any hope of…
what possible reading of "I made the call to get these out early when exploits hit in the wild" contorts into "these exploits hit in the wild after i made the call to get these out early" with flipped causality?
this is basically how raku fixed perl regex
was this discussion not about apostrophes? but yes, different sets of pronouns work differently. more to the point, those different ways are not confusingly akin to contractions.
does your terminal on your laptop smoothly resize to match the same terminal session constrained by the screen dimensions of the phone you just opened it on so that you can monitor something from either? can you easily…
"its" is precisely parallel to "hers" though?
having a base there at all would seem to embody an inherent concern as to the self-determination of such islands insofar as one wants to keep determining the fate of the base
changing what cursor actions prompt it to stop hiding
presumably somewhat more like nebula
maybe then we'll pin hashes instead of filenames, and oops now anybody can fork my/domain and hand out a link that looks official with whatever contents they wish
when people left their laptops unlocked, we used to wrap their sudo so that the output would be pre- and postfixed with ascii dolphins
phones let you type … effortlessly
would you care to share your interpretation of the function of the word "just" upthread? because that would appear to be the operative part doing the reducing that you've conveniently left out here.
potentially overly-aggressive spam filtering? the first comment by that account happens to start off with "The new $39.99 USD Anker Nano 45W(A121D) charger" verbatim.
mainly i just mean dataset configuration and arrangement within the filesystem in general as it pertains to whatever you're actually doing. if you can reliably send writes with different storage characteristics…
> ZFS needs around 1-5GB of ram per TB of storage ...per unique TB written to datasets with deduplication enabled, of course, not the pool as a whole (even though that ram cost is indeed at the pool level). there are…
if you don't trust something to survive an atomic filesystem snapshot, why would you trust it to survive sudden power loss?
well the good news is you can indeed already just have unified cpu/gpu memory on linux with an igpu on good old replaceable ram. i've done it on 8th gen intel stuff i picked up dirt cheap used. for the most part,…
you can just hash the metadata masking out the hash as all zeroes or anything similar to get around that, like header checksums that ostensibly include themselves
(to be clear, i have been on mastodon/fedi for coming up on a decade now and have no qualms about the way leaving or sunsetting an instance works. part of the magic imo is that old posts from long-dead instances…
i've always thought one of git's strengths is offering robust aliasing and subcommand flexibility. why not spend three seconds making git have split too?
running this the other direction it seems a touch odd to suggest my own instance's 6969 character limit is capable of conferring some amount of authority, but hey i'll take it
unless i misunderstand the implication as to their behavior on touchscreenful computers, this would seem to poorly address the concern upthread of explicitly expecting the touchscreen hardware, and thus the concomitant…
railway guns go all the way back to the us civil war, but i suppose we can still quibble on locomotive there.
sure, i'm happy to recant my rather tepid defense of chainguard in the case that what was said upthread was a blatant fabrication. i'm even open to being convinced that it was. as it stands though, what i replied to…
what exactly is the point of maintaining coordinated disclosure even if one believes in it wholeheartedly in the case where the thing in question is under active exploitation already and there is no longer any hope of…
what possible reading of "I made the call to get these out early when exploits hit in the wild" contorts into "these exploits hit in the wild after i made the call to get these out early" with flipped causality?
this is basically how raku fixed perl regex
was this discussion not about apostrophes? but yes, different sets of pronouns work differently. more to the point, those different ways are not confusingly akin to contractions.
does your terminal on your laptop smoothly resize to match the same terminal session constrained by the screen dimensions of the phone you just opened it on so that you can monitor something from either? can you easily…
"its" is precisely parallel to "hers" though?
having a base there at all would seem to embody an inherent concern as to the self-determination of such islands insofar as one wants to keep determining the fate of the base
changing what cursor actions prompt it to stop hiding
presumably somewhat more like nebula
maybe then we'll pin hashes instead of filenames, and oops now anybody can fork my/domain and hand out a link that looks official with whatever contents they wish
when people left their laptops unlocked, we used to wrap their sudo so that the output would be pre- and postfixed with ascii dolphins
phones let you type … effortlessly
would you care to share your interpretation of the function of the word "just" upthread? because that would appear to be the operative part doing the reducing that you've conveniently left out here.
potentially overly-aggressive spam filtering? the first comment by that account happens to start off with "The new $39.99 USD Anker Nano 45W(A121D) charger" verbatim.
mainly i just mean dataset configuration and arrangement within the filesystem in general as it pertains to whatever you're actually doing. if you can reliably send writes with different storage characteristics…
> ZFS needs around 1-5GB of ram per TB of storage ...per unique TB written to datasets with deduplication enabled, of course, not the pool as a whole (even though that ram cost is indeed at the pool level). there are…
if you don't trust something to survive an atomic filesystem snapshot, why would you trust it to survive sudden power loss?
well the good news is you can indeed already just have unified cpu/gpu memory on linux with an igpu on good old replaceable ram. i've done it on 8th gen intel stuff i picked up dirt cheap used. for the most part,…
you can just hash the metadata masking out the hash as all zeroes or anything similar to get around that, like header checksums that ostensibly include themselves
(to be clear, i have been on mastodon/fedi for coming up on a decade now and have no qualms about the way leaving or sunsetting an instance works. part of the magic imo is that old posts from long-dead instances…
i've always thought one of git's strengths is offering robust aliasing and subcommand flexibility. why not spend three seconds making git have split too?