Phil Deakins

No. I'm saying exactly the opposite - that everyone has his/her own Second Life, and nobody needs to "eff off and go join Tinder" because they don't share BilliJo Aldrin's view of Second Life. First she said that "its YOUR second life" and followed it by saying that all those who have a particular Second Life that they choose can "eff off and go join Tinder". In the space of a few lines she totally contradicted herself. That's what I pointed out.

Make up your mind. You want it both ways. Either it's my Second Life, in which case I am free to feel deceived if that's what I choose, or I can "eff off and go join Tinder" because it's not my Second Life. Nice try, but you can't have it both ways.

I'm still leaning towards my previous thought. The 4-byte (assuming 4 bytes) integer that is used for an account's flags has plenty of spare bits for flags we don't know about, and one of them has been, or is still being, used for other things, such as being thought to be a bot, perhaps from ARs. When agent_automated is requested for an account, instead of ANDing the flags with 0x4000, it is ANDed with another number that examines 2 of the bits. Anything > 0 indicates either scripted agent, or the other, or both, and is returned as scripted agent. It would fit with being able to change the status in the Scripted Agent Status page, and it sticking as 1 or 0. For that page, only the 0x4000 bit is ANDed. And it could possibly fit with my false positives, especially if individually they were ARed rather than seen together with other ones. It may be an old flag that is no longer used, but any that were set in the old days remain set. Bots and Picks.

The 4 remaining false positives have never had anything changed about their account. They are just 4 of many that I created way back and used only for the purposes they were created. Wicked's account was changed a long time ago, when it was briefly a Premium.

We have cat bots now?

Well, I got a reply on the ticket, but not what I was looking for. It was as I thought - a support ticket is a request for a fix the account's problem, and that's what it got. Wicked Leigh is now not returned as scripted agent lol. However, my JIRA attracted a response from Maestro Linden. He asked me to take each of the false positive accounts over to Bellisseria to see if they could get in. That's how I discovered that Wicked Leigh is no longer a scripted agent lol. The other 4 can't get in. So we may make some progress on finding out what causes the false positives. I'm still leaning towards my current theory that I posted on the previous page, even though Wicked Leigh was never used as a bot, at least not after traffic bots became illegal.

I have a high-tech security system that would be ideal for it

Seriously? It is futile to suggest such a thing.

I opened a support ticket yesterday for one of the 5 accounts that are wrongly returned as scripted agents, hoping to find out what the cause is. I'm not bothered about getting an agent's flag changed, which I think is what a support ticked would be for. I'm only interested in reporting a bug. It is troublesome for SL that AGENT_AUTOMATED returns false positives, and must be regarded as unreliable. If it's a bug, then surely a JIRA is the way to go. But if it behaves as intended, then I think we need to know why it does it. I've developed a very rough idea of what might possibly be causing it, but I do think we need to know. ETA: Incidentally, there isn't a category that's even remotely suitable for a support ticked so I has to choose one that has nothing whatsoever to do with it. Maybe it won't even be accepted.

I doesn't mean what you are implying. It means 'of one mind'; i.e. multiple individuals are of one mind about something. I am unanimous about that

TIL that, although banlines only go up a short distance, they are actually effective all the way up the parcel column. I was helping a customer, who told me that the my security device allows another avatar in the level because it's in the white list. But after it's logged out and logs back in, it lands outside the parcel, and she thought that the LevelGuard was doing it. She TPed me over and I landed outside too, as did an alt of mine. This was on and around a platform way up in the sky. It turned out that she had banlines turned on. They didn't prevent avatars from moving onto the platform, but they did prevent them from landing there. So banlines have an effect all the way up the parcel column.

If LL's policy on scripted agents has changed since they introduced the scripted agent status, then I've missed the change. It wasn't a requirement back then unless they were on land that was set to show in search.

So am I? lol

I certainly will. I haven't written all these posts only to keep quiet if I find anything out

Sorry about what? The laugh? I thought it fit beautifully I've submitted a support ticked for Wicked Leigh, hoping to find out why it happens. There was no remotely suitable option in the Account Issue list and I had to pick one that's unsuitable. I hope it goes through.

A thought is meandering through my mind I did use a lot of bots at one time, and I'm wondering if the false positives accounts were reported and flagged back then as individuals. I registered some obvious ones but not others, and odd ones might have been reported. A Linden might have simply flagged the reported one, and not looked for others. It's just a thought. @Silent Mistwalker I'm back to not altogether ruling out the bots possibility

I don't really see a problem. Since the 'scripted agent' status came in a long time ago, there have been many posts about us not being able to recognise them. The posts were about bunches of avatars that appeared to be traffic bots but there was no way of knowing for sure. Of course, traffic bots wouldn't be registered as scripted agents, or they wouldn't be traffic bots . So what difference does it make if a bot is registered as such or not? There is no requirement for bots to be registered as scripted agents. It's not against the rules for them not to be. I think that LL introduced the AGENT_AUTOMATED option so that people could report bunches of bots that appear to be traffic bots but aren't registered as scripted agents, instead of reporting all groups of avatars that just may be traffic bots. It's a time-saver for LL

