Vogel612

Leek is a slangy term for someone physically inept

@SᴀᴍOnᴇᴌᴀ yep. It's a pun on Smoke Detector.

lol dat username @Lauchmelder

roughly half of the comment deletions from 2024 were attributed to non-diamond users, which is probably to a large extent system-automatic flag handlings for comment flags

Small sidenote to that: there are (quite a few) conditions where comments are automatically removed, that may have been a useful tidbit of information

IINM that's just a system prompt based off thread detection that performs a system-action if triggered

that "move comments to chat" thing isn't even a specific privilege.

@RMunroe that alt text is only problematic because bq is such a tiny unit... it's like the gram calorie of radioactivity... if that was an Sv that would be quite appropriate to have in a HAZMAT container

yup.

duga, I answered that AFTER the edit...

it's called neutrinos :D

double tapped

@Mast "openGL" and "high-level library" don't really go together

It's basically the difference between: if (transaction.IsPaid) and if (transaction.Payments.Select(p => p.Amount).Sum() >= transaction.Basket.Items.Select(i => i.Price).Sum())

I think it's more about making the conditions associated with these statements as impactful as possible on the abstraction level of the surrounding code.

or something like that :)

/lurk

Monking and a slightly late happy new year :)

datacenter

they used to run out of a single fully-in-RAM SQL Server instance with live replication to a hot fallback within the same datacenter and a fallback readonly setup on the second DC

the product itself doesn't look like it's hard to migrate, but all the stuff around it most likely is a headache

@SᴀᴍOnᴇᴌᴀ SO specifically had invested heavily in highly optimized self-hosted code with full infra control, so I'm not surprised it took them longer to pull the trigger on migrating to cloud

That shout out thing has been ongoing for quite a while now. It's basically a closing thing on the podcast to tie the whole thing back into stackoverflow proper

"log in with this password. You will be prompted to input your own, new password"

AIUI the generated password is just a one-time password

none of that really matters, considering the original requirements of the question, though

while you are correct in that the restriction reduces entropy, it is the state of the world that that used to be a fairly common requirement (just like mandatory password rotations) and it is prudent for a password generator to match such requirements to make generated passwords fit to existing (however bad) password policies

IIRC using the lang prefix pushes the highlighting spec directly to the highlighter implementation. Not using it sidesteps via the tag, where a highlighter language can be configured by mods, but it's been a few years since I looked into that

I never said it did cause an invalidation ...

@Gao from a quick skim: The formatting of code is subject to review. That includes indentation. So the second code block should not be edited (assuming that an answer exists), hope that clears it up a bit :)

also how are you handling multiline input?

@Peilonrayz does "up" do history? because Ctrl+R is awesome

@Peilonrayz "A while back" is probably half a decade now

IINM it also queries Programmers.SE and stackoverflow?

to be fair the posting to chat should not be affected, it's more the way duga queries the site that might be interesting

Should Duga be on the list of tools that need to be not affected by the planned rate limiting? meta.stackexchange.com/questions/403002/…

@pacmaninbw the supreme court made it legal for cops to commit most crimes quite a while ago. Extending that privilege to the president is not really a big leap :/

@Reinderien well, it would be more kafka to not be allowed to edit your own answer because the question it's on happened to be subject to an edit war

it's a good thing

the fun thing is that the answers that are already there can still be edited

Monking

Monking

Monking

the run: commands are shell

 [...]
    steps:
  - name: Setup MSYS2
    uses: msys2/setup-msys2/@v2
    with:
      update: true
      install: >-
        git
        make
        gcc
  - name: Checkout
    uses: actions/checkout@v4
  - name: Build
    run: make CC=gcc
  - name: Test
    run: make CC=gcc test

might be something horrible like an updated build being pushed out to the CDN weirdly and thus cache-breakered styles not being available at the moment you loaded the page initially

if in doubt blame caching

looks like an incomplete page load

"logic decides" ... how nice.. elaborate on your axioms, though/

morning? I'm quite late to finishing work :D