Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 7 of 7
  1. #1
    Senior Coder Nightfire's Avatar
    Join Date
    Jun 2002
    Posts
    4,266
    Thanks
    6
    Thanked 48 Times in 48 Posts

    lisencing, copyrighting, etc gimme some legal jargon

    (as posted at the the-pit)

    is copyrighting or lisencing (sp?) a php package I've created worth it? I've created a journal (a very basic downloadable version of LiveJournal) and would like to either sell copies of it, like vbulletin do, or distribute it free, like phpmyadmin. What's the best way to prevent ppl from copying the source, editing random parts, like "Powered by (journal name) blinded.org.uk" to their own site...

    and please translate your legal jargon into nightfire text (baby language if possible, I'll prolly understand that, being the idiot I am )

  • #2
    Banned
    Join Date
    Mar 2003
    Posts
    224
    Thanks
    0
    Thanked 0 Times in 0 Posts
    two ways:

    1)you will have to make a server-side script that gives them a d/l whenever they get you the cash.

    2)hide behind the law and hope people listen

    for the thing about protecting the power by stuff. Your best luck is to hide it in deep code :-} And the law protects against that if u put it in end license agreement

  • #3
    Senior Coder
    Join Date
    Jul 2002
    Posts
    1,628
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Licensing(?)

    I'm not sure I understand what exactly you made?
    A PHP script? (I think that's what you mean so i'm going to rant.)

    Yes, add a big ol' copyright on the script too, this will stop some people.
    Should you try selling it?
    Of course, the least that can happen is you make some money .
    To add some incentive on actually buying it you can release a "demo" type, still fully functional, but lacking features you can implement in a paid version.

    Otherwise if it's going to be an easily edited file, then you just can't worry about it too much, it's out of your hands, all you can do is release it anyway.

    *shrug*

    PS: Nightfire I work at a law firm I hear legal jargon alot, it scares me too!
    Last edited by cg9com; 04-15-2003 at 06:17 AM.

    Moderator: General web building

    Get out from under them, resist and multiply.
    Get out from under precipice and see the sky.

  • #4
    Senior Coder
    Join Date
    Jun 2002
    Location
    near Oswestry
    Posts
    4,508
    Thanks
    0
    Thanked 0 Times in 0 Posts
    You basically can't; you just have to trust people and hope that enough are honest enough to pay you. Make sure that before downloading, users have to go through a terms of use page and click "I agree" - that's contractually strong enough that if someone does rip you off, you won't have to work hard to make a case.

    Works for me
    Last edited by brothercake; 04-15-2003 at 09:40 AM.
    "Why bother with accessibility? ... Because deep down you know that the web is attractive to people who aren't exactly like you." - Joe Clark

  • #5
    Regular Coder
    Join Date
    Nov 2002
    Location
    Bristol, UK
    Posts
    932
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Personally I prefer OpenSource code. All my code I try to release as OpenSource at some time or other. All I do is put a disclaimer and copyright notice in, and include a copy of the GPL.

    I have no idea what mattover-matter meant. He regularly seems to be off on a tangent... well, to my way of thinking. Maybe he's just trying to up his post count?

    ::] krycek [::
    ithium | SOAPI | SDP | PTPScript manual
    "ithium is a non-profit webhost, which is pretty much unique. The mission of ithium is to provide free hosting resources for worthwhile and needy non-profit projects, which otherwise may not be able to obtain such facilities. The money from commercial customers goes to maintain ithium's servers and further development."

  • #6
    Regular Coder
    Join Date
    Jun 2002
    Location
    UK
    Posts
    577
    Thanks
    0
    Thanked 0 Times in 0 Posts
    for catching them, you could sneak a little callback function as <img src passing the request_uri to a script at your site.

    also remember, most people who would use something like that will not know as much about scripting as you - if they did, they'd write their own, so hiding sneaky code bits isn't too tricky.

    Personally I'm more in favour of open-sourced development though do ask to be contacted when people use my distroed code for commercial sites.
    Ökii - formerly pootergeist
    teckis - take your time and it'll save you time.

  • #7
    Regular Coder
    Join Date
    Jul 2002
    Location
    This little Earth.
    Posts
    383
    Thanks
    0
    Thanked 0 Times in 0 Posts
    i think that, as Ökii says, whoever uses ur stuff will really need it and probably can't do it themselves, otherwise they wouldn't bother.
    but assuming the above, why opt for open source? because if whoever needs it can't be bothered with the source anyway, the source will be useless for them. it'll only be any use to code-literate snitchers, who'll edit it here and there and present it as their own work and try to make money out of it.
    eh well, that's what i think.
    but if you do go opensource, just add a Terms and Conditions of Use as bro said, and u're probably as safe as you can get. some people actually read those terms. like me.

    and as someone said from the pit:
    "If you're really concerned, print off a copy with the date on and post it to your lawyer (but tell him not to open it!) - that way you have proof that you wrote it before a certain date."
    i say ditto.

    Originally posted by krycek
    I have no idea what mattover-matter meant. He regularly seems to be off on a tangent... well, to my way of thinking. Maybe he's just trying to up his post count?
    ::] krycek [::
    hardy har har!!
    Last edited by ASAAKI; 04-15-2003 at 11:56 PM.
    'If you don't stand for something, you'll fall for anything.'


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •