Springer, This is actual quite a big subject, I would be happy to look at this with you at length. Let me however make a few points that may lead you to a solution first.
- Consider TiddlyWiki single files as a "smart document", basically they are a document like any other file, but they use a browser to provide for editing. The smart comes from it ability to customise functions and features in the document itself. - If someone can't get to the file they can't get the content - they use an organisations standard security - Unlike documents, unless you have a local app like tiddlydesktop the browser security is an additional level of security standard documents don't have, for example word and excel macros can wreak havoc on the local computer. - If you can view something, anything, you can copy and export it, this is true with almost anything, this is no different with tiddlywiki, though unlike other documents you can configure tiddlywiki to make modification difficult. To expect a higher level of security than that, from tiddlywiki is unreasonable. Only line of business applications using a server and client has a chance of securing data more tightly - but it is still, if you can see it you can copy it rule, and now days many line of business apps are in the cloud with their own security issues. - If you have a secure file on a system, that only authorised people can write to that file and location,will guarantee it is the source of truth, because people can not write back to the file unless permitted to do so, even if they make it look different in their browser. - If you are using Microsoft teams you should be able to share tiddlywiki's like documents, and choose the rights to save. - I have written a business application in tiddlywiki that uses sharepoint (Teams is on top of sharepoint in many ways), the key is demanding checkout before you can save, and renaming .html to .aspx - I have posted on this previously - To get it to load quickly I put it in a wiki library - I was a global admin for microsoft O365 and SharePoint for some years, then I changed roles and lost my permissions, but I was able to get anything I wanted with a little "legitimate hacking". - With a few tricks, the best way to host tiddlywiki I have found in a corporate Office environment only requires write access to a wiki library and some "secret knowledge" In closing I stand ready to implement tiddlywiki solutions for other businesses in the future, so shared effort on this issue has relevance to my business. Perhaps we could build a business case document? Alternatively as a former super admin and being aware of the machinations in IT Departments, I personally would ignore them all, and would workaround their ignorance. Regards Tony On Sunday, June 21, 2020 at 7:38:59 AM UTC+10, springer wrote: > > Eric, that is roughly what my first very first query indicated (that I > wanted to host an html file in that way)... Once it was clear that this > wasn't a "dumb" web page (for which they want to sell me on enhanced > substitutes), they replied with something about only hosting content that > they were "subscribed" to... > > The fact that TiddlyWiki is open-source and very well established didn't > seem to bypass that concern... > > I suppose it's something about needing to feel like they can "support" > whatever kinds of information-resources exist on their own servers. (As if > I'd go knocking on their door when I run into some challenge with > developing my TW content...) > > Anyway, I will keep following up in hopes that they can give me a server > space that works within the relevant permissions. > > I do think that if TiddlyWiki gets a real footprint in educational > settings (which might in turn benefit from something like an off-the-shelf > "package" with plugins that reduce the learning curve for educators), its > profile will take off. > > Thanks! > > -Springer > > On Saturday, June 20, 2020 at 4:47:54 PM UTC-4, Eric Shulman wrote: >> >> On Saturday, June 20, 2020 at 12:16:07 PM UTC-7, springer wrote: >>> >>> I showed one of my tiddlyspot sites to my helpful IT person and asked >>> whether the university cost host a tiddlywiki file on a server on its >>> domain somewhere such that access would be limited to members of such a >>> team (or in any other way mediated by our SSO's AD subsets). The response >>> was a whole bunch of enthusiastic suggestions about available apps that I >>> could work with *instead* -- apps that would (from her point of view) serve >>> the same functions as TiddlyWiki. >>> >> >> As you know, a TiddlyWiki is *just* an HTML file... not an "app" in any >> conventional sense. >> Instead of showing them one of your TiddlyWiki files (and how wonderful >> and versatile it is!), I'd simply say: >> >> "I have a single HTML file (and perhaps related image files) that I'd >> like to post to an SSO-protected website. >> How can I upload those files so that only users of that SSO can *view* >> them in their web browser?" >> >> This hopefully avoids any apprehension they may have that TiddlyWiki >> could pose any security risks. >> >> -e >> > -- 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/33f01b93-877a-4859-8056-4d6ef711746fo%40googlegroups.com.
