Peter Stindberg

Keywords also get scanned for that, btw.

Good point!

Too little, too late. Already now we see "highspeed throwaway bots" that get registered en masse, fly under the radar for a day or two, get discarded before any compliance crackdown can get hold of them. Rinse. Repeat. The genie is out of the bottle. The Lab could make registering new accounts harder, but that is against their own best interest.

Simulator release 2023-01-27.577942 was rolled out last Tuesday, but quickly showed some annoying side-effects, so an emergency rollback was made. I posted a workaround on the Talk page (https://wiki.secondlife.com/wiki/Talk:LlReplaceSubString ) which you can use to prepare for the new feature. We'll see if it gets rolled out properly tomorrow.

Simulator release 2023-01-27.577942 finally brings a function for this: https://wiki.secondlife.com/wiki/LlReplaceSubString

That is a good solution @Mollymews! For coarse-resolution scripts I usually have a "seconds to full hour" routine, that I call at the end of the timer: float SecondsToFullHour() { list TimeStamp = llParseString2List(llGetTimestamp(),["-",":"],["T"]); return 60 - llList2Integer(TimeStamp,6) + ((60 - 1 - llList2Integer(TimeStamp,5)) * 60); }

lol, okay, if I query region_idle only once on startup, there's no wonder that it does not trigger 😛

I changed the script to use a single - regular - timer yesterday, and the effect persists. If I set the interval to a second, and write every completed 60 seconds into a log, when the region is empty, I only get about 32 entries. Strangely enough, I have region_idle detection in the script already, but it never fired. I need to check its implementation again.

I am using the sensor sweep as a fine grained secondary timer. The main timer is on an hour loop. Yes, I know I could have done it differently, but for now, that is the setup. llSensorRepeat("", NULL_KEY, AGENT, 0.1, 0.1, 1); I use this statement, along with the no_sensor event, when I noticed something odd. If I am in the same region, no_sensor triggers about once a second (a little less, since a lot is going on in the script). If the region is empty - devoid of any agent - the triggering speed halves! I assume the Lab has inlcuded some mechanisms by now, to slow down certain stuff when nobody is around?

Yep, seem to be back.

I reach out to each and every customer myself, a few days after their purchase. My products require setup, and while I did an extensive manual and some videos, some customers still struggle with the setup. So I prepared a notecard, thanking them for their purchase, and offering assistance should they require help. About 5% follow up on the notecard, and once their issue is resolved (often it's even a suggestion or idea they have) I ask them if they could leave a review. Most do, some say they never review and that's fine by me as well. Most of the people who leave a review after this leave a 5 star review. Not a single one is paid for. I am sure there are paid-for reviews. Some merchants even state it in the product listing that you get a certain percentage back if you leave an honest review. But I doubt (and hope) that the problem is as widespread, as you fear.

As a merchant, I see the danger more in negative reviews from competitors.

Though tbh, I (as a merchant who gets many reviews) fear that the name in the email is merely an oversight on behalf of the devs, and will go away sooner or later.

This is the email you get (emphasis mine):

@RyokoTensaki Can I place one of my trackers somewhere on your sim? For the past couple of months I am doing some research on the issue and have trackers on 5 sims already, in order to spot movement from Sim to Sim. Right now, I have a list of 297 confirmed roaming bots already - about 20 new ones in the past 4 weeks.