Third Party Viewer Registry and PAR

So if you look back in this blogs history to February 25th,  http://blogs.modularsystems.sl/lgg/2010/02/25/ you  will see that I applied PAR to the registry a day before hand.

I had originally planned to keep all this correspondence about it private, but I have lost my patience with it and figured I would give you guys a little bit of insight on what is going on.

My first request was denied with this response. (on march 9th)

Thank you for your application to the viewer registry. We are unable to
proceed with the application for the following reasons:

1)    The feature list is not complete or is deliberately
obfuscating the inclusion of potentially malicious features.
2)    Grid Proxy is not part of the application, but Grid Proxy is
required to run the plug-ins.

If you wish to apply to have Grid Proxy listed in the registry, please
update this application with the necessary information or file a new one.

Which was absolute bull shit, and very insulting.  For the first point, the thought that I was obfuscating the inclusion of malicious features is absolutely absurd, it doesn’t even have a exporter!  So I figured that he meant that my “feature list” was not complete.  This point is absurd as well, as you can see Kirsten’s viewer (and many others) do not have a complete feature list.

So to play along and resolve this, I re-applied with a complete exhaustive list of every feature in there, as well as being much more clear and addressing the second point, how it is based on the code in grid proxy which is included in the program.

I figured they really didn’t bother to look and read anything more than the name.  And since it said “plugins” they just assumed it meant something useless that doesn’t even run without getting grid proxy or something.

So then I get to wait an entire month for this email response on April 12th

Thank you for your update to the viewer registry. As mentioned in our original communication, we are unable to proceed with the application for the PAR Plug-Ins, as the directory is intended for software which logs in to our servers, which the plug-ins on their own, do not.

If you wish to apply to have listed in the registry a software client that logs into our servers, please update this application with the necessary information.

Best Regards,
The Second Life Viewer Registry Team

Which seems to once again show an ignorant understand of what I submitted, regardless of the new information which I felt was inescapably clear. (Yes, PAR DOES log into second life)

So I was forced to consider that maybe they are not considering grid proxy applications as “viewers” and thus do not belong on the registry.  I responded back the same day explaining how it does truly log in, and that ignoring proxy programs will really leave a big loop hole in the registry, not to mention how it makes all my work look malicious if it isn’t listed.

Frustrated with the response time, I talked with Joe in one of the emerald meetings about this (I was so..wound up about this that I even let my voice crack for the recording), and he assured me that they have fixed the problem, and assigned a new team which meets and discusses things daily.

Today I gave up on waiting for a response, and went to talk with Joe again at his second brown bag concerning the policy.  His response was logical and made sense,  he clearly stated that proxy applications do belong on the registry, because they do log in, and that he does wish to encourage their development.

If only the other lindens I was corresponding with heard the word…

TL;DR;  I am completely disgusted with how my application has been handled thus far.

GPL Idiots and Arrogant Selfish Bastards

GPL is basically an open source license that generous coders can use to release all the information and time they took to make a project for free to anyone who sees the value in their knowledge.

It basically states that anyone can take and modify someone’s GPL code to do w/e the hell they want, so long as it stays GPL licensed. (aka, the modifiers must also give out the source code as well)

Now this is a wonderful little license. It lets generous coders be able to teach the world, while also insuring that this productive cycle continues as long as the project lasts. Basically all of my recent programming has been learned from open source code, and I, as well as millions of people are forever indebted to the programmers who released it.

You must realize that releasing a project of yours open source practically removes your ability to profit from it. The code and everything it takes to create an exact duplicate of what you have created, are now free to the world.

——————————————————————-

So here is the issue. People are selfish. Especially ignorant people who are so prideful of the modifications they have made, that they completely forget where 90% of the code they are using is from.

They slap the original creators in the face, and break the law and their own integrity when they take this code, and distribute it closed source.

So Neil, fuck you for doing this to my code. And to all other modified closed source “private” viewers based on LL’s code, you’re a disgrace to yourself.

Security and Privacy

When security removes privacy, your doing it wrong.

Furthermore, I hate people who abused privacy and ruined it for the rest of us.  If you are one of the people that have caused the stereotype “only bad people need privacy”, I really hope you suffer greatly for eternity.

“A thief always has the best lock” is total b.s. as well.  It does not take a thief to understand vulnerabilities and weaknesses in security.  Nor does it take a thief to have something meant only for themselves.

  • Calendar

    • August 2019
      M T W T F S S
      « May    
       1234
      567891011
      12131415161718
      19202122232425
      262728293031  
  • Search