Cerise Sorbet

Yes, that's exactly what it means. A single group notice to a group with 5000+ members uses up the quota in one shot. The policy isn't going to be too too black and white, because humans using very large groups will hit that number regularly. They will have to use the duck test to identify the automated messages.

For what it's worth, one of the biggest causes of group chat overload is being addressed.

The only real downside to using a larger maxlength is that is uses more memory. The default stayed at 2048 because that size was hardcoded for several years, so old scripts would suddenly start crashing if bigger-than-expected strings started to pour in.

Your pastebin file is too large. By default llHTTPRequest only grabs the first 2048 bytes, and for that page, it happens to be the first 52 lines. $ head -c 2048 rrr.txt | wc -l 52 You can use a custom HTTP_BODY_MAXLENGTH to grab the whole thing.

JT Castanea wrote: They would know...I think they would know...from the key number yes...no? Login histories. They have a pretty good if not perfect idea who is who.

Probable situation for the fraud/theft thing: a single person did something bad, or perhaps decided to try to buy cheap (actually stolen) L$ from an outfit like that mmook place. LL sees a bunch of accounts joined SL about the same day from the same address, assumes they are alts waiting in the wings, and bans the lot of them. On the getting banned from individual places, it's become really, really common for busy clubs and shops to boot out avatars that are fewer than X days old, X can range anywhere from about 3 to 90 days. They are working on the assumption that an account that can last X days is probably not a throwaway grief account, and will let them in after that point. It seems kind of pointless to me, given rampant phishing, and that repeat troublemakers already know to make extra accounts in advance and let them age; but there you go.

Going to echo the others, fglrx does the job for me. It's nice that those driver projects take note of the standards, but they really need to take note of Postel's law too.

Not so d'oh, really =D Until the mesh parts became available, replacement hands looked really, really bad, or there would be a big invisiprim glitching all over the place.

The left and right arms share a single section of the clothing/skin texture, it's mirrored, so two hands gone is what you will get with those alpha wearables. To get what you want, mesh hands (just wear the right hand, your custom stuff on the left) would work.

Old thread is old, but this feature was rattling in the back of my mind as documented somewhere. And, as it turns out, old feature is old, really old. It was added in version 0.9. Text/logos on clothing will stretch less and look better across a broader range of avatar body types. Previously text would become distorted but now texture UV maps are adjusted for each morph.

You'll find that if inworld drama is mentioned around LL employees, they will generally say nothing or change the subject, because they don't go there. In the past a Linden or two with too much time did become former Lindens after getting into inworld drama, so it's not going to be on anyone's list of fun ideas to try. LL is now smaller than it used to be. In any given month there are a million of us, and only a couple hundred LL employees who work on SL. Only a fraction of those actually interact directly with the customers, others are doing office work or toiling in the code mines or banging on hardware. They're not going to have the time to notice many people, let alone dish dirt,

There are lots of authorized options to buy Linden dollars that don't use credit cards or Paypal. If you want to convert L$ back to cash, the only remaining channel is Lindex, and they only like to use Paypal. There used to be more ways to do this, but the US government decided to meddle in virtual currency this year adding some onerous new policies that made this impracticable.

Mostly XML-RPC still exists because the Magic Boxes LL inherited from SLX still use it. Once LL gets around to making no-copy stuff work with direct delivery, that will be the end of their own need for it. You will definitely want to read this blog post; LL really, really wants to retire the thing.

The Shelter has been using repeaters like that since Hector was a pup. Maybe you could poke your head in there and ask if there has been any trouble.

No, but you can raise the mouth and reduce the chin depth to fake it.

It's all journaled and backed up. Sometimes it can take a long time for those databases to get revved back up, caught up to date and back on track, but it will get there.

MaxFPS debug setting seems to have accidentally leaked into the LL settings file but it's an orphan. (Firestorm normally uses this setting, but it's broken in the current beta.) The LL code isn't actually referencing MaxFPS at all, but it does have the YieldTime setting. (On FS, when this feature is working, it does still throttle the frame rate if the system is lightly loaded. The sleep time is simply eaten up by the idle process in that case.)

MaxFPS has been broken for a few months.

How are you building the object? What kinds of prims is it made of? Maybe there is a more reliable way to do it from that end. Twisting usually works pretty well, layering not so much. Also round shapes, like cylinders and spheres, are much more reliable for this than irregular shapes.

If you are trying to defeat the "automatic alpha mask" feature, the last line ought to be enough, but should only be used if the texdture on every face actually has an alpha channel. You can do this in the SL editor, just set transparency on that face to 1%; a script for this seems odd. This trick does hurt viewer performance, so I hope you are only using it where it's really necessary.

Ok, I added the missing tag, and that fixed the crash, so this one's not the server's fault.

Looks like the bug is really with Second Life 3.6.12 (284430), the maintenance RC. On that version I can get the Help>About crash in Drawbridge. I also got it to happen just down the road, in Gallinas, running on LeTigre. The trail of the log is 2013-12-05T01:46:37Z llui/llpanel.cpp(621) : error2013-12-05T01:46:37Z ERROR: LLPanel::getString: Failed to find string ErrorFetchingServerReleaseNotesURL in panel floater_about and sure enough, there were some major changes to that version's floater_about.xml and that tag is missing, The same viewer doesn't crash at my house, which is also on Magnum, presumably because it managed to fetch the release notes OK there. It's not crashing with Second Life 3.6.11 (283787), or Firestorm or Singularity.

Yes, this happens sometimes, the web login info doesn't get handed over from your viewer login properly. There should be a login button or link on the profile page when that happens, go ahead and click that and log in (again). From there, it will typically work normally for the rest of the session. And yeah, this is a problem that a cache clear won't fix. Adding ... and now I see that my.secondlife.com seems to be hanging on logins anyway, so you may just have to wait for someone to get out the paperclips and scotch tape and fix the site again.

It's not really needed. that 'else return' will let you skip the (msg=="exitClose") test, which can't be true in this case, but you could do the same by changing the second "if" to "else if". The 'else return' near the bottom isn't really doing anything at all.

OK, Maekju is on Second Life Server, so it was part of yesterday morning's rolling restart. I'm afraid you will have to wait for support to get back to you then.