Ann Otoole

Josh Susanto wrote: >lawyer up Good idea. Where can I send my $L to make that happen? to the international association of internet lawyers and know-it-alls?

dude... they are fixing it. why not be patient?

lawyer up or stfu and let them find the bad code.

of course my avatar looks exactly like me.

Of course they work weekends. There has always been ample evidence of their working weekends. People just like to poke fun sometimes. I would love to poke some fun on his topic (humor puts out fires) but it is just too serious for that.

climb the stump baby

1. There is more than one team working to deliver features. 2. SLX served SL faithfully for years without scrambling the database. Short of LL banning third party marketplaces another shall rise. Period.

no. you roll the database back to last week and leave it alone. don't tell us to manually fix your database destrruction because whatever is doing it you still have in there until you roll it back.

why don't you do the responsible thing and close SLM until this is fixed?

eh... if it ain't making the tier then there is no reason to keep it. you don't need land to sell on marketplace anymore. however, bear in mind a lot of people do look to see if you have an in world store before buying. also matters when marketplace is dogging.

Sera Lok wrote: ... PLEASE upgrade the network, the servers, the whatever, to make this site function as it should. ... This sort of issue is not something to throw hardware at without a clear comprehension of why the problem exists. It could be a simple matter of database parameters slowing things down or logs filling up or the database having to constantly extend the space available. LL needs some expensive consultants in there and then act on the recommendations.

the message you received something perhaps?

so a few select merchants that magically have code that works are now going to consolidate all the hobbyists under their LL allowed umbrella? Very interesting.

They need a database expert to analyze what is happening. Good luck with that.

mysql is free. Oracle costs big bucks. you get what you pay for since Oracle bought out mysql. enjoy.

So basically the issue is the LL commerce team referring to something they in their minds called "magic box listings" in a manner that is different from what their paying customers refer to SLM listings which is what is on SLM. There are no "magic box listings". There are only SLM listings.

you realize LL told everyone to change the names because of search right? and now they are telling people they have to effectively relist millions of items. And there is only a matter of days to do this right?

Using Linux by chance? re: https://jira.secondlife.com/browse/WEB-4548?

exclusive like ripped game textures?

If that actually works then all we do is open magic boxes, copy to inventory, delete the scripts in the inventory folder(s), and bulk copy the folder over to the dd source directory. Maybe 10 at a time to make sure they get there. I'll still hold off a bit and see if the sky falls. In theory DD will be tons better than having to rely on LSL scripts that are subject to the whims of the load placed on the region from the other regions on the same host.. I hope it does work. I would love some good news for a change. Might even make me want to finish learning mesh and start making stuff again.

only one week to deployment lol.

so if this process takes 5 minutes per, someone with 500 products is expected to expend 42 hours complying with a commerce team idea.

Travel well Pamy. You are in the real SL now. We will all meet up with you in the future.

I think you read that wrong. Things will be business as usual except for DD items which will land in their assigned received items folder structure. I am still wondering how the existing magic boxes will be automatically converted. The idea we must manually convert is unacceptable. Every time I turn around I am faced with burning weeks on commerce team "ideas".

sounds like stream global is the outsourced support company and they have to log each read post with a service request.