Innula Zenovka

For over a year now, Tilia also have been payment processors for inworld-purchases in games made with the Unity engine, so it's not just an LL thing any more https://www.lindenlab.com/releases/tilia-unity-partnership

Tilia are payment processors. I pay money from my bank account/credit card to Tilia, and they transfer the funds to my US$ account with Linden Lab. I then use the funds in my LL US$ account to buy L$ or to pay Tier -- Tilia aren't involved in those transactions. They just help move the funds from my credit card to the LL US$ account, but Tilia don't know what happens to them after that. Similarly, when I cash out, I ask LL to transfer funds from my L$ account to Tilia, who send the money to my PayPal account. The basic idea is to separate off activities that are regulated by US federal and state licencing and reporting requirements for online cash transfers and have those all handled by a separate specialist legal entity, Tilia, so LL's accounts department don't have to worry about them, and so that they're kept completely separate from in-world L$ transactions between residents. To my mind, it protects resident privacy -- Tilia, who are subject to privacy legislation as it applies to financial services providers, are the only people with access to my First Life details,, but don't have access to any information about my inworld activities or transactions, which only LL know about.

Linden Homes use llTextBox for adding names to the access list, I think, and also for adding custom colours when you're decorating. When you need any sort of free-form input from the user, llTextBox is generally a much better way of obtaining it than is trying to explain to the user how to use the chat bar to input it on a non-zero channel, at least in my experience.

I don't use Firestorm very often so I don't know if the bridge is still part of the viewer, but I recall it is/was a HUD attached to one on the Center HUD attachment points. That would make it undetectable by script -- HUDs aren't visible to llGetAttachedList https://wiki.secondlife.com/wiki/LlGetAttachedList Nor can you detect what viewer someone is using (you used to be able to ages ago, but no longer. I agree with @Solar Legion -- this looks to me like a generic message that mentions Firestorm simply because that's the most widely used viewer.

I don't think the seated avatar flags were around in 2010. The lab keep adding flags to it, though, it's really worth keeping an eye on to see what you can read with it. I find it I use it all the time, for lots of different purposes. https://wiki.secondlife.com/wiki/LlGetObjectDetails

Depends what you're scripting, I guess. It's very useful if you're trying to keep track of, and coordinate, several mobile objects on a region, and it solves no end of problems if you're trying to handle (and animate) several avatars sitting on the same linkset. It also gives you access to a flag I find incredibly useful -- OBJECT_CREATION_TIME, which returns the time the original mesh of an object was uploaded or, if it's a regular prim, the time the original prim of which the item is a copy was rezzed. This is as unique as a UUID and enables you to know for sure what an item is, regardless of what it's called, and also to detect whether it's a genuine item you've made or a copy someone else has made.

However, since rolling back these features would involve breaking what's been one of the most fundamental and important functions available to scripters ever since I started in 2007 -- llGetObjectDetails -- thus stopping no end of scripted objects from working, I can't see it happening.

It's both strange and unfair that it mentions that I'm a scripter but not that you are, considering how much more active you are in the Scripting Forum than am I.

It says "As an artificial intelligence language model, I don't have access to specific information about users in Second Life or any other virtual world." That's another way of saying "I don't know," to my mind. When it does know about someone, it tells you: It gave me a very similar answer when I asked it about Prok, presumably because both inara and Prok are well-known bloggers. Long-term residents may be interested to know it's heard of Stroker Serpentine, about whom it's very complimentary. It has, however, never heard of Jumpman Lane (or, if it has, it's wisely keeping quiet about it).

I asked it for you

I think they float in water, too.

I know they're sometimes used to enforce bans on posting slurls and urls in group chat, for example, by automatically removing posting rights from people who break the rule. I would imagine they're used to enforce bans on swearing, too.

No, it doesn't have to be, but if someone wants to use a bot to moderate the group and has a house on Bellisseria, why should they have to buy or rent a parcel elsewhere simply to accommodate the bot, when it can live rent-free on Bellisseria?

You can hire bots to moderate group chat. I can imagine someone wanting to roll up their own bot to do that for a non-commercial group they owned.

Certainly scripts can see everyone on the region -- use llGetAgentList([AGENT_LIST_REGION],[]) to pull the uuids of everyone on the region, and then feed those to llGetObjectDetails and similar functions. I'm not sure about neighbouring regions, though. llGetAgentList shouldn't be able to see people in child regions. I've got an idea llSensorRepeat may be able to see them if they're in range, though llSensor can't, but I'm really not sure.

