Jump to content

Shuichi Shinji

Resident
 View Profile  See their activity

  • Posts

    63

  • Joined

  • Last visited

 Content Type 

Everything posted by Shuichi Shinji

  1. Shuichi Shinji
    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"?
  2. Shuichi Shinji
    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 online - other items listed on the same region at that same time are not affected - so the region also doesn't matter - since many media-related listings are affected, it appears logical they also used similar keywords If I could comment on any of the Jira issues, I would, but I dunno who I have to bribe to be able to do that :-)
  3. Shuichi Shinji
    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... associated, but unlisted/inactive (the naming of these terms is a little inconsistent, I hope you know what I mean).
  4. Shuichi Shinji
    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...
  5. Shuichi Shinji
    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 this is a coincidence. I have no explanation for that, though, other scripts which use HTTP requests to contact a server are still listed, and I can't really think about a reason why only this one script of mine is affected. In your case, maybe there are different issues surfacing here, so your items vanish because of something else... who knows.. it's just a guessing game ^^
  6. Shuichi Shinji
    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 effort for now ^^ Another new and unrelated item I listed together with the relisted items is still there.
  7. Shuichi Shinji
    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.
  8. Shuichi Shinji
    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).
  9. Shuichi Shinji
    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...
  10. Shuichi Shinji
    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.
  11. Shuichi Shinji
    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.
  12. Shuichi Shinji
    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 ^^
  13. Shuichi Shinji
    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 see if they have an update ready already or whether they are even aware of the issue yet. If there is no update and you get no response, you can always leave an appropriate review, but as a creator myself, I can only ask for some patience - not everyone can reply immediately.
  14. Shuichi Shinji
    Thank you very much for the update and best wishes for your first life things which are most important ^^
  15. Shuichi Shinji
    As far as I understood it, the Magnum server version will be rolled out grid-wide eventually, so all SHX boards will break - or someone can convince the SHX owner to update the script... it's just one simple change after all. Otherwise, another product has to be bought and yes, many SHX users won't be happy about that...
  16. Shuichi Shinji
    That helps no one... I made some suggestions what you could try and check, apart from that I can't help any further... I just tried http://bigdaddys.digistream.info:20368 with my script which tries the following and all 3 work: http://bigdaddys.digistream.info:20368/7.html http://bigdaddys.digistream.info:20368/stats?sid=1 http://bigdaddys.digistream.info:20368/stats?sid=1&json=1 This is my request function call: llHTTPRequest( StreamReqURL, [ HTTP_USER_AGENT, "Stream/1.0 (Mozilla Compatible)", HTTP_METHOD, "GET", HTTP_BODY_MAXLENGTH, 16384 ], "" ); (HTTP_METHOD and HTTP_BODY_MAXLENGTH shouldn't be necessary here, but I added them for Icecast's HTML status page which is somewhat lengthy...) Edit: Second Life RC Magnum 17.06.29.327400
  17. Shuichi Shinji
    Yes, I read that too, but I don't see an underscore in the URL ("http://bigdaddys.digistream.info:20368") and none in the user agent ("XML-Getter/1.0 (Mozilla Compatible)"), that's why I was looking for another possible reason...
  18. Shuichi Shinji
    Is it still the same warning (control character) or something else? If it's the same, could you please post the line where URL is set, too? If it comes from a config notecard, you could check if there is a leading or trailing space or another character that doesn't belong there. You could also add an llOwnerSay( "'" + URL + "'" ); just before the request and post the result here... If it's a different warning, try renaming "XML-Getter" to something shorter - I had the problem that "Stream/1.0" works, but "Stream-Script/1.0" didn't because the headers became too long...
  19. Shuichi Shinji
    @Linnrenate Crosby There is a space character at the end of "/stats " which needs to be removed ^^ Using "/7.html" also works like it used to be for v1 streams. You can also try "/stats?sid=1" for the same as just "/stats", but with explicit stream ID or "/stats?sid=1&json=1" for JSON output which is easier parseable (there are LSL functions for it, see one of Oz's older posts).
  20. Shuichi Shinji
    Could you post the llHTTPRequest function call, please? Maybe the issue can be seen there. Checking http://bigdaddys.digistream.info:20368/7.html works, at least...
  21. Shuichi Shinji
    Do you still have spaces or newlines in the URL or newlines in the user agent?
  22. Shuichi Shinji
    @Lyndka Cochrane If you seach for "dj board shoutcast icecast" on MP, there are some alternatives on page 1 already (ignoring the also found SHX products). I don't want to advertise for any of those products and I haven't tested any of them, but at least one sounds as if it allows some of the options you need (multiple parcels, configuring by notecard), so it might be worth a try - we will probably try it in our club. I was seriously thinking about doing my own, but seeing the already available alternatives, I decided not to because it would be quite some work to re-implement all the SHX features (and you can be sure that even the exotic features are needed by some and requested). Maybe someone else really is going to do it or maybe an existing board already comes close... or both - it's always good to have some alternatives (as this issue now proves) ^^
  23. Shuichi Shinji
    I at least found servers where both variants work (see my above post) - from the link you posted, it seems they just support the v1 and v2 way of requesting stream info now, but not sure if every v2 server does that. Requesting it the v2 way also works (XML or JSON), but if the header gets too long, it seems you won't get an answer either way (which happened when using "Stream-Script/1.0" instead of "Stream/1.0" as custom user agent in my script). It's like living a little too close to the edge, so any way to shorten the headers or something else Oz mentioned they might have in mind, would be very welcome in a later update. For now, most servers seem to work again - after shortening the user agent string, I didn't find a server that didn't - so I am happy the way it works now and look forward to the grid-wide rollout (right now, old scripts throw script errors on new regions and vice versa). @sirhc DeSantis Breaking old content is not so good, but in this case I think, preventing hacks like the one that was used to get the stream info takes precedence. Anyone who is still active inworld, can easily update the scripts with the info provided here. If SHX doesn't get updated, I don't care much about its creator, but for customers, it feels bad because they have to buy something new now. Ok, there are already systems available which look good and are not too expensive (a fact which prevented me from doing my own SHuiX ^^), but I can already see the outrage once this is rolled out grid-wide. I hope I am wrong, tho, and I do support the current solution. @Oz Linden Thank you for all the work and effort to solve this issue with us
  24. Shuichi Shinji
    Apparently, the HTTP header just gets a little too long and omitting the custom user-agent is enough to keep the length within some limit. Using a shorter custom user-agent also works. So it's the header length again...
  25. Shuichi Shinji
    Yes, it seems that omitting the user agent is the only change required to make it work with this server. Maybe it doesn't like 2 User-Agent lines or wants it in a different format. I used "Stream-Script/1.0 (Mozilla Compatible)", but it worked before with "LSL Stream Info (Mozilla Compatible)" in the old hack (which I can't try anymore because of the spaces).
×
×
  • Create New...