search

mdshack / shotshare

Open source image sharing application
https://demo.shotshare.dev/
MIT License
138 stars 10 forks source link

Option to copy a hyperlinked thumbnail to the clipboard instead of merely the URL #16

Open Raytle opened 10 months ago

Raytle commented 10 months ago

My Typical Use Case

Obviously other users would have different use cases. Nonetheless, I think an example would help you to easily understand how users might use this feature.

I use Google Workspace (primarily Google Docs) kind of, sort of like a wiki. I tend to post many images inside of my Google Docs. To avoid surpassing Google Workspace's 15GB freemium limit, I like to keep videos and images out of Google Docs and off of Google Drive.

Therefore, instead of merely having a URL of an image I upload to ShotShare copied to my clipboard, I would like to get a thumbnail that is hyperlinked to the image I just uploaded to ShotShare.

My Typical Workflow

  1. I would configure Flameshot to have an option to upload images to, what would be, my self-hosted instance of ShotShare (instead of the default image sharing site which is, surprise, surprise, Imgur https://i.imgur.com/cQPrqNG.png)
  2. Take a screenshot using Flameshot.
  3. Press the Enter key to upload the image from my clipboard to ShotShare (instead of Imgur).
  4. Open up a Google Doc.
  5. Choose Paste so that the hyperlinked thumbnail of the image would be pasted into that Google Doc.

Primary Benefit of the Feature for me

I will be able to avoid creating large Google Docs (and concomitantly remain within the 15GB limit imposed on the Google Workspace's freemium version), yet see a little thumbnail which I could click on to see the image I had posted to ShotShare.

Related Features

  1. Allow users to define the border thickness and color to help them to subconsciously realize without even thinking, "Oh yeah, that thumbnail [in, for example, a Google Doc] is of an image I posted on ShotShare."
  2. Allow users to choose the percentage of the original size for the size of the thumbnail. Because someone, somewhere might actually want larger "thumbnails", allow users to enter 1 to 1000, where 100 would be the original size (100%), 1 would be 1% of the original size, and 1,000 which would be ten times the original size.
  3. Allow users to choose JPG, PNG, or, well, I don't know much about image formats, but perhaps another image format.
  4. Allow users to choose to create thumbnails in color or grayscale. (Think of users who are serving wepages from an IoT device which, despite having limited resources, does actually serve webpages).
  5. Allow the user to press a hotkey to cycle between paste link only, paste hyperlinked thumbnail, and paste thumbnail only.
  6. Ideally create a version that doesn't require a database at all (not even SQLite). I'm thinking of DokuWiki which makes it trivial to backup and redeploy. I am thinking of users who don't plan to actually scroll through images on ShotShare, but rather only intend to link to images on ShotShare. For them, I'm guessing a database might not be necessary, particularly if they only had, say ten thousand or twenty thousand images on ShotShare. I suppose, if someone were to have many millions of images on ShotShare, they might need at least an SQLlite database, in either case.

Integrations with other FOSS

  1. Get the devs at Flameshot to include this feature as an option in Flameshot.
  2. Get the dev at SingleFile to include this feature as an option in SingleFile. This point would be very helpful to me, because even if I upload a HTML file I created with SingleFile to Google Drive, I need to download it from Google Drive to view it because Google Drive does not natively display HTML files, and because I refuse to use any plugins, in my Google Drive (because I'm extra cautious about using plugins), and because many of the HTML pages I create with SingleFile are large.

Final Note

SingleFile is the bees knees because, in a sense, it is as if it generates a PDF in that the files it creates are WYSIWYG (What You SAW Is What You Get), yet because it actually generates HTML, the files it creates are generally much more performant than PDFs.

mdshack commented 6 months ago

Having not pasted many images into Google Docs, would the https://[instance]/image.(png|jpg|whatever) link be what you needed to upload your image?

I have heard of Flameshot, but seem to remember their integration point being rather light/non-existent. I have integrated with ShareX, but know this doesn't really apply to Linux.

In ShareX you can actually configure what link gets copied, which is cool, if we can do anything like that for Flameshot that would be slick. Alternatively, if Flameshot doesn't pan out and you have ideas for a client, I am also all ears!

Raytle commented 6 months ago

Having not pasted many images into Google Docs, would the https://[instance]/image.(png|jpg|whatever) link be what you needed to upload your image?

I don't understand that question.

I have integrated with ShareX, but know this doesn't really apply to Linux.

Unless I were going to take a huge performance hit to run it under WineHQ, ShareX doesn't apply to Linux.. at all.

I ended up deciding to simply use with Google Workspace after all because I don't want to the hassle of dealing with hosting shotshare.