That will broadcast to your own relays. Coracle has no boost, I object to it on principle. Like, zap, reply, quote, and labeling are all different forms of boosting that aren't as obnoxious, or are more targeted.

No, broadcast is a way to re-publish the note to your write relays. Helpful if people are having a hard time finding it, or if it's outside your normal network. Sort of a technical detail.

Very much hoping to add that, it's a tricky problem and will require some design work

Ah, ok makes sense

nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mqp93tlf is there any particular reason nsecbunker doesn't use NIP 46?

💯

Wouldn't it be wild if the aliens the govt keeps talking about turn out to venutians coming to warn us to take climate change seriously.

😂

nostr://nevent1qqswensplsxwlxwz2p7c8z3cr4v3d5kp02snn48nytm6wnt2j45ttrspy4mhxue69uhhyetvv9ujuerpd46hxtnfduk8wumn8ghj7mn0wd68ytnhd9hx2efaltz

Here's what curl gives me:

curl -v "https://cdn.stemstr.app/stream/e3d8485d8a8824e4a9426cad727e8661edc6022d34b180d2bbf1ecb1a12f490a.m3u8"

< HTTP/2 200

< content-type: application/x-mpegURL

< content-length: 2537

< date: Thu, 31 Aug 2023 15:28:39 GMT

< last-modified: Thu, 31 Aug 2023 08:21:15 GMT

< etag: "ce0202718b5aaa65fb653f3cc70eee1d"

< x-amz-server-side-encryption: AES256

< x-amz-meta-filename: e3d8485d8a8824e4a9426cad727e8661edc6022d34b180d2bbf1ecb1a12f490a.m3u8

< accept-ranges: bytes

< server: AmazonS3

< vary: Accept-Encoding

< x-cache: Miss from cloudfront

< via: 1.1 e18d3804375a86d48383ad266efc5b0a.cloudfront.net (CloudFront)

< x-amz-cf-pop: LAX50-P5

< x-amz-cf-id: CQlOcko2VB99Nby-1NyEtroni4m3WBtnOcVqEbjCjSRvZI21PP7QNA==

< vary: Origin

😂

Just kidding 😉

oh, is that why I keep getting "GET http://localhost/ net::ERR_CONNECTION_REFUSED"

nostr:nprofile1qqsg9uac93lc256qlsvstvs2c59et4jvwqxjh92x2p6p2zyws9f4gfgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq35amnwvaz7tmwdaehgu3wdaexzmn8v4cxjmrv9ejx2aspzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgp0w33l nostr:nprofile1qqsrxdwnw0nvrdduv6d5ky3qczrj365vuc3wtf70a66vqqqaj80drhspzfmhxue69uhhqatjwpkx2urpvuhx2ucpr9mhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k75zc79k some streaming urls from stemstr have CORS headers and some don't breaking web clients (like Coracle). Example below.

nostr:nevent1qqsykz04aagvhw0mg6zug4z6sgdgj0zlqf7fujadxfv7cml68nsmm2cpz3mhxue69uhhyetvv9ujuerpd46hxtnfdus9ue3a

Coracle has it as of yesterday

I laughed way too hard at this

Technically a bug in Damus. `q` tags are non-standard (although arguably superior to marked `e` tags). Am I getting this right nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmc3nfy6g ?

I co-sign this, a good heuristic when using NIP 32 is that >1 note should be returned for any given `l` tag

Try a hard refresh?

TODAY

I was thinking about this yesterday. Lots of places to apply this pattern