jtolio
commented
2 years ago This is great!
Out of curiosity - if we instead allowed you to upload your TLS cert in some secure way to your Storj bucket and then we served HTTPS content with your domain's TLS cert, would you prefer that more or less than this? Obviously it's a very different feature than an image gallery, but it sounds like that might have helped with your original plan? What seems like a better feature to you? (whynotboth.gif is totally a valid answer, just trying to prioritize)
TopperDEL
kmozurkewich
stefanbenten
iglesiasbrandon
I'm developing a photo-gallery-app - you might have heard about it. :) With that app users can create albums and upload images from their smartphone into a buckt. They can then share a link to a generated index.html to view that gallery in the browser with others. So far so good.
My main problem now is that the generated URL (e.g. https://link.eu1.storjshare.io/raw/access/mybucket/albumname/index.html) cannot be served due to phishing problems. So I would have to provide an own domain (like storjgallery.de), add some DNS-entries and "wrap" the linkshare-service with my own domain. That works quite good if I'm ok with providing only HTTP-urls. If I want to add HTTPS, things get complicated. As my app uses the access grant of my users and I'm not providing a "gallery"-service, I do not want to host anything here. But to provide HTTPS-URLs for dynamically generated subdomains (like myusergallery.storjgallery.de) I need to provide a SSL-certificate and thus be a proxy between the user and linkshare.io. All traffic would have to go through my service or I would at least have to provide the static parts (like index.html) through my server and load the bigger assets (the images) via gateway-mt.
Long story short: I talked about this with @stefanbenten. And during the discussion we figured out that there might be a quite easy way to get this problem fixed in an elegant way: The current linkshare-service provides a "landing page" if the URL does not contain "/raw/" and leads to e.g. an image. We could utilize this and add another template, that serves as a "base" for a gallery. So if I call the linksharing-url with a specific path or parameter, it would serve me a standard gallery template (like we already created during the hackathon in spring 2021) and load the dynamic content (albumname and pictures to show) from a file within the provided bucket.
In the end it would go like this:
In the end, the user could retrieve a URL like the following from the app: https://storjgallery.io/accessgrant/albumname and once the user clicks it, it shows a nice gallery. Only the images are dynamically loaded from the users bucket. The static template-assets might be provided by the linkshare-service like it is done today with the "node-map-template".
This would definitely help alot with the app I develop and make everything quite easy. The effort on thet gateway-mt-service should not be that much.
I would appreciate a discussion whether this is possible or not and if I might get that feature. My app is nearly finished, it's "just" missing that HTTPS-part. It would be awesome to get a clean solution without me having to proxy anything and mess with automatic generated DNS-entries. Thank you!