SocialEngine Announces Anti-Piracy Commitment! (blog.socialengine.com)
Unless it's Johnny Depp in Pirates of the Caribbean, piracy is just not a good thing. In an effort to deter piracy of our script and of expert products, we are stepping up our anti-piracy measures. 

We have added a site verification tool to aid in this effort. With this tool, people can check whether a site has a valid license and submit invalid sites to us. This tool gives no details to the person checking, other than a yes or no to the validation. This tool is the same thing other sites use to aid in anti-piracy efforts.

Should a site be submitted to us, we'll take it from there to check for a valid license and contact the site owner. We'll also be making an effort to let third party experts know of piracy of their products should we find it.

These efforts are necessary as piracy causes a loss of income and hence, a loss of money to go toward research and development. 

Thank you all for your help and contributions! 
    • 1
    Gabry I just tried my website to see if it has a valid license :D ... and is saying Nooo ...well if i input without www then i have a license .. maybe the team can work a little on this just not to receive false reports ... nice tool waiting for this for long time ... i know some devil's that should go to hell ...mu ha haaa !!!
      • 1
      Donna Did you check your license in your dashboard and make sure it's set up as your domain shows? :) Thank you for your feedback and glad you like the tool.
        • 1
        Gabry Yes i have check it ... the small problem is that if you input a domain with www it can give that doesn't have license and if you try without www then is ok ... i am afraid that some people will not be aware of this and they will report domains that actually have license.
          • 1
          Donna Yes, thank you for that info. I've added it as a bug to fix. Same for clients that didn't put a valid url such as http://socialengine.com and instead put just socialengine.com . It has to be a valid url even for our own license check internally in the dashboard. However, some don't seem to have done that. Not sure what issues that will cause later on with the certified marketplace and those without valid domains.
            • 1
            Donna I have a report in already for the www/non-www issue.

            As for your site, you should fix that issue as it will create SEO problems. Either use .htaccess rules to force www or non-www. Whichever one you want should be how it is always served on any browser.
            • 0 1 vote
            • 1
            gs Hmmm. Although FF/Chrome show mine as domain.com, IE includes http://www.

            In FF/Chrome, if I include the http://www. it accepts it then immediately removes it as the page loads.

            My guess is that the tool can be modifed for this, as well as http: and https: as some sites (such as mine) will be switching between those occasionally as testing is performed with the certificate.

            ==>"Not sure what issues that will cause later on with the certified marketplace and those without valid domains. "
            My concern here is what is defined as 'without valid domains', i.e. will many 'valid' actually be flagged as 'invalid' due to an improperly working/coded tool.
            • 0 1 vote
    • 1
    gs Thank you, thank you, thank you.

    Looking forward to even more being done (such as what's in other posts here and @github about Cores and licensing checks for 3rd-Party Devs).

    Question: Where do we input the URLs (prod + dev) for the tool to verify against? I ask because there may be many of us (me included) that haven't input this info somewhere (because I don't know where), and that may create a lot of incorrect 'No's. Site-ADMINs should be aware of how/where to do this to help prevent them from being tagged incorrectly, as well as preventing much wasted time researching 'pirate' sites that in reality are not illegal (they just haven't entered their URLs in the proper place).

    Again, thanks for this - a move in the right direction for all of us (SE, 3rd-Party Devs, and us valid ADMINs).
      • 1
      Donna Log in to your client dashboard and you'll see it where your license is. :) Let me know if you can't find it.
        • 1
        gs Thanks Donna.

        I'm glad I asked - mine was 'unknown'. At the time I purchased SE I wasn't sure which domain I was going to use.

        One more question: there's only 1 domain/URL allowed, so where do I enter the other one (i.e. I thought we had 1 license that covered for 1 production and 1 development installation/URL). Although both are currently simply folders beneath the same domain, I was planning on moving the Dev environment to dev.domain.com. How do I do this, or will the sub-domain not matter to your verification tool? I ask this because many 3rd-Party devs, they require I provide both URLs, even if one of them is a sub-domain.

        Thanks again.
          • 1
          Donna One more thing, make sure you put it as a proper url including the http:// or https:// .
          • 1
          Donna You are allowed a development site (closed for public access) on the same domain as your license. Either in a subdomain of it or subfolder. The tool probably won't work to validate a subdomain of the main domain but even if someone submitted it, we would see it's valid.
            • 1
            Donna A public site is an active community allowing registrations and performing as its own community.

            I suggest you password protect the directory. Your host can help with that if you don't know how. Once it is password protected, you only give the directory log in details to those you want to allow on it. :) Similar to my site, http://data66.info/dev5 . It also helps keep bots from slamming the server and taking resources and putting it in search results.
            • 0 1 vote
            • 1
            gs ==>"You are allowed a development site (closed for public access)..."
            Sorry for my ignorance, but how do I keep the dev 'closed for public access'.
            - Do you mean simply not allowing Users?
            - What about if there are several beta Users - are they considered 'public'?
            - How do I prevent search engines from including what's in development into their search database (ie so it doesn't display this content to the public)?

            Thanks.
            • 0 1 vote