but it technically is a fork no? because if the original nsite gets updated, the copy won't or does it?
Semantically, yes. Where I take pause is that by virtue of how this works, you downstream isn't editable, until you upload something entirely new; and then it's completely disjointed. With upstream, we're working out how broadcast optional updates safely.
The thought process behind how this works is really just about leveraging existing blobs and offloading changes to nostr. Once anything changes in the blobs it's just another deployment.
It's an inverted fork maybe?
The high-level ecosystem of how this works is also greatly different. Basically, the blobs keep multiplying until "perfection" where it is no longer necessary to make any changes to the blobs, because any changes required can be done dynamically via nostr.
It's something else IMO.
The thought process behind how this works is really just about leveraging existing blobs and offloading changes to nostr. Once anything changes in the blobs it's just another deployment.
It's an inverted fork maybe?
The high-level ecosystem of how this works is also greatly different. Basically, the blobs keep multiplying until "perfection" where it is no longer necessary to make any changes to the blobs, because any changes required can be done dynamically via nostr.
It's something else IMO.
2❤️1
