Patented Technology - No need for encryption?

I was just wondering seeing as you have now applied for a patent on your SEO technology whether that means that you will still need to encode the files if you successfully receive the patent? Or is there something else that is stopping you from releasing your code?

I'd like to see that but some how, I don't suppose it will happen due to technical reasons.

Originally Posted by Alfarin

I'd like to see that but some how, I don't suppose it will happen due to technical reasons.

I don't see what technical reasoms there could be. Unless you are referring to releasing the code to license holders?

Patenting, copyright, and encryption are all separate forums of security. Having a patent in place or copyright protection, does not necessarily mean that code should be released open source.

Originally Posted by Joe Ward

Patenting, copyright, and encryption are all separate forums of security. Having a patent in place or copyright protection, does not necessarily mean that code should be released open source.

I understand that, but this would mean that vBSEO has more protection than say IPB or vB yet it still remains closed source. I also understand that vBSEO is not as large as those two and any pirating would hurt your business more, but I don't really see how encryption helps with that.

Anyway fair enough, I guess vBSEO is always going to be closed source which really is a shame.

Originally Posted by Cromulent

which really is a shame.

not really

doesn't the encrypting help with performance too ?

You can see all the big admins that are using vbseo, if they aren't worried about the "hidden code" on their big sites, don't you think you'll be okay on your site ?

It just takes a little trust I guess..

Originally Posted by Loco

not really

doesn't the encrypting help with performance too ?

You can see all the big admins that are using vbseo, if they aren't worried about the "hidden code" on their big sites, don't you think you'll be okay on your site ?

It just takes a little trust I guess..

Don't get me wrong, it's not a problem as such. But it is always nice to be able to customise the software that you run on your forum. The fact that it is encrypted does not worry me (hence the fact I purchased it) I just like having the option of modifying it.

If you ever allow customizing of the code, then the support becomes impossible for those who have customized, and the bug tracking becomes a nightmare.

I would rather it just remain the way it is.

I believe the policy like the one employed by Jelsoft would be advantages for all parties.

Closed source is not the same as readable. vBulletin is readable, but closed source.

I guess I'm confused as to your goal in seeing the code with the terminology you are throwing around.

What is the goal?

Originally Posted by noppid

Closed source is not the same as readable. vBulletin is readable, but closed source.

I guess I'm confused as to your goal in seeing the code with the terminology you are throwing around.

What is the goal?

The goal is was trying to get across was simply to have human readable source code with the same license restrictions as we have now.

I think the goal is as he said have the ability to modify it if he wanted to.

Having the source readable also allows for plugins to be developed easier by indivuduals.


Adopting the vbulletin policy of allowing plugins but making it absolutely clear they are not supported (in fact modified boards are not supported in general) I think would help with the "nightmare" part mentioned above.