I get that the static pages can be linked to Nostr posts. To make that work, I'd have to create a Nostr post of some kind outlining, for example, my About page.

My random post on Nostr would be an article titled "About" and then the content is below. Then you take that link and place it not the spot you want it in npub.pro.

No problem so far.

I'm just thinking of future revisions. If I updated my "Services" page 5x, that means I have 5 different "Services" articles floating around on Nostr. A user can come find one (an old one), point to it and say, "No. In this post, which is in writing -- says your prices are such and such," when in reality, the *latest* "Services" page has the updated information, right?

There'd have to be some sort of disclaimer somewhere on your profile bio or the website itself stating what is "latest" to reduce the chances of disagreements in the future.

Also, do our followers want to see 16 different published drafts or updated pages of the same page in their feed just because we needed to make an update to a static page?

That's what I can't figure out in my workflow so far. I'm not quite sure what to do with it.

That's where I got stuck in the "building" part. On my regular website (not Nostr), I've updated the web pages a lot. Here on Nostr, had I done that, it would have created the (as an example) 16 different posts each containing a different version of the page.

I'm not sure if what I'm describing is making sense.

Reply to this note

Please Login to reply.

Discussion

Good question

If you use long-form article as a static page then it's a replaceable event - every time you edit it the old version is deleted by relays and new version is saved. Even if someone saved an old version you can always show them the newer event and the protocol rules that say "new one replaces old one". It's the same thing with web pages - someone could save old version with old pricing and start asking questions, at least on nostr you have signatures and open timestamps to make sure no fake claims can be made.

Ok, wasn't aware of this.

Which clients have been specifically tested with the article format with updating that work as described above with npub.pro?

Not all relays (and maybe clients?) are required to honor all parts of a protocol just because a request is made. For example, a user can use a client to request a deletion of a post, but not all relays are required to honor this. Some clients do not offer the option.

Which ones did you find work properly?

It doesn't much matter which relays honor what - your signatures and timestamps matter. With old internet anyone could take a screenshot or save a webpage with old pricing (or even make a fake one) and start asking questions. On nostr you have signatures and structured events, so a) no fakes possible, b) much easier to prove you published newer event with newer pricing, especially if that event has comments and likes from other people.

Honestly, I'd say this is overthinking, edits/deletes exist, most relays support them, most apps support them, and bad actors will always find loopholes to ask stupid questions.

Kind 30000 addressable events and d tags should meet the static page requirement. Only the latest is saved by the relay.

What that does that mean in English for non-techy people?

I'm a technical writer by trade, but I don't eat, sleep, or breathe Nostr technology for fun or for business. If I did, then I'm sure I would have understood what you said.

I'm just interested in what things work and where.

There is an event type for long form or blog writing that is replaceable by the author. For example, if I write an entry entitled “My summer vacation 2024”, it will be published. And later on, if I update and republish “My summer vacation 2024” it will overwrite the old one of the same title. This event type could be used for static pages that are updated every once in awhile.