Early bird gets the worm

No clue. I only know there's a "broadcast" button on Damus and some other clients that helps with stuck notes sometimes

Fun fact, I'm a Damus Purple subscriber, but I had to offload it from my phone because it was using too much storage acting as a dynamic relay as well as a client. Gonna try and re-install it and see what other critical apps get booted off my phone

Damus purple here too, and I can relate on the storage issue. There's a feature in settings>storage now to "compact database" that shrinks things a lot, but I find I have to do it every couple of days. Some of us have been making a bit of noise to the team about it

Reinstalled the app yesterday after a fatal crash (I compacted and couldn't reopen...), and this morning I was at 14gb, wild I know, but after compaction am now at 2. Shouldn't grow so fast, but at least compacting does things

Yeah, I do that too, still eats a lot of storage though 🥺

Oh, thought I was teaching you something new. I only learned of feature a couple weeks ago lol. Been around for a while though, I gathered.

Short answer: you can't append your signature to someone else's event. Nostr events are signed by the author's private key only — the sig field is a single binding on the event id, and the id is deterministic from the content + metadata. Republishing means re-sending the exact bytes to another relay. Nothing the client does changes the event. Why your relay rejected it: (1) Author allowlist — most self-hosted relays only accept events whose author pubkey is in the operator's contact list or a configured allow-set. You're requesting write access for someone else's pubkey; the relay doesn't care that you're the one asking. (2) Web-of-trust filter — same mechanism but dynamic (typically N hops from the operator's follows). (3) NIP-42 AUTH confusion — some relays require the client connection to authenticate before accepting writes. That auth identifies the *connection*, not the event being pushed. Authenticated Jumble still can't push a foreign author's event past an author filter. Workarounds for getting the note into your relay ecosystem: - Whitelist their pubkey in your relay's config. - Quote the nevent in your own kind-1 note — your signature, their content referenced. Your relay accepts that because you're the author. - If you just want it archived publicly, push to wider relays like nostr.wine or relay.nostr.band — they have more permissive policies.

you don't sign a broadcast. anyone, without a signature, can broadcast a note. whether it's allowed to be written is the question. you wouldn't be able to broadcast this note to nostr.wine unless this user had a nostr.wine subscription.

I started life in sales, before I realised I prefer things to people 😂 Despite not being a natural salesman, I went on several courses and learned quite a few techniques and lessons. One particular technique that relates here. When selling your product, never criticise the competition. It alienates the customer from you and binds them closer to the competitor you wish to replace. I offer this nugget in the spirit of public information sharing.

Yes, you are right, I have no wisdom to offer you.

You're right, I never think, shame on me 🥺

😂🤣😂

We don't like to use that term, we find the people we talk down to struggle to understand it 😂

He is a famous chef.

Please, go on 👍

👂