I'm an amateur security-type, but I'm more so a creative type. I cannot imagine any scenario that would be a problem other than a UID-permalink opening unintended tiddlers in addition to the intended tiddler.
It should not matter any, but I've been a programmer for close to 40 years. One of my expertise is relational database design. So I feel ridiculously confident that this is perfect. Small. Lean. Quick. Simple. Stable. Robust. Doesn't break anything. But all of the experience/expertise in the world doesn't mean the scenario that makes me eat crow isn't just around the corner. If you are planning to include me solution in the micro-chips for the rocket that will take you to Mars, don't do it. The UID thing is just a field to help build stable permalinks. One would likely never create a UID for every tiddler in his/her TiddlyWiki. Only for those that one needs. For example, to include a link to a specific tiddler in an email, or in a post here, or from anything on the web to the specific tiddler in your TiddlyWiki on the web. The only way to get an unintended duplicate UID is for you to manually set duplicate UID's in a bunch of tiddlers, or to import from some other TiddlyWiki a tiddler with same UID. Likelihood is small, maybe nil. If it happens, it breaks nothing. There is nothing anywhere that cares about a UID other than a link somewhere intended for a specific tiddler that might cause additional non-related tiddlers to also show. The UID thing doesn't permeate into anything else. The TiddlyWiki core knows nothing about UID's and doesn't care. Plug-in's out there don't know about UID's and don't care. If you want to complicate the UID-permalink thing with all sorts of dates, that's okay. If it makes you feel better, then it isn't a waste of your time. Anything more complicated/convoluted than plain sequence of numbers for UID would be a huge waste of my time. Really, I'm begging for anybody to prove me wrong. Prove that it breaks anything. Not that there would be much value in the bragging rights. I'm no super-hero, over here. However, if you really believe that this simple thing will have huge negative consequences going forward, it would be really good to know earlier than later. But prove it, for everybody's benefit. On Sunday, May 9, 2021 at 11:26:13 AM UTC-3 ludwa6 wrote: > I understand, Charlie, how you are only trying to solve the problem w/in > scope of a single wiki -and if that were a truly closed system, then indeed > your solution solves the problem, if i'm understanding it correctly. > > However: i do see how easily tiddlers with the same ID could wind up in > the same wiki in my case, where i've got a mitt-full of different editions > that i am drag&dropping tiddlers across without due care, i suppose (mainly > owing to that phenomenon Dave Gifford has described so well in his take on > the "What is #TiddlyWiki" > <https://groups.google.com/g/tiddlywiki/c/jIhG30rx1PU/m/153I2Xl7BQAJ> > question. See: it's Silly-Putty, as i said :-). > > So, i have to ask: in case of UID conflict: is what would happen indeed as > innocuous a condition as what you describe, i.e.: the two named-alike > tiddlers would both display to the WWW browser who comes in on that link? > No other problem you can forsee arising out of that? > > I do still think that the create date/time is sufficiently granular as to > make the risk of similarly-coded tiddlers as near-zero as you could want, > especially if combined with and/or hashed by some other factor. I gather > that this doesn't work for those pesky "$:/" tiddlers -but that's fine, > since we don't want it to (and there's no way such a thing could happen by > accident, right?) > > /walt > On Sunday, May 9, 2021 at 2:59:14 PM UTC+1 [email protected] wrote: > >> It will always be unique within one TiddlyWiki. Same as "Sequence >> numbers" in an Oracle Database. >> >> The UID isn't really a counter. It gets the the largest value of UID >> that exists among the tiddlers, then gives "this tiddler" the greatest >> value + 1. >> >> So not a counter in the sense of a stored value in some field. Maybe, >> for performance, I'll have to set things up that way someday, but not for >> now. >> >> That said, this is only about unique and stable permalinks for Tiddlers >> in a TiddlyWiki, not about unique identification of tiddlers. >> >> If you wanted to, you could create a bunch of tiddlers, and copy-paste >> the UID's among a bunch of them so that a UID permalink actually opens a >> group of related tiddlers, if that's something someone wanted. >> >> To reiterate: The UID's are not about unique identifiers for tiddlers. >> That's a different problem, but one that I don't think needs solving. >> Well, until it ever bites me in the caboose. It hasn't yet, but my caboose >> is polished and ready for the bite at any time. >> >> That aside ... >> >> Say we both have TiddlyWiki's that use this UID thing I've developed. >> >> And say I import one of your tiddlers into my TiddlyWiki, and I now have >> two tiddlers that have UID values of 55. One of mine, and the one I >> imported from your TiddlyWiki. >> >> Who cares? >> >> Every URL link out in the wild that references my TiddlyWiki with UID 55 >> will now open with my tiddler and your tiddler. >> >> However, my original intent for the UID permalink is not borked. We can >> still easily get to my tiddler. >> >> If your tiddler (UID=55) gets to be a real pain, then I'll strip the UID >> off of your tiddler that is in my TiddlyWiki. >> >> Anyway, all of that said, this UID-permalink thing does what it is >> supposed to do in the problem scope I'm thinking, but is in no means meant >> to solve the problem scope of unique identifiers for all the tiddlers in >> the world. That is not a problem I am interested in at all. >> >> >> On Sunday, May 9, 2021 at 10:43:06 AM UTC-3 PMario wrote: >> >>> Hi, >>> TLDR; I think a "counter" used as UID will fail in the short run! >>> >>> I did my post my concerns at github. >>> https://github.com/Jermolene/TiddlyWiki5/discussions/5668#discussioncomment-715278 >>> >>> -mario >>> >> -- 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/d8d9a29a-3bf8-4539-8be6-2c17ac70ee1dn%40googlegroups.com.
