ello, friends.In the meantime, there's coverage of Steelhead Bay by the SL Newser, and by New World Notes. I'm proud that Gearhaven has their small mooring station there to support the cause. May Steelhead Bay thrive.
At 8:00 am on Monday, May 15, 2017, I received a Cease and Desist letter from legal counsel representing [Exxxxx Dxxxxxxxxxx and Akimeta Ltd. This letter demands that I cease all use of Ozimals intellectual property.
I don’t personally agree with this claim, but I do not have the means to fight this in court, therefore I have no choice but to comply.
As of the morning of Wednesday, May 17, 2017, my products and their associated games will cease to function.
This means:
All databases supporting the bunnies and Pufflings will be offline.
Support, both inworld and through the ticket portal, will cease.
All Ozimals inworld groups will be closed.
Pufflings will cease to function.
Any bunny who is Everlasting will continue to function, as he or she does now: without cost.
Any bunny who is not Everlasting will be unable to eat and will hibernate within 72 hours.
This really [fxxking] sucks, and I’m sorry. It was never my intention for the time we’ve all spent with the bunnies and the Pufflings to end like this. I want to thank you from the bottom of my heart for all of the support this community has given me over the last seven years. I wish there was more I could say.
Malkavyn Eldritch
Showing posts with label copyright. Show all posts
Showing posts with label copyright. Show all posts
16 May, 2017
tombstone hand and a graveyard mine
Well, this is upsetting.
21 July, 2014
he'd find a powersource and then he'd pick what plugs to pull
If you don't mind the fact that the maker is pretty much ripping off everyone on and off the grid with copyright-infringing avatars...then you can take advantage of a 90% off sale on Marketplace. You know, if you don't care that practically everything you see there was likely first built in 2009 and hasn't been updated...or that much of it is direct theft of other game developers' intellectual property. But hey. Go wild if you want. I'm not your mom.
Also, apparently Thor's female now. (Comics-verse, not movieverse, it should be noted. Still, entertaining.)
More Hair Fair coverage! (Part the first, part the second, part the third, and part the fourth, seen previously.)
We start with Alli&Ali's "Andrew" hair. It's not the best front shot, because it nearly makes it look like it has a heightened, lofty crown, but in actuality, it's a tousled razor bob, that seems--at least from showing it on me--to be pretty reasonably unisex. I'm showing in in "Hair 4" (a dark brown) and "Hair 7" (a copper-red), respectively.
Next up, the "Barbarella", which I wanted to like with every fiber of my being. (Because...Barbarella, come on now.) It's an iconic hairstyle for an iconic character, which Alli&Ali...utterly fails to pull off.
In the banner shots, I'm showing off "Hair 10" (the pale blonde) and "Hair 6" (a rich burgundy). But it really doesn't matter what color we're discussing, as shown below:
This points out the flaws seen in all shades of this style by concentrating on the shades "Hair 3" and "Hair 6", I believe. There are more than a few issues, but I'm specifically discussing the alpha issues--which are prominent and annoying--and the misaligned strands (specifically shown here down the back, but there's a few on the bouffant crown, too). It's depressing to think that in 2014, there's a designer who's still putting out styles that look like they were made in 2008.
Then there's "Fiona", which I'm only showing off in "Hair 11", because it was the only hair I actually had to adjust and resize out of the box. It also suffers from alpha issues, but not as much as "Barbarella".
Finally, there's "Gaby", and...the less said about it, the better. I will say one thing: I really wish they'd taken the trouble to add better texturing, on the hair rollers if nowhere else.
All in all, these styles had promise and creativity behind them, but...outside of the first, spunky unisex "Andrew", they're not exactly hits out of the park. Which is sad, because with a little updating, some mesh templates here and there, even, they could meld the old and the new and turn out some really innovative things, I think. Things that wouldn't look like the standard center-part long-mesh style we're seeing everywhere these days.
You can find Alli&Ali on the Brunette sim.
And the usual report of what I'm wearing, now from high above the Sanguinarius Community Center:
Eyes: Poetic Colors gives out a LOT of freebies, but Lano Ling also makes really good eyes for sale. These happen to be the "autumn moon" freebie, bright sclera version, but I do have more than a few PC eyes that I've bought. Really excellent shading, and incredible color variations.
Skin: After Curio returned to the grid, Ms. Phoenix sent out the "Party Girl Megapack" to everyone in her group. This is the "Moonbeam" (light tone) skin, "Potion 1" variation.
Outfit: The "Demon" asymmetric strapless number from FashionNatic for the dress (and I honestly can't remember if it was a freebie, or if I bought it on the Marketplace), then SN@TCH's "Aspen" knit stockings in Red (not shown), and DV8's "Eternal Love" boots in Red (and DV8 is unlinked, because they closed again) (also not shown).
Tattoos: Lipstick is from The Sugar Garden; it's the "Bitten" Dolly Lips in Dark. And the chest tattoo is from REDRUM, it's the "Sacred Heart" tattoo.
Still using Nam's Optimal Skin 2 for the Windlight setting, and I've also pushed up my graphics a little to include basic shaders, atmospheric shaders, and the Advanced Lighting Model setting. (It's important to note that even under the relatively stripped-down Singularity viewer, my current drug of choice, that I still can't move with Advanced Lighting on, because of the induced shading, I think.) Anyway, there you go--these shots are not my norm of point-and-shoot standard-midday lack-of-Windlight pics. More to come!
Also, apparently Thor's female now. (Comics-verse, not movieverse, it should be noted. Still, entertaining.)
More Hair Fair coverage! (Part the first, part the second, part the third, and part the fourth, seen previously.)
 |
| (from the Hair Fair album; a perky, tousled style called "Andrew" that's suitable for either sex) |
We start with Alli&Ali's "Andrew" hair. It's not the best front shot, because it nearly makes it look like it has a heightened, lofty crown, but in actuality, it's a tousled razor bob, that seems--at least from showing it on me--to be pretty reasonably unisex. I'm showing in in "Hair 4" (a dark brown) and "Hair 7" (a copper-red), respectively.
 |
| (from the Hair Fair album; the sadly executed "Barbarella") |
Next up, the "Barbarella", which I wanted to like with every fiber of my being. (Because...Barbarella, come on now.) It's an iconic hairstyle for an iconic character, which Alli&Ali...utterly fails to pull off.
In the banner shots, I'm showing off "Hair 10" (the pale blonde) and "Hair 6" (a rich burgundy). But it really doesn't matter what color we're discussing, as shown below:
 |
| (from the Hair Fair album; the flaws in "Barbarella") |
This points out the flaws seen in all shades of this style by concentrating on the shades "Hair 3" and "Hair 6", I believe. There are more than a few issues, but I'm specifically discussing the alpha issues--which are prominent and annoying--and the misaligned strands (specifically shown here down the back, but there's a few on the bouffant crown, too). It's depressing to think that in 2014, there's a designer who's still putting out styles that look like they were made in 2008.
 |
| (from the Hair Fair album; "Fiona" and its frizzy flaws) |
Then there's "Fiona", which I'm only showing off in "Hair 11", because it was the only hair I actually had to adjust and resize out of the box. It also suffers from alpha issues, but not as much as "Barbarella".
 |
| (from the Hair Fair album; the "Gaby" style for Hair Fair 2014) |
Finally, there's "Gaby", and...the less said about it, the better. I will say one thing: I really wish they'd taken the trouble to add better texturing, on the hair rollers if nowhere else.
All in all, these styles had promise and creativity behind them, but...outside of the first, spunky unisex "Andrew", they're not exactly hits out of the park. Which is sad, because with a little updating, some mesh templates here and there, even, they could meld the old and the new and turn out some really innovative things, I think. Things that wouldn't look like the standard center-part long-mesh style we're seeing everywhere these days.
You can find Alli&Ali on the Brunette sim.
And the usual report of what I'm wearing, now from high above the Sanguinarius Community Center:
Eyes: Poetic Colors gives out a LOT of freebies, but Lano Ling also makes really good eyes for sale. These happen to be the "autumn moon" freebie, bright sclera version, but I do have more than a few PC eyes that I've bought. Really excellent shading, and incredible color variations.
Skin: After Curio returned to the grid, Ms. Phoenix sent out the "Party Girl Megapack" to everyone in her group. This is the "Moonbeam" (light tone) skin, "Potion 1" variation.
Outfit: The "Demon" asymmetric strapless number from FashionNatic for the dress (and I honestly can't remember if it was a freebie, or if I bought it on the Marketplace), then SN@TCH's "Aspen" knit stockings in Red (not shown), and DV8's "Eternal Love" boots in Red (and DV8 is unlinked, because they closed again) (also not shown).
Tattoos: Lipstick is from The Sugar Garden; it's the "Bitten" Dolly Lips in Dark. And the chest tattoo is from REDRUM, it's the "Sacred Heart" tattoo.
Still using Nam's Optimal Skin 2 for the Windlight setting, and I've also pushed up my graphics a little to include basic shaders, atmospheric shaders, and the Advanced Lighting Model setting. (It's important to note that even under the relatively stripped-down Singularity viewer, my current drug of choice, that I still can't move with Advanced Lighting on, because of the induced shading, I think.) Anyway, there you go--these shots are not my norm of point-and-shoot standard-midday lack-of-Windlight pics. More to come!
10 June, 2013
let me open my teeth and cradle you there
RL Dolcett, anyone? Ergh.
Back on the 3rd, I spoke on a viewer controversy that's been brewing for some time. Earlier (as in, I past-dated it so it could be boring back in January), I linked Kirsten's initial EULA and credits in full. This had to be agreed to before I even downloaded the viewer. The CoolVL viewer was just a simple install, nothing overly complicated about it.
Then I opened each viewer in turn, on the grid.
The first thing "Blackbird" told me was that my outfit didn't exist. Which was strange to me, as I could clearly see my outfit, and it was the same one I'd been wearing the last time I logged in with Singularity. Odd.
Then I went looking for the 'About' tab. It's not under Help, first of all; it's under the 'S19' tab itself:
Henri is correct, no specific authors are listed other than KirstenLee Cinquetti under this tab.
How'ver, under the 'Licenses & Copyrights' tab, there's this. Which looks fairly official with all bases covered, to me. Unless Henri is claiming that he, himself, coded his viewer entirely by hand, with no help from any other code source, what Kirsten seems to have done is credit the original (hence, first) coder for purposes of licensing--then left off anyone else who might have had a hand in redoing the code, either in sections or in whole.
There's a further point at the bottom of that tab, to see "licenses.txt" for more information, but I can't seem to find that anywhere within the program files.
I had no warning that this viewer was infested with malware, adware or a virus, but I don't use the same program Henri uses to detect those sorts of things.
I then popped open the latest CoolVL build. I got a EULA agreement there, too:
Simple, fairly succinct, and to the point. Also, no virus warning either when I installed it, or when I ran it (not that I expected to see one).
Then I went looking for the 'About' feature for CoolVL. I begin to see his point, because whereas the Kirsten viewer just credits KirstenLee Cinquetti for everything, Henri Beauchamp credits anyone who might have stared at the code for five minutes:
And the CoolVL 'Licenses & Copyrights' tab mimics the S19 viewer's list fairly exactly, which tells me that's just a standard legal block all viewers are supposed to list.
Then for some reason, I turned green. At least I go with the furniture? Still don't know why that happened (I didn't change eyes, outfit, hair, or skins while I was running these comparisons), but I took it as my cue to get off the grid.
Once off the grid, I searched through the CoolVL viewer files, and did track down the 'license.txt' file, with absolutely no difficulty. (The full text of that file can be read here.) And that has about the same amount of info that KirstenLee's EULA agreement had, only better organized.
So...and always keeping in mind I know next to nothing about viewer coding...I'd say, just in my opinion, that at least part of this is due to misunderstanding, on one or both sides. I'm fairly sure that Cinquetti thinks tossing in the copyright information into an installation agreement is the same as having it in the viewer; whether that's safe to say, I wouldn't be the one to ask. That there is more information, and more names, listed in Beauchamp's viewer is uncontested; but there's still one question remaining.
Does Cinquetti's saying "brought to life by KL" constitute claiming sole ownership of the viewer and its attached code? I ask that because of this, from Beauchamp's full listing in the 'license.txt' file:
That, I think you'd have to ask an IP rights lawyer about, and I'm not one.
Back on the 3rd, I spoke on a viewer controversy that's been brewing for some time. Earlier (as in, I past-dated it so it could be boring back in January), I linked Kirsten's initial EULA and credits in full. This had to be agreed to before I even downloaded the viewer. The CoolVL viewer was just a simple install, nothing overly complicated about it.
Then I opened each viewer in turn, on the grid.
 |
| (from the bizarre album) |
The first thing "Blackbird" told me was that my outfit didn't exist. Which was strange to me, as I could clearly see my outfit, and it was the same one I'd been wearing the last time I logged in with Singularity. Odd.
Then I went looking for the 'About' tab. It's not under Help, first of all; it's under the 'S19' tab itself:
 |
| (from the bizarre album) |
Henri is correct, no specific authors are listed other than KirstenLee Cinquetti under this tab.
 |
| (from the bizarre album) |
How'ver, under the 'Licenses & Copyrights' tab, there's this. Which looks fairly official with all bases covered, to me. Unless Henri is claiming that he, himself, coded his viewer entirely by hand, with no help from any other code source, what Kirsten seems to have done is credit the original (hence, first) coder for purposes of licensing--then left off anyone else who might have had a hand in redoing the code, either in sections or in whole.
There's a further point at the bottom of that tab, to see "licenses.txt" for more information, but I can't seem to find that anywhere within the program files.
I had no warning that this viewer was infested with malware, adware or a virus, but I don't use the same program Henri uses to detect those sorts of things.
I then popped open the latest CoolVL build. I got a EULA agreement there, too:
 |
| (from the bizarre album) |
Simple, fairly succinct, and to the point. Also, no virus warning either when I installed it, or when I ran it (not that I expected to see one).
 |
| (from the bizarre album) |
Then I went looking for the 'About' feature for CoolVL. I begin to see his point, because whereas the Kirsten viewer just credits KirstenLee Cinquetti for everything, Henri Beauchamp credits anyone who might have stared at the code for five minutes:
The Cool VL Viewer is brought to you and maintained by Henri Beauchamp.I will say, that is a much more comprehensive list.
Special credits:
The Cool VL Viewer MacOS-X builds are courtesy of Hyang Zhao (v1.25 and former), Guru Coyote (v1.26.0 to v1.26.4) and Kathrine Jansma (v1.26.4 and later).
The Cool VL Viewer logo (Burning Ice) is courtesy of Amari Kanto.
Coders:
99% of the code in this viewer was written by Lindens (Philip, Tessa, Andrew, Cory, James, Ben, Char, Charlie, Colin, Dan, Daniel, Doug, Eric, Hamlet, Haney, Eve, Hunter, Ian, Jeff, Jennifer, Jim, John, Lee, Mark, Peter, Phoenix, Richard, Robin, Xenon, Steve, Tanya, Eddie, Avi, Frank, Bruce, Aaron, Alice, Bob, Debra, Eileen, Helen, Janet, Louie, Leviathania, Stefan, Ray, Kevin, Tom, Mikeb, MikeT, Burgess, Elena, Tracy, Bill, Todd, Ryan, Zach, Sarah, Nova, Tim, Stephanie, Michael, Evan, Nicolas, Catherine, Rachelle, Dave, Holly, Bub, Kelly, Magellan, Ramzi, Don, Sabin, Jill, Rheya, Jeska, Torley, Kona, Callum, Charity, Ventrella, Jack, Vektor, Iris, Chris, Nicole, Mick, Reuben, Blue, Babbage, Yedwab, Deana, Lauren, Brent, Pathfinder, Chadrick, Altruima, Jesse, Teeny, Monroe, Icculus, David, Tess, Lizzie, Patsy, Isaac, Lawrence, Cyn, Bo, Gia, Annette, Marius, Tbone, Jonathan, Karen, Ginsu, Satoko, Yuko, Makiko, Thomas, Harry, Seth, Alexei, Brian, Guy, Runitai, Ethan, Data, Cornelius, Kenny, Swiss, Zero, Natria, Wendy, Stephen, Teeple, Thumper, Lucy, Dee, Mia, Liana, Warren, Branka, Aura, beez, Milo, Hermia, Red, Thrax, Joe, Sally, Magenta, Mogura, Paul, Jose, Rejean, Henrik, Lexie, Amber, Logan, Xan, Nora, Morpheus, Donovan, Leyla, MichaelFrancis, Beast, Cube, Bucky, Joshua, Stryfe, Harmony, Teresa, Claudia, Walker, Glenn, Fritz, Fordak, June, Cleopetra, Jean, Ivy, Betsy, Roosevelt, Spike, Ken, Which, Tofu, Chiyo, Rob, Zee, dustin, George, Del, Matthew, Cat, Jacqui, Lightfoot, Adrian, Viola, Alfred, Noel, Irfan, Sunil, Yool, Rika, Jane, Xtreme, Frontier, a2, Neo, Siobhan, Yoz, Justin, Elle, Qarl, Benjamin, Isabel, Gulliver, Everett, Christopher, Izzy, Stephany, Garry, Sejong, Sean, Tobin, Iridium, Meta, Anthony, Jeremy, JP, Jake, Maurice, Madhavi, Leopard, Kyle, Joon, Kari, Bert, Belinda, Jon, Kristi, Bridie, Pramod, KJ, Socrates, Maria, Ivan, Aric, Yamasaki, Adreanne, Jay, MitchK, Ceren, Coco, Durl, Jenny, Periapse, Kartic, Storrs, Lotte, Sandy, Rohn, Colossus, Zen, BigPapi, Brad, Pastrami, Kurz, Mani, Neuro, Jaime, MJ, Rowan, Sgt, Elvis, Gecko, Samuel, Sardonyx, Leo, Bryan, Niko, Soft, Poppy, Rachel, Aki, Angelo, Banzai, Alexa, Sue, CeeLo, Bender, CG, Gillian, Pelle, Nick, Echo, Zara, Christine, Shamiran, Emma, Blake, Keiko, Plexus, Joppa, Sidewinder, Erica, Ashlei, Twilight, Kristen, Brett, Q, Enus, Simon, Bevis, Kraft, Kip, Chandler, Ron, LauraP, Ram, KyleJM, Scouse, Prospero, Melissa, Marty, Nat, Hamilton, Kend, Lordan, Jimmy, Kosmo, Seraph, Green, Ekim, Wiggo, JT, Rome, Doris, Miz, Benoc, Whump, Trinity, Patch, Kate, TJ, Bao, Joohwan, Christy, Sofia, Matias, Cogsworth, Johan, Oreh, Cheah, Angela, Brandy, Mango, Lan, Aleks, Gloria, Heidy, Mitchell, Space, Colton, Bambers, Einstein, Maggie, Malbers, Rose, Winnie, Stella, Milton, Rothman, Niall, Marin, Allison, Katie, Dawn, Katt, Dusty, Kalpana, Judy, Andrea, Ambroff, Infinity, Gail, Rico, Raymond, Yi, William, Christa, M, Teagan, Scout, Molly, Dante, Corr, Dynamike, Usi, Kaylee, Vidtuts, Lil, Danica, Sascha, Kelv, Jacob, Nya, Rodney, Brandon, Elsie, Blondin, Grant, Katrin, Nyx, Gabriel, Locklainn, Claire, Devin, Minerva, Monty, Austin, Bradford, Si, Keira, H, Caitlin, Dita, Makai, Jenn, Ann, Meredith, Clare, Joy, Praveen, Cody, Edmund, Ruthe, Sirena, Gayathri, Spider, FJ, Davidoff, Tian, Jennie, Louise, Oskar, Landon, Noelle, Jarv, Ingrid, Al, Sommer, Doc, Aria, Huin, Gray, Lili, Vir, DJ, Yang, T, Simone, Maestro, Scott, Charlene, Quixote, Amanda, Susan, Zed, Anne, Enkidu, Esbee, Joroan, Katelin, Roxie, Tay, Scarlet, Kevin, Johnny, Wolfgang, Andren, Bob, Howard, Merov, Rand, Ray, Michon, Newell, Galen, Dessie, Les, Michon, Jenelle, Geo, Siz, Shapiro, Pete, Calyle, Selene, Allen, Phoebe, Goldin, Kimmora, Dakota, Slaton, Lindquist, Zoey, Hari, Othello, Rohit, Sheldon, Petra, Viale, Gordon, Kaye, Pink, Ferny, Emerson, Davy, Bri, Chan, Juan, Robert, Terrence, Nathan, Carl and many others). The Snowglobe branch of the SL viewer includes source code contributions of the following residents: Able Whitman, Adam Marker, Admiral Admiral, Agathos Frascati, Aimee Trescothick, Alejandro Rosenthal, Aleric Inglewood, Alissa Sabre, Angus Boyd, Ann Congrejo, Archimedes Plutonian, Ardy Lay, Argent Stonecutter, Armin Weatherwax, Asuka Neely, Balp Allen, Be Holder, Benja Kepler, Biancaluce Robbiani, Blakar Ogre, blino Nakamura, Boroondas Gupte, Bulli Schumann, bushing Spatula, Carjay McGinnis, Catherine Pfeffer, Celierra Darling, Cron Stardust, Cypren Christenson, Dale Glass, Drewan Keats, Dylan Haskell, Dzonatas Sol, Eddy Stryker, EponymousDylan Ra, Eva Nowicka, Farallon Greyskin, Feep Larsson, Flemming Congrejo, Fluf Fredriksson, Fremont Cunningham, Geneko Nemeth, Gigs Taggart, Ginko Bayliss, Grazer Kline, Gudmund Shepherd, Hamncheese Omlet, HappySmurf Papp, Henri Beauchamp, Hikkoshi Sakai, Hiro Sommambulist, Hoze Menges, Ian Kas, Irene Muni, Iskar Ariantho, Jacek Antonelli, JB Kraft, Joghert LeSabre, Kage Pixel, Ken March, Kerutsen Sellery, Khyota Wulluf, Kitty Barnett, Kunnis Basiat, Latif Khalifa, Lisa Lowe, Lockhart Cordoso, maciek marksman, Magnus Balczo, Malwina Dollinger, march Korda, Matthew Dowd, McCabe Maxsted, Michelle2 Zenovka, Mm Alder, Mr Greggan, Nicholaz Beresford, Nounouch Hapmouche, Patric Mills, Paul Churchill, Paula Innis, Pixel Gausman, Peekay Semyorka, Peter Lameth, Pf Shan, princess niven, Renault Clio, resu Ampan, Ringo Tuxing, Robin Cornelius, Ryozu Kojima, Salahzar Stenvaag, Sammy Frederix, Scrippy Scofield, Seg Baphomet, Sergen Davies, Shawn Kaufmat, SignpostMarv Martin, Simon Nolan, SpacedOut Frye, Sporked Friis, Stevex Janus, Still Defiant, Strife Onizuka, Tayra Dagostino, TBBle Kurosawa, Teardrops Fall, Techwolf Lupindo, tenebrous pau, Tharax Ferraris, Thickbrick Sleaford, Thraxis Epsilon, tiamat bingyi, TraductoresAnonimos Alter, Tue Torok, Twisted Laws, Vadim Bigbear, Vector Hastings, Vex Streeter, Vixen Heron, Whoops Babii, Wilton Lundquist, Zarkonnen Decosta, Zi Ree, Zipherius Turas.
The remaining 1% of the code is what makes this viewer so much better and unique. This viewer includes code contributed by (in alphabetical order): Able Whitman, Aimee Trescothick, Aleric Inglewood, Alissa Sabre, Ardy Lay, Armin Weatherwax, Boroondas Gupte, Carjay McGinnis, Chalice Yao, Dale Glass, Elektra Hesse, Gigs Taggart, Guru Coyote, Hazim Gazov, Henri Beauchamp, Jacek Antonelli, JB Kraft, jcool410, Jonathan Yap, Kadah Coba, Kathrine Jansma, Khyota Wulluf, Kitty Barnett, Lance Corrimal, Latif Khalifa, Marine Kelley, McCabe Maxsted, Michelle2 Zenovka, Mm Alder, Moon Metty, Nicholaz Beresford, Nicky Dasmijn, Robin Cornelius, Satomi Ahn, Siana Gearz, Shyotl Kuhr, Sione Lomu, Techwolf Lupindo, Thickbrick Sleaford, Tom Meta, Vadim Bigbear, WhiteStar Magic, Zi Ree, Zwagoth Klaar and other, unknown authors.
 |
| (from the bizarre album) |
And the CoolVL 'Licenses & Copyrights' tab mimics the S19 viewer's list fairly exactly, which tells me that's just a standard legal block all viewers are supposed to list.
 |
| (from the bizarre album) |
Then for some reason, I turned green. At least I go with the furniture? Still don't know why that happened (I didn't change eyes, outfit, hair, or skins while I was running these comparisons), but I took it as my cue to get off the grid.
Once off the grid, I searched through the CoolVL viewer files, and did track down the 'license.txt' file, with absolutely no difficulty. (The full text of that file can be read here.) And that has about the same amount of info that KirstenLee's EULA agreement had, only better organized.
So...and always keeping in mind I know next to nothing about viewer coding...I'd say, just in my opinion, that at least part of this is due to misunderstanding, on one or both sides. I'm fairly sure that Cinquetti thinks tossing in the copyright information into an installation agreement is the same as having it in the viewer; whether that's safe to say, I wouldn't be the one to ask. That there is more information, and more names, listed in Beauchamp's viewer is uncontested; but there's still one question remaining.
Does Cinquetti's saying "brought to life by KL" constitute claiming sole ownership of the viewer and its attached code? I ask that because of this, from Beauchamp's full listing in the 'license.txt' file:
The origin of this software must not be misrepresented; you must not claimKirsten says, there was never a claim of sole ownership. Henri says, there IS a claim of sole ownership, by virtue of that single line under 'Authors & Credits'. So...who's right?
that you wrote the original software.
That, I think you'd have to ask an IP rights lawyer about, and I'm not one.
27 March, 2013
now what I hold are the memories we barely made
A friend tipped me to this mesh piece on the Marketplace; it's attributed by its "creator" (and I use that word very, very loosely) under a "Creative Commons" license.
The problem with that? This is the Witch character from the Left 4 Dead games, in a Santa hat. Even the outfit she's in is directly ripped from the game.
And perusing the rest of his store, I am left with the inescapable conclusion that if there's anything there that hasn't been ripped from a major entertainment or game studio, it's only because it's been ripped from someone else, in world. He's a thief, pure and simple. It's still depressing beyond words that people feel the need to do that for whatever limited gain it gets them.
In other news, a friend of mine came across a 2012 study documenting the amount of virtual exposed skin on avatars in Second Life. What remains most compelling to me is that they excluded nearly all roleplaying sims (more on that later), and excluded all avatars who were over ninety days old.
If you're interested in the breakdown percentages, I highly recommend reading through the study, but I am going to mention the final tabulated results from the captured images (which were captured between 2011 and 2012, respectively). The amount of covered skin, on average, for male humanoid avatars, runs about 71% (with an additional note which indicates that 71% figure relates to a covering of 75% to 100%, excluding head and hands).
Considering that most avatars, from first day in to three months in, are still subsisting on a diet of freebie clothes and shapes, that actually makes sense. Excluding furs (who tend to wear less overall), and most roleplay sims (where more skin might be revealed), that pretty much indicates the standard population of any travel hub.
That female avatars of the same age range do not do the same is expected; but what's interesting (to me, at least), is how that change is demonstrated. There is not one single block of coverage, as is generally seen in the male figures (71% nearly covered, 19% two-thirds covered, 9% half-covered, and a slim 1% nearly naked). Instead, it's split nearly in half--female avatars, on average, waver between exposing up to 74% of their skin (38% of all female avatars observed), to exposing nearly half of their skin (47% of all female avatars observed), and that makes up the bulk of their total percentages. Only 15% remains, with 10% revealing nearly all skin, and a narrow 5% covering up nearly all skin.
We all fall prey to it from time to time, it's just easier in a virtual setting. Women dress how they dress not to impress men, generally, but to feel attractive themselves. Thing is, for most of us, "attractive" defaults to showing cleavage, or long legs; wearing heels instead of more comfortable shoes; wearing makeup instead of just cleaning our face and having done with it.
We do these things not because we necessarily feel they're important, but because we've been socialized to do these things. Our mothers told us how to dress, just as their mothers told them how. Our friends, instructed by their mothers and grandmothers, teach us as we teach them.
Be feminine. Stand up straight. Be coy, shy, inviting. Wear perfume. Wear makeup. Make sure your breath is fresh. Say yes, not no. And throughout all these messages, the one overwhelming one emerges--that women must be pretty at all times, if they hope to "snare a man". It is no surprise, then, that this melange of rules and restrictions seep into the virtual spaces we find ourselves using.
In Second Life, particularly, this is telling--because, while we, ourselves, have choices on the skins we wear, the shapes we wear, the clothing, for the most part we are buying what others have made. Which means we're literally conforming on a basic level to everything we were conditioned to believe before. There are virtually no skins, for child avatars or adult ones, that come without makeup. There are very, very few hairs that don't look like they've had some product, or gel, or mousse, used on them. There are few fashions (that are not specifically designed for roleplay, medieval sims, or neo-Victorian ones) that are not short first, or that don't expose a great deal of cleavage.
So, making these choices, wearing these clothes, wearing these shapes, and eyes, and hair, and adornments--we fall right back into the conditioning patterns. We understand why men dress to wear clothes that do not expose much skin. But most of us don't bother to understand why women dress to expose skin.
(Back to that roleplay sim. The single roleplay sim they did examine was one of the Star Wars roleplay sims, though they do not say which one in the study. There--and there alone--captured images of avatars were compared directly with stills from the Star Wars movies, in particular the "prequel" trilogy, with head and hands excluded from analysis. In this separate observational study, they also excluded furs, but retained their restriction of no one over ninety days old.)
The problem with that? This is the Witch character from the Left 4 Dead games, in a Santa hat. Even the outfit she's in is directly ripped from the game.
And perusing the rest of his store, I am left with the inescapable conclusion that if there's anything there that hasn't been ripped from a major entertainment or game studio, it's only because it's been ripped from someone else, in world. He's a thief, pure and simple. It's still depressing beyond words that people feel the need to do that for whatever limited gain it gets them.
In other news, a friend of mine came across a 2012 study documenting the amount of virtual exposed skin on avatars in Second Life. What remains most compelling to me is that they excluded nearly all roleplaying sims (more on that later), and excluded all avatars who were over ninety days old.
If you're interested in the breakdown percentages, I highly recommend reading through the study, but I am going to mention the final tabulated results from the captured images (which were captured between 2011 and 2012, respectively). The amount of covered skin, on average, for male humanoid avatars, runs about 71% (with an additional note which indicates that 71% figure relates to a covering of 75% to 100%, excluding head and hands).
Considering that most avatars, from first day in to three months in, are still subsisting on a diet of freebie clothes and shapes, that actually makes sense. Excluding furs (who tend to wear less overall), and most roleplay sims (where more skin might be revealed), that pretty much indicates the standard population of any travel hub.
That female avatars of the same age range do not do the same is expected; but what's interesting (to me, at least), is how that change is demonstrated. There is not one single block of coverage, as is generally seen in the male figures (71% nearly covered, 19% two-thirds covered, 9% half-covered, and a slim 1% nearly naked). Instead, it's split nearly in half--female avatars, on average, waver between exposing up to 74% of their skin (38% of all female avatars observed), to exposing nearly half of their skin (47% of all female avatars observed), and that makes up the bulk of their total percentages. Only 15% remains, with 10% revealing nearly all skin, and a narrow 5% covering up nearly all skin.
We all fall prey to it from time to time, it's just easier in a virtual setting. Women dress how they dress not to impress men, generally, but to feel attractive themselves. Thing is, for most of us, "attractive" defaults to showing cleavage, or long legs; wearing heels instead of more comfortable shoes; wearing makeup instead of just cleaning our face and having done with it.
We do these things not because we necessarily feel they're important, but because we've been socialized to do these things. Our mothers told us how to dress, just as their mothers told them how. Our friends, instructed by their mothers and grandmothers, teach us as we teach them.
Be feminine. Stand up straight. Be coy, shy, inviting. Wear perfume. Wear makeup. Make sure your breath is fresh. Say yes, not no. And throughout all these messages, the one overwhelming one emerges--that women must be pretty at all times, if they hope to "snare a man". It is no surprise, then, that this melange of rules and restrictions seep into the virtual spaces we find ourselves using.
In Second Life, particularly, this is telling--because, while we, ourselves, have choices on the skins we wear, the shapes we wear, the clothing, for the most part we are buying what others have made. Which means we're literally conforming on a basic level to everything we were conditioned to believe before. There are virtually no skins, for child avatars or adult ones, that come without makeup. There are very, very few hairs that don't look like they've had some product, or gel, or mousse, used on them. There are few fashions (that are not specifically designed for roleplay, medieval sims, or neo-Victorian ones) that are not short first, or that don't expose a great deal of cleavage.
So, making these choices, wearing these clothes, wearing these shapes, and eyes, and hair, and adornments--we fall right back into the conditioning patterns. We understand why men dress to wear clothes that do not expose much skin. But most of us don't bother to understand why women dress to expose skin.
(Back to that roleplay sim. The single roleplay sim they did examine was one of the Star Wars roleplay sims, though they do not say which one in the study. There--and there alone--captured images of avatars were compared directly with stills from the Star Wars movies, in particular the "prequel" trilogy, with head and hands excluded from analysis. In this separate observational study, they also excluded furs, but retained their restriction of no one over ninety days old.)
25 January, 2013
there's a message that I'm sending out, like a telegraph to your soul
So if you read part one and part two of the grand Candy Mountain/Yulicie controversy, you thought that was over and done with, right? Well...no. Which is why this is the third part.
I realized something about all this was bugging me, and it wasn't just not having the dress to compare the Vellent Retro frock to. So, after pondering for four days, I dropped Ms. Legend a notecard.
She wrote back. Apparently she made over thirty-five variations of this, some of which only went out for limited-edition release. However, there were a couple interesting things that came out in her answer:
That's what both dresses look like when laid over each other--if they'd used different base mesh forms, this would have shown that. As it was, they perfectly aligned, with only bits of the texture flashing on and off. This is what's going to make evaluating mesh (and mesh texturing) difficult: six different designers can buy this particular cocktail dress and turn out hundreds of different dresses. The dress form itself does not change. The mesh of the dress does not change. Just the texturing--which Ms. Legend calls "template", by which I think she means her created texture and shadow-map--for the mesh.
Okay. We know they both used the same dress form now. That's fact, that's undeniable, and it's bound to happen when full-perm mesh constructs are sold. What about the dress textures themselves?
That's where things get tricky.
A tip from a friend informed me I could actually rez the dresses out, instead of just trying them on, so for this entire picture run, that's what I did.
Candy Mountain's dress is on the left (note the star on the back), and Yulicie's "Vellent" is on the right. And it does look as if they've drawn shading in different places.
Here are both dresses from the front--the "Vellent", again, on the left, Candy Mountain's dress (note the Peter Pan collar) on the right.
Something was really starting to bug me, though, about the pattern itself. I couldn't put my finger on it, quite yet, so I rezzed out another version of the Candy Mountain dress. Now, Candy Mountain frocks are left and right, leaving Yulicie's "Vellent" in the center.
Here's the tricky bit. This is an extreme close-up of Yulicie's "Vellent" dress, showing a little jag in one of the drops of the painted texture itself.
And here, while it's difficult to see, is that same jag on the front of the Candy Mountain dress.
Okay, so what does that mean? Well, if I had to hazard a guess, Ms. Legend bought the template sometime in 2012, textured it with her own textures (not the six-pack that comes with the package from Ms. Imako), and released it. Then went a little crazy with brightly-colored tea dresses until she had those many, many variations.
Ms. Neaph, on the other hand, looks like she might have wandered across the Imako mesh dress recently, and picked it up. There's nothing inherently wrong with that, by the way--mesh forms that Ms. Imako releases are released with full permissions.
But. See that last picture? There's a complication, I think.
Namely, it looks like the drippy 'frosting' texture (or whatever it's supposed to be) on the Yulicie version has been flipped, front to back.
I'm going to go a little farther out on this limb, and say that it looks--at least to me--that the Yulicie dress uses the same texture as the Candy Mountain dress, which was released first, as far as I know.
I want to note: I don't know Ms. Neaph, I'm not saying she's infringing anything with her outfit. It's perfectly possible someone handed her the dress, and the texture, and she just did some quick recoloring for variation, some additional shading across the bust, et voila, her "Vellent Retro" released for the event.
But however she got it, I am saying that it's the same texture as on the Candy Mountain dress. How that happened, I'm not even hazarding a guess, but this comparison run is done, at least for me: the "Vellent Retro" dress does use the same texture as Candy Mountain's "Puddi" dress.
I realized something about all this was bugging me, and it wasn't just not having the dress to compare the Vellent Retro frock to. So, after pondering for four days, I dropped Ms. Legend a notecard.
She wrote back. Apparently she made over thirty-five variations of this, some of which only went out for limited-edition release. However, there were a couple interesting things that came out in her answer:
[19:54] Mynx Legend: (Saved Tue 22 Jan 2013 08:02:01) I made the dress templates all by hand, I never ever use photo sources or purchased templates. I can happily send you a non-special edition candy dress for you to inspect. (These were made in September with my Tea dresses)It's good to have that confirmed, at least, because as the photos will show, there's virtually no difference in the actual mesh structure of both dresses:
[19:54] Mynx Legend: (Saved Tue 22 Jan 2013 08:04:08) PS: Here is the screenshot of my first WIP of my cupcake dress: http://www.flickr.com/photos/mismatch/8010759491/ If that helps you out at all
[19:54] Mynx Legend: (Saved Tue 22 Jan 2013 08:06:02) The dress is a mesh source from Meli Imako, but I haven't used the shading map provided - I don't enjoy doing that. Also, sorry for all the IMs. My brain is a bit scattered today.
 |
| (from the Comparisons album |
That's what both dresses look like when laid over each other--if they'd used different base mesh forms, this would have shown that. As it was, they perfectly aligned, with only bits of the texture flashing on and off. This is what's going to make evaluating mesh (and mesh texturing) difficult: six different designers can buy this particular cocktail dress and turn out hundreds of different dresses. The dress form itself does not change. The mesh of the dress does not change. Just the texturing--which Ms. Legend calls "template", by which I think she means her created texture and shadow-map--for the mesh.
Okay. We know they both used the same dress form now. That's fact, that's undeniable, and it's bound to happen when full-perm mesh constructs are sold. What about the dress textures themselves?
That's where things get tricky.
A tip from a friend informed me I could actually rez the dresses out, instead of just trying them on, so for this entire picture run, that's what I did.
 |
| (from the Comparisons album |
Candy Mountain's dress is on the left (note the star on the back), and Yulicie's "Vellent" is on the right. And it does look as if they've drawn shading in different places.
 |
| (from the Comparisons album |
Here are both dresses from the front--the "Vellent", again, on the left, Candy Mountain's dress (note the Peter Pan collar) on the right.
 |
| (from the Comparisons album |
Something was really starting to bug me, though, about the pattern itself. I couldn't put my finger on it, quite yet, so I rezzed out another version of the Candy Mountain dress. Now, Candy Mountain frocks are left and right, leaving Yulicie's "Vellent" in the center.
 |
| (from the Comparisons album |
Here's the tricky bit. This is an extreme close-up of Yulicie's "Vellent" dress, showing a little jag in one of the drops of the painted texture itself.
 |
| (from the Comparisons album |
And here, while it's difficult to see, is that same jag on the front of the Candy Mountain dress.
Okay, so what does that mean? Well, if I had to hazard a guess, Ms. Legend bought the template sometime in 2012, textured it with her own textures (not the six-pack that comes with the package from Ms. Imako), and released it. Then went a little crazy with brightly-colored tea dresses until she had those many, many variations.
Ms. Neaph, on the other hand, looks like she might have wandered across the Imako mesh dress recently, and picked it up. There's nothing inherently wrong with that, by the way--mesh forms that Ms. Imako releases are released with full permissions.
But. See that last picture? There's a complication, I think.
Namely, it looks like the drippy 'frosting' texture (or whatever it's supposed to be) on the Yulicie version has been flipped, front to back.
I'm going to go a little farther out on this limb, and say that it looks--at least to me--that the Yulicie dress uses the same texture as the Candy Mountain dress, which was released first, as far as I know.
I want to note: I don't know Ms. Neaph, I'm not saying she's infringing anything with her outfit. It's perfectly possible someone handed her the dress, and the texture, and she just did some quick recoloring for variation, some additional shading across the bust, et voila, her "Vellent Retro" released for the event.
But however she got it, I am saying that it's the same texture as on the Candy Mountain dress. How that happened, I'm not even hazarding a guess, but this comparison run is done, at least for me: the "Vellent Retro" dress does use the same texture as Candy Mountain's "Puddi" dress.
18 January, 2013
oh, he's slightly clever, to just a certain extent
Homeland Security is now telling people not to download Java updates. Java has no response as of the writing of this, though they really should--either a brief press release saying they're sorry, or a brief press release saying they're working on it and don't hate them. Either would be fine.
Back to Candy Mountain vs. Yulicie!
Since I only have the one photograph to use for comparison, I'm thinking my best bet is to just list the dress features and go from there.
I do love the texture of the fabric; it's making me wish I'd actually acquired this when it was released (even if it was in flan colors)! How'ver, the features of the dress as I see them:
And now, some shots of the "Candy" dress from Yulicie for comparison:
This is Yulicie's Vellent Retro mesh dress, in "Tutti-Frutti".
So, first up: this doesn't have a Peter Pan collar. It also seems to have actual cap sleeves, not demi-caps, but to be fair, I only have Candy Mountain's product shot to look at, not an actual wearable copy. And while the skirt is similar, it doesn't seem precisely exact, at least texture-to-texture-wise.
Tossing in a couple close-ups here, this one specifically showing the draw lines across the chest. Candy Mountain's dress clearly has four wider draw lines; Yulicie, for comparison, has four draw lines, but narrower ones. And Yulicie's designer adds in a wrinkle along the right-hand side, as well. (I'd go back to Candy Mountain's dress for comparison, but it's obscured in the one shot I have by the "LIMITED EDITION" printing across the shot.)
The second close-up features the scoop neck of the Vellent Retro dress. And, while we're here, let me say that having this scoop neckline on this color makes it look very similar to the traditional "boat-neck nautical-inspired tops and dresses seen around and about--without verging into Flashdance territory. Plus, let's bring up the one thing I still like about well-made mesh outfits--that they look like actual clothing hanging on a body, not design work painted on a body.
The side of the dress, to show the flow of the skirt, basically. I don't have any views on the side of the Candy Mountain dress, so this is basically just me showing you the side of the dress, because, dress side. Essentially.
And the back of the dress, same reasoning.
Finally, a shot of the other dress color in the pack, "Strawberry Avalanche". This also shows the basic flaw of this--well, any--mesh outfit, but let me stress, it's not the fault of this dress that our avatars clip through the fabric. It's actually the fault of the clipping our avatars do in general, because there's no anti-clipping code in the SL client. (And likely never will be.)
My end conclusion: I'm wondering if this was just a case of similar templates, again. I went looking on the Marketplace to see if I could find the base template used, and nothing came up with this specific shape, so the jury's still out on the possibility. (To be fair, I didn't ruthlessly pursue a search using all potential search terms, either).
I think there's definite similarity, but whether that similarity is because Yulicie scarpered off with Candy Mountain's LE dress is decidedly unclear. The textures used are different, the sleeve styles at least appear to be slightly different, but to me, it does look like both designers went to the same template maker for this outfit.
If anyone knows who that is, do let me know, and I'll do my best to post pics of the base template used.
Last notes: I was wearing size M for both versions of the Vellent Retro dress. I did alter my base shape for two slider points: breast size, and torso muscles, both found under the Torso slider settings. I only needed to drop by two points on each setting, though, so it didn't put me out by that much. And after I adjusted those two slider settings, the dress fit perfectly.
(Worn [besides the dress] for this entry: Rue's "Cabal" skin, 'Naif' variant, in Powder [no idea if it's available now, though I know you can find reasonable facsimile skins in her shop]; the Leafy lipgloss tattoo in "Ice" over that; Discord Designs' "Starstruck Eyes" in Sophie [might still be available at the store at a DEEP discount if you look around]; GG's duotone pink/pink OTK socks [Naoki Ninetails designed them, but GG doesn't seem to exist anymore. She says her items are now under the Locke Couture imprint on SL Marketplace, but nothing seems to be there]; ploom's "Dawn" hair, a ring-curled mesh pony style in one of the "Candy" color-pack variants [in this case, blonde base with ombre pink/blue tinting]; and Dare Designs' "Looking for Strange" mesh boots in bubblegum pink [an in-store special a few months back]. And I took all the shots in the Sky Retreat skybox, designed by Desperation Isle Productions but provided by (and floating in a sim owned by) Little Dreams Estates. It's pretty here. I like it.)
Back to Candy Mountain vs. Yulicie!
Since I only have the one photograph to use for comparison, I'm thinking my best bet is to just list the dress features and go from there.
 |
| (from the Comparisons album: the "Puddi" dress from Candy Mountain, again |
I do love the texture of the fabric; it's making me wish I'd actually acquired this when it was released (even if it was in flan colors)! How'ver, the features of the dress as I see them:
- Peter Pan collar
- demi-cap sleeves
- cloth fold/cloth stretching shadowing across the chest
- a bas-relief printed 'nubbly' texture across bodice and upper section of skirt
- bell skirt, patterned in the same 'nubbly' texture for the upper section, and a straight deep custard yellow for the lower section
And now, some shots of the "Candy" dress from Yulicie for comparison:
 |
| (from the Comparisons album) |
This is Yulicie's Vellent Retro mesh dress, in "Tutti-Frutti".
So, first up: this doesn't have a Peter Pan collar. It also seems to have actual cap sleeves, not demi-caps, but to be fair, I only have Candy Mountain's product shot to look at, not an actual wearable copy. And while the skirt is similar, it doesn't seem precisely exact, at least texture-to-texture-wise.
 |
| (from the Comparisons album) |
Tossing in a couple close-ups here, this one specifically showing the draw lines across the chest. Candy Mountain's dress clearly has four wider draw lines; Yulicie, for comparison, has four draw lines, but narrower ones. And Yulicie's designer adds in a wrinkle along the right-hand side, as well. (I'd go back to Candy Mountain's dress for comparison, but it's obscured in the one shot I have by the "LIMITED EDITION" printing across the shot.)
 |
| (from the Comparisons album) |
The second close-up features the scoop neck of the Vellent Retro dress. And, while we're here, let me say that having this scoop neckline on this color makes it look very similar to the traditional "boat-neck nautical-inspired tops and dresses seen around and about--without verging into Flashdance territory. Plus, let's bring up the one thing I still like about well-made mesh outfits--that they look like actual clothing hanging on a body, not design work painted on a body.
 |
| (from the Comparisons album) |
The side of the dress, to show the flow of the skirt, basically. I don't have any views on the side of the Candy Mountain dress, so this is basically just me showing you the side of the dress, because, dress side. Essentially.
 |
| (from the Comparisons album) |
And the back of the dress, same reasoning.
 |
| (from the Comparisons album) |
Finally, a shot of the other dress color in the pack, "Strawberry Avalanche". This also shows the basic flaw of this--well, any--mesh outfit, but let me stress, it's not the fault of this dress that our avatars clip through the fabric. It's actually the fault of the clipping our avatars do in general, because there's no anti-clipping code in the SL client. (And likely never will be.)
My end conclusion: I'm wondering if this was just a case of similar templates, again. I went looking on the Marketplace to see if I could find the base template used, and nothing came up with this specific shape, so the jury's still out on the possibility. (To be fair, I didn't ruthlessly pursue a search using all potential search terms, either).
I think there's definite similarity, but whether that similarity is because Yulicie scarpered off with Candy Mountain's LE dress is decidedly unclear. The textures used are different, the sleeve styles at least appear to be slightly different, but to me, it does look like both designers went to the same template maker for this outfit.
If anyone knows who that is, do let me know, and I'll do my best to post pics of the base template used.
Last notes: I was wearing size M for both versions of the Vellent Retro dress. I did alter my base shape for two slider points: breast size, and torso muscles, both found under the Torso slider settings. I only needed to drop by two points on each setting, though, so it didn't put me out by that much. And after I adjusted those two slider settings, the dress fit perfectly.
(Worn [besides the dress] for this entry: Rue's "Cabal" skin, 'Naif' variant, in Powder [no idea if it's available now, though I know you can find reasonable facsimile skins in her shop]; the Leafy lipgloss tattoo in "Ice" over that; Discord Designs' "Starstruck Eyes" in Sophie [might still be available at the store at a DEEP discount if you look around]; GG's duotone pink/pink OTK socks [Naoki Ninetails designed them, but GG doesn't seem to exist anymore. She says her items are now under the Locke Couture imprint on SL Marketplace, but nothing seems to be there]; ploom's "Dawn" hair, a ring-curled mesh pony style in one of the "Candy" color-pack variants [in this case, blonde base with ombre pink/blue tinting]; and Dare Designs' "Looking for Strange" mesh boots in bubblegum pink [an in-store special a few months back]. And I took all the shots in the Sky Retreat skybox, designed by Desperation Isle Productions but provided by (and floating in a sim owned by) Little Dreams Estates. It's pretty here. I like it.)
16 January, 2013
she'd kill for a bite of those shiny red pennies
The text in full from Cool VL's "licenses.txt", found within the viewer itself.
(This is also past-dated, to spare anyone who doesn't really need to see this, this. Because it is long, dry, and quite dull.)
(This is also past-dated, to spare anyone who doesn't really need to see this, this. Because it is long, dry, and quite dull.)
===========
Logitech License
===========
End-User License Agreement for Logitech LCD SDK
This End-User License Agreement for Logitech LCD SDK ( “Agreement”) is a legal agreement between you, either an individual or legal entity (“You” or “you”) and Logitech Inc. (“Logitech”) for use of the Logitech LCD software development kit, which includes computer software and related media and documentation (hereinafter “LCD SDK”). By using this LCD SDK, you are agreeing to be bound by the terms and conditions of this Agreement. If you do not agree to the terms and conditions of this Agreement, promptly return the LCD SDK and other items that are part of this product in their original package with your sales receipt to your point of purchase for a full refund, or if you have downloaded this software from a Logitech web site, then you must stop using the software and destroy any copies of the software in your possession or control.
1 Grant of License and Restrictions.
This Agreement grants You the following rights provided that You comply with all terms and conditions of this Agreement.
- (a) Logitech grants You a limited, non-exclusive, nontransferable license to install and use an unlimited number of copies of the LCD SDK on computers . All other rights are reserved to Logitech.
- (b) You shall not reverse engineer, decompile or disassemble any portion of the LCD SDK, except and only to the extent that this limitation is expressly prohibited by applicable law.
- (c) At your option, you may provide reasonable feedback to Logitech, including but not limited to usability, bug reports and test results, with respect to the LCD SDK. All bug reports, test results and other feedback provided to Logitech by You shall be the property of Logitech and may be used by Logitech for any purpose.
- (d) In the event Logitech, in its sole discretion, elects to provide copies of the LCD SDK to more than one individual employed by You (if You are not a single individual), each such individual shall be entitled to exercise the rights granted in this Agreement and shall be bound by the terms and conditions herein.
2 Updates.
Logitech is not obligated to provide technical support or updates to You for the LCD SDK provided to You pursuant to this Agreement. However, Logitech may, in its sole discretion, provide further pre-release versions, technical support, updates and/or supplements (“Updates”) to You, in which case such Updates shall be deemed to be included in the “LCD SDK” and shall be governed by this Agreement, unless other terms of use are provided in writing by Logitech with such Updates.
3 Intellectual Property Rights.
The LCD SDK is licensed, not sold, to You for use only under the terms and conditions of this Agreement. Logitech and its suppliers retain title to the LCD SDK and all intellectual property rights therein. The LCD SDK is protected by intellectual property laws and international treaties, including U.S. copyright law and international copyright treaties. All rights not expressly granted by Logitech are reserved.
4 Disclaimer of Warranty.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LOGITECH AND ITS SUPPLIERS PROVIDE THE LCD SDK AND OTHER LOGITECH PRODUCTS AND SERVICES (IF ANY) AS IS AND WITHOUT WARRANTY OF ANY KIND. LOGITECH AND ITS SUPPLIERS EXPRESSLY DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD-PARTY RIGHTS WITH RESPECT TO THE LCD SDK AND ANY WARRANTIES OF NON-INTERFERENCE OR ACCURACY OF INFORMATIONAL CONTENT. NO LOGITECH DEALER, AGENT, OR EMPLOYEE IS AUTHORIZED TO MAKE ANY MODIFICATION, EXTENSION, OR ADDITION TO THIS WARRANTY. Some jurisdictions do not allow limitations on how long an implied warranty lasts, so the above limitation may not apply to you.
5 Limitation of Liability.
IN NO EVENT WILL LOGITECH OR ITS SUPPLIERS BE LIABLE FOR ANY COSTS OF PROCUREMENT OF SUBSTITUTE PRODUCTS OR SERVICES, LOST PROFITS, LOSS OF INFORMATION OR DATA, OR ANY OTHER SPECIAL, INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING IN ANY WAY OUT OF THE SALE OF, USE OF, OR INABILITY TO USE THE LCD SDK OR ANY LOGITECH PRODUCT OR SERVICE, EVEN IF LOGITECH HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO CASE SHALL LOGITECH'S AND ITS SUPPLIERS’ TOTAL LIABILITY EXCEED THE ACTUAL MONEY PAID FOR THE LOGITECH PRODUCT OR SERVICE GIVING RISE TO THE LIABILITY. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to you. The above limitations will not apply in case of personal injury where and to the extent that applicable law requires such liability.
6 U.S. Government Rights.
Use, duplication, or disclosure of the software contained in the LCD SDK by the U.S. Government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988) FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Logitech Inc. 6505 Kaiser Drive, Fremont, CA 94555.
7 Export Law Assurances.
You agree and certify that neither the LCD SDK nor any other technical data received from Logitech will be exported outside the United States except as authorized and as permitted by the laws and regulations of the United States. If you have rightfully obtained the LCD SDK outside of the United States, you agree that you will not re-export the LCD SDK nor any other technical data received from Logitech, except as permitted by the laws and regulations of the United States and the laws and regulations of the jurisdiction in which you obtained the LCD SDK.
8 Termination:
This Agreement is effective until terminated. Upon any violation of any of the provisions of this Agreement, rights to use the LCD SDK shall automatically terminate and the LCD SDK must be returned to Logitech or all copies of the LCD SDK destroyed. You may also terminate this Agreement at any time by destroying all copies of the LCD SDK in your possession or control. If Logitech makes a request via public announcement or press release to stop using the copies of the LCD SDK, you will comply immediately with this request. The provisions of paragraphs 3, 7, 8 and 12 will survive any termination of this Agreement.
9 General Terms and Conditions.
If You are an individual signing this Agreement on behalf of a company, then You represent that You have authority to execute this Agreement on behalf of such company. This Agreement will be governed by and construed in accordance with the laws of the United States and the State of California, without regard to or application of its choice of law rules or principles. If for any reason a court of competent jurisdiction finds any provision of this Agreement, or portion thereof, to be unenforceable, that provision of the Agreement shall be enforced to the maximum extent permissible so as to affect the intent of the parties, and the remainder of this Agreement shall continue in full force and effect. This Agreement constitutes the entire agreement between You and Logitech respect to the use of the LCD SDK and supersedes all prior or contemporaneous understandings, communications or agreements, written or oral, regarding such subject matter.
===========
APR License
===========
Copyright 2000-2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
==============
Base32 License
==============
* Copyright (c) 2006 Christian Biere
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. Neither the name of the authors nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
============
cURL License
============
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1996 - 2002, Daniel Stenberg,.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose
with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN
NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not
be used in advertising or otherwise to promote the sale, use or other dealings
in this Software without prior written authorization of the copyright holder.
=============
expat License
=============
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
================
FreeType License
================
Portions of this software are copyright (c) 2003 The FreeType
Project (www.freetype.org). All rights reserved.
==========================
FSI FontShop International
==========================
Certain of the fonts in the Meta family of copyrighted typefaces are
used in Second Life under license from FSI FontShop
International. Copies of such Meta fonts that are included in the
Viewer are not themselves open source and are not available under the
GPL license, and they may not be copied. Developers may use those
fonts solely to the extent necessary to use or customize the Linden
Software in Second Life and to develop and distribute content solely
for use in the Second Life environment, and for no other purposes.
Second Life developers who wish to make other uses of Meta fonts must
obtain a license from FSI FontShop International at www.fontfont.com.
==========
GL License
==========
Mesa 3-D graphics library
Version: 6.2
Copyright (C) 1999-2004 Brian Paul All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
=========================
glh OpenGL helper library
=========================
glh - is a platform-indepenedent C++ OpenGL helper library
Copyright (c) 2000 Cass Everitt
Copyright (c) 2000 NVIDIA Corporation
All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above
copyright notice, this list of conditions and the following
disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials
provided with the distribution.
* The names of contributors to this software may not be used
to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
`AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Cass Everitt - cass@r3.nu
=======================
JPEG Library 6b License
=======================
This software is based in part on the work of the Independent JPEG Group
================
JPEG2000 License
================
Copyright 2001, David Taubman, The University of New South Wales (UNSW)
The copyright owner is Unisearch Ltd, Australia (commercial arm of UNSW)
Neither this copyright statement, nor the licensing details below
may be removed from this file or dissociated from its contents.
Licensee: Linden Research, Inc.
License number: 00024
The licensee has been granted a COMMERCIAL license to the contents of
this source file. A brief summary of this license appears below. This
summary is not to be relied upon in preference to the full text of the
license agreement, accepted at purchase of the license.
1. The Licensee has the right to Commercial Use of the Kakadu software,
including distribution of one or more Applications built using the
software.
2. The Licensee has the right to Internal Use of the Kakadu software,
including use by employees of the Licensee or an Affiliate for the
purpose of performing services on behalf of the Licensee or Affiliate,
or in the performance of services for Third Parties who engage Licensee
or an Affiliate for such services.
3. The Licensee has the right to distribute Reusable Code (including
source code and dynamically or statically linked libraries) to a Third
Party, provided the Third Party possesses a license to use the Kakadu
software.
==================
ogg/vorbis License
==================
Copyright (c) 2001, Xiphophorus
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
- Neither the name of the Xiphophorus nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===============
OpenSSL License
===============
Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this
software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
endorse or promote products derived from this software without
prior written permission. For written permission, please contact
openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL"
nor may "OpenSSL" appear in their names without prior written
permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE. ====================================================================
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com). This product includes software written by Tim
Hudson (tjh@cryptsoft.com).
=======================
Original SSLeay License
=======================
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written
by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as
the following conditions are aheared to. The following conditions
apply to all code found in this distribution, be it the RC4, RSA,
lhash, DES, etc., code; not just the SSL code. The SSL documentation
included with this distribution is covered by the same copyright terms
except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in
the code are not to be removed.
If this package is used in a product, Eric Young should be given attribution
as the author of the parts of the library used.
This can be in the form of a textual message at program startup or
in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
The licence and distribution terms for any publically available version or
derivative of this code cannot be changed. i.e. this code cannot simply be
copied and put under another distribution licence
[including the GNU Public Licence.]
==================
xmlrpc-epi License
==================
Copyright 2000 Epinions, Inc.
Subject to the following 3 conditions, Epinions, Inc. permits you, free of charge, to (a) use, copy, distribute, modify, perform and display this software and associated documentation files (the "Software"), and (b) permit others to whom the Software is furnished to do so as well.
1) The above copyright notice and this permission notice shall be included without modification in all copies or substantial portions of the Software.
2) THE SOFTWARE IS PROVIDED "AS IS", WITHOUT ANY WARRANTY OR CONDITION OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF ACCURACY, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
3) IN NO EVENT SHALL EPINIONS, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR LOST PROFITS ARISING OUT OF OR IN CONNECTION WITH THE SOFTWARE (HOWEVER ARISING, INCLUDING NEGLIGENCE), EVEN IF EPINIONS, INC. IS AWARE OF THE POSSIBILITY OF SUCH DAMAGES.
============
zlib License
============
'zlib' general purpose compression library version 1.1.4, March 11th, 2002
Copyright (C) 1995-2002 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty.
In no event will the authors be held liable for any damages arising from the
use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
The origin of this software must not be misrepresented; you must not claim
that you wrote the original software. If you use this software in a product,
an acknowledgment in the product documentation would be appreciated but is
not required.
Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
This notice may not be removed or altered from any source distribution.
Jean-loup Gailly
jloup@gzip.org
Mark Adler
madler@alumni.caltech.edu
==============
libpng license
==============
COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:
If you modify libpng you may insert additional notices immediately following
this sentence.
libpng versions 1.2.6, August 15, 2004, through 1.2.18, May 15, 2007, are
Copyright (c) 2004, 2006-2007 Glenn Randers-Pehrson, and are
distributed according to the same disclaimer and license as libpng-1.2.5
with the following individual added to the list of Contributing Authors:
Cosmin Truta
libpng versions 1.0.7, July 1, 2000, through 1.2.5, October 3, 2002, are
Copyright (c) 2000-2002 Glenn Randers-Pehrson, and are
distributed according to the same disclaimer and license as libpng-1.0.6
with the following individuals added to the list of Contributing Authors:
Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant
and with the following additions to the disclaimer:
There is no warranty against interference with your enjoyment of the
library or against infringement. There is no warranty that our
efforts or the library will fulfill any of your particular purposes
or needs. This library is provided with all faults, and the entire
risk of satisfactory quality, performance, accuracy, and effort is with
the user.
libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are
Copyright (c) 1998, 1999, 2000 Glenn Randers-Pehrson, and are
distributed according to the same disclaimer and license as libpng-0.96,
with the following individuals added to the list of Contributing Authors:
Tom Lane
Glenn Randers-Pehrson
Willem van Schaik
libpng versions 0.89, June 1996, through 0.96, May 1997, are
Copyright (c) 1996, 1997 Andreas Dilger
Distributed according to the same disclaimer and license as libpng-0.88,
with the following individuals added to the list of Contributing Authors:
John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
Greg Roelofs
Tom Tanner
libpng versions 0.5, May 1995, through 0.88, January 1996, are
Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.
For the purposes of this copyright and license, "Contributing Authors"
is defined as the following set of individuals:
Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner
The PNG Reference Library is supplied "AS IS". The Contributing Authors
and Group 42, Inc. disclaim all warranties, expressed or implied,
including, without limitation, the warranties of merchantability and of
fitness for any purpose. The Contributing Authors and Group 42, Inc.
assume no liability for direct, indirect, incidental, special, exemplary,
or consequential damages, which may result from the use of the PNG
Reference Library, even if advised of the possibility of such damage.
Permission is hereby granted to use, copy, modify, and distribute this
source code, or portions hereof, for any purpose, without fee, subject
to the following restrictions:
1. The origin of this source code must not be misrepresented.
2. Altered versions must be plainly marked as such and
must not be misrepresented as being the original source.
3. This Copyright notice may not be removed or altered from
any source or altered source distribution.
The Contributing Authors and Group 42, Inc. specifically permit, without
fee, and encourage the use of this source code as a component to
supporting the PNG file format in commercial products. If you use this
source code in a product, acknowledgment is not required but would be
appreciated.
=================
Vivox SDK License
=================
RSA Data Security, Inc. MD5 Message-Digest Algorithm
Audio coding: Polycom¨ Siren14TM (ITU-T Rec. G.722.1 Annex C)
Open Source Software Licensing
Each open source software component utilized by this product is subject to its own copyright and licensing terms, as listed below.
*************************************************************
*************************************************************
/**
* OpenAL cross platform audio library
* Copyright (C) 1999-2000 by authors.
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Library General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Library General Public License for more details.
*
* You should have received a copy of the GNU Library General Public
* License along with this library; if not, write to the
* Free Software Foundation, Inc., 59 Temple Place - Suite 330,
* Boston, MA 02111-1307, USA.
* Or go to http://www.gnu.org/copyleft/lgpl.html
*/
*************************************************************
*************************************************************
RTP code under Lesser General Public License
/*
The oRTP library is an RTP (Realtime Transport Protocol - rfc3550) stack.
Copyright (C) 2001 Simon MORLAT simon.morlat@linphone.org
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
************************************************************
************************************************************
/*
* The Vovida Software License, Version 1.0
*
* Copyright (c) 2000 Vovida Networks, Inc. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. The names "VOCAL", "Vovida Open Communication Application Library",
* and "Vovida Open Communication Application Library (VOCAL)" must
* not be used to endorse or promote products derived from this
* software without prior written permission. For written
* permission, please contact vocal@vovida.org.
*
* 4. Products derived from this software may not be called "VOCAL", nor
* may "VOCAL" appear in their name, without prior written
* permission of Vovida Networks, Inc.
*
* THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND
* NON-INFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL VOVIDA
* NETWORKS, INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT DAMAGES
* IN EXCESS OF $1,000, NOR FOR ANY INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
* PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
* OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
* USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
* DAMAGE. *
*
* This software consists of voluntary contributions made by Vovida
* Networks, Inc. and many individuals on behalf of Vovida Networks,
* Inc. For more information on Vovida Networks, Inc., please see
*
*
*/
*************************************************************
*************************************************************
Internet Software Consortium code
/* This is from the BIND 4.9.4 release, modified to compile by itself */
/* Copyright (c) 1996 by Internet Software Consortium.
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
* ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
* CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
* DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
* PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
* ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
* SOFTWARE.
*/
*************************************************************
*************************************************************
*************************************************************
http://tinyxpath.sourceforge.net/
TinyXPath is covered by the zlib license :
www.sourceforge.net/projects/tinyxpath
Copyright (c) 2002-2006 Yves Berquin (yvesb@users.sourceforge.net)
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any
damages arising from the use of this software.
Permission is granted to anyone to use this software for any
purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must
not claim that you wrote the original software. If you use this
software in a product, an acknowledgment in the product documentation
would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and
must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
************************************************************
************************************************************
THE FREE SOFTWARE FOUNDATION
Any customer may request the source code for all open source portions of this product which are covered by the Free Software Foundation's General Public License (GPL), for a period of three years from purchase. Please contact the vendor from whom you obtained this product for instructions. A fee equivalent to the cost of making the code available may be charged. Alternatively, customers may choose to download desired GPL components directly from their original vendors. Specifically, this product contains the following GPL-licensed components:
From Vivox:
- Assorted software components. To request source, contact Vivox at:
Vivox, Inc.
Attn: customer support
40 Speen Street Suite 402
Framingham, MA 01701
========================
google-perftools license
========================
Copyright (c) 2005, Google Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
* Neither the name of Google Inc. nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Subscribe to:
Posts (Atom)
it's just your shadow on the floor
(This section was written on July 11th...) Great. Sat myself down today after oversleeping, and told myself sternly I was not going to log...
