Hi Walt,

It should be trivial to modify the permalink button to produce links as 
https://tiddlywiki.com/#:[created[20140904085700000]] but the creation time 
is not guaranteed to be unique (the link will then open both tiddlers, so 
no harm is done), although in practice it usually will be

An alternative is to make the permalink button add the current title to a 
separate field (say permalink) and use that field to produce a URL like 
https://tiddlywiki.com/#:[permalink[aReadableTitle]] 
<https://tiddlywiki.com/#:[created[20140904085700000]]> The strength is 
that the URL then will be human-readable and you have the history of old 
titles, but again, it is not guaranteed to be unique

If you are not afraid to add plugins, there is a plugin (
https://ibnishak.github.io/Tesseract/pluginsandmacros/index.html#UUID%20Plugin) 
to create UUIDs that can also be used to populate a separate field to get 
URLs like https://tiddlywiki.com/#:[uuid[anUUID]] 
<https://tiddlywiki.com/#:[created[20140904085700000]]>

Best,
Anders

onsdag 5. mai 2021 kl. 15:50:00 UTC+2 skrev TiddlyTweeter:

> Ciao cj.v..., 
>
> Interesting! 
> Functionally that is working like a SURROGATE permanent REDIRECT. *It is 
> a clever solution!* but requires the logic of the Wiki to change 
> considerably and its owner to know what to do. :-)
>
> HOW, for instance, do you quickly generate a PERMALINK you can quickly 
> post online?
>
> Probing :-)
> TT
>
> On Wednesday, 5 May 2021 at 15:43:16 UTC+2 [email protected] wrote:
>
>> G'day walt,
>>
>> That is a huge pain point for me.  In my previous career, I relied 
>> heavily on the ProjectForum Wiki to keep track of everything.  It did not 
>> use page names in URL links, but rather used auto-generated unique 
>> identifiers.  So I could change page titles to my heart's content, knowing 
>> that URL links were always stable.
>>
>> My approach, still formulating it, is to edit tiddlers via custom forms.  
>> The tiddlers have auto-generated unique identifiers stored in the title.  
>> What would normally be the title goes in a field.
>>
>> That works fine right as-is for structured data.  I haven't looked into 
>> setting up the formatting buttons (bold, italics, etc.) for formatting text.
>>
>> I think this could still work for you well if you have an easy way to 
>> lookup tiddlers via a field instead of via title, and if you can overcome 
>> that mindset change.
>>
>> On Wednesday, May 5, 2021 at 5:34:24 AM UTC-3 ludwa6 wrote:
>>
>>> The more i use TW, the more concerned i become about maintaining data 
>>> integrity -and so this issue has boiled to the top of my queue: how can i 
>>> continue to enjoy the benefits of TW (+ Relink plugin) flexibility, without 
>>> compromising the integrity of Permalinks?  
>>>
>>> This feels like a deep problem that goes right to core TW architecture- 
>>> since, as PMario explained in last thread 
>>> <https://groups.google.com/g/tiddlywiki/c/kTrAbuneCkA/m/lAsdkriFAgAJ>, 
>>> tiddler immutability is tied to its Title (so how can Relink even work, i 
>>> wonder?)- but if i've learned anything here, it is to not underestimate the 
>>> creative problem-solving ability of this group :-)... SO:
>>>
>>> From a non-technical perspective, what i'd like to do is have some 
>>> immutable UID (based on date-time, or maybe date+ a serial number, like 
>>> yyyy-mm-dd-serialnum) that is used for Permalinks (i.e. shared w/ the 
>>> outside web that is not Relink-aware), but still have Title field and 
>>> Relink plugin (and everything else for that matter) work just as it does 
>>> now, from the TW editor's perspective.
>>>
>>> Is this a reasonable feature design goal, i wonder?  If so, i'd like to 
>>> do what i can to help make it happen!
>>>
>>> /walt
>>>
>>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/e94c7143-bcee-4c96-9b4f-3de99ed4eefen%40googlegroups.com.

Reply via email to