X.KOJIRA.IO
Timeline

brugeman

[email protected]
npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy
Building https://npub.pro https://nsec.app and https://nostr.band

Create beautiful nostr-based websites with Npub.pro
relay.nostr.band now let's you search through these events
Ah also you app is passing zap request in base64 encoded form, instead it should be url-encoded.
I see zap receipts don't work because zap request 9734 event doesn't have "relays" tag (https://github.com/nostr-protocol/nips/blob/master/57.md#… - zap receiver doesn't know where to publish the receipt.
Ah yes! Didn't notice the Zap symbol on kinostr. Did you try to figure out how to add some wallet integration? For one-click zaps or for creating wallets for signing-up users?
Cool! Which of your apps have zaps? Zap receipts are published by receiving wallet, so I don't think your app is responsible for that.
How about ln/zaps?
Did it work?

Btw did you try integrating LN/zaps to your vibed apps?
Have you tried asking it to add nostr-login library as a drop-in solution?
Hm... that's interesting!
Adding 100k on top
Thanks for the post! Is there something we should improve next?
> I've opted to go with the vanilla bunker/nostrconnect flow, which allows me to display a simple interface to users.

In flotilla, I see nostrconnect:// QR-code, but not a clickable nostrconnect:// link - on mobile Amber could handle it and I wouldn't need to click on the QR code to copy-paste it to Amber. Does it make sense?
Actually both nsec.app and amber work according to master nip46, they just use the same remote-signer-pubkey and user-pubkey - nothing in the spec says this is forbidden, it's a valid behavior.
Thanks for the report, are you publishing some images right from the nostr.build admin panel? I guess they just don't have full hashtag support yet. cc npub137c5pd8gmhhe0… npub1nxy4qpqnld6km…
npub137c5pd8gmhhe0… npub1nxy4qpqnld6km… Hi you have Disallow / in robots.txt, which means files hosted by nostr.build can't be used for link previews on Twitter.

This is how preview looks w/ nostr.build image:
https://i.nostr.build/BFQYR5lKopDK6eUf.png

And this is from another server open for crawlers:
https://i.nostr.build/2TssmMmt8CJ3zDGk.png

Is there a chance you'd allow twitterbot explicitly? It shouldn't abuse you, I guess.
Everyone can have their own Instagram

nevent1qqsd8z4u64s…
Coming soon, Karnage designed the thing.
Deal, thank you!
100% agree, that's why I'm saying offering this as nip96 option (even if paid, restricted etc) could serve those use cases, and I'm guilty as anyone in digging hyped stuff without looking through existing NIPs first. And you sure didn't waste time implementing nip96, it seems to be quite good, even if a bit too verbose for my taste.
I agree with you about imgproxy, but then there's no NIP for "accepting optimized version after the fact" and I'd say it's probably much trickier than you say. Anyways, you don't have to offer this option if you don't like it, I'm just comparing the NIPs.
You are right 99.99% of the time it's ok to trust the media hosting someone is using for trivial memes etc. But if some controversial video is released, it would be great if anyone could re-upload the original to other servers and they'd all serve the original and any client could verify it's original, etc. That's the problem blossom is solving.

Re. my use case, I'd like to host some code in the same "link rot avoiding way", and I know you wouldn't probably transform it anyway, but I will also upload images that shouldn't also be transformed. I haven't considered git, and maybe I could even just host it all in nostr events... We'll see.

My point in posting here was to understand what problem blossom solves vs nip96, and I'd say a small addition to nip96 could make it supercede blossom and you could then just ignore it :)
Ok so I need a storage server integration for our product. Blossom is very simple spec focused on fighting link rot and decentralization, key to which is that uploaded files must not be modified, so my app wouldn't have to trust the server. Blossom invents it's own auth instead of nip98, needlessly.

Wrt nip96, which I didn't consider, but looking at right now, it's much more verbose and covers a lot, and uses hash for addressing, but lacks one critical thing - I want to ask the server to keep the original and do no transformations. Adding this one option would make it a superset of blossom and I would be able to use it. Maybe there's such an option and I missed it in the nip96 spec?
I'm all about howto guides these days, please check out https://nostrconnect.org/ and let me know what's missing.
Also wrt 'headphones' example. Instead of looking through my wot circle for reviews, I could post 'please help me choose headphones' message that could propagate through my wot circle until some experts see it. They could reply with 'here is a one liner big advice, and here are a couple links for you to read, and if you want to hop on a call - schedule here and it will be 5000 sats'. This might turn out as a better solution to 'help me buy headphones' problem than trying to fix fake reviews or increase the review density in my wot.
Can you please tell me mo about vectorized trust? Maybe a link to read?
It is nip46 implementation, we can say it's a bunker in your browser.
We still haven't heard your feedback on nsec.app, we really miss it!
Does nsec.app usage break the satcom?
older →