So many web host implementers already. Let's go!

GM.

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

Reply to this note

Please Login to reply.

Discussion

Free relay owners

They should be able to just block certain kinds of they want to

They can 😑 But should they? They knew from the beginning that Nostr is more than just notes

We have no say if they "should" or not. Everyone does whatever they want here. :)

Nah, they shouldn't 😉 No one promised them an easy life 😂

yep. strfry write policy will be coming in clutch for me soon enough... xD

Isso pode ser uma revolução sem precedentes

can we make a nftshowroom like nftshowroom.com? they used a Hive thing to run it. Hive runs like Steemit. It has keys but more than two. like address key, posting key, secret key and I think one or two more keys. Nftshowroom is much like the Ethereum setup. maybe we already have that. is it raretoshi dot com?

nft is a shitcoin

One thing that is annoying with IPFS is when you push an update it’s a new CID. It sounds like this might be similar for a new nostr event ID on each update? Or, could there be a way to update the content while preserving the event ID so it wouldn't have to be changed in source each time?

The two ways are proposed. They have different use cases.

This looks great for bundles, but get weird for modular stuff, doesn’t it? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 you should create one for the nostr-tools bundle

I'd say it's the opposite. It's great for small scripts, one per event ID. I'd keep scripts in max 75kb or so to make sure they fit in any relay out there.

Oh yeah, absolutely, if you are thinking about it from the nostr side of things. But when it comes to actually building something with it, you don’t want to fetch 30 different small files whenever someone accesses your website. This is exactly why we have web pack today

any recommendations?