GM from napplets in funstr

Posting paint art uploaded to blossom servers from napplets running inside 44billion :)

🦆 View quoted note →

GM from composer napplet running in 44billion

Also if anyone knows of simple nostr "other stuff" sites that need reviving or need to be faster I'm happy to create PRs. Its 2026 there is no reason nostr powered sites should be slow. View quoted note →

@calle I got a PR for reviving following.space and making it considerably faster

GitHub

Revive following.space with Applesauce, relay discovery, and improved pack workflows by hzrd149 · Pull Request #25 · callebtc/following.space

Summary Revive following.space with a shared Applesauce runtime and restore the full follow-pack workflow: discovery, creation, editing, deletion, ...

I switch it from NDK to applesauce, added full outbox support, faster loading using NIP-77 sync, outbox support for follow back feeds, and a bunch of other stuff I'm forgetting. I would appreciate it if you could sent an agent over to review it I also published the revived site as an nsite if you want to test it https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5followspace.nsite.lol/

I gave

Blossom Servers

a face lift, its not much faster and is more useful for finding and reviewing blossom servers.

NWT > NIP-98

GitHub

GitHub - Open-Ranking/nostr-web-tokens: Nostr Web Tokens (NWTs) are signed Nostr event used to convey claims between parties on the web.

Nostr Web Tokens (NWTs) are signed Nostr event used to convey claims between parties on the web. - Open-Ranking/nostr-web-tokens

🌸 View quoted note →

nspam model by @utxo the webmaster 🧑‍💻🍁 seems to be fast, adding proper support for it in applesauce so apps can easily us it. @utxo the webmaster 🧑‍💻🍁 it would be cool to somehow have it accessible over blossom so that the model could be fetched from any server in case it went down.

Halved the 7 day sync time for @Derek Ross's contacts and the 30 day outbox sync is down to about 1 minute I should mention this is just measuring the syncing and downloading of events from the relays and not fetching the contacts outboxes, that takes about 5-8 seconds or so. This also limits the max relays to 30 so not all users outboxes are being connected to, only the most common ones that provide the most coverage. increasing this to 80 seems to find more events and doesn't take much longer but probably uses a lot more bandwidth. View quoted note →

#asknostr anyone have a few links to some of the old hell threads? I need to test loading performance in Applesauce.

@Let's Fo Live and maybe @mar? I found an annoying issue in

Let

Your own Nostr live page with chat, zaps, and OBS widgets. Hosting and updates handled by LFL Cloud. Use a zapparti.com address or your own domain.

I would do more but my clanker cant find the source code.

gitworkshop - Decentralized Git

Decentralized GitHub alternative over Nostr for browsing repositories, managing issues, and collaborating on pull requests.

NIP-45 defines the COUNT request as a request... not a subscription and therefor does not need a followup CLOSE message. I hope most relays implement it this way otherwise they are about to feel a lot of pain from my new feature in applesauce :) Not requiring a CLOSE message is a good thing though since it reduces the messages over the wire by 50%

The outbox model works, and it works really well. More sync tests from the upcoming version of applesauce, first one tries to connect to all my contacts relays ( 165 ) and gets ~1900 events in 34s. the second connects to the 30 most common and gets ~1700 events in 18s. Both syncs are for loading all events your contacts have posted in the last 24 hours, so plenty of content for a normal nostr client. ( it also helps that nostr is slowing down so there is less content to load ) View quoted note →