Jump to content

Shuichi Shinji

Resident
  • Content Count

    49
  • Joined

  • Last visited

Everything posted by Shuichi Shinji

  1. Yes, of course you are right, I am terribly terribly sorry.
  2. Works for me again as well. Thank you for asking and maybe it was an oops, who knows.... happens ^^ @Kacey Delicioso It was not an SHX issue because other scripts requesting stream info also didn't work. The streams themselves worked, but not the stream info (if requested by script, i.e. from an SL server IP, not a user client IP... because the latter also worked). And it was only streams from this stream provider as far as I know (and maybe only a few), so assuming it was something on their side was justified. It was definitely no SHX issue and no USER ERROR. And announcing song titles i
  3. Thank you for asking. The cause remains unknown, though. What's the actual difference between the stream that works and the others, apart from public/private? Or, what effect does public/private have in regards to answering an HTTP request? And even then: why did it suddenly stop working? (Not blaming or pressuring you, just curious what caused it.)
  4. Do you know if the other streams work on those boards, too? I can access classicrock109 just fine with my script, but not the other ones. Would be interesting to see whether they work or not on the boards. They do work from a browser.
  5. I don't think that public/private setting has any relevance here. Getting the stream info in a browser works, getting it in SL doesn't. Both send a HTTP request including the URL and some headers before. Additionally, the "client" IP is different (actual client IP in case of browser, some SL server IP otherwise). So the logical conclusion would be that something is blocked on the server side, either by IP or something in the headers, probably user-agent or another header indicating the request is coming from SL. Maybe ask the datacenter, especially if they have done something like that in the
  6. I tried it too and don't even seem to get a reply at all anymore. Edit: After I setup my script to not try Shoutcast v2 first, but v1 imeediately, I now get the same error response as you. Possible other reasons why it doesn't work in SL could be: additionally sent headers, so the request becomes to large and is rejected by the server SL being blocked by user agent - previously it was possible to spoof the user agent, but not anymore and maybe the server owner blocked requests coming from SL for their sheer amount (not sure if Chuckles Orfan has any influence on that, maybe on
  7. That's great news, thank you very much :-)
  8. For me, it wasn't popular products at all, so I doubt this is what was triggering it. 3 of them were rather new and the other one had only 12 sales so far. However, they've all been in the same category and were also related products. Other related products that were almost the same and also listed at the same day were not affected, only the variants that included the same script were. Since I didn't lose any reviews and only a few sales, I relisted them several times - now without adding any keywords, they've stayed and were not unlisted anymore. Since the 4 items with the same script also ha
  9. I don't think it's that because I renamed almost all of my listing names (adding FULL PERM) to the name, and only 4 were unlisted, and only for one of them I didn't change the name. Now I wonder whether I should file a ticket, too... I already relisted the items manually and there were no reviews on them yet. Did you (any of you) have to mention the listing IDs or did LL find out themselves which ones to restore?
  10. Ok, I admit, that first made me chuckle... but I think, there is a slight difference between a company that offers a service used by thousands of customers, some of which pay for it, and ensure its smooth operation - and a hobby scripter (however professional his work might be) who is on his own and has got a RL and didn't even break these things himself... But also LL consists of real people (yes, I heard) and mistakes happen and they are working on it, even if we don't hear much. And yes, this issue is a pain in the ass and I can understand anyone who is upset, especially if selling in
  11. Is the unlisting still happening for others? My 4 relisted items are still there, albeit without filled out Features and Keywords, so it would be good to know if they are there because of that or because it's not happening at all anymore...
  12. As I wrote above, it seems to me that relisting without making it active yet or relisting without adding keywords might work. Whether it's a good idea in case of a potential rollback or recovery of the lost listings by other means is another story... Did they give you no hint what to do.. except "sit back and wait"?
  13. I have relisted one of my items once again, but without adding features/description/keywords, but set it active and also opened the MP listings window in the viewer. The item is still there after hours - and so are my items that are inactive, but with features/description/keywords. So my guess is as follows: - something in features/keywords triggers this - it can't be the description because I use the exact same description in 2 other listings that are still there - the listing needs to be active - opening the MP listings window is not the cause - it can even happen without being
  14. Well, they found a good fix last time with the HTTP request issue with streaming servers, so I still hope for the best ^^ I relisted one item again and activated it after filling out all details (again)... but I still avoided opening the MP listings inside the viewer afterwards.. and so far my listing is still there... However, I don't dare to open it now to see if this really is what causes the listings to be disassociated :-) Edit: Now it vanished, without me opening the MP listings window.. but only the one that was listed/activated.. the others I relisted/associated are still there...
  15. Yes, mine as well. I relisted them again, but did not set them active again yet (they appear as unlisted in the web interface, but they are associated), and also didn't open the MP listings in the viewer since relisting them. So far, they are still there...
  16. In my case, that's not true - only listings containing one certain script (streaming server related) and exactly those listings, no others, were affected. All others of my items, also newly listed ones, are still there. I mostly sell full perm scripts, so none of these items contains anything "no copy" and they are ok. Also, the other contents of the affected listings were used in other listings as well and without issues, so they are likely not responsible. Considering that Saii from SHX is massively affected, apparently also Vea products and other media-related things, I don't think thi
  17. I am having the same issue, although it only affects 4 of my listings. All 4 contain the same script (although in different versions) which is requesting music stream info. None of my other items uses this script. Maybe it's just coincidence, though... Edit: See also https://jira.secondlife.com/browse/BUG-202640 which seems to point in a similar direction. Another edit: I relisted them because I thought it was due to the issue with items becoming unlisted when the inventory has not fully loaded yet, and they became unlisted again (with a fully loaded inventory)... so better save the
  18. You can apply the update because the change is grid-wide now, not just on Magnum anymore, As for the tip jars, I updated mine (you can look me up on MP; I won't further advertise here) and there are others in this thread mentioning to sell tip jars, so they will also be a safe bet ^^ One is even using my streaming script, but seems to have updated it himself, as the actual change is pretty easy... Edit: I updated my full perm tip jar scripts, intended for tip jar creators; I'm not selling tip jars myself.
  19. You're welcome ^^ And you can try any v2 server too, it seems.. they all seem to support the v1 way now as well... you can maybe try by commenting the v2HTTPRequest line (not sure if that's enough because I don't know your script, but you can try).
  20. Oh yes... that's the line you still have control characters in. You need to change the first line into: v1HTTPRequest=llHTTPRequest(URL + "/7.html",[HTTP_USER_AGENT,"XML-Getter/1.0 (Mozilla Compatible)"],""); (and of course no space after "/stats" in the 2nd line) You can also use something else than "XML-Getter" in the first line ebcause it doesn't get XML... but it doesn't really matter...
  21. Sorry, that wasn't what I meant... just add the line I posted before the line you posted in your script, please... and it will print the value of the URL variable in local chat. In your line, I can only see the variable, but not what's in it - the stream URL, of course, but maybe additional stuff that doesn't belong there.
  22. You could ad the following just before llHTTPRequest - this outputs the URL in local chat, so we can see if it contains anything that doesn't belong there: llOwnerSay( "'" + URL + "'" ); You can just post the printed line here... Another thing would be to not use "XML-Getter" in the user agent, but something shorter. This was my issue, but it's actually got nothing to do with control characters, so this might not be the issue here, but could still be good to keep in mind.
  23. The underscores in HTTP_USER_AGENT do not matter - they have to be there because that's an LSL constant. There must be no underscores in hostnames in the URL string (and also no spaces, newlines etc.). I tested your stream on a Magnum region and it works fine. To find the issue, I had already asked for some simple checks; maybe Chloe can help you doing them. I know I am not Oz, just trying to help ^^
  24. I guess creators are hesitant to put an update on MP already because the update would not work on non-Magnum/Cake regions yet, only after they are rolled out grid-wide. Of course they could sell both versions as one package (I do that with my tip jar scripts), but who reads instructions and uses the correct version ^^ Christina tested the Lastat board on a Blue Steel region, so of course it still worked there (who knows why her SHX didn't work). Saii already offers an update for SHX - and for other products, maybe wait till the server change is rolled out grid-wide or contact those creators to
  25. Thank you very much for the update and best wishes for your first life things which are most important ^^
×
×
  • Create New...