Forked chachi and deployed it to nsite so it cant go down anymore. I'm not going to maintain it but maybe this will help if you use it :) https://gitworkshop.dev/hzrd149.com/git.shakespeare.diy/chachi https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5chachi.nsite.lol/

Best joke I've heard all day

Zaps coming to gitworkshop. I can't wait to start zapping issues and PRs :D

Built another fun example of who is zapping who

We need more of these things running, but more importantly we need a way for clients to discover and understand that the blobs only last 24 hours

👀 https://.nsite.lol/ Thanks

Awesome, I'm bookmarking this so I can come back and learn more how it works :)

Great listen, I recomend it if you still haven't heard about FIPS

Added an example of this functionality to the small zap-galaxy project I vibe coded https://zap-galaxy.shakespeare.wtf/ The app is now aware its deployed as an nsite and shows a picker of previous versions of itself. then when a version is selected it will navigate to that specific version. The version is isn't hard-coded, its fetched live from nostr relays so that when a new version is deploy it will show up in the list. or the user can load the latest version that stays up-to-date with the deployment.

I'm not even sure how to type an emdash, my keyboard does not have a key for them.

Mute the emdash "—" character and never see bots again, your welcome :)

I vibe coded support for publishing nsite versions from shakespeare. based on the pending PR https://github.com/nostr-protocol/nips/pull/2287 This will allow apps built in shakespeare and deploy as an nsite to have a history of all previous versions. so if you vibe code a cool nostr app and deploy it users can always go back and run older versions. This is hard to show with screenshots, but this effectively enables "internet archive like" behavior for nostr apps deployed from shakespeare

Would be cool if google had some kind of password manager to store the nsec the first time and then fetch it again on next login

I just vibe coded a small app to help me stay on top of replying to all my friends GMs https://gm-protocol.shakespeare.wtf/

Its a tradition of posting GM notes every morning and responding to your friends GMs :D

So if another app implemented the same sign in with google flow using oauth it would get a different key?

Is this storing the "nsec" or an "ncryptsec" in the password manager? If there is a navigator.credentials in the browser id love to find a standard ways to load out of it. If the app needs the full nsec I would rather it store it in the password manager than localStorage :)

Keys are stored in google account or is there a server storing the keys with oauth signin?

GM

built a great server for this https://nostrarchives.com/ I don't think it has everything your looking for but it has a lot of good stats

GM