Thanks for the feedback so far guys, but it sounds like I emphasized the wrong thing here. Single file TiddlyWiki works out of the box in Teams or otherwise with no problem using the SharePoint ASPX thing - I probably shouldn't have mentioned ASPX as I probably turned off part of the audience that could help. That's pretty cool and lets you replace the built-in Wiki that Teams provides (which is terrible) with a TiddlyWiki.
My problem is only that I have my whole team using a Wiki using BOB for it's simultaneous co-editing experience as our primary project management software, and it isn't exposed as a http: address. So I'm not looking to host it a different way than I am (I just set aside a dedicated computer on our local network to run BOB), but I need to "trick" Teams by giving it a url starting with http: I mentioned SharePoint because I know I can put any file on SharePoint and have access to it via a http: address, so my thought was to fake a .html file that solely contained an iframe to the 10.1.#.#:8080 address as a kind of hack to bypass Team's url filter. Unfortunately web stuff and networking is probably my weakest area of knowledge. I guess in thinking through it, this is more a question of how <iframe> works, if it can be given a src="10.1.#.#:8080" type address (so far it appears no?) or if there are any similar ideas on how to make that work. Thanks! -- 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/af8a4c38-adde-4657-8a74-f6368f8229e0o%40googlegroups.com.
