Colton Armstrong

Have you followed my other talk with the dynamic paths? :3

Hi~

Once the trap is passed, it's a permanent flag on the interaction, and you can't go back above it.

The fact it's selectable is for graphs like this one:

I mean Voresky already has features that basic Bluesky doesn't.

We'll see what's getting pushed, and how we can work them around.

This may not be clear enough actually, yeah. Reading back, this is indeed confusing. So, okay, without the trap, doing "go back one node" all the way to the top lets you escape normally.

If there's a trap, you can't go back above it.

Yes, it counts.

- planning to have timed nodes to have a default choice, paused letting them chose whenever they want
- good question, not sure yet, let's start with prey only and we can expand?
- already the case - nodes are closed based on CW, and the processor denies a proposal if there's no possible exit at all

I can allow you to access staging if you want to test things out :3

It's technically already deployed, just gated behind a feature flag.

I have 5 versions of the website. "dev", "test", "staging", "next", and "prod". It's currently disabled for prod.

"dev" and "test" are two separate db on my local machine.

"staging" is a separate prod db.

"next" hits prod's db.

I might need help with testing this :3

So traps evaluate at the entry and you don't see them coming as a result.

Traps don't trigger PONR, so no mandatory respawn. The prey can still advance through paused nodes. And the pred can still free a trapped prey.

This is the case now.

More seriously though, I'm just laying the groundwork for the next big update...

... Which will probably be make or break for the platform, and I need to nail it properly.

Never <3

... been there done that, honestly.

In an old job, former colleague of mine was looking for an issue in production. He spent some time googling about it, when he finally found a very detailed and specific stackoverflow question that was EXACTLY the problem...

... with no replies
... written by me.

So Voresky depends on Bluesky's Appview, but there's still lots I can control on my end. Deploying a full appview would use considerably more resources, but it's an option if push comes to shove.

I mean, there's so many inconsistencies around Bluesky's API, but this one's the latest that just bit me...

*shrinks you*

It was already on my radar :3

HAH!

Maybe Voresky might be the right client to use after that actually~

We'll see exactly how it affects the normal features, but as long as I control this client, well...

I can keep displaying the timelines I want.

Yeah I'm fixing this like in 5 minutes :3

Yes, that :3

Oh? Tell me more.

I might, yes. Originally I set it to no changes to avoid people rapidly changing their name and causing confusion. I'm wondering what the right middleground here is.

In the meantime I can patch your name, let me do this real quick ^^

Bluesky API derp moment:

`getQuotes` silently returns empty with a handle-based URI, but returns the actual quotes when using a DID.

`getLikes` and `getRepostedBy` both resolve handles, `getQuotes` doesn't.

Why?

And it returns 200 with an empty response instead of an error...

Yes ^^

Clever use of game mechanics.

Don't abuse it :3

ALSO you can exclude some branches yourself first.

These can be manually do-over without any safeword :3

There's a duplicate path button?