Update: I did eventually find the terms of service. You have to be logged in to getpersonas.com in order to see them. Also, the DMCA information is linked at the bottom of getpersonas.com as “Legal Notices”.

Although I couldn’t find the terms of service for submitting a Persona to getpersonas.com, the FAQs indicates that you must agree to the following:

1. You either own all the elements of your design OR you are authorized worldwide to reproduce and distribute them (and allow others to do so) by the owner or the law.
2. Your design does not contain provocative, offensive, or sexual content (i.e., it is G or PG-rated).
3. Your design does not include identifiable elements of any non-celebrity person(s) other than yourself or individuals who have given you permission to do so.
4. Your design does not depict violence or Nazi imagery, nor is it discriminatory or hateful.
5. Your design does not relate to gambling.
6. Your design does not violate any applicable law or regulation or the rights of any person or entity.

It’s pretty clear from through the Personas inventory, that a lot of people are simply ignoring these restrictions, and Mozilla doesn’t have the volunteer capacity to enforce them.

So if you discover an image that is a violation of your trademark or copyright, you must submit a DMCA takedown notice in order to get it removed. I was unable to find this information on getpersonas.com, but I did find it on the main Mozilla website, so I wanted to share it with anyone who needs it.

Be aware, though, that based on the information at the end of that section, Mozilla might post your DMCA request to the Chilling Effects website.

My latest CCK Wizard is now officially available on AMO.

As noted in previous posts, this version primarily focused on coexistence of multiple CCKs, as well as updating the proxy configuration to match Firefox 3.6. I also added some usability enhancements, including the ability to open an existing configuration.

The most interesting feature I brought back is the ability to hide a CCK so that it can’t be uninstalled. Here’s some background.

With Firefox 3.5 and previous, there were two options you could add to your extension that only affected it if it was installed in the same directory as the EXE – hidden and locked. Locked preventing the extension from being uninstalled (but it could still be disabled – so kind of useless) and hidden preventing it from being seen at all (which of course prevented it from being disabled or locked). Mozilla removed hidden for Firefox 3.6 but left locked behind. What I’ve done is made it so that if you specify locked, it means hidden. This was the easiest way to make this work and has the nice side effect that if in your deployment, you need to hide other extensions, just mark them as locked.

Support for the CCK Wizard is provided through Google Code.

Enjoy!

Do you need to do even more customization of Firefox for your organization? That’s what we do. Contact Kaply Consulting.