Messages - drapps [ switch to compact view ]

Pages: prev • 1 [2] 3 4 5 6 • next
6
General Software Discussion / Re: What the hell is OpenCandy?
« on: September 30, 2009, 12:09 PM »
Scancode, et al,

Hey y'all (yeah I said "y'all"), hope you're all having a great Wednesday!

DC<>Users is what makes DC great!

I agree, no question. :)

Regarding the FAQ, Whoops. FIXED!  I added instructions for those publishers that currently don't use an OpenCandy subkey. See http://www.opencandy.com/faqs/#opencandy-removing-registry-entries Thanks for pointing it out and I appreciate the time you took to read through the faqs. I'm a big fan of a "second set of eyes" especially when they come from the outside looking in.

I have more great news...

Regarding changing OC registry entry location to an OC subkey as a requirement, it was in the pipeline but I wasn't sure we would be able to get it into the version 1.3.1 update (which is rolling out shortly with the NSIS bugfix). But... we did! As of v1.3.1, all ALL OpenCandy publishers are REQUIRED put OpenCandy related registry entries inside an OpenCandy subkey within the publisher's registry key.

Take good care everyone. :)

7
General Software Discussion / Re: What the hell is OpenCandy?
« on: September 24, 2009, 05:16 PM »
Hi Everyone,

I’m back. Things have been hectic. Of course moving took much longer than I thought; I didn’t realize how hard it would be with the baby and doing 95% of the move myself!

Anyway…

Scancode,

Regarding the registry entries:

I misspoke (miswrote?) and should clarify that currently, per our Publisher’s Kit Integration Guide, it is only a requirement that OpenCandy related registry keys be stored within the publisher’s registry key. We don’t specifically require that they be within an OpenCandy subkey, though most publishers (MediaCoder excluded, obviously  :) ) do put them within an OpenCandy subkey.

OpenCandy files in temp directory:

I/we owe you a big THANKS! You’ve actually discovered a bug with v1.3 of our plug-in that only affects NSIS based installers. Only the dll (OCSetupHlp.dll) should be in a user’s temp directory (when it’s unpacked by the installer) and it should be removed once the publisher’s installation is completed. This doesn’t change what I said above about when a recommendation is accepted. When that happens an OpenCandy folder containing the dll (OCSetupHlp.dll) and the text file (OpenCandy_Why_Is_This_Here.txt) are created within the publisher’s installation directory to facilitate the download and installation of the recommended software and once finished, the folder and files are automatically removed (unless one of those things listed in the OpenCandy_Why_Is_This_Here.txt happens: power goes out, etc... ).

We’re in the process of wrapping up version 1.3.1 which rectifies the issue. It'll take a bit before all our publishers have updated their builds. This bug does not affect OpenCandy publishers with Inno-based installers.

Oh yeah, the FAQs are up (http://opencandy.com/faqs)!

Be well everyone  :)

8
General Software Discussion / Re: What the hell is OpenCandy?
« on: September 13, 2009, 07:42 PM »
Hi scancode (or Scancode) and DC'ers!

Hope all of you are well. I'm in the middle of moving (and re-setting up my lab) right now but I'll be back tomorrow to post more information. I figured I could throw a couple of things out here now.

The FAQs I promised are finally done and are going to be posted tomorrow (what coincidence!). The FAQs include information about the registry entries. Quickly though, even if you don't accept a recommendation, bookkeeping information about the publisher's software you did install (in your case Scancode, MediaCoder) are created within the publisher's registry key inside an OpenCandy key (so in this case it should be HKLM\Software\MediaCoder\OpenCandy\) as well as a non-reversible identifier created via a random number generated which helps us prevent fraud/gaming and also lowers the likelihood that a declined recommendation will be shown again in the future.

Something big I want to announce... We've updated our plug-in (which all publishers are in the process of updating to/re-integrating), to version 1.3, so that OpenCandy provided files are only TEMPORARILY copied to the computer IF a recommendation is accepted and then they are deleted after the recommended software is downloaded and installed. So no more OpenCandy files will be left behind anymore! Which also means (by the very nature of not leaving OCSetupHlp.dll behind) that we have eliminated uninstall tracking for our publishers. It could take up to 4-6 weeks for everyone who participates as a publisher to update their installers with the new plug-in though (based on their release cycles, etc).

Thanks again everyone! Be well. :)




9
General Software Discussion / Re: What the hell is OpenCandy?
« on: May 30, 2009, 04:24 PM »
Fine, mouser, I'll quit.

I am referring to reply 104 that has not been done.
There is no eula for open source posted with an install of these programs.
-cmpm (May 30, 2009, 09:47 AM)

As stated in post #104... ALL publishers that were NOT ALREADY disclosing OpenCandy in their EULA have been notified that they need to do so. I expect it may take another couple of weeks or so for them to update their builds. We're on it! :)

In addition, no NEW publishers have been allowed to launch "powered by OpenCandy" installers without disclosing so in their EULA.

Thanks :)

Dr. Apps

10
General Software Discussion / Re: What the hell is OpenCandy?
« on: May 29, 2009, 03:53 PM »
OK -- here's the deal...

If you're familiar with the GOTD site (giveawayoftheday.com), today (5/29) they're offering a copy of StarBurn. StarBurn offers in an very upfront, opt-in/out way to add a toolbar etc -- check out the high % of negative comments & comment ratings, mainly because the add-on's even offered.
-mikiem (May 29, 2009, 03:19 PM)

It's funny that you posted this because this morning I was scrambling to find out what "Skymediapack" was and whether it was a required component of Starburn. I didn't think it was because I've installed Starburn many times before and never noticed it.

I DON'T think Starburn was "very upfront" about Skymediapack at all. There is ZERO explanation in the Starburn installer of what Skymediapack is, what it does (like change your home page), whether it is optional AND to top it off... it's pre-checked to install (aka opt-out). So, many people are probably installing Skymediapack by accident which is why they're mad. I would be too. I (obviously) didn't install it, but some people in the GiveAwayoftheDay comments are saying that Skymediapack doesn't have an uninstall entry.

The way I look at it, this is exactly the reason why OpenCandy exists. OpenCandy recommendations are crystal-clear that they are optional, there's useful information about what a recommended application (or service) does (app highlights), and all OpenCandy recommendations are OPT-IN.

Dr. Apps

EDITED: forgot the word 'application' and added '(or service)' in the sentence "...about what a recommended does (app highlights)..."

Pages: prev • 1 [2] 3 4 5 6 • next
Go to full version