It’s just uploaded to one of the many providers that give file uploading services. You are likely on a free plan of a freemium model. 

 Amber on android is the best solution for android, as the signer is always local.

Nak is my goto but only cli based so out of scope for most people.

Gossip is really good too and I use it extensively.

@BlackCoffee is working on a hardware device, like a coldcard for your nsec that does remote signing.

Nip-46 is still rough around the edges, mainly because the spec was so bad at first and there were so many iterations. It’ll be better. 

 That said, I think there is a lot to be said about large clients becoming signers, @jb55 expressed interest in doing this at some point, so did @miljan 

 Oh cool! Going to get a pair 🙏 

 And that’s a good thing.

Indexers and caching layers have uses, but speed and particularly data availability are better accomplished with outbox. AFAIK primal is working on supporting it, it’s just early. 

 Why? Outbox is gaining more and more adoption. 

 I just use Fiatjaf!s nak for that

cat file.md | nak event —sec yournsec -k 30023 -d random-if -t title=Title wss://… 

 This 

 Kalymnos.

I wish; nah, too out of shape to climb hard or project; I’m just climbing onsights up to 7a and the odd 7a+ 

 Toooons of extreme high quality routes on those grades 😉 

 I started making one this vacation; been logging my sends on it. Called “mono” 👌 

 😂😂😂🎯 

 👌 

 Just be active for a while and you’ll find your flock and your flock will find you.

👌 

 I stand by my statement 

 HAHAHHAHAHHAA 🎯 

 Imagine the meeting...

"fuck man, people are pissed as fuck, what should we do?"
"I dunno, man, what if, like, we tell people it's christmas?"
"NOICE! LFG!"

nostr:nevent1qvzqqqqqqypzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3xamnwvaz7tmsw4e8qmr9wpskwtn9wvhsqgy0gpsumat3aplzvkyt0q3phvvwcfmxzreahz3f4lnhwt52785xngzntrsh 

 You only get your next ration if you applaud 

 It’s a kind 30023 written from a long-form client like highlighter.com and yes, it’s markdown 

 Would love to see this. Is nuts.cash using NIP-60? 

 😂😂😂 

 ☑️ Quote support added to highlighter.com

https://m.primal.net/KaOX.png  

 ITS ALREADY BETTER THAN THE CUCKED SOCIAL NETWORKS 

 I agree. 

 I’ll add quote support tonight and I will revise what happened with the scheduling 🤝 

 for broken clients that will not rendered the tagged event properly:

it's a kind 5132 event (I just came up with it, but it has a NIP-31 tag so there's no excuse to not render it with proper context)

it tags the area (Kalymnos), the crag (Arginonta), the route (Anna-Maria) and it includes some info about the ☑️ I did this morning.

Hundreds of thousands of users keep their data (including me, until today) in a platform that doesn't even allow you to backup your data, it was sold a few years ago to a fairly sketchy company that is trying it's hardest to monetize the data capture as much as possible.

Nostr will eat ALL OF IT.

https://m.primal.net/KXjW.png 

 sounds like that belongs more in bluesky 

 ☑️ onsighted Anna-Maria, 6c

Vacation = going climbing and starting to keep my scorecard as nostr events

#crimpstr

nostr:nevent1qqs0spg7f83jwc5kszk7aynkcwxkz8r6ej0dar00zkwt6vygmf66nscprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75s8s3xa3 

 Bro, I have so much feedback, don’t tempt me 

 Not sure how people would feel if their podcasts listens were public.

But I guess 95% of people would not approve of that. 

 If you don’t have to stick your nsec in to use it, I don’t have a problem with it not being open source.

NIP-46 will be a huge win, @merryoscar 

 If this is some play with Saylor’s “Bitcoin is stored energy” and fountain’s v4v angle, you’re a sarcasm genius, sir 

 @merryoscar stop the censorship 

 😂😂😂😂😂😂 

 Yes, and i think this is where things might go in one year of development 

 Bro, we all already knew you were a total nerd. 

 the only way nostr works as a censorship-resistant protocol -- formerly known as gossip.

the basic idea is instead of everybody writing to 3 or 4 or 10 "popular" relays each pubkey says "I'll write to relays X, Y and Z, you can find me there"

Now all a user needs to be able to make available is this very small event (which dedicated relays like Purple Pages focus on) that maps pubkeys to relays.

That way, if User A is censored by a vast majority of the relays, followers of that user can still continue to find their content without noticing that any type of censorship is going on.

(Imagine if all of Trump users could have continue to interact with his account when he moved to Truth social without even realizing that anything was happening)

---

There's a lot more to outbox than this, but this is the basics. 

 Yeah, I think relays (that want to) should return multiple versions of replaceable events if you include a “limit” query when REQing for a replaceable event; that way any client could easily implement a recovery tool 

 I'm pretty sure, yeah; I just signed out, signed back in, then used it for maybe a few minutes and noticed I wasn't following someone whom I was 99% sure I was following (that should have been the tell) so I casually pressed the follow button.

I'm with terrible internet right now, so that probably didn't help 

 Thanks, you enjoy it too. I am about to take off ✈️ so couldn’t read your entire note yet, replying to the sentiment and parts here:

being forced at the protocol level to give power to relays to create events on my behalf is a non-starter for me, specially when I’m not sure what you get in return for that high cost.

Delegating signature to an explicit remote signer without requiring it at the protocol level is not the same imo 

 > if people are OK with using custodial LN, it would be insane to say that trusting a hosting provider to not modify your shitpost or that that would be unacceptable risk.

It’s wildly not as important some sats people are willing to risk by offloading custody for convenience; I think using the “shitposting” case is a cop-out or a strawman; or perhaps not even that; I care A LOT more about my speech than a few million sats that I would keep with a custodian.

(Part of the reason why I don’t drink alcohol) 

 I enjoy having these conversations too and appreciate your work on pkarr 

 > because clients can fake things to

Are you referring here to the “you always must trust the rendering”? John made that point the other day and I honestly don’t get it; your wallet can always show you a balance of 22M bitcoins but that doesn’t mean anything.

But maybe you’re referring to something else entirely? 

 > Finally if you don't accept delegation at all, then you are forcing users to a maximalist trust model that they don't want, and forcing them to deal with the risk of losing their keys for that choice you are forcing on them.

I think delegation is fine but not required by the protocol; that’s what Bluesky is largely doing and I don’t think that solves anything much like if Bitcoin was required to be used via coinbase AND a large list of custodians.

I think this delegation is better opted-in on the distinct users’ setups 

 I’ll be on vacation the next few days and my wife is already giving me the look for responding while she is tending to the kids 😂😂😂

Would love to sit down for a coffee someday; do you go to some conferences? 

 Is this really John? 

 I am actually a throwaway from turkey; island next to Kos 😅 

 I’m a simple man:

Exploring new ideas.
Climbing. 

 Oh maybe with the switch to asciidoc 

 Yes. Vipassana. 

 What does “link different sets of profile data” mean? Different kind:0s? If that’s what you mean, then no. A nip-05 just resolves to a pubkey; you *could* resolve to different relays that have different kind0s, but that’s unlikely to take in most clients and what will end up happening is the newest kind0 will be used.