Thank you. This works great.
Well, as great as VisoPlaces worked before anyway.
I'm using Fenix Web Server to handle things... it's light/simple/easy.
I can't wait for Google to integrate this into GoogleEarthVR.
So, I didn't exactly find a "solution," but I did find the reason for the issue and a workaround. Apparently TiddlyWiki gets unhappy when you have ~300 mb of image tiddlers. I resolved it by moving those out of the wiki proper, making them accessible from a local server (I used Fenix for this - super easy), and including them as external images (i.e., something like [img width=500 [http://127.0.0.1/Images/Sample.png]]
).
Perhaps running a server like Fenix web server http://fenixwebserver.com and the folder it serves files from is synced with google drive. Only lan users will be be able to access the site although you can create a shareable link for persons outside your network to see the site
How many images do you have in total? How big is your image folder?
But having a webserver is not that complicated honestly. If you have python installed, you can use python -m http.server <PORT>
, but if you don't or don't really know how to use the command line, you can have a look at fenix
But I feel we don't have the whole picture here. What are you trying to achieve in a more general way?
Does he ever get an error?
We had an issue with a member of our community that had ISP level issues explicitly between our subnet, and his subnet. It turns out, someone within his IP Range/Area was caught doing some bad things, and my ISP had blacklisted his whole subnet. It took MONTHS to get it worked out, and required me to provide lots of technical information (netstat's, traceroutes, tcp sniffing, etc) and had to hand-hold my member (ie, tell him EXACTLY what to do to get me in the info) to get the same info from him.
First thing to do would be to test if its Ark, or not. Try putting up a simple static web server (and of course forward ports) and see if you can connect from your phone using your data plan. If ok, then have him try, if still no-go, also have him try on his phone (off the wifi obviously). This will give you some insight as to whether it's a setting on your side, a setting on his side, or an issue between your ISPs.
For a quick/simple static web server, you could check out http://fenixwebserver.com
Also, use a non-standard port, as ISPs often block port 80/443 unless you have a business plan.