Nostr Web Client

Sir Libre 1y ago

nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9

I don't think it makes sense to put the xml into a kind 1 note.

Kind 1 is intended to be for short text notes.

https://github.com/nostr-protocol/nips

Maybe something like kind 30041 would be more appropriate?

Also is nostr really a good place for feeds? Some feeds are several megabytes in size.

My feed is about 1.5 MB in size. The Bowl After Bowl feed is 6.4 MB

What happens when I publish a new episode?

Does the outdated nostr version exist in perpetuity?

If so that could add up to wasted HD space pretty quickly considering there are over 4.37 million podcast feeds that we know of.

I'm not a nostr expert but there's got to be a way to say delete my old note, this is it's updated replacement.

Maybe nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr might have some insights

Reply to this note

Please Login to reply.

Discussion

StevenB 1y ago

You're probably right. I have no idea what I'm doing. I'm just playing around right now.

StevenB 1y ago

I think there's a way to tell the relay to update the event based on the ID, sort of like when you update your profile.

hzrd149 1y ago

This wont work for many reasons, but mainly because as you pointed out the RSS feeds are generally larger than the max event size most relays have set

Also using kind 1's for data is generally a bad idea since it conflicts with social clients (bad UX) but I'm guessing your using them mostly to test

nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 if you want to distribute RSS feeds via nostr then something like blossom + nsite ( https://github.com/nostr-protocol/nips/pull/1538 ) might work better since its a lot closer to traditional http. but its still early days and it while it "works" the documentation isn't written 😀

I've talked to nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu about this a little

Sir Libre 1y ago

At the moment I'm leaning towards that it's retarded to try to replace the existing RSS infrastructure. (I'm willing to be convinced otherwise)

RSS is Rock Solid. It's been time tested, battle hardened and it just works.

The argument that having to have a server to host one's feed is somehow difficult or out of reach for most folks is ridiculous. There are currently 4,370,848 feeds that say otherwise.

Why re-invent the wheel?

Granted there are some things that nostr can do that RSS can't and vice versa, but the RSS spec is very flexible and extensible. After all that's what the podcast namespace is all about.

We can find ways that make RSS and nostr play nice with each other but to try to replace RSS seems like folly to me.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

it's very simple to also serve regular HTTP over the same socket, the websocket connections start the same as normal HTTP requests, with an upgrade header, which initiates the websocket handshake

https://mleku.realy.lol will return you a little message that i set to include the NIP-11 information (which all the clients don't seem to update very often btw)

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i should also add that both khatru and relayer ( https://github.com/fiatjaf ) have got little slots to let you put arbitrary web handlers in them to do such things as the http server you need for RSS documents, really you just need another process running that fields the updates and rewrides the static files that the webserver can serve)

i haven't done this terribly much with my fork of all this but i made it do some basic things, thanks to your nostrudel relay page showing the content of the normal https socket i put something in there

il_lost_ 1y ago

My idea is this, is already a valid nostr event. (I don't know how to create this event)

{

"content": "{\"Plebchain Radio\": \"https://media.rss.com/plebchainradio/feed.xml\", \"Thank God for Nostr\": \"https://feeds.simplecast.com/VsKScJdA\", \"Bowl After Bowl\": \"https://feed.bowlafterbowl.com/feed.xml\", \"Radio Detox\": \"https://feeds.rssblue.com/radio-detox\", \"Bitcoin Review\": \"https://bitcoin.review/feed.xml\", \"Bitcoin Takeover\": \"https://bitcoin-takeover.com/audio/feed.xml\", \"The Bitcoin Podcast\": \"https://media.rss.com/bitcoinpodcast/feed.xml\", \"The Chris Liss Podcast\": \"https://api.substack.com/feed/podcast/27666.rss\", \"zenstr podcast\": \"https://anchor.fm/s/e07cc4b0/podcast/rss\", \"The Progressive Bitcoiner\": \"https://api.substack.com/feed/podcast/2158428.rss\", \"Hivemind: Ideas from the Edge\": \"https://api.substack.com/feed/podcast/2358372.rss\"}",

"created_at": 1734027180,

"id": "4c1f781e6a23e93f8df40c5249ee5665efc1b666149c24887e139fb91cb3073c",

"kind": 31818,

"pubkey": "79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798",

"sig": "a77c09804c09d8f436ed7af09792491254501da8247e3f8d39a2906f06f20c957c9e02c2ce6ec659239e3929be71e6e32f3c78a6cd5f63a24a2308918b89d01d",

"tags": [

[

"d",

"nostr podcast"

[

"title",

"nostr podcast"

]

}