Jump to content

Sayrah Parx

  • Content Count

  • Joined

  • Last visited

Everything posted by Sayrah Parx

  1. Maybe you logged into the beta grid?
  2. The additional risk is that it could happen at any time, on any day, without more than 5 minutes notice. It's bad enough to only get 5 minutes notice within a certain time window on a specific day. I think a good rule to start with would be 10 minutes warning for every hour in the window. So a during a 3 hour window there should be at least 30 minutes warning. A 24 hour window should have at least 4 hours warning.
  3. Sandbox Island is a main grid AWS region that looks good for testing. Anyone know any others?
  4. I've asked a few times in the past for the maintenance restart warning time to at least be doubled, from 5 minutes to 10 minutes. I don't understand why it would be a problem for the rolls to end 5 minutes later, or to start the rolls 5 minutes earlier if they really want it to end at the same time. It is about having respect for the customers who are paying for the regions, and the people who manage the regions for the people paying for them. I'm not really sure that the employees understand that people are paying for this, and that it's not just their personal sandbox that they get paid t
  5. I think it's important for SL to not be tied to a single cloud computing service, regardless of how people feel about Amazon. Imagine if people in Europe could choose to host their estates on a European service partner, to have less latency for Europeans.
  6. Your friend could only cash out L$ sale proceeds through a verified PayPal account regardless. So you're better off selling L$ and cashing out the proceeds yourself, and then sending them money directly through PayPal instead of going through Second Life/Tilia.
  7. For anyone wondering, it looks like main server regions will only be restarted if they've been up for 10 days, since there was no RC roll last week. It would still be good to know if anything is being rolled to the RC regions this week.
  8. I wanted to buy a really cute top a few months ago, but didn't just because of the unhideable brand name in the center. It wasn't even like a real logo or anything, it was just in a font and looked like it took them 5 seconds to put over the texture. It's such a waste when low-effort, unhideable prominent branding ruins something nice for no real reason like that. The strangest part is they did take the time to make the text white on dark colors and black on light colors.
  9. Wow, you're right that "Sandbox Astutula" and "Sandbox Pristina" are premium only. I couldn't try "Sandbox Verenda" because it's offline. It seems like "Sandbox Exemplar" and "Sandbox - Weapons testing" are gone altogether. But Nick is right that "Sandbox Wanderton" is still good. Scripts are only "off" at the parcel level and not the region level, so you just need to be at least 50 meters above the land mesh (at least ~76 meters on Z).
  10. It's definitely hard to find a good sandbox there to test things, hopefully this helps: http://wiki.secondlife.com/wiki/Preview_Grid#Regions_on_Aditi
  11. That's correct, it would technically be possible to change anywhere, but mainland is controlled by the Linden governance team and the mainland region settings are almost never changed from the defaults.
  12. It means that the ranges for shout, say and whisper are getting turned into region settings like water level. Settings like that normally aren't changed from the default on mainland, but could be changed to custom values on any private region by an owner/manager. The ranges will probably stay at 100, 20 and 10 respectively on any mainland. It would allow any private region to not be consistent with the ranges in the rest of SL, so you would have to check what the ranges are every time you TP into a private region.
  13. That's why any new larger ranges need to be on a new separate option that can be turned off, instead of creating the ability to change the current ranges. It would be great to be able to turn off the shout and say range in the viewer as separate options too. We don't want estates to come up with their own ranges for everything. Instead there should be viewer options to hear within the current estate, region, parcel, shout, say and whisper ranges. New options for estate, region and parcel should also obey vertical limits according to the viewer settings, i.e. max vertical range should be sh
  14. You're right that the visibility in the viewer of who is in chat range, and what the chat ranges are, isn't going to be the issue. The issue will be having to check and memorize the local chat thresholds every time you enter a new region. That is what people will have to get into the habit of doing before anything else. It will be a nightmare to have that as a constant concern, and it will make people hesitant to communicate in local chat. I'm sure that's not the intention, so I hope you will reconsider making any of the chat ranges variable by region. It would also be good to know what p
  15. Making chat ranges for whisper, say and shout inconsistent across SL will only make things worse. People would not be able to trust local chat at all. It would be better to have new message range types for estate, parcel and region chat, and allow people to decide if they want to listen to any of those new three and choose which of the six ranges to send on by default. That way someone could send on estate, region or parcel, but if a listener has those off then it would still check if they were in shout, say, or whisper range.
  16. It depends if the name is directly in a message from the script, or if it's in the footer of an offline message. The script probably gets the account name when it's rezzed and keeps it without checking again. So in that case you could just rez a new vote box. If it's a message from Linden Lab saying "Sent by Old Name", that could take about a day or two to switch to the new name.
  17. It's good to see them trying. I recently had a friend request sent to me get dropped due to the cap and only found out about it from the offline e-mail. Group invites may also get capped and dropped. There's no way to accept either of those from the offline e-mails. The idea for group notices was to have it part of group settings and not from a script. Many of us have already posted our criticism of llTargetedEmail. But it's also good to see a new focus on using e-mail for messages, because communication is so important to the economy. Anything that can reduce reliance on the capped sto
  18. It's great if you have a way to edit others' objects and have no other way to contact them. It's a great way to be sent offline messages and notices, after the offline message and notice cap was reduced 40% from 25 to 15. For most groups, it would be great to have the option of notices only being sent to e-mail when not logged in for that particular group, in the same way there are options for receiving chat and notices for each group. If sending e-mails is better for the SL infrastructure than storing offline messages and notices for the next login, then this seems like a great first step.
  19. It's very strange because it's something I thought would be great for a long time, but it doesn't seem to be planned well at all. As a general concept, it's something we've needed for a long time to be able to reduce offline notices and IMs, but the implementation looks terrible and practically useless for most situations. Now that we're finally aware of the attempt to make something like this possible, I imagine that any feature request would be met with "we're not going to do _____ to make it actually worthwhile because we've painted ourselves into a corner with how we've already implement
  20. That's really interesting. It probably means that the new simulator support is to make it possible for real avatars to communicate with the mobile clients that are connected to some other service.
  21. When you use something completely non-graphical like METAbolt or pikkubot, the avatar is the same and indistinguishable from someone using a graphical viewer. The avatar is whatever it was the last time you logged out.
  22. I was able to confirm in all of these that object_rez doesn't occur with an object that has on_rez: Featherston Chapel Bolsena Clarabella Red Light Center Notteterna Creole Tranquil Dream II Animus City Rain Song Aladonia Island Raine Lake Epimetheus Envar I wasn't able to confirm or deny in Alexandria Falls due to not being able to rez anywhere. I was able to find that it worked in Playa dela Seduccion and Cape Hatteras. Maybe Playa dela Seduccion and Cape Hatteras have been restarted recently or something else happened that could be a clue.
  23. I was able to get access to the six "_____ Sandbox 1" and "_____ Sandbox 2" regions that are on 537423 by joining the Second Life Beta group, and both events work as expected like they do in other 537423 regions like Venrigalli, Sirrakuk and Nadelhorn. Still no change in Toroge, Fearly and Korzun.
  24. I noticed it looked like you were testing object_rez without testing on_rez inside the rezzed object at the same time. So I tested object_rez with a non-scripted object and did get the object_rez event in those 3 regions. So apparently if the rezzed object has an on_rez event then the object that rezzed it doesn't get the object_rez event in those 3 regions.
  25. I confirmed that in Toroge, Fearly and Korzun, which are on 537423, the object_rez event doesn't happen. The on_rez event does still work as expected. But the object_rez event definitely DOES NOT work at all. I confirmed with the same test that on_rez and object_rez still work as expected in 536748. But I tested in Venrigalli, Sirrakuk and Nadelhorn, which are also on 537423, and both events work. So the bug doesn't seem to depend on 537423. But it's definitely a problem in Toroge, Fearly and Korzun which all happen to be on 537423. I would test in Magnum Sandbox A, LeTigre
  • Create New...