William - thanks for responding. > TW has the ability to deny the ability to read and/or write to the wiki > when served on node, but does it have this ability on a per tiddler basis? > That is a separate feature you kind or hint at or just gloss over. >
Access to the wiki needs to be read/write, however a filter can be applied to the save process to only permit $:/namespace/* tiddlers to be saved. A bad actor could defeat this of course. So in effect it does have this ability on a per tiddler basis. > > Otherwise, this doesn't look much different than serving several wikis > like Bob currently does. With the added benefit to being able to search > through all the wikis. > Bob place may overlap with this, but this is much simpler and can also add value in single file tiddlywiki cases. I believe there is a way to search through all wikis with Bob. It is not serving several wikis it is serving one and a number of name spaces. > > So, breaking down the feature requests, we can say: > > > 1. Add ability for TW to choose to save to multiple subdirectories. It > is already able to save to the Files directory in addition to the Tiddlers > Directory, but with the specific use case you are talking about, you now > need to interface user names to the filesystem. I don't know enough about > what usernames are limited to in TW, but the FS definitely has > limitations. > Older FS default to other than UTF8 encoding, and EXT can support > different > ones depending on the server. I don't know what the situation is on > Windows. Node will probably handle that, but there will be cases where the > User Name and the Directory don't match. Also, if the Username is a First > Name and Last Name, should TW make one folder, two folders First Name > first > or two folders Last Name first? I tend to favor the last, which can reduce > the number of folders in the top level directory. > > I don't think I am asking for "Add ability for TW to choose to save to multiple subdirectories", I only ask that with permissions available we can save/download a subset of tiddlers to another file (on the server or locally), just as we currently write to tiddlywiki.html. We can ensure usernames are unique, and even store a hashed filename to save with. eg; in the user name tiddler <<qualify filename>> The folders I suggested were only "virtual" folders, that appear to be there just as mydomean.com/tiddlername appears to be a static tiddler. > > 1. Add the ability to have r/w permissions on the Folders. This is the > simplest method, and give nobody the right to edit the main Tiddler top > level. This gives you all the benefits, without having to have a canonical > source for all wisdom, the top level tiddlers. > > In this case perhaps we could use the server to allow/disallow saving the tiddlers to the logged in user name space, but not necessary with trusted users. > > 1. Additionally, add r/w permissions to tiddlers. This should not be > too difficult, in terms of implementation. Each tiddler would get a hidden > field with predetermined values. In the wiki model, we could take a page > from Facebook and include group permissions, which would allow for, say, > adding receipts that are viewable from anyone in the accounting group, or > if writing articles, anyone in the editor group. That makes it a set of > fields, however. > > Interesting but I my suggested solution unnecessary. > > 1. The ability to version control the tiddlers. > > Some solutions already exist and should operate independently. > > 1. The ability to diff the tiddlers. > > Easy with cross namespace tiddlers. > > 1. A UI for those functions. > > Yes > > 1. Extrapolating: The ability to modify username on import. Possibly > the ability to change multiple usernames at import. > > Yes, but not always necessary if the import is into a namespace, or change control copies an approved tiddler over a master tiddler. > > 1. Create namespacing for tiddlers. I have no idea if this is in TW > currently. If this were done, I can foresee a lot of performance use cases > in large wikis. > 1. You could could namespace each connection to the server, and > only serve the tiddlers necessary for the current view. This is almost > certainly needed if you have 100 people using the same wiki. Other > wise, > your bandwidth cost will grow extremely quickly out of control. This > would > force most searches be done server side. > > I am not sure about performance issues here. Only the total size of wiki will be an issue and 100,000s of tiddlers are already known to work well. If only one name space is loaded at a time this will give a performance gain. > Alright, see if this is close to the idea you are expressing? Correct > anything that is wrong with it, or add to it. > Done, Thanks for your contribution. Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/a65e3d21-d17a-4d62-a203-2fadd1832440%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
