Show newer

@mcc

The general principle I've heard many times is that one should not care about noise alone. (That said, noise can help in diagnosis of other problems -- many issues have specific angles of flexion at which noise/crepitus might occur.)

Also, there is at least one completely benign reason for joint noise (I'm not sure how common it is in knees): cavitation creating and collapsing bubbles. This is why you can crack your knuckles.

@not2b @lauren

The "everything else" will not include other libraries that Chrome loads though.

@munin

Without any lathed parts, or also without parts that were made with lathed tools etc.?

@munin How much do you want to cover by the notion of the same tool? For example, golang compilers usually get built with earlier major versions thereof (and eventually with a C compiler) -- would they count?

@mattblaze @ai6yr @douglasvb

and starts to arrange for such accidents, because they tend to happen too rarely for their liking.

@b0rk

For that reason also running `foo` and `cat | foo` will exhibit different effective stdin buffering behaviour -- in the former case `foo` will see your input line-by-line while in the latter likely will see it only once you send EOF (the buffer is iirc 16KiB).

@b0rk

The behaviour of stdout handling (at least in glibc) depends on whether it's a terminal: terminals get line buffering, pipes and regular files get a fixed-size buffer. This means that a program that runs for a long time and slowly outputs stuff to stdout will appear to be stuck when its output is redirected to a file _or even piped to `tee`_.

@AubreyDeLosDestinos @rysiek

Since when does it have them? I didn't see any up to ~2w ago.

@katanova @aeischeid @SymTrkl

I wasn't suggesting appealing to higher power. The change I described is a purely client-side one (and is probably similarly confusion-engendering as the "ignore DMs" switch some people enable).

WTAF. Firefox has "sponsored shortcuts" on new tab page: support.mozilla.org/en-US/kb/s

@rysiek who I think might be ~interested

@katanova @aeischeid @SymTrkl

Do you see any obvious problems with a stronger version of "no DMs" where one doesn't ever see any posts that are not public?

@TechConnectify @SymTrkl

Would solving just this (causing you to never see non-~public responses) be a significant improvement for people in positions similar to yours?

spoiler 

@_thegeoff Hmm... I thought the ending claimed that the clone that returned lived for some time on Earth.

Also, expose to whom? The people who operate the Earth end of the operation and thus can probably tell that no new engineers are being sent up? But yes, I didn't consider this option, and the people dealing with helium shipments need not have been in on the whole thing.

@TechConnectify @sqrt2

I think that sqrt2's complaint is different: the author of that comment is now getting ~your experience, albeit nearly only on a single comment of theirs.

spoiler 

@_thegeoff

When I watched it, I got mightily confused near the end: I couldn't imagine why the guy is trying to commit suicide (I think something earlier in the movie implied that the accelerations of the cargo railgun were too high for humans).

@rysiek @DamonHD ah, I just realized that I don't know how DNS TTL works in _clients_. Thanks, I will need to look it up.

@rysiek @DamonHD wouldn't it be ~1xTTL+epsilon? (The recursive resolver would reask once TTL has expired, would promptly get the new answer, with only requests it was serving before it got the new answer getting old responses, no?)

@rysiek @DamonHD

Does this mean that your way of mitigating ddoses would kick in on that timescale?

@rysiek @Herover

Did you choose not to only coalesce concurrent requests because that's more fiddly, because the load difference between 1/10 Bq (or should I say Hz) and 1/[time it takes to serve the request of the backend] is meaningful, or for some other reason?

@kuba @rozie @tomo @arkd @tomek

Jest, strzelam, więcej oponentów palenia w np. parkach niż picia. Powiązanie takich dwu zakazów uczyniłoby oba bardziej trwałymi.

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.