“Uh, has the world been absolutely free of self-replicating objects since open-source? No, it has not.”

Sorry Prokofy I misunderstood your original question. When you asked “So why do they continue to keep coming on Agni and harming it?” in response to “Oh except for Uma, the new public access 5-sim grid just for open source coders to have a place to play with experimental builds without harming Agni.” I assumed you were talking about the open source version of Second Life. Since you were actually asking about self-replicating LSL scripts, libsecondlife bots, and fake notecards I’ll save the discussion for another thread.

No, not being privy to such info I didn’t use the method you outlined.
All I did was bug reported, about 5 times, then finally got Concierge to look into it – you’d think THEY’D know about that security@lindenlab.com wheeze, wouldn’t you?
Fritz came out several times to check it out, requesting temporary Estate Manager status twice so he could verify it – which he did, several times, Hermia dug into the logs and verified just how many times I was able to reproduce it after it was ‘fixed’ too…

Anyway… just a thought.

Has the world been free of CampBots? No, there are more of them than ever, sucking down sim resources and of course ill-gotten casino money not intended to be stolen in this fashion.

Soon to come: dancebots, or fillupyoursimbecausewehateyoubots.

All of these are products made or produced or copied and tweaked by libsl and its spinoff groups.

BTW, Open Source Fan Club is the new W-Hat hideout, and the members who were all around sending out a fake notecards (like one by Partyhats Loll claiming Pathfinder and Cubey Terra were griefers and “warning” newbies”) are all in it, along with Lindens. I asked several of the Lindens why they were in a group with known griefers who harass other people. Several of them left after my question.

* Overview
* Instructions to reproduce (this is why a test grid is needed, to make sure your repro works)
* Why this is a threat (can crash one or more sims in this case)
* Your name, e-mail address, and Second Life name
* Optionally a patch to fix it if this is a viewer problem, or speculation on what is causing the problem

Often times you can pull a Linden aside to confirm a problem as well.

Having said that, when I discovered a simple series of legitimate estate tool actions which could reliably crash a sim, I had to demonstrate the ‘exploit’ – actually poor coding by LL – over and over again before anyone took any notice. Despite submitting bug reports for a couple of weeks, and reporting it to Concierge representatives and even giving them Estate Manager status so they could reproduce it themselves. That’s not taking into account the number of times it was ‘fixed’ either…

Still, one wonders what level of mayhem it’ll be necessary to wreak on Uma to capture LL’s attention regarding a crashing ‘exploit’ (bug)?

I couldn’t really say without more detail about what harm is going on here, but I’m sure you don’t need to be told how to report abuse from another resident. The opensl code is the same viewer code that everyone else runs and is fully capable of working with the stable grids. But lets say you found a potential sim crashing exploit, by logging on to Uma to test you won’t be killing a main simulator and it helps the Lindens identify the problem without having to dig through long log files of activity.