Use TinyPNG API in App to Compress Files Before Sending to Spee.ch #1670

New issue

Closed

opened 2018-06-21 18:09:52 +02:00 by QuirkyRobots · 6 comments

QuirkyRobots commented

2018-06-21 18:09:52 +02:00

(Migrated from github.com)

Smaller Files = Faster Files, Less Storage, Less Overheads.

TinyPNG is a service I can't live without for my web development work, even after professionally compressing in Photoshop, I can still save a further 40% with TinyPNG.

Many/most content providers have no idea how to compress images for the web. With this in the LBRY app, they wouldn't have to, they would get vastly small files without having to do anything.

TinyPNG supports lossless, lossy and resizing. Lossless should be mandatory with other options being optional.

However, there is a charge, like Amazon AWS. But if it works out that you save more from smaller files then it's not only worth in terms of finance, but also in terms of having a better experience with faster files and less congestion.

The below image (thumbs.jpg) was a typical image a typical user would upload to LBRY.

## Smaller Files = Faster Files, Less Storage, Less Overheads. [TinyPNG ](https://tinypng.com/developers) is a service I can't live without for my web development work, even after professionally compressing in Photoshop, I can still save a further 40% with [TinyPNG](https://tinypng.com/developers). Many/most content providers have no idea how to compress images for the web. With this in the LBRY app, they wouldn't have to, they would get vastly small files without having to do anything. [TinyPNG ](https://tinypng.com/developers) supports lossless, lossy and resizing. Lossless should be mandatory with other options being optional. However, there is a charge, like Amazon AWS. But if it works out that you save more from smaller files then it's not only worth in terms of finance, but also in terms of having a better experience with faster files and less congestion. The below image (thumbs.jpg) was a typical image a typical user would upload to LBRY. ![image](https://user-images.githubusercontent.com/29914179/41731043-b639cfca-75c0-11e8-84d4-96dacee05ff8.png)

QuirkyRobots commented

2018-06-21 18:11:58 +02:00

(Migrated from github.com)

Example:

curl --user api:YOUR_API_KEY \
     --data-binary @thumbs.jpg -i https://api.tinify.com/shrink

**Example:** ``` curl --user api:YOUR_API_KEY \ --data-binary @thumbs.jpg -i https://api.tinify.com/shrink ```

👍 1

btzr-io commented

2018-06-22 02:21:11 +02:00

(Migrated from github.com)

Open source: https://github.com/lovell/sharp

👍 2

QuirkyRobots commented

2018-06-22 10:21:11 +02:00

(Migrated from github.com)

I was going to suggest adding an open source option but didn't know of any or if they produced good results. I'll see if there is a test area for the one above and give it a go.

alyssaoc commented

2018-08-11 02:03:53 +02:00

(Migrated from github.com)

@tzarebczan should this be closed in favor of 1770?

kauffj commented

2018-08-13 15:22:49 +02:00

(Migrated from github.com)

Any optimization behavior that is logical to add to the desktop is presumably logical to add to spee.ch directly. So this should probably be a ticket on spee.ch.
If moving to spee.ch, it is decently likely this should be done locally rather than via a 3rd-party API.

1. Any optimization behavior that is logical to add to the desktop is presumably logical to add to spee.ch directly. So this should probably be a ticket on spee.ch. 2. If moving to spee.ch, it is decently likely this should be done locally rather than via a 3rd-party API.

tzarebczan commented

2018-09-16 19:55:05 +02:00

(Migrated from github.com)

Issue moved to lbryio/spee.ch #599 via ZenHub

Issue moved to [lbryio/spee.ch #599](https://github.com/lbryio/spee.ch/issues/599) via [**ZenHub**](https://www.zenhub.com/)