Yeah the encoded param is regenerated on any block change, so you’ll know if there’s a change. I’ve been thinking of ways to lock down content. Maybe a separate hashed entity in the document config that is only able to be decoded with a localStorage key on the client that authored the content. Thanks for your input!
Comments
I assume you would need some sort of hash/encryption to make sure the link is not changed in anyway. I wonder who would need that though.
Then again, with that long param at the end of the url, it looks like it should be unique anyway unless the message is the same.
Yeah the encoded param is regenerated on any block change, so you’ll know if there’s a change. I’ve been thinking of ways to lock down content. Maybe a separate hashed entity in the document config that is only able to be decoded with a localStorage key on the client that authored the content. Thanks for your input!