
…so… LL made a new update. And with it… came ABSOLUTELY NO CHANGE LOG.
We recently made several changes to the Second Life servers to address a potential security issue. To take advantage of the recent server upgrades and ensure that Second Life functions as you expect, we have released a new version of the Second Life Viewer.
Residents using the Official and Release Candidate versions of the 1.23.4 Viewer are required to update to version 1.23.5. Those of you still using version 1.22.11 will be offered version 1.23.5 as an optional update. If you choose to remain on 1.22.11, you may notice changes in the way notecard editing behaves. If you use a viewer not created by Linden Lab, you may also see changes in the way notecard editing behaves. To avoid any potential confusion caused by these behavioral changes, we strongly recommend that you immediately update to the new 1.23.5 Second Life Viewer.
We apologize for any inconvenience this update may cause.
Read the bolded text. Okay. Now read it again. Now let it absorb…
This is a HUGE deal – meaning that any and all residents on 3rd party viewers or running the older releases will NOT have be able to open/edit notecards.
Scripts, vendor notecards for merchants – it's something "not revealed" and very damaging – this is a critical issue – and LL is not releasing the "changes" the made.
They are however recommending (not forcing) the new viewer. Pitiful.
This is a HUGE deal – meaning that any and all residents on 3rd party viewers or running the older releases will NOT have be able to open/edit notecards.
Scripts, vendor notecards for merchants – it's something "not revealed" and very damaging – this is a critical issue – and LL is not releasing the "changes" they've made.
They are however recommending (not forcing) the new viewer. Pitiful.
This is a HUGE deal – meaning that any resident on 3rd party viewers or running the older releases will NOT have be able to open/edit notecards.
Scripts, vendor notecards for merchants – it's something "not revealed" and very damaging – this is a critical issue – and LL is not releasing the "changes" they've made.
They are however recommending (not forcing) the new viewer. Pitiful.
Oh okay how lame. I communicate with different people thought notecards and lets face it some third party viewers are better then the SL viewer. Do you think the over popularity of these viewers is what made LL say "Look here we are going to fuck up notecards for all yall so come back to us"?
I think it's kind of clever for LL to intentionally break notecards to regain people using their viewer. Now if only they'd stop fucking around and adopt the some of the awesome features of the third party viewers…
When will people realize that LL can do whatever THE HELL THEY WANT! You can moan and complain, but they'll always have the last say. That is the way it will always be. One day, they might even decide to make the 3rd party viewers totally incompatible.
SL is not a democracy, it is a dictatorship. If you don't like it, then really should give up playing altogether and do RL stuff.
Strangely, this notecard 'bork' coincides just a day after the release of the 'jiggly boobs effect' in the Emerald viewer – Possibly something that LL doesn't like its image to be associated with? If so, in future expect 3rd party viewers to be totally phased out by LL.
LL is doing "buddy" deals with Dreamland, once again… https://blogs.secondlife.com/thread/3581
Okay after further reading I think that I understand the recent upgrade…
The official SL viewer only allows full perm items to be sent in a notecard, but the check if the item is full perm or not is only client (viewer side). Some 3rd party viewers saw this as an exploit, and disabled this check, so residents could put non-full perms objects in notecards. (see where I'm going with this?)
Basically, some 3rd party viewers (Emerald etc) allowed no transfer items to be put into a notecard. This meant that you could put all your copy permission only items into a notecard and give them to your friends or in some cases send them to entire groups of people, and people will get these items for free!
This has been going on for some time now, but recently the increased popularity of the Emerald viewer due to the jiggly boobs effect, has made it an urgent security bug for LL to fix, as more and more people were sending out no-transfer items in notecards.
Haven't used the official viewer for a long time. Ha ha. They just gave me a reason to download and install it again.
I use Emerald and I've just tried a few things with notecards, opening, modifying, saving etc. Everything works as it should. I don't see what they've changed, except closing the security loophole. Am I missing something that SHOULD be allowed and isn't? I couldn't find anything wrong.
Yeah, I think all that about notecards being broken for ppl using 3rd-party viewers was a bit, um, premature. Not to say utter BS.
LL fixed my defect!
* VWR-13868[c]: Sculpted prims in complex linked sets vanish – Raised 'RENDERMAXNODESIZE' from 4096 to 8192
LL needs to decide if they are going to be open source in sharing their code or stop it all together. You can't be only halfway open source – that really goes against the spirit of the open source community.
Emerald had nothing to do with this and it didn't allow you to put non-fullperm items into notecards either. I don't quite understand why people are bitching about the Lab for fixing this serious permission exploit that allowed fullperming any script, object, texture, animation or whatever.. seriously, make up your mind. You won't be able to edit notecards inside objects without the 1.23.5 viewer, but Emerald and most of the other 3rd party viewers will release updates very soon.
“the Lab for fixing this serious permission exploit that allowed fullperming any script, object, texture, animation or whatever.. seriously, make up your mind.”
still have not … lacking details … is it confirmable that permissions CHANGED inside a notecard? or do the items snap back into original permission flags on arrival? surely that undermines copy and transferability settings. my main point of interrest is about changing modify flag on scripts, since that lill’ detail would completely break many dependand vendor systems & stuff
Err isn't this a good thing or have I missed something
it doesn't matter how good this change is, I need to bitch about SOMETHING!!!!