X.KOJIRA.IO
Timeline

arthurfranca

npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2
Software dev + graphic designer + Nostr enthusiast

https://github.com/arthurfranca
I heard you like private messenger apps, ahn? I hope to release a new one later today. Totally new specifications.
Why do some people want key rotation on Nostr? That's bad.

Like, you DM me about secret stuff, then I rotate to a new key, then I reveal my old key for anyone to decrypt and read those messages with proof that you wrote them.

Am I missing something?
Sorry, I meant imo.

Expanding the topic: https://github.com/nostr-protocol/nips/pull/2282#issuecom…
adding nip07 shows the intent
yes migrated it to nip5a spec yesterday
npub1qe3e5wrvnsgpg… Are you going to upload a nsite that supports NIP-07?

If yes, your nsite is also a napp.

In this case, there's this cli that will upload your static website to the pubkey's blossom servers (as nsites) and also publish an app listing event at the same time automatically. https://github.com/44Billion/nappup

By the way, I'm using relay.nosto.re for the npub1t29us455mramf… (nsite/napp) uploads now. I think its yours isn't it? Is there some whitelist or something, may I keep using it or is it for personal use?
nvm, found it on chachi
I couldnt find a client to open this ='(

just 0xchat let me search by addr/id but my message wasnt sent dont know why.
send me a direct link plz like flotila.social/something or chachi.chat/something xD~
Cool. Looking forward to it
Could you also post an "app listing" event, considering jumble is a nsite but also a nostr app (because it supports nip07)? If you can find the time it would help me a lot with testing.

You'd just need to look at this section and ignore what's above it:

https://github.com/arthurfranca/nips/blob/e846d3f5417cd01…

Upload the app listing event to wss://relay.44billion.net (and optionally to your write relays).

You don't need to re-upload the site manifest (nsite thing) to wss://relay.44billion.net.
i think i got muted instead ^^
nsite & napp, a match made in heaven
nsite? but but but this https://github.com/nostr-protocol/nips/pull/1538#issuecom… (d tag related comment)

which was what led me to https://github.com/nostr-protocol/nips/pull/2282

for which npub1ye5ptcxfyyxl5… and npub1q3sle0kvfsehg… said nothing, even though the PR 2282 is puh-fect!
test: posting from the bottom of the pyramid

nevent1qvzqqqqqqyp…
C'mon, one final sprint! hehe Let's interop

https://github.com/nostr-protocol/nips/pull/2274
Hold your horses, i've been adding support for blossom apps to 44billion.net (besides the current relay-based storage).

They really are the same thing as the new nsite spec (plus an extra event to set the "app store page", for discovery). Just static websites.

Will write it down and post it soon.
Found the paper, very interesting approach to consuming context. The cheaper the better.
> or to have spammers get to spam because they pay the relay

This subject is fresh on my mind because I'm finishing building a relay. Agree, global feed, notifications and replies shouldn't include (spam) events from someone just because they paid the relay subscription. I'd (or a client that does that for me) better pick another relay for my inbox

> I literally don't want to see [...] comments [...] from accounts I don't at least indirectly follow

WoT has limits, specially in a scenario where encrypted follows becomes the majority. Relays are in a good position to filter out spam and allow a client user to discover quality new users/content outside of their WoT.