I don't think that bots or no bots is behind it. If LL has a system where known or suspected bots were flagged somewhere, and it's being looked at when returning agent info, so that matches set the AGENT_AUTOMATED flag when it's requested, a lot more of my accounts would be flagged like that. When I used bots, they were used in much larger bunches than a mere 4 or 5, and they would have been flagged. But I am leaning towards the idea that something from the past is checked when AGENT_AUTOMATED is requested, and, if matched, bit 15 is set for the return but not actually in the account's data. The account page says 'human' but the returned agent data says 'scripted agent', so it's looking like the code checks something else, and modifies bit 15 accordingly when returning the requested AGENT_AUTOMATED data.

That the bit was allocated for some reason in the dim and distant past, and then forgotten about? That's what it's looking like to me. And it's still effective because registering and deregistering doesn't fix it. If I register a false positive account as a scripted agent, and then deregister it so that the account says it's controlled by a human, the flag is still set (scripted agent) when AGENT_AUTOMATED is returned. But thinking about that, where does the account page get its information from when it says that the account is controlled by a human? Is it the same database that llGetAgentInfo() gets it from? If it is, they can't show different things OR something is actually setting that bit in the process of sending the agent info. I only have 2 accounts that are new enough to have a Resident last name, and they come back ok. But it's such a minuscule sample that we can't read anything into it about the age of the accounts. We're not going to get to the bottom of it, and it's up to LL to figure it out - if they actually want to. They should because it's an honest-to-goodness bug.

It did jog my memory, thank you. In fact I went through that process myself. Just this account though, none of the others.

Not both ways, but Peter knows mine now. I have around 70 accounts and I've only tested around 25 of them. I don't see any need to test the rest. I could test them but it would a daunting task as most of them would log in to various parts of SL and I would have to bring them to my place. I think that what I have is enough I did set one of the false positives to being a scripted agent, and then back to being a human, but it made no difference. That's a bit odd really, as setting and resetting the flag ought to have left that account's bit reset. The account has been logged in multiple times since then, and it's still returned as a scripted agent; i.e. that bit is set. I can see it. Two of the false positive accounts were created in 2007, and 2 were created in 2010. Wicked Leigh was a paid-for alt. I have many other accounts that were also created in 2007/8 that were actually used as bots. Not the 2010 ones though. I have plenty of those too but they were created for their Picks. In other words, there is no similarity between them, except that they are old. I haven't tested all my accounts but, of the ones I've tested, other accounts similar to those aren't returned as scripted agents. Maybe I should test all my accounts and check their creation years. I've never heard of that. Whatever the reason, bit 15, the one that's used for AGENT_AUTOMATED, was or is being used for something else, and since I tested setting and unsetting the scripted agent status of Wicked Leigh, without curing it, it seems like it's currently being set for some other reason, which itself could be an old reason that's been forgotten about. ETA: I logged more in and found another one - created in 2007. White I was doing it I found many that were created in 2007, many in 2010, and a few in between, that weren't wrongly identified as scripted agents. I also found a couple that were correctly identified as scripted agent.

This is interesting. I was contacted by someone who has been running scripted agent detectors for some time. The one test that I hadn't done was test the false positive avs on other land. I couldn't imagine how the land could make a difference, and it doesn't. I took my false positive avs to his detector and it also wrongly reported them as scripted agents. Then I wondered if it's something to do with just my accounts, but he has also detected false positives. Nothing like the percentage I have, but false positives just the same. They are out there........lurking

Love asked that question in another thread. Of the 4 of 16 that were wrongly identified as scripted agents, none had been logged in with Speedlight. On the other hand, some of us who were not wrongly identified as scripted agents, had been logged in with Speedlight. One was logged in with Speedlight at the time I did the 16 avs test, and it wasn't wrongly identified as a scripted agent. So I've come to the conclusion that it's nothing to do with Speedlight. Apart from me, they had all been logged in with bot software in the past. Most of them were logged in with bot software for the test, but only 4 of them were wrongly identified. So bot software isn't the reason either. At least not the bot software that they've used in the past. I've only ever used my own bot software for any of them. Even if it is something to do with Speedlight, bot software, or something else, bit 15 wasn't available for a scripted agent flag, so it's bugged.

It doesn't exist. Not for you. But, as we have seen in this and other threads, it does exist for some people. Whether or not their annoyance is justified is nobody else's business. It's their world, not yours.

That's how this started lol. A few days ago, a potential customer just wanted a means of removing bots, so I added it to my LevelGuard, just for her. Since she has a whole sim, the LevelGuard was ideal. It didn't make it into my normal version that's on sale though. But I might add it later.