00:55 <TimMc> For just sharing links, you could grab the grain URL on demand (somehow)... but it really would be nice to have grains support deeplinking in general.

01:26 <ocdtrekkie> TimMc: https://oasis.sandstorm.io/shared/A9MKYwaMtKZ1p5xC5KQlknXDP4muS7NyAyE_JKI7di4/files/Android/

01:26 <ocdtrekkie> Works for Wekan cards too.

01:27 <ocdtrekkie> The problem is just that grains can't see their own URLs, neither the grainId (for those who already have access), nor the share link (if you want to share that deep link with permissions).

01:28 <ocdtrekkie> isd: Davros updates the URL in the browser, FYI. Just tested.

01:28 <ocdtrekkie> In fact, when you first load a Davros grain, it adds /files

01:28 <ocdtrekkie> And when you click on a folder, it adds /foldername to that.

01:33 <isd> Happen to know how it does that?

01:33 <TimMc> was just about to ask that

01:34 <TimMc> Does it send a postmessage or whatever informing the outer frame of the update? In that case, sharing links could always work.

01:34 <TimMc> (for apps that send those updates)

01:53 <ocdtrekkie> No earthly clue, isd. I know that it works, I do not know how it works.

02:33 <jwhisnant> should a sandcats.io domain work, assuming that I enable port forwarding? I would think so, but it doesn't seem to work. I checked DNS. I am not convinced that my router firewall's isn't lying to me. Are there any ports other than 80,443,25 that I would need?

02:42 <isd> jwhisnant: should be okay, but your ISP may also be mucking with things. More likely than not port 25 is blocked, but you probably want to be listening on a higher port for that anyway (and it's only needed for incoming mail).

02:42 <isd> RCN blocks port 80, so mine isn't accessible via http (but https is fine).

02:43 <isd> I am on my way out the door though; can't stick around to help unfortunately.

04:54 <kentonv> isd, TimMc: https://docs.sandstorm.io/en/latest/developing/path/#updating-the-url-page-title-from-your-app

11:17 <TimMc> kentonv: Got it, makes sense.

13:29 <jwhisnant> isd: thanks for your help. turns out it was a routing problem. My router would resolve by name, find the IP address (which was its OWN interface, since I am doing port forwarding) and then drop the packet. It works fine now that I am on another network (at $work).