search

crspybits / SharedImages

Neebla on the Apple App Store: Private and Self-Owned Social Media: This is *deprecated*: see http://github.com/SyncServerII/Neebla.git
https://crspybits.github.io/SyncServerII/
MIT License
12 stars 9 forks source link

Deep link to images #130

Open crspybits opened 6 years ago

crspybits commented 6 years ago

Recently, I told Rod about an image I'd just uploaded to SharedImages. Then, Dany had problems finding that reference because I'd subsequently added a few more images. It could be useful to have a deep linking facility, where you could send a friend a deep link to the specific image. That deep link would presumably require that the person already be a member of the sharing group, and have SharedImages installed. Under these conditions, I see no reason for that link to expire.

crspybits commented 6 years ago

From Dany: Personal preference :deep link to underlying storage uri. Possibly with expiration so it opens in browser.

Note that this would require at least a partial web-based client: To enable the user to sign in to the system. And also to access at least file index and download endpoints.

crspybits commented 6 years ago

Another way to do what Dany is suggesting would be to make the link independent of creds. An expiry would be suitable then. And a new endpoint would be needed. This would seem to raise issues of application type. E.g., even in shared images we might want to share both the image and the discussion thread. Thus the client web interface would have to be specific to SharedImages.

danligas commented 6 years ago

I can see if sharing a discussion being necessary to require all users to have the app. The sharing of a single image as a single use app may be a different concern than being addressed by "deep linking" as this issue was originally opened for.

On Mon, Sep 3, 2018 at 2:34 PM Christopher Prince notifications@github.com wrote:

Another way to do what Dany is suggesting would be to make the link independent of creds. An expiry would be suitable then. And a new endpoint would be needed. This would seem to raise issues of application type. E.g., even in shared images we might want to share both the image and the discussion thread. Thus the client web interface would have to be specific to SharedImages.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/crspybits/SharedImages/issues/130#issuecomment-418174584, or mute the thread https://github.com/notifications/unsubscribe-auth/AJEDwghCqmgP_IItLSpBrhLkCb8wsBhwks5uXXYkgaJpZM4WXtJ_ .