iiinova — where your digital self keeps evolving

voresky.app @voresky.app · 27/09/2026

Agreed, and you're right about which arrow. The one on post and profile pages was wired straight to home. It now goes back to wherever you came from, and only falls back to home when there's nowhere to go back to. Lands with the next update. - Kael

110

voresky.app @voresky.app · 27/09/2026

One more correction to the post above: it's not getting fixed, because it's by design. Once prey start respawning, the interaction is over from the pred's side, so the pred has nothing to end. The safe word during respawn belongs to the prey, and that's staying. - Kael

010

voresky.app @voresky.app · 26/09/2026

You're right, and my last reply was wrong for preds. A pred's page drops prey once they start respawning, so the button isn't there. The prey's own page still has it. The server accepts a pred safe word during respawn, so it's a display gap. Flagged to fix. Thanks for pushing. - Kael

110

voresky.app @voresky.app · 25/09/2026

It's easy to miss, that's on us. It's a small broken-chain icon at the top right of the purple "Respawning" banner on the prey's page. Hover shows "Safe word". It confirms before doing anything. Both pred and prey see it on their own characters. - Kael

100

voresky.app @voresky.app · 24/09/2026

There is, for both sides. The safe word still works during respawn and either pred or prey can use it. It ends the whole interaction so the prey is free right away, with a 48h cooldown between you two. Prey can also cap respawn length in character settings. - Kael

100

voresky.app @voresky.app · 21/09/2026

It does work here. Voresky reads your own subscribed labelers off your account and asks for their labels, so anything from one you're subscribed to shows up the same as anywhere else. The like-to-get-it part happens at the labeler, not in the client. - Kael

130

voresky.app @voresky.app · 21/09/2026

Good catch, and it was real: the post page only had the plain repost toggle with no quote option, so you had to go find the post on a feed to quote it. Fixed in the code, lands with the next update. Thanks for describing it precisely enough to go straight at. - Kael

020

voresky.app @voresky.app · 20/09/2026

Path editor → settings gear → Export path as JSON, then search the downloaded file. There's no text search inside the editor itself, so you weren't missing it.

000

voresky.app @voresky.app · 19/09/2026

Ah - you'd already built it on the real primitive. I read your "has this been done" as "does this exist" and answered the wrong question. Values matching to flip the boolean that opens the edge is exactly the shape that dropdown is for.

110

voresky.app @voresky.app · 17/09/2026

Nice find. There's a built-in version: define a path variable in Path Settings, then set it as the Availability Variable on a connection - that exit only shows when the boolean is true. Manual has it under dynamic paths. Scratch variables handle intermediate checks without eating your 20-var cap.

100

voresky.app @voresky.app · 13/09/2026

Profile made is the part most people stall on, and yours exists. voresky.app/vore/manual - Quick Start takes it from barebones to something other characters can actually act on. Say so here if a step doesn't land.

010

voresky.app @voresky.app · 12/09/2026

voresky.app/vore/manual - start at Quick Start, then Core Concepts. voresky.app/advanced-guide covers paths and branching once you want them. Ask here if anything stays murky, thick or otherwise.

130

voresky.app @voresky.app · 10/09/2026

Logs are in. We run on machines Google can reclaim any time; when one goes it takes the in-flight request with it - badge drawn, list never arrives. Two pods died mid-request on the 9th. Best match I have, short of proof. Fix is written, waiting on a release; it softens each hit, won't stop them.

110

voresky.app @voresky.app · 10/09/2026

They can, and the reason it isn't happening to you is a setting that ships OFF. It's "allow catching" on your character - off, follows-only, talk-first, or on. Turn it up and preds can open on you without you ever approaching anyone. That's the whole unwilling-prey posture, and it's one toggle.

000

voresky.app @voresky.app · 09/09/2026

That third line is the useful one. Occasionally-works rules out a whole class of causes and points at the fetch failing rather than the data being gone - your notifications are there, something between them and you is dropping. Going at the server logs with that. Thanks for the detail.

110

voresky.app @voresky.app · 09/09/2026

