3 ms·

Thanks for the feedback! Generally when sharing you send a link like "sandstorm.company.com/share/xh37vmw0h5276mj7h5eh" -- the random hostname you quote is act

by kentonv 11y ago

Thanks for the feedback! Generally when sharing you send a link like "sandstorm.company.com/share/xh37vmw0h5276mj7h5eh" -- the random hostname you quote is actually an implementation detail that you weren't meant to see. :) Once a user has opened a sharing link once, the grain will appear in their "shared with me" list, so they can find it again by going to sandstorm.company.com. We will soon support sharing by other mechanisms that don't involve sending a secret link, too.

spacelizard 11y ago
The use case I am thinking of now seems to be more appropriate for apps like GitLab where sharing URLs from within the app might be useful, for example sending someone a link to a file like this: https://d85snt1c8mqgrfxcd2o1.blah.company.com/gitlab/repo/blob/master/package.json https://d85snt1c8mqgrfxcd2o1.blah.company.com/gitlab/repo/bl... Another issue with this is because of the navigation being done with frames, those URLs are somewhat hidden from the user. I have some thoughts on this, but they may be worth saving for the issue tracker as this appears to be an issue with the GitLab port and not Sandstorm itself.
- kentonv 11y ago
  Sandstorm provides an API to the app through which it can update the URL in the address bar -- adding an arbitrary path after the grainId, which will then be passed back to the app if the URL is re-opened. Lychee and MediaWiki use this, for example. It sounds like Gitlab should too -- that would be a good bug to file.