Hi MerlinG

This is Christopher, head of Customer Outreach here at Pogoplug.

There wasn't anything necessarily wrong with the manner in which shares worked before.
In fact, we made it easier for shared users to View and Download shares with public shares.

Having done this and based on feedback from our users, it made sense to make all collaboration shares password protected.

Kindest Regards,
Christopher Louie
on behalf of the Pogoplug Team

MerlinG said: No you broke it. Don't try to spin this, because I am not buying your lame explanations. Basically, you are now trying to collect email addresses and build your user base. That is very transparently obvious. I guarantee you that the majority of your users did not want to require their recipients to create and account and log in just to access a shared file. Yousendit does not require that. And, having public files is not the same concept as sharing a folder with one person and not requiring them to login to get it. This aint facebook. You are a company without a clear identity, and your interface simply sucks. First the mantra was "who needs the cloud" and "be your own cloud". Now you discontinue most of your devices and are trying to push the cloud on everyone. You ignore common UI conventions and completely re-invented the wheel. When the wheel was not broken.

Hi MerlinG

Thanks for the update.

View/Download shares you previously created are still valid for the sharee. Unless you required password authentication these share links expired after two weeks by default. If you required password authentication for previously created shares, these migrated seamlessly to 'Collaboration' folders.

If you want to share using email, we made it easier to share a public link.

We brought Pogoplug Cloud front and center because we're proud of it and now users can take advantage of the Pogoplug service using hosted storage or local storage via one our devices or a Pogoplug enabled computer. We do want additonal Pogoplug users and customers of Pogoplug and Pogoplug Cloud is just one great way to do this.

Hardware is just as important to us as it has been in the past. Rest assured we continue to develop, release and support hardware. While I can't reveal anything just yet, please stay tuned for new hardware announcements.

Kindest Regards,

Christopher Louie

on behalf of the Pogoplug Team

Hi,
I like the new technique because it has made easier for shared users to View and Download shares with public shares 

*** Deleted By Moderator ***

Matt,

My post discussed the removal of embed links and the missing share e-mail adresses. But if you think the comment here about removal of embed links is all that anyone needs to see, I guess as a moderator or editor, you can do what they do in support, just ignore the problems, or respond with "we can't reproduce the problem" or "solved" with no solution.

Sorry to have offended your sense of relevance.

Dr. Towle

PS: By ignoring problems here, where they are reported and can be addressed, the problems will end up being broadcast to potential pogoplug users and do little to help promote the product or the quality of support provided. That would be a shame, since it has some good features, but as the chinese proverb says, one bad ruins a thousand goods. A really smart company would solve the problems as they are reported, and not stall and delay solutions until small problems become thoroughly annoying,

It might not seem relevant, or on point, but there is a bigger picture here about changes made that impact the usefulness of pogoplug. From that point of view, my comment was very relevant. as it addresses a very useful way to share something without involving pogoplug except in the html code.

And I wanted to restate some of the problems that have been introduced by this new "collaboration" scheme, something that was also mentioned in an earlier post here.

Whatever, as they say, if Cloud engines wants people to report problems, they need a better way. I've tried the direct reporting and it rarely works, as the issues are immediately marked as "closed" and of course nobody else can read my bug reports so we may all have the same issues with Cloud engines, but cannot determine that with the support system.

These public posts provide a way to share common problems, and hopefully will get more attention when several users all realize that they have the same issues.

Is that relevant to fixing problems? What's your solution to fixing problems?