You don’t need to bump the thread; we are aware of this.
Ok, sometimes it’s difficult for us to know that you know. On the substance, I’ve always considered picapp to be one of the many great features of wordpress, and I would like to keep it, as do many others I gather. So thanks in advance for helping us out.
From poking around over on the picapp website and reading their comments in variousl places, and doing some thinking about this issue, I’m convinced that using or keeping picapp is NOT in the best interest of anyone, especially the blogger. You all need to read this over at the picapp site carefully and let it sink in: http://picapp.zendesk.com/entries/261665-picapp-widget-is-taking-over-my-image-original-links .
Issues as I see them:
2. By picapp changing the URLs you set on your images (those that do not come from picapp) they are in essence implying ownership of those images. (The thinking: The image links to picapp, so obviously the image came from picapp).
From my experience, few people really understand copyright and fewer still would understand the implications of allowing picapp to hijack their image links.
I cannot believe that any lawyer would sign off on this scheme of theirs.
I did the same poking around and I’m so happy I never ever used one of their images.
” Picapp enable an automatic install to the self-hosted WordPress.org (not WordPress.com). The Picapp widget is currently not available for WordPress.com users.
WordPress.com demands a specific integration to enable 3rd party widgets, we are working on it, stay tuned on our blog for announcements regarding this issue.
Then there’s this > New! – Earn money with Picapp
Staff could implement the code on the back end (where it would be secure and not accessible to anyone to hack it), but everything I’m reading is like nails down a chalkboard.
YUP – I agree 100%
I’m still not comfortable with the fact we didn’t install ANY widget, and they lied and claimed we had and then fixed the problem behind the scenes. Believe me, I’m not mistaken: at no time did we install any Picapp widget on either of the blogs, and the behavior was evident on both of them. A cover-up does not bode well for the future. They should just come clean.
I contacted them (sent you a BCC rain) and it will be interesting to see if they reply.
I got to thinking, the first time I clicked on one of your non-picapp images, I ended up with a picapp URL in the browser address bar and thought perhaps I had clicked the wrong image, but I was sure I hadn’t. The second time I clicked it I got the right URL, the one you had assigned to the image.
I could have clicked on the wrong image, or perhaps I did not. I can’t be for sure, but from everything I’ve read, this whole things wreaks.
My personal guess is, they fixed this fast. I got the BCC: well said.
If I don’t get a reply, I’ll do it as an open letter on a high-profile blog somewhere.
If I currently HAD a high-profile blog, I’d offer to post it on mine.
Yeah, same here. I could always put it in my 0/10 PR design blog, but I am probably about the only one that would see it although even unfinished, it is getting some google hits and averaging about 20 page views per day.
@ raincoaster , @thesacredpath
Many Thanks for the feedback!
we just saw it in our own eyes on another blog ( we could never reproduce this error when we checked your blogs ) and think we have a lead on what happened.
Seems that due to the fact our picapp-images embed code include much of the functionality of the widget code , in some cases the following error happens : when a registered user , that has picapp images on it site , re-register to the new service , the new images she posted are being affected from the code that is part of the embed code in the post/s below (as long there are picapp images in the same page). this is why , we assume you saw non-picapp images getting the “lightbox effect” .
once we will confirm this today , we will change our activation flow so that bloggers who are not interested in the widget will be able to ‘let us know’.
we are indeed sorry for the inconvenience . we get much traction and feedback for the new product and are thankful for your comments who help us to improve.
Interesting, and thank you for the update.
The problem is, it affected even images that were uploaded before this past weekend, when the widget functionality was enabled. It affected images that were uploaded for the previous five days (those are the ones that were on the front page).
And I haven’t re-registered for the service, nor do I think the network admin did.
You can see the error in action right now on my blog http://ayyyy.com
Whatever WAS fixed is now unfixed.
Houston… we have a problem.
Two, really, since all these updates are going here instead of on http://raincoastermedia.com
How am I supposed to take over the world at this rate?
Seems picapp is trying to horn in on your action.
I’m sorry to keep you waiting for news while we looked into this on our side, but I have news now:
PicApp has decided to no longer support the original implementation of the PicApp shortocde for WordPress.com. We are disappointed by this news, but understand that PicApp is taking their business in a new direction. As of today, PicApp will no longer work on WordPress.com. Old usages of the shortcode will continue to function as long as PicApp will allow them to, but we do not plan to switch to the new method of image selection they are providing and any shortcodes entered into new posts will be automatically removed.
I know this news will be disappointing to some who were regular users of PicApp, but we believe this decision is best for WordPress.com as a community and as a platform.
The topic ‘Picapp.com’ is closed to new replies.