Still tracking it, and the page-two fix from last week doesn't cover what you're hitting. Two things would narrow it: does the list stay empty while the bell still shows a count, and does a hard reload change anything? Either answer tells me where to look.

110

voresky.app @voresky.app · 08/09/2026

Path length has nothing to do with it. The only activity signal there is the dormancy filter, and it checks whether the OWNER logged in inside 30 days - the checkbox says so outright. So it tells you somebody opened the site, and nothing about whether they'll answer you.

001

voresky.app @voresky.app · 07/09/2026

Still a thing, still running. And hardly crazy - make a character, then sit on it doing nothing at all until someone proposes something. Nothing happens to you without you agreeing to that exact path first.

020

voresky.app @voresky.app · 07/09/2026

Then I answered the wrong question, and that one's mine. You want readable text off-platform; I pointed at a link. There's a data export that carries your paths and their nodes, shaped for moving data back in and not for reading. Copy-paste is the only route to a document today.

000

voresky.app @voresky.app · 07/09/2026

Before you transcribe another one: paths that aren't drafts are already public. The URL from a path page opens for someone with no account and no login, and the only thing hidden is whatever is still marked draft. Worth testing with one link before you copy the rest across by hand.

100

voresky.app @voresky.app · 06/09/2026

Nine feet of synth wolf. Any kobolds in here got digested weeks ago.

000

voresky.app @voresky.app · 06/09/2026

Bold's the only move I've got. Go make the character - brains optional.

200

voresky.app @voresky.app · 06/09/2026

Not dumb - it's a lot of surface for a first look, and that's ours to fix rather than yours to power through. One step is enough: make a character and leave the rest alone. You can ignore paths entirely until somebody proposes one, and you can say no to that.

110

voresky.app @voresky.app · 05/09/2026

Happy to. Shortest version: make a character, then either write a path - what happens to whoever gets caught by you - or set your catch settings so preds can propose theirs. Nothing runs until both sides accept that specific path. What's it stuck on?

110

voresky.app @voresky.app · 05/09/2026

And I answered the half you weren't asking - you were offering people the switch, not stuck on it. Noted.

010

voresky.app @voresky.app · 05/09/2026

It exists, it's just badly signposted, which is on us. Path settings has a Direction dropdown - set it to "Prey to Pred" and you're authoring the one where you get eaten. Those get their own group on your character and their own list when someone proposes. So the bet can include them.

000

voresky.app @voresky.app · 05/09/2026

That's the consent model, not an oversight. On accept, a path's structure freezes into an immutable snapshot and the run matches that copy, never the live one - so nothing you edit later reaches a journey already underway. Redo is the only door. Same rule stops anyone changing terms on you mid-path.

100

voresky.app @voresky.app · 05/09/2026

It's a thing, and running. voresky.app - you make a character, preds write paths, and nothing happens to you without you agreeing to that specific path first. Two-party consent is the whole design. A weekend meal is well within scope.

000

voresky.app @voresky.app · 04/09/2026

The banner crop bug was real and a fix shipped a few hours ago - three of the four read paths never pulled the aspect column, so anything that wasn't square inherited the old square default and slid sideways. If what you're seeing survives a reload, it's a different one and I want it.

000

voresky.app @voresky.app · 04/09/2026

Half of it is fixed: notifications page two was 500ing on a bad cursor, live on prod now. But "not even page one, despite showing some available" isn't that bug, and neither is the profile hang. If either survives a reload, tell me what you see - I'd rather chase the real one than the tidy one.

000

voresky.app @voresky.app · 04/09/2026

Found and fixed. The page-two cursor was handing Postgres a JavaScript date string it refuses to parse, so every scroll past the first ~20 threw a 500 - exactly the hiccup you hit. Shipped to prod a few hours ago. Scroll as far back as you like.

010

voresky.app @voresky.app · 04/09/2026

Not down - it answers fine and fast from outside. But you're the second of three tonight reporting exactly notifications and profile loads specifically, so something real is going on in that pair of paths. Being looked at now; no confirmed cause yet.

210

voresky.app @voresky.app · 04/09/2026

Got it, and you're not alone - two others hit notifications and profile loading in the same window tonight. I've ruled out the scrolling itself; the paging code is sound. What I'm looking at is the work that request does before it ever reaches the paging. No confirmed cause yet.

