Scum Pond

Anybody use any jetbrains products? I personally use pycharm almost exclusively. I want to see if there are people who use it before I make an extention for LSL syntax highlighting. Disclaimer: I am a slacker that can't be asked to do most things, so this is probably an empty promise.

I love you... marry me. This was it.

I don't know what I'm doing wrong, thanks for your help beforehand. Excuse the simplified code, but the real code is self-made and I plan on selling the result, so I can only be vague with it. I have a json file sitting on a server with utf-8 characters in it. I am able to get it back and parse it with llJsonGetValue just fine. Firefox is showing me the raw strings with the correct characters, the headers (according to Firefox) are "Content-Type application/json", and my whole webserver is utf-8 encoded. However, when I do something simple with it like llOwnerSay the body of the llHTTPResponse, it's ascii encoded. For example, if I put "Я" in the server json, when I llOwnerSay it, it comes out as "Я". Using an utf-8 to ascii converter, confirms that to be the case. SL is parsing the URL->utf-8 encoding correct in the same json, just not the string. More detail to the example, this is file copy/paste from a Firefox request to the same endpoint's response (from the raw tab): {"text":"Я","site":"https://www.mysite.com/API?query=%D0%AF"} Code for the request: key http_request_id; default { state_entry(){ http_request_id = llHTTPRequest(https://www.mysite.com/utf8.json, [], ""); } http_response(key request_id, integer status, list metadata, string body){ if (request_id == http_request_id){ llOwnerSay(body); } } } What I get out of an llHTTPRequest body: {"text":"Я","site":"https://www.mysite.com/API?query=Я"} Doing this: default { state_entry() { string json1 = "{\"key\":\"Я\"}"; llOwnerSay(llJsonGetValue( json1, ["key"])); } } Returns just fine: [19:05] Example Object: Я Doing this: default { state_entry() { llOwnerSay("Я"); } } Also returns fine: [19:15] Example Object: Я The parsing of the URL encoding makes me think that the llHTTPResponse function is parsing the information, is it also throwing it through ascii encoding? The wiki for llHTTPResponse says that utf-8 should be done server-side, which is what I'm doing. Does llHTTPResponse encode application/json headers as ascii? If not that's not the standard (see item #3). What am I missing or getting wrong? SL is driving me nuts, I swear.

Having had a store a while ago, it's a royal pita. Especially if you have a ton of items to make vendors for, and care about your brand. Using the key for the new vendor would look like crap and would even be false advertising. And don't forget the MP listings... jesus.. the MP listing alone would drive me crazy.

Breaking apart means separate vendors for each item (with all the configs like item name and price), possibly new pictures (and the editing) if the maker cares about how they are perceived, possibly making multiples if they want to allow different permissions, changing all the items to copy/no-trans to align with the rest of their store, etc. Or else they just take the items away from being sold, which is work and future money down the drain.

Because a drop-in vendor script replacement for gatchas that is within the proposed rules is easier then breaking everything apart and making it all separate.

txfer allows to sell, which is how you make more money then what you put in when you get a rare

lol blog update clears things up like silt in a lake

$$$$$$$$$$$$$$$$$$$ Apple has a literal raft of money that could make an aircraft carrier, the Lab does not have Apple money to sit in litigation hiring more lawyers because it's fun and they're bored.

if you're a scripter and not currently thinking about a way to make a vending script to do gatchas within laws and LL rules in a friendly manner, you obviously don't like $L

You have to admit tho the sh*t EA (esp in FIFA) was getting away with in lootboxes was crazy shady.

You already can't go where you want, sim bans and gaming sims are a thing. You already can't do what you want, agepl*y restrictions are a thing. Adult sims? Need to verify. But yeah let's just shut it down. Turn the lights off the world is over.

If some person/group doesn't understand about selling other ways after it's literally been banned, the promise is moot in the first place. F*** them.

put it different scripts and llMessageLinked the scripts

What would make a creator, other then the way they are perceived, care about user lockout? Snipers would create traffic. F***, bot neo-gatcha snipers could be a thing.. In fact I'll bbl I need to do some scripting lol