We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Content ownership, copyright and security

Home Forums General Questions Content ownership, copyright and security

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #46225
    xeon
    Customer

    Hi there,
    For those of you using Verge3d or any other WebGL solution commercially and have had to integrate your applications with your client’s IT departments, wrangled with the client’s legal teams, or had to prove the security of content or data. How are these battles going?

    Xeon
    Route 66 Digital
    Interactive Solutions

    #46292
    Crunch
    Customer

    Hey Xeon, judging by the response ( or lack thereof), thinking you might be relatively isolated in your struggle for “integration”. Can I asked more (in general terms of course) about what you are trying to integrate?

    The way I see it, a “verge app” is just a webpage (no offense to the Soft9soft team!).

    (for the record – I a NOT referring to a newer Verge features that allows the code to be complied into an exe as Electron provides)

    A webpage can be comprised of any combo of HTML, CSS, Javascript or WebGL.

    Provided your “page” isn’t asking for, nor storing any personal user data, what is the hurdle?

    Maybe you just are not just explaining it right to the client?

    WebGL, as magical as it is, is a web standard – just like HTML. There are no additional programs to download (cough cough… like Macromedia FLASH) to execute.

    So with any concerns about “security”, can’t you just refer them to the browser company? (ie, Google, Firefox, Apple)?

    #46304
    xeon
    Customer

    Integration as in software we aren’t facing any problems. Integrating with client IT teams is a mixed bag. When we take on projects we are either a sole provider/developer and there is no problem or we are asked to work as a team with existing client IT. It’s in these situations where the battles begin. The most frequent is security. Webgl is still heavily frowned upon on where security is a concern. In most cases where we fight the fight the concern was based on out of date information. But these battles can also weaken relationships with clients and can put us into adversarial situations we would rather avoid, not to mention the project delays they can cause and $$$$$$ in legal fees to overcome and satisfy all parties.

    We are also finding these issues are more prevalent in the US.

    Another issue that keeps popping up is level of detail in the gltf file. Since the file is exposed clients are afraid the models will be used without there permission. This possible of course, but it’s a legal issue of content rights. We as a developer have to acknowledge their models are exposed much like a photo. This adds for some interesting conversations about how much detail to allow and parts that should not be allowed.

    End user Privacy is always a concern. There are some easy ways to solve it. But when personal information does have to flow into or out of the webgl app we run into a higher level of scrutiny with code reviews, additional security audits… etc.

    So for those out there with similar issues … I am curious how your team is handling these challenges.

    Xeon
    Route 66 Digital
    Interactive Solutions

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.