Is there an actual policy that prohibits use of TW, considering that there is no server component and it would be read only? If not, one approach is to show them some static HTML exported from TW and ask about how to host that and other similar files using SSO protection. Once you know how, hosting one HTML file is as easy as hosting another.
On Saturday, June 20, 2020 at 11:38:59 PM UTC+2, 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/d81ac8e5-6ed7-4653-abee-1504472ec026o%40googlegroups.com.
