I agree with you and see the problem. One simple solution is just sharing links like https://tiddlywiki.com/#:[created[20140904085700000]]
Here is a demo for a new permalink button. It creates a new field called permalink and inserts <slugified title>-<created>. Since the title is unique at creation, this string should be unique (?). Further, it copies the appropriate link to the clipboard; https://tiddlywiki.com/#:[contains:permalink[new-tiddler-20200509141702846]]. If you change the title, the button appends the new <slugified title>-<created> to the permalink field so that both links go to the same tiddler
With the popularity of the relink-plugin, it is much easier for users to change tiddler titles, without messing up the wiki itself.
There has been a very nice idea from Anjar: https://groups.google.com/g/tiddlywiki/c/QOzs3CVtosU/m/_vxFgUeKBAAJ
to use: https://tiddlywiki.com/#:[created[20140904085700000]] as a permalink.
There is a problem with core system tiddlers. They don't have a created field. See Proposal
A second version looks like this: https://tiddlywiki.com/#:[contains:permalink[new-tiddler-20200509141702846]], where the "Permalink" button creates a new field: permalink ... This solution needs write access to the wiki. So this would be the option for the author to create a "human readable" + machine searchable info.
The problem here is, that the modified field will be updated to the time where the permalink was created. .. But IMO that's ok.
!! The Proposal is:
* If the `permalink` field doesn't exist, * use the last part of the link-info eg: -20200509141702846 and search the `created` field * If there is no tiddler with this created field, or the "created-key" doesn't exist (core shadow) * search for system tiddlers, that have the same `<slugified title>` as reqeusted in the tiddler search.The only think we would need to check, if core tiddlers have unique "sluggified titles"
Here is a demo for a new permalink button. It creates a new field called permalink and inserts <slugified title>-<created>. Since the title is unique at creation, this string should be unique (?). Further, it copies the appropriate link to the clipboard; https://tiddlywiki.com/#:[contains:permalink[new-tiddler-20200509141702846]]. If you change the title, the button appends the new <slugified title>-<created> to the permalink field so that both links go to the same tiddler
Best,Anders--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7a484ee5-05f0-48cf-a7dd-8cd15c72a6c4n%40googlegroups.com.
...If you want to try that you can create a view template that tests if the tiddler is missing. If it is it will display the missing message and you can interrogate the URL used to get there and propose the users click a search button to find the tiddlers new title, if by no other method than a unique created date. You could have a table somewhere that it searched for the old title, and find the correct and latest new title.
This has the advantage of tiddlywiki informing the user the link has changed. Like a html 404 page with a search facility. This could even suggest the user open an archived wiki.
I can share more if you want to go that way.
With "Using URL's containing search and reference to a unique ID is superior to permanent links" the key point is a permanent link is that, permanent, it should remain permanent, if we must rename something then we are after a non-permanent responsive link (however it is done).
YouTube video: TiddlyWiki: A Prototype of UID's for stable permalinks