WordPress.org

Support

Support » Reviews » Jetpack by WordPress.com » Untested outlet for abuse

Untested outlet for abuse

  • annmariedwyer

    @annmariedwyer

    1. Integration with WP.com. No reason for sites built off Automattic’s personal playground.

    2. Sends information to WP.com without “connection”. e.g. My feeds are showing up in WP reader. I never wanted this back. Ever.

    3. Features turned off onsite are available to WP.com users, who mistakenly believe you can see them “liking” your posts.

    4. Turns itself on with no option to disconnect features if you do not like them

    5. Malfunctions often rendering ALL links on the page (including those generated by outside API) to the base URL. This includes header image. The only way off of pages is to type in a URL to another page.

    6. Each update requires three or more “bug fixes”. Beta testing is limited to users who are on .wordpress.com; Alternatively, only Automattic employees are testing it with no idea what the .org base truly does when it is not hobbled by Automattic only offerings.

    7. Privacy issues with statistics. No information available about what will be shared and already is being shared with WP.com.

    8. Statistics do not recognize such referrers as Google+. Reporting erroneous at best. No true representation of traffic. Often statistics are belied. e.g. Some days there are more comments from users than JetPack reports page views.

    9. Superfluous CSS.

    10. Logs out user with every change.

    I could go on, but I believe it pointless. I doubt anyone reads these.

Viewing 15 replies - 1 through 15 (of 18 total)
  • ChrisSale

    @chrissale

    I read it. Thank you.

    afeique

    @afeique

    Totally read it, thanks. Maybe next time you should go on ;o

    HayManMarc

    @haymanmarc

    I read it , too. Thanks.

    gregory.hk

    @gregoryhk

    a detailed explanation. thank you. very useful.

    cindy123

    @cindy123

    The most useful review! You should have gone on.

    I read it and now, thanks to your time and effort, will save my time and patience by avoiding this plugin like the plague. Thank you for your service. Please accept my gentle pat on the back.

    Thanks for the heads up, serious enquirers read this stuff, you know! My question is where are the Devs. responses?? All I see is People agreeing.

    Devs, please comment, some of these criticisms are completely valid and need addressing.

    Thank-you for a great all in one plugin.

    what they said… Please feel free to rant on and on. It was helpful

    useful info…was going to try it out. got saved in last minute

    thanks so much… was on my way of installing it to all my clients – thanks god i didn’t…

    Chris

    @marketeerland

    You made the difference for me personally… I was researching whether or not I should install this. Not.
    Thanks!!

    3. Features turned off onsite are available to WP.com users, who mistakenly believe you can see them “liking” your posts.

    If you’re correct, this sounds like a bug. I hope you reported it.

    4. Turns itself on

    Jetpack is only activated when you choose to activate it after installation. Other than that I don’t know what you mean.

    with no option to disconnect features if you do not like them

    You can deactivate each unwanted module easily. You need to click on the Learn More button on the module card, and a Deactivate button will appear next to it. This is partly why I’ve only given the plugin a 4-star rating. IMO Jetpack should have all modules disabled out of the box. I don’t like Automattic making assumptions about what users will find useful by default. but this is a minor complaint since users will generally be spending some time configuring the features they want anyway.

    5. Malfunctions often rendering ALL links on the page (including those generated by outside API) to the base URL. This includes header image. The only way off of pages is to type in a URL to another page.

    I haven’t seen this happen, but I’ll check it out. Have you tried to get to the bottom of it in the support forums before posting this review?

    7. Privacy issues with statistics. No information available about what will be shared and already is being shared with WP.com.

    8. Statistics do not recognize such referrers as Google+. Reporting erroneous at best. No true representation of traffic. Often statistics are belied. e.g. Some days there are more comments from users than JetPack reports page views.

    You can easily disable the stats module if it bothers you that much.

    No plugin is perfect, including Jetpack, but I don’t feel Jetpack deserved a 1-star rating.

    Plugin Author Jeremy Herve

    @jeherve

    Thanks for this review.

    I think you may be working from some misinformation or assumptions that aren’t correct, so I’ve gathered some information about the issues you experienced:

    2. Sends information to WP.com without “connection”. e.g. My feeds are showing up in WP reader. I never wanted this back. Ever.

    The WordPress.com reader is a feed reader, like Google Reader. Feed readers can display any blog with a public RSS feed, whether it’s WordPress or not. It has nothing to do with Jetpack.

    4. Turns itself on with no option to disconnect features if you do not like them

    To turn off a Jetpack module, click Learn More, then click Deactivate. Also, note that we know that it’s counterintuitive and have plans to make it easier based on user feedback.

    5. Malfunctions often rendering ALL links on the page (including those generated by outside API) to the base URL. This includes header image. The only way off of pages is to type in a URL to another page.

    I can’t reproduce this. If you post about it in the Jetpack forums though, we will definitely help you look into it. I’m not sure it’s related to Jetpack, but I can’t tell without more information.

    Each update requires three or more “bug fixes”. Beta testing is limited to users who are on .wordpress.com

    Beta testing is open to anyone. If you are interested in doing beta testing for Jetpack, we’d love that and I’ll help you get started.

    9. Superfluous CSS.

    CSS you see as superfluous might actually be needed for a reason you haven’t considered. If you post specifics about which CSS you think is superfluous and why in the support forum, we will check it out.

    10. Logs out user with every change.

    I can’t reproduce this. If you post some details about how to trigger this issue in the Jetpack support forum, we will check it out.

    Thanks again.

    Thanks Jeremy for responding to this report. Seems like a reasonable response. I guess making the UI more transparent as you suggest will allay many criticisms, as it appears that some of the problems raised were due to misunderstanding about how to configure jetpack.

    Thank-you

    @annmariedwyer: Great review! +100

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Untested outlet for abuse’ is closed to new replies.
Skip to toolbar