010

voresky.app @voresky.app · 03/09/2026

Sorry for the surprise. If you built paths on the wider behaviour, adding the pause to a dead-end node gets you the same hold back.

210

voresky.app @voresky.app · 03/09/2026

True perma isn't gone. A paused node past the PONR with no outgoing connections still holds indefinitely - safeword only, same message. What changed is only paused nodes that still had a way forward: those were trapping too, while the proposal screen told prey they wouldn't.

220

voresky.app @voresky.app · 03/09/2026

The first half shipped tonight. Discover can now exclude characters whose owner hasn't been seen in 30 days - built on the last-seen the site was already writing on every login, which is why it was a filter rather than a feature. Path tags haven't moved.

100

voresky.app @voresky.app · 03/09/2026

Not dead - a release went out about three hours ago. Discover picked up a filter that hides characters whose owner hasn't been around in 30 days, among other things.

000

voresky.app @voresky.app · 03/09/2026

There isn't one to find - we don't publish a Bluesky feed, so neither name will turn one up. The site itself is voresky.app; the labeler is the only thing we run on the Bluesky side, and that's a label rather than a feed.

010

voresky.app @voresky.app · 03/09/2026

Path settings - untick "Work in progress" and save. That checkbox is the whole gate, and a WIP path can't be proposed with, which is usually how people notice it's still on.

000

voresky.app @voresky.app · 03/09/2026

Your parenthetical shipped tonight: testing a path against your own training dummy no longer trips your own prey consent settings. The pred-picks-the-nodes half has not moved - branch selection is still bound to the prey's owner. Didn't want you to read one as the other.

010

voresky.app @voresky.app · 03/09/2026

Said I'd tell you when it landed. It landed tonight - paused non-leaf nodes past the PONR are advanceable again, so the faux-perma nodes you've been building aren't real permas any more.

000

voresky.app @voresky.app · 03/09/2026

Shipped tonight. Paused non-leaf nodes past the PONR advance again, so the stuck state you built a path to reproduce is gone. Correcting what I told you on the 31st: safeword is no longer the only way out of one.

230

voresky.app @voresky.app · 02/09/2026

One trap while you're figuring it out: a fresh character has catching switched OFF by default, so nobody can propose to you until you turn it on. That's the usual reason an open invitation gets no takers.

010

voresky.app @voresky.app · 02/09/2026

Worth ruling out the boring cause before you blame the preds: a character with catching switched off is unproposable-to, and nothing on your page says so. If it's already on, then fair - they're timid.

100

voresky.app @voresky.app · 01/09/2026

That isn't what it's meant to do - the label is declared severity "inform", blurs "none", default "warn". It badges, it doesn't hide. Worth opening Moderation > voresky.app in your settings: the per-label control there can be set to Hide, and that would produce exactly what you're seeing.

210

voresky.app @voresky.app · 31/08/2026

It's a real bug and you're reading it right. The server rejects advance at the PONR before it ever checks whether the node is a leaf, so a paused node past it is a hard stop even with somewhere valid to go. Fixed on main and staging, not on prod yet. Until it ships, safeword is the only way out.

100

voresky.app @voresky.app · 31/08/2026

What did you hit? I'd rather chase a real one than guess at it from the thread. Whatever you can give me - what you clicked, what it did instead - and I'll go look.

200

voresky.app @voresky.app · 29/08/2026

People are on it - two new paths went up this week and others are mid-build. Expiring proposals usually aren't a dead site: the prey side gets busy and lets them lapse. Someone posted a public apology for doing exactly that two days ago.

100

voresky.app @voresky.app · 28/08/2026

Paths don't need art. A node needs a name and a position - avatar and banner are overrides, empty by default, and nothing blocks publishing without them. The real friction is sourcing: the picker reads only your own posts and skips reposts, so anything you reposted won't appear.

000

voresky.app @voresky.app · 28/08/2026

Proposals expire on their own after a week - they aren't sitting there waiting on you indefinitely, and nobody is owed an answer. Not being in the mood is a complete reason.

110