Cannot rrecommend

  • I know the programmers put a lot of work into this and credit is given that, but I cannot recommend for the following reasons:

    1) Had to punch another hole in the firewall to allow access to an api.

    2) I randomly picked an image in media (currently only 100 images) to smush (1.6mb image). It sat there for some time before I gave up. VPS system with 8g memory, quad core processor.

    3) I’m not sure I would like to have my images or relevance thereof floating around on an Amazon bucket.

    4) The plug-in is being sold (the sales pitch) to reduce bandwidth, but requires bandwidth to get anything accomplished, if anything.

    Uninstalled, left over database entries removed.

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hi @ohgoodiee,

    I’m sorry to hear that you were not satisfied with Smush, but to be fair – many of your points are not true.

    1. There are no inbound connections to Smush from external servers, so there is no need to adjust firewall rules.

    2. Did you have any errors in the debug.log? Usually, it takes 10-15 seconds for an image to be processed and this does not really rely on your server, as all the processing is done on the API to keep your server running as fast as possible.

    3. Smush does not upload your images to Amazon. You must be confusing this with another plugin.

    4. Smush is marketed as an image optimization plugin. Smush, and most other image optimization plugins, will compress images on an external API to remove the extra processing from your server and make it run faster.

    Best regards,
    Anton

    Thread Starter ohgoodiee

    (@ohgoodiee)

    I’m sorry you didn’t like my review. So lets review a couple of things

    If you have an api call. In this case to Amazon at 34.x.x.x, there has to be a response. Hence the opening in the firewall or you will receive a cURL 7 error. Established fact. What all transpires in the api call; I didn’t take the time to look at all the code. With that being said. If the image is not done on the server, then it must be done somewhere else. Amazon.

    There were no errors generated when I attempted to smush an image. After looking at it for 15 minutes, I had other things that needed to be done and moved on.

    I did not state that it did upload images to Amazon. But if the processing is done elsewhere, then where is the image? I am not confused. I have been writing code since the mid 70’s when cobal & fortran were all the rage.

    Now we can go back and forth about this all day long, I could download the plug-in and pick through the code, but I do have other things to do.

    In closing, I stated “cannot recommend”. This plug-in has a huge front end and is mainly for sales. For the everyday person that is looking for help with their WP installation, I would not recommend this plug-in. People are looking for a lightweight plug-in with a few switches and done.

    @ohgoodiee,

    I never said I didn’t like it ) On the contrary, I really appreciate your detailed opinion. It helps us make the plugin better. Thanks!

    cURL 7 errors do not always indicate an issue with the firewall. As I said before, Smush API is not located on AWS servers, we use DigitalOcean. Unfortunately, we had some downtime on our APIs, so you were probably just unlucky to do compression during this period.

    But if the processing is done elsewhere, then where is the image?

    The image is still on your server. The API only processes an image, we don’t store it. Smush processes millions of images each month, there’s no way we can store them, ever if we really wanted ??

    Best regards,
    Anton

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cannot rrecommend’ is closed to new replies.