Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
7
Comments
74
Joined
1 yr. ago

  • There are some sites where Anubis won't let me through. Like, I just get immediately bounced.

    So RIP dwarf fortress forums. I liked you.

  • Yes! Thanks

  • Bring your own tea into the workplace?

    Tea bags are fine, but I recently discovered tea resin. It's basically a small block of concentrated tea that you dissolve into hot water. Not quite as good as fresh leaves, but more portable (dozens of servings fit in a tin the size of a USB stick) and very resilient against going bad.

    I have a small selection of resins on emergency stash in my work bag, in case the coffee machine at the office is broken.

    • I like sharing
    • I never found any good direct downloads for all the movies and shows I wanted
  • What do you mean by handling the keyfile?

    You can generate your ssh keys outside of docker and make them available in the container through a mounted directory. You will need to manually copy the public key to your remote host authorized_keys file anyway.

  • I always thought that wish-granting is instant, even if the effects of that wish are delayed.

    So if I wish for something to happen in 5 days, it's granted in the moment and guaranteed to happen. That raises a question though: Can I wish to cancel a wish I have already made, but whose effect has not yet taken hold? On its face, this should be possible, but if we take it as a given that all valid wishes are always granted at the moment of utterance, then it might be physically/psychologically impossible for me or anyone else to revoke the wish before its IRL effect is complete.

  • The pain of keeping it around will outweigh the pain of needing it and not having it.

    Quick boot into windows to help a friend test something on your machine?

    • Twenty-five bajillion updates since you never logged in
    • Windows "helpfully" cleaning up your Linux bootloader
    • Any shared NTFS partition between windows and Linux is almost guaranteed to be left in a "dirty" state when windows shuts down, meaning you have to run ntfsfix before Linux will mount it again

    And suddenly, that's where you'll be spending the whole afternoon. I agree with the others who say a VM is probably good enough.

  • Shouldn't he be folding little origami animals or something?

  • You should report this to somewhere like 404 media

  • SRE:

    • Receives a slack message that lighbulb is broken
    • Realizes that they never got an alert when the light went out
    • Fixes their monitoring thresholds
    • Routes all broken lightbulb alerts to a slack channel nobody reads
  • I do that for data I want to persist, but which I don't care about backing up (eg caches)

  • I can outsource things like ddos protection to my cdn provider, but that would still be just kinda hoping I didn’t have any attackable surface I didn’t think of prelaunch.

    In that case, I wonder if your money would be better spent on contracting a security review. If you're worried about unknown attack surface, I'm not sure that funding organized crime to rent a botnet would help. Botnet operators rely on you to tell them what to attack, so you're unlikely to discover anything new here. Better to hire a professional and get a fresh opinion.

  • Is this something you're self hosting for fun, or is it some kind of business?

    If you're running web services for a business, you should look into existing load test tooling/infrastructure. Some of it can be fully managed, or other solutions might have a degree of setup involved (eg spinning up worker nodes in AWS or whatever). The hard part is designing your load test to match IRL traffic patterns, but once you have that down you can confidently answer questions about service scalability.

    A load test is not a DDoS test. Load tests tell you how much legitimate traffic your services can take. DDoS consists of illegitimate traffic which may not correspond to what your web services expect.

    Usually you don't test your systems for something like a DDoS. You would instead set up DDoS protection through a CDN (content delivery network) to shield yourself and let someone else handle the logistics of blocking unwanted load. It's a really hard problem to solve.

    Depending on what you want to learn, running your own DDoS is unlikely to be very instructive. Most "DDoS as a service" networks are not going to tell their customers how anything works, they just take your bitcoin and send some traffic where you tell them.

  • Maybe they once read the thing and got an answer, but now they forget what the specific answer was.

    This happens to me often with technical documentation or history books.

  • Small blessings. Seeing a WSL user means that some dev out there didn't have to implement Windows support.

  • I realize that this is a humor post, and not necessarily the right place to provide advice, but never underestimate the power of adding a Q&A meeting to someone else's calendar. Someone doesn't want to make time to explain mystery tool? Well you just made it for them. Usually I try and be polite by asking before I arrange something.

  • WRONG!

    • The proper amount of coffee is actually "Up to the number 3 on my grinder's fill chamber"
    • The proper waiting time is 6 minutes
    • The proper vantage point for casting judgement is behind a keyboard

    I'll see you at the world barista championship