Charlie,

I am not sure. I can't find that specific reply in this thread. Can you 
give me a link from the actual reply please?

I expect its something similar but with a different scope.

Thanks
Tones

On Thursday, 22 July 2021 at 13:12:58 UTC+10 [email protected] wrote:

> Silly question:  are you suggesting you are going to build what I already 
> built and mentioned a little earlier in this thread (Jul 20, 2021, 10:09:07 
> AM) ?
>
> On Wednesday, July 21, 2021 at 10:17:10 PM UTC-3 TW Tones wrote:
>
>> Springer et al,
>>
>> Forgive me for repeating myself, although a lot of interesting ideas, I 
>> believe these to be *non-problems.* 
>>
>> A simple solution is available here. an Example would be an alternate 
>> button to simple permalinks, I think someone else used a share icon. When 
>> clicking this on a given tiddler, it would assign a next number to a field 
>> in the tiddler (basically issuing a unique value field - not a UID or 
>> serial or GUID) then use this field/number to uniquely identify the tiddler 
>> shared, so it does not matter if it's title is renamed. Then generate a url 
>> that instead searches for any (but only one) tiddler with that field value.
>>
>> If *anyone asks* I will build this share button soon.
>>
>> That is if someone wants to publish a robust permalink for a tiddler 
>> who's title may change they use a built for purpose alternative to 
>> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
>> they should be impermalinks.
>>
>> Here is a working example
>> a tiddler with the "permalink" field=1
>> the url wiki-url.html#:[permalink[1]] 
>> In the wiki <a href="wiki-url.html#:[permalink[1]]">Open target</a> this 
>> can be dragged to bookmarks/favourites
>>
>> However I personally choose my tiddler names well enough when needed so 
>> they need not change in future, and if I am publishing a link somewhere it 
>> is to access specific content. the link has a purpose, and once someone has 
>> the link the purpose is fixed in time and should always honour its original 
>> share.
>>
>> A version of the above method where the link filter 
>> is [has[permalink]last[]] will always link to the largest permalink value, 
>> so one is sharing a link to the latest permalink tiddler or post.
>>
>> Another supportive trick is to hide the field from the editor with a 
>> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
>> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
>> thus once set you have to go out of your way to alter the permalink 
>> value, that is its more permanent.
>>
>> Further developments (optional reading)
>>
>>    - Since the addition of the unused title operator, it is possible 
>>    (more to the point easier) to use this to generate a unique and 
>> incremented 
>>    tiddler title and serial number. 
>>    - Rather than shadow tiddlers I am using this not only to generate a 
>>    tiddler Serial Number (TSN) but a "ghost tiddler" that follows any 
>> tiddler 
>>    and provides a way to save metadata for any tiddler or field there in 
>>    (regardless of the title)
>>    - My only issues left are 
>>       - Finding a way to generate/assign such TSN and Ghost tiddler in 
>>       bulk.
>>       - rebuild a parallel solution - system serial number, to assign a 
>>       serial number to core and shadow tiddlers without touching them
>>    - Actually I have found you need only assign serial number where to 
>>    need them, say for these permalinks or compound tiddlers, that is with 
>>    subtiddlers that use the serial number for the parent rather than the 
>> title 
>>    or a tag.
>>
>> Regards
>> Tones
>>
>> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>>
>>> About obsolete permalinks: 
>>>
>>> Surely a variant of the relink plugin could help maintain bread-crumbs 
>>> for obsolete links:
>>>
>>> Whenever relink does its thing, have it offer to create a 
>>> dictionary-tiddler entry pairing old-name and new-name; then have a 
>>> filter-condition ViewTemplate element show up at the bottom of old-name 
>>> tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
>>> perhaps pre-pending a note explaining that the old "Bombay" is now called 
>>> "Mumbai"...
>>>
>>> At first, I was worried about the case where I change tiddler title from 
>>> "Bombay" to "Mumbai" and then later generate a different one called 
>>> "Bombay" -- but there, too, I might be interested in seeing such a 
>>> ViewTemplate addition! After all, if I ever had shared a permalink to 
>>> #Bombay, some signposts around the changing namescape could be useful!
>>>
>>> -Springer
>>>
>>> On Tuesday, July 20, 2021 at 9:09:07 AM UTC-4 [email protected] wrote:
>>>
>>>> This is such an awesome thread.
>>>>
>>>> On Tuesday, July 20, 2021 at 9:04:07 AM UTC-3 Soren Bjornstad wrote:
>>>>
>>>>> *Walt,* the thing that bugs me most about the “immutable title/ID” 
>>>>> idea is that unless your notes are also going to be immutable, the 
>>>>> *content* of a note can still change so much as to make the reference 
>>>>> not effective anymore. So I don't see much point in bothering, as long as 
>>>>> you can avoid having links break. Presumably the thing you were looking 
>>>>> for 
>>>>> won't move so far away from the updated note that you'll be unable to 
>>>>> find 
>>>>> it, anyway (probably not more than one link away).
>>>>>
>>>>>
>>>> Hence why I have an awful lot of love for relink.  I would have a rough 
>>>> time without it.  No broken (internal links) with Relink.
>>>>  
>>>>
>>>>> It is a good point on external links breaking, though. It would be 
>>>>> cool if you could set up redirects within TW, so that you could at least 
>>>>> have an incoming link to an old title go somewhere somewhat relevant. I 
>>>>> guess you could just leave the old title with a link to the new one, but 
>>>>> without an obvious way to distinguish redirect tiddlers from other 
>>>>> tiddlers, they would probably get in your way and make you think they 
>>>>> were 
>>>>> the “real” tiddlers all the time.
>>>>>
>>>>>
>>>> Link rot.  Redirects is a possibility.  I much prefer UID fields and 
>>>> providing links to a Tiddler in some TiddlyWiki with a "UID" reference.  
>>>> (related thread: A Prototype of UID's for stable permalinks 
>>>> <https://groups.google.com/g/tiddlywiki/c/l2Mwu3pOAXw/m/fuvWrwpDBwAJ>)
>>>>
>>>> So if I want to provide folk with a link to a specific tiddler in some 
>>>> TiddlyWiki, in a way that allows me to change the tiddler title 
>>>> willy-nilly 
>>>> without breaking the link, I would give folk this:
>>>>
>>>>  
>>>> https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]
>>>>  
>>>> <https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:[uid[2]]>
>>>>
>>>> For some reason, I prefer this than setting up redirects.  
>>>>
>>>>

-- 
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/dab359da-0a4d-4995-a44e-50f900720b72n%40googlegroups.com.

Reply via email to