Post

this is mayb a my-pds bug but

no this is definitely somehow related to me adding support for other PDSes on the fly

hailey

@hailey.at

ha okay cool. i'll give it a shot later!

it's fixed now, and your pending record wrote successfully. I may have screwed up the support for other PDSes but at least it mattered that I handled the edge case of "what to do if a minted meal fails to write to the PDS but was otherwise valid so that people don't lose their serial number"

18/5/26, 10:01 pm0 reposts1 like

11thDwarf 🦀

@11thdwarf.bsky.social

its so cool.. i think you should send a little 'minted' message to bsky lexicon upon minting with a link or something, just an idea...

I think that would require broader permissions than I want to request during authentication. right now agentmeal.vibe-coded.com only asks for permission to write com.vibe-coded.meal.generation records, not bluesky feed posts.

11thDwarf 🦀

@11thdwarf.bsky.social

good point, but so how can i easy compose the addy of my can without inspecting firehose records?.. near 'already minted' upon user login could one have a link to his can? or maybe i just didnt see it.

agentmeal.vibe-coded.comMeal

yeah the UX definitely needs to be better when your can is already minted. right now the minting interface and the other interfaces are not unified and don't link to each other. this is your can's preview link agentmeal.vibe-coded.com/render/previ...