Thanks. But I don't see how what that has to do with using llHTTPRequest. Without a separate agreement in place (for e.g. as a sub-processor or vendor), there is no default right that any third party has to collect, store, process, or transmit a Second Life Resident’s Personal Data outside of Second Life." That's concerned with what the third party does with the data about the object owner's UUID and legacy name after they've received it, and stipulates that, whatever they're doing, they do without LL's consent. And if the receiving site does, despite this, store or process the uuid and legacy name contained in the x-headers, then it's up the resident whose data has been stored or processed to take the matter up with whoever is storing or processing it: Linden Lab cannot govern activities that happen outside of the Second Life platform. Where Residents determine violations happen outside of Second Life, such as when Personal Data is presented on third-party websites without their consent, multiple options are available. Every Resident is encouraged to begin by contacting the individual operating the site in order to achieve a peaceful resolution. This can take the form of a personal request using an email address they provide for this purpose, or by submitting a form (usually called a Data Subject Access Request) on their website to request your information to be removed. Other options may include contacting regulators to file complaints against third-party websites, their hosting providers, or their content delivery networks where the site operator or hosting provider cannot be determined. Residents of California can learn about their options here: [1] Residents of the European Union and the UK can learn about their options here: [2] https://wiki.secondlife.com/wiki/Linden_Lab_Official:Using_Personal_Data?_gl=1*1bxxpyb*_ga*MjAyMjYxOTM5Ny4xNjc1NTk1Mzk4*_ga_T7G7P6DCEC*MTY4MDI4MzI5MC40MjAuMS4xNjgwMjg2NjE4LjU5LjAuMA..*_fplc*bXQ3QlNNMXFVMFJsSnYlMkJ1RkxDS2c0MFlhSTM0bTBsQWJxN3ZGZk9NZlJLMGl0YW5MTDIxUEclMkZPbjh4Zm9OUXhLVGNyY2N4N1VLRE1uNnZTZVEydCUyQlk5Z3FVNmtwTzJOeUhmYXFJeVVnRGZ2TVBLT0E1S1BodWFYMHVNcHlRJTNEJTNE#Objecting_to_the_Use_of_Personal_Data Fair enough. How does this affect me as a scripter, so long as I'm not sending the data to my own website and, on receiving it, storing or otherwise processing it?

Can you expand on this, please? What are PII rules and in what way can llHTTPRequest() be said to break them?

Is that comparable, though? In SL, if people want to complain about something, rather than phone a call centre to harass front-line staff, they have to submit either Support Tickets or Abuse Reports, as appropriate. The reports are then passed to the appropriate team, who can triage and investigate them without keeping increasingly irate customers on hold. When someone from Governance investigates a complaint about an unregistered bot, it's going to take only a very cursory inspection of their account history to establish they're not a bot. Determining that someone is a bot would probably take longer but I think a quick inspection of their recent movements, Chat/IMs, and transaction history should soon satisfy an investigator if they're not a bot.

You can have 500 people on the region's allowed list, so unless your club is on a region that doesn't allow public access (not the best place for a club, perhaps) I doubt that would be an issue.

According to the LL post about it, When deny_bots is ON, all scripted agents that are not explicitly listed in the estate’s Allowed Access list will be denied access to all of the regions within the Estate. You don't need to ask the Estate Owner to give the bots Estate Manager status, just to add them to the Region's Allowed Access list.

Yes, I agree that "there is a bit of a panic now that is not entirely rational always." It's fanned, to my mind, by speculation in these forums about hypothetical wrongs hypothetical bots may or may not be committing, whether now or at some hypothetical point in the future. If anyone has evidence that people who run bots are, in fact, engaged in data scraping or whatever, then let them take it to LL and, if appropriate, the relevant data protection authorities in their jurisdiction,. If they don't have any evidence, then perhaps that means there's nothing to worry about. Scripted agents -- bots -- have a variety of uses, some legitimate and some, at least potentially, illegitimate. To my mind, rather than worrying about bots in general and what they might get up to, given the chance, it would be a better idea to concentrate on defining what these illegitimate uses might actually be, how evidence of such illegitimate activities might be gathered, and what LL might be expected to do when presented with it. If people have evidence that LL's Terms of Service or Community Standards are being broken, or criminal offences or civil torts are being committed, then let them present that evidence to LL or to the relevant authorities. If people are worried that an unknown avatar's behaviour suggests they're an unregistered bot, a simple visitor tracker should provide sufficient documentary evidence to support an abuse report, so LL can investigate the matter further. Otherwise, let's please stop worrying so much.

In order to protect residents' privacy we perhaps need a scripted tool that enables other residents to track their movements round the grid, down to the exact coordinates of their destination each time. What could possibly go wrong?

So you say, and yet no one, in the almost 20-odd years that SL has been going, has yet taken it upon themselves to offer such a service, though at various times people have certainly set up as SL private eyes, not just as role-play but also offering, for a fee, to find out what your partner is up, and I am sure I remember once reading about someone who offered virtual "honeypot" entrapments, so you could find out how well your partner behaved when given the opportunity to misbehave. And I've certainly known people whose vindictive and obsessive exes have gone to frightening lengths to track them round SL harassing them. The capability to do what you describe has been around as long as bots have but it's yet to happen. Personally, I'd rather try to deal with actual problems rather than hypothetical ones that could theoretically happen but, in 20 years, have yet actually to occur in the wild. The only two actual complaints about bots of which I'm aware in the current outbreak of concern are the publication online of highly speculative figures about people's marketplace sales, and the publication of some very badly indexed SL profiles in the same place (I had to struggle to find mine). Other than the fact that the website belongs to a business that runs bots for what seem to me to be perfectly legitimate purposes -- trying to identify regions where bona fide events are taking place, and trying to track regions on Belliseria with vacant parcels -- I can't see what the connection with bots is, They may be involved in grabbing SL profiles (I just don't know what role bots play in that automated process, but I guess at least they may provide the uuids to feed into whatever's pulling the profiles) but it's hardly a core part of the business if they are. What other than that do we know bots are doing that's objectionable? Not objectionable stuff that they might be doing, or might possibly do at some point in the future, but bad things they're actually doing right now? Turning up on people's land unexpectedly, certainly, though it's not just bots that do that, of course, and we do have land tools to mitigate the problem, but what else? I suppose we count ourselves fortunate that SL moral panics are about things like bots, while First Life ones are considerably more serious and sinister.