Yes, I was surprised to see 191 in the file properties (and ...

𝕳𝖊𝖓𝖗𝖎𝐤 𝕱𝖑𝐲𝖒𝖆𝖓

npub1n3ejxm6kt6ush4rgrs57hvkecxuqunscfndlsntd5apwnyr8pjmqrme7su

hex

d72acc5ffe476a7a6784ffe7bf81fb26750e2b6702e88cb80f01410adbfbeb6f

nevent

nevent1qqsdw2kvtllyw6n6v7z0leals8ajvagw9dns96yvhq8szsg2m0a7kmcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsfcuerdat9awgt635pc20tktvurwqwfcvyeklcf4k6wshfjpnsedslz7l2t

Kind-1 (TextNote)

2026-01-19T20:12:07Z

↳ 回复 sunamiold (npub1vpf582eklpnh5rf47l3c0ynmmtl53z5jk0tj07e2g08h49tner2qhu2z8c)

191-192 is pretty rough! 256 is probably the least we would expect nad 320 kbps feels like a standard. Ideally RSS feed would have two files, one for ...

Yes, I was surprised to see 191 in the file properties (and 192 via more professional software).

True, if Tidal can do it, so can we. An ideal scenario would be to upload a 16-bit / 44.1 kHz WAV, automatically generate a 320 kbps copy for RSS feeds, and preserve the original file as a lossless option for those who care. That said, having “just” the 320 kbps file would also be fine with me. If the conversion is done well and without additional tampering, such as normalization, most people wouldn’t hear a difference.

原始 JSON

{
  "kind": 1,
  "id": "d72acc5ffe476a7a6784ffe7bf81fb26750e2b6702e88cb80f01410adbfbeb6f",
  "pubkey": "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6",
  "created_at": 1768853527,
  "tags": [
    [
      "e",
      "c965b4652ed5467f88ca3736859d91eeb57280de59e984996137d59714934d56",
      "",
      "root"
    ],
    [
      "e",
      "b3ea15e4e1e8407a821afb04c9eda5de30dc8453162e8f6fe1c9123e208bf503",
      "",
      "reply"
    ],
    [
      "p",
      "6538925ebfb661f418d8c7d074bee2e8afd778701dd89070c2da936d571e55c3",
      "wss://eden.nostr.land",
      "mention"
    ],
    [
      "p",
      "605343ab36f8677a0d35f7e387927bdaff488a92b3d727fb2a43cf7a9573c8d4"
    ],
    [
      "p",
      "cbd2ff2aca546769a8da6b2d3876da47a01ee6902a8ce060a955471b0b92b116"
    ],
    [
      "p",
      "9c73236f565eb90bd4681c29ebb2d9c1b80e4e184cdbf84d6da742e990670cb6"
    ],
    [
      "r",
      "wss://pyramid.fiatjaf.com/"
    ],
    [
      "r",
      "wss://nos.lol/"
    ],
    [
      "r",
      "wss://relaypag.es/"
    ],
    [
      "r",
      "wss://relay.primal.net/"
    ],
    [
      "r",
      "wss://relay.snort.social/"
    ]
  ],
  "content": "Yes, I was surprised to see 191 in the file properties (and 192 via more professional software).\n\nTrue, if Tidal can do it, so can we. An ideal scenario would be to upload a 16-bit / 44.1 kHz WAV, automatically generate a 320 kbps copy for RSS feeds, and preserve the original file as a lossless option for those who care. That said, having “just” the 320 kbps file would also be fine with me. If the conversion is done well and without additional tampering, such as normalization, most people wouldn’t hear a difference.",
  "sig": "0c39c6ed0a5d709087ebd3807b0939ff2d9bd4a80357549059e176320e0635835ee5e0c51f23017ea9146ecd172c3fd9a18822102270d534c9d52ae87c8483a4"
}