“Follow my path and you’ll be fine.”

Later, at a Republic Tribunal:

“… and obviously no sane pilot on a training mission would ever consider attempting to navigate those obstactles without weeks of study in advance. And so I exhort the jury not to consider leniency, but to find the defendant guilty of first degree premeditated murder of their wingman pilot in training. The prosecution rests this - quite frankly open-and-shut - case.”

And a Python developer is born!

Source: I moved on from an abusive relationship with JavaScript to a healthy not-at-all-controlling equal partner relationship with Python. And four spaces makes perfect sense, once I really considered Python’s point of view…

Have you ever been to PowerShell Summit? It’s the only nerd conference I’ve ever attended where only about half the attendees actually realized they are nerds at a nerd conference. I love the vibe. It’s got style and pizzazz.

That said, the added entry for PowerShell would still be: “You are a nerd.”

Well shit. It’s got me dead to rights on a couple of these.

What a fantastic redition of those tradgic orphans!

I’m sure it would bring great joy, if their story was any less unfortunate!

This is terrific. Thank you for starting this discussion.

I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.

I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.

But we know from XMPP that proprietary extensions are a huge problem.

I’m planning the same.

I like to roll a d4.

4 - Adlib an outcome that is favorable to them, beyond all reason. With my players, sometimes this just means nothing at all happens. In these cases I’ll use anything to make it work out for them, from divine favor, to a key NPC breaking rank “I always loved you guys!”

3 - They achieve what they hoped for, and as many weird (but reasonable) side effects as I can think of also happen.

2 - As little happens as is reasonably possible. Often, with my players, that means just 6d6 fire over a 20ft radius. Often after having whatever they tried misfire first, only to have them try again.

1 - I unpack a nice handful of d12 and roll for blast radius, save DC and damage.

Modified, of course, for the situation.

Specific damage on a 2 or 1 should - like anything they couldn’t reasonably prepare for - be attention grabbing, but unlikely to be lethal. A 2 should as anticlimactic as reasonably possible.

Let’s not defederate from every corporate player. Some of them can probably respect reasonable rules of civility.

But fuck Meta. We already know how this plays out.

We know there’s a huge wave of hatred and misinformation incoming. We’ve seen it on their other platforms.

Yeah. I’ll switch to an instance that is defederated from Threads, if mine doesn’t.

I left Meta’s other properties to avoid state sponsored hate speech. I won’t use a platform that gives hate speech a platform.

I don’t need to wait to know if Meta will do that. I already know.

12d1 is the way to go.

In epic scaled games, I work around this with a “reroll at -20”. So the rogue in this case would have had about a 25% chance to recover on a DC10 check.

I also always include an in-game explanation. In this case, I would have made it a huge flashy “boon of insight” from the Paladin’s deity.

Then it’s all the more fun if the rogue actually manages the re-roll. “Dude, I even tricked your god!”

I would also RP right into it. “A voice from on high intones ‘I dunno, seems legit, to me.’”

Similarly if the rogue actually fails:

“A voice from on high intones ‘Seriously, you need to stop falling for this crap. I’m going to send you an amulet of insight or something. What’s your next stop?’”

I’ve had players have this exchange, and then the Paladin decided to ignore the rogue’s critical miss, and just roll with it.

Paladin to the rest of the party “I forget what they said exactly, but it was a very convincing argument!”

I actually did this once…I swear there was a good reason. I promise it wasn’t anywhere that mattered.

Edit: I think it was a personal journal repo that I wanted daily versions of, but couldn’t be bothered to actually check in.

I was being more evil than that, saying that if one is gonna push direct to main, might as well maximize the possible damage to everyone else’s branch.

Well that’s about half my commit messages that are going to be nonsense on weekends projects, now. Thank you!

Not with that attitude! /s

You forgot this --force flag.

Yeah. I don’t know if the ‘follow’ piece does anything useful for anyone.

But as a professional developer, I have found that my GitHub account now prevents me from getting asked FizzBuzz at interviews. So whichever bit is causing that nonsense to stop, I hope they keep.

Incidentally, for anyone who hasn’t typed ‘import antigravity’ into an interactive Python terminal…you should - as Dr Seuss says, “These things are fun, and fun is good.”