Small code.
Open possibilities.

Yes. Sign in as its author and choose Manage publication, or open Your napplets from the identity menu. Unpublish keeps the files for later republishing at the same address. Delete hosted data asks for confirmation and shows progress for each relay, upload and repository. Shared files may stay; Soy’s Git server retains a recovery archive for 90 days. Downloads, forks and independent copies cannot be recalled. Lifecycle guide.

A napplet is a small web creation with a signed Nostr listing. Relays help clients discover it, Blossom hosts its files, and this client verifies and runs it in a sandbox. soyLI turns a local project into that publication and shares its Git source. Compatible clients can discover the same napplet; it belongs to its creator’s key, not a website login.

No website account or sign-in is needed to create, remix or propose changes. soyLI can create a Nostr signing identity or connect one you already use. Browsing and playing also need no site login. Likes and comments require sign-in; sharing links and anonymous zaps do not.

In soyLI, run soyli account list, then soyli account use YOUR_ACCOUNT_ID with the account ID or npub you want. Existing projects keep their creator binding, so switch back to that creator when publishing them.

On the website, open the identity button and select a saved identity or connect another. Website and CLI selections are separate. Identity commands and backups.

You can publish under a separate pseudonym without providing a real name, email or profile. Every napplet still has a public signing key, and publications under that key can be linked together. Publishing is pseudonymous, not a guarantee of anonymity.

Public source, Git authorship and commit history can reveal identifying information; infrastructure providers can also see connection information. A fresh key alone does not remove those links. The identity guide explains creating another key and the release status of account create --new.

It reuses your selected identity so repeat setup does not replace it. account backup saves or locates that same key’s backup. A different identity needs explicit creation with account create --new; previous identities and backups are retained. See the identity instructions for details.

soyLI signs with your OS credential store and saves an owner-only, unencrypted nsec backup outside your project. soyli account backup prints its location; encrypted exports are also available. On the website, key creation includes an encrypted recovery download. Remote signers keep the creator key themselves. Preserve a private backup: this site cannot recover a lost key for you. Backup and restore instructions.

No global Bun or Node installation is needed. The macOS and Linux soyLI downloads include their runtime and prepare the project toolchain. You need Git and a supported system credential store to publish. Use any editor or coding agent you prefer; new projects include Napplet skills and guidance. An AI subscription is not included or required. Setup requirements.

Yes, when you share it through soyLI. Publishing or proposing shares source and pushed Git history, including earlier versions of files. Editing and making local checkpoints do not upload anything. New projects use MIT; check and preserve the existing license when remixing. Keep credentials and private notes out of the repository. The edit-to-publish workflow.

A remix gives you a local copy to work on. From the same copy, publish an independent napplet or propose improvements to the original author, or do both. A proposal includes source changes and a playable preview; the author decides whether to merge and release it. Proposals require a Git-backed original. Remix and contribution commands.

Yes. soyli config shows publishing destinations, and soyli config init makes editable local overrides. Choose compatible Nostr, Blossom and GRASP services. The website’s Network settings control your browsing providers separately. See the defaults and how to change them.

Open your napplet page, connect the creator identity and choose Named link to claim /@your-handle/your-slug. It follows future releases. The Share control also offers a player link that opens directly in the immersive view. Portable Nostr addresses continue to work without a named route.

This site’s administrators can hide content here. That does not erase copies held by other clients, relays or file servers. Published code and files can be copied and remixed, so there is no universal undo for a public release.