Jump to content

Qie Niangao

Advisor
  • Posts

    10,758
  • Joined

  • Last visited

Everything posted by Qie Niangao

  1. Only old fogeys sort inventory. I stopped using email folders the day I joined the gmail beta, so many years ago. And yet, as a new scripter—and old programmer—it took me a while to accept that LSL has no concept of files or filesystem. (Closest it gets is read-only access to object Notecards.) Turns out LSL was just a bit ahead of its time:
  2. Interesting. Sit Target teleporters have been around for ages and they certainly do work across region borders, but I'm surprised they've changed since the wiki recorded back in 2009:
  3. Apparently I have SomaFM stations set as "land radio" on some of my parcels, which doesn't have much impact becaus I almost never have sound turned on myself, and my parcels don't generate a lot of traffic. It makes me wonder, though, how small this streaming world really is, if little ol' SL ever contributes noticeably to SomaFM's demand. Perhaps a busy event might draw a hundred avatars (or more, across several regions) and maybe most have streaming audio enabled, so if a stream usually gets just a few hundred listeners, SL could be a signficant factor, I guess. In contrast, if a stream got a few hundred thousand listeners, nobody would care what SL demand may come or go. So evidently the scale is smaller than that. Imagine we had to come up with a technical solution. I think Coffee is headed in a promising direction with: Six months may be a bit generous because any listener could retain the stream URL until it quit working, and use it anywhere on (or off) the grid. Suppose they "sold" a land radio script that took payment in daily increments (like, a year's worth in advance, say), where paid-up units automatically get a new working stream URL every 24 hours. Might that be viable? In theory, listeners on unpaid parcels could snoop those URLs (llGetParcelMusicURL() would need the landowner to be complicit to mechanically leak the new URLs, but anybody can get them inside the viewer), but I think a lot of folks would happily pay-up instead. Certainly more than donate now, right? Maybe this is trying too hard.
  4. I agree, with a couple caveats. First, I'd recommend carrying something like a smartphone everywhere you go, or at least a phone capable of both placing emergency calls and recording video, either of which one day may save your life or somebody else's. (A sim card is not needed to call 911.) Second, however, all devices need regular updates to reduce security vulnerabilities, and that means a reasonably up-to-date version of the operating system, and that tends to mean a pretty new device (or, in the case of Android, an up-to-date third-party ROM). [ETA: I meant to add (redundantly) that I'd expect most MFA implementations to (eventually) support authenticator registration by some means besides scanning a QR code, and then basic desktop browser-based authenticators work just fine without access to cams or scanners. Also, I would never push for SMS text-based authentication; security-wise it's pretty obsolete even though some places definitely still use it.]
  5. In SL, MFA is still optional, as is Microsoft's move to get rid of account passwords for now, but eventually passwords as an authentication secret will vanish everywhere. They simply do not work and never have. Long before the Lab makes MFA mandatory (if that even happens within the SL product lifespan), they'll surely get it working with any of the many desktop authenticator apps that can be enabled by text instead of QR code. (Or maybe they already have this, I didn't play with it that much.) For now I only set it up for an alt's account, just to ride out the first wave of bugs.
  6. It may be open to market research, but my guess is that they'd lose more Mainland business than they'd gain at this point. Bellisseria is a great illustration of how Mainland might have been, but while it's true that the orb & whitelist ban restrictions came to Bellisseria after it first opened, that all came quite early in its expansion, before many orb aficionados could establish full entitlement. Also, at that point, Bellisseria was under such great demand—further heightened by the new neighbor-friendly landownership policies—that it could easily absorb a few folks returning to Mainland for their augmented "privacy" role-play. Mainland itself is a very different situation now, with ancient orb-worship an entrenched religion of believers in the god-given property rights of pixels. If intrusive parcel and script settings were no longer available on Mainland, of course Estates could fill the demand, but I'd fear more than a few folks would just quit SL land ownership altogether, out of spite. On the other hand, if the Lab can convince itself that, net-net, more tier will get paid with a less explorer-hostile Mainland and more of the "privacy" market moved to Estates, they simply must do that. Two tangents: I don't recall the whitelist banline ever being other than 50m Above Ground Level. I vaguely recall the explicit "blacklist" bans extending upwards from 768 to 4096m when the build height was raised, but I'm not real sure about that history. It's possible that further development enabled by the cloud migration could make it much less expensive to run sparsely-populated regions. No idea where that may stand on the priority list for server development.
  7. I'm pretty sure, though, there used to be some enforcement against hair-trigger orbs. Not sure when we heard about it, but I'd guess sometime around when Zindra was created, and the reported penalty was only return of the scripts with a warning; I don't recall anybody saying a suspension was involved. Somebody should go to Governance (or Concierge?) user group to see what the Lindens actually think the Mainland policy even is now. I'd be surprised if there's agreement (and more surprised if they agreed that zero-warning kick-bans were just fine). As I usually post to these threads, it's far too late now to establish a meaningful "right to roam" policy for Mainland, but that once upon a time it would have made LL a lot of money over the years to limit the more restrictive access features (whitelist banlines, llTeleportAgentHome) so they'd operate only on Estates. For one thing, the pretend-privacy aficionados and proprietors of animatronic brothels, etc., would be paying slightly more for Estate fees than for Mainland tier, and more interestingly, Mainland would have been as visitor-welcoming as Bellisseria which has proven a very big draw (and, I'd suggest, not only for vehicle users).
  8. Once all bugs and other griefing vectors are fixed, some desperate ne'er-do-well might resort to vehicle abuse. Do let's hasten to prevent that at all cost, lest fun be had in the meantime.
  9. Of course you can always make touches ineffective, but you rightly want them to be impossible. If there will really only be a few destination buttons, personally I'd do the unthinkable and put a script in each button so I can move the script to a state with no touch-related handler, thus making it visibly unclickable. (Remember not to use touch_start in a state-cycling script; use touch_end instead.) Another option, needing only one script, would be to make the real, touchable button surface separate from the button label, and then to make the button untouchable shrink that touchable part and bury it within another part of the assembly until it should be touchable again. To be safe, this approach should also include the logic that makes touches ineffective, just in case somebody cams inside and manages to paw at the hidden touch surface. If hovertext is acceptable, there's always PRIM_TEXT as the "link" version of llSetText(), but maybe you wanted something else.
  10. I have no expectation that a "AAA game level designer" could do anything at all with SL, but just to be clear about Rod Humble's tenure, if anything he wasn't budget-constrained enough. It was his time as CEO that saw the Lab buy Desura, LittleTextPeople, and Blocksworld, launch Patterns and Creatorverse, and oversee the death throes of the earlier-acquired Avatars United. A whole lot of money and time was squandered back then.
  11. Just to show what I've been fussing with: which should be viewable on Flickr as a 360 view of 360-view spheres.
  12. Yeah, but the current issue doesn't seem to have anything to do with the IP of the audio content. Rather, they appear to be claiming some IP rights to the streaming service itself (as curators or something?), and anyway they're in a position to impose "terms" on providing that service. But I can't figure out how this benefits them. I get it that they're trying to defeat scrobbling* and so they poison the Shoutcast-standard Now Playing URL "<stream:port>/7.html" with a lame beg for donations (see, e.g., http://ice6.somafm.com/groovesalad-128-mp3/7.html ), and yet they expose those direct streaming URLs in their radio station directories (e.g., https://somafm.com/groovesalad/directstreamlinks.html ) with the rationale: So they don't seem to be insisting that one use their own (pathetic) web player, and indeed the direct stream URLs work just fine in a browser (e.g., https://ice6.somafm.com/groovesalad-128-mp3 ) so I don't know exactly what they're doing (matching user agent string? seems unlikely), and even more mysteriously, why. What am I missing? _______________________ *I also don't understand why anybody would want to discourage scrobbling / now-playing info, although I gather the EU banned Shazam which is kinda like scrobbling I guess? Do they also confiscate all Android phones with that magical ambient Now Playing local hash on background music? It's like lawyers are pining for the good ol' days of Napster lawsuits. I don't understand any of it.
  13. *blush* Well, I may have "elaborated" some. For the nonce, though, I'm still wanting to hide some specific stuff on those 360 images as TPVs do with Derender. It occurred to me, though, that the whole 360 object rendering process might be different enough that Derender can't exclude what gets into those images. So that's another conditional hurdle, the list now standing at: Does the Lab intend to merge 360 code into the main viewer branch? Will TPVs have that 360 code (either inherited from the main branch or on their own separate 360 branch)? Will Derender functionality work on 360 code in anybody's viewer? (Incidentally, ya know that glitch that happens sometimes where some random link of an object just doesn't show up? until, maybe, after you select the object of which it's a link? Not surprisingly, perhaps, that also occurs in some 360 images, of which I happen to have photographic evidence.)
  14. Yeah, but I'd take it further: Please let me decide what other parcel contents to draw while anyone's cam is on my parcel. I'm fine with the neighbour's fetish for hemorrhaging hippo hovercraft when viewed in the context of their very special parcel, but not so much on mine. Visitors may turn off my parcel-specific content curation, but give us a chance or give up on Mainland. (Meanwhile, though, may I please have a viewer that lets me hide one particular bleeding artiodactyla blimp whilst creating a 360 snapshot?)
  15. Does anybody know if other viewers will adopt the 360-degree snapshot capability? I presume that depends on whether it will be merged into the Lab's main viewer branch, as opposed to being stranded on a project viewer as it was for years, so do we know if that's the plan? The reason it matters is that other viewers offer Derender functionality that is absent from the Linden viewer (or, at least, I sure can't find it). That poses a real problem when trying to use the 360 viewer on Mainland where there's a lot of kruft floating overhead. That stuff is rarely visible with typical Mainland draw depth, but a much deeper than usual setting produces better, more complete 360-degree images. I'd sure like to hide some of that mid-depth stuff from my Mainland 360s.
  16. SomaFM may have some fantasy that Linden Lab is responsible for the streaming content to which parcels may link, but that's not true, and no more true than the fact Google may return SomaFM URLs or we might post one on social media. There is no streaming into SL, there is no streaming through SL, there is only streaming from URLs posted as a courtesy in SL's parcel metadata. Arguably viewers might be in a position to pay for the content they stream based on those URLs, inasmuch as they actually make a connection to the client machine's audio streaming libraries. SomaFM should take that up with Firestorm and see how far it gets. (They are, objectively, idiots—but to be fair, they're probably idiots with financial problems.)
  17. An object only has physics on one region, so any parts that extend into a region other than where it's rooted will behave as if phantom on that other region. (I'm not sure that's what you mean, though.) [ETA: Probably that's not what you mean, inasmuch as "objects... would be wholly in one or the other region", and if region crossings are infrequent it may not matter anyway, but nonetheless: common practice is to invisibly overlap the region border a few meters from both directions to make crossings a little smoother—which may still not be relevant, I'm not sure.]
  18. Meh. Every developer thinks their job is impossibly more challenging than every other developer's, and it's always somebody else's fault. Developing from or refactoring a large existing code base? It's always krufty "spaghetti code" written in an obsolete language by cavemen, and if only we could start from scratch it would be just a weekend's work. Sansar is a perfect example of what happens when actually starting from scratch: just watch those pages fly off the calendar while requirements drift into a backwater of market irrelevance. That said, SL avatars specifically have accrued so many layers of mostly incompatible functionality that it's now impossible to learn all the ways they can be visually and functionally broken, let alone how to fix them. A "newbie" after a few months will have stumbled on most of the failure conditions for their specific choice of avatar and can safely attend public events as long as they don't try a new head or skin or push the wrong shape slider, or any of the myriad other ways to uncover incompatibilities across the many strata of avatar customization detritus that we worship as Creator-blessed content.
  19. It's a good idea to get accustomed to the format @Quistess Alpha suggests because there are many LSL functions that take a list of parameters as an argument, and eventually in some script it's likely to matter how many distinct function calls get made, or whether all the parameters are likely to get set during the same simulation frame. Just a note about the IP address thing: if you're lucky enough to have an actual domain name such as stream.wqxr.org, by all means use that in preference to a corresponding IP address which will become invalid if, for example, WQXR changes streaming providers.
  20. Ah, yeah, AFAIK the Malwarebytes thing is unique to the problem @Cyrene Price describes of teleports failing only when returning to a region already visited during a login session. I see this thread is about teleport failures more generally, and I should have been more specific.
  21. This sounds like a bug found in Malwarebytes. Do you happen to use that? If so, can you see this jira? It includes a hint for how to configure Malwarebytes to behave nicely with SL teleports.
  22. Agreed that anything that actually blocks Linden waterway should be reported, and you should make a point of following up to see if it's been resolved. If not, enlist some friends to add ARs. (Governance claims that one AR is as good as many. It's simply not true. No fault of Governance, but Mainland generally needs residents to do more of the work to get things done.) The bad part is that there's nothing to be done about the cheap security systems. They cannot eject nor teleport home anybody who isn't actually on the owner's parcel at that instant (so if one gets caught by them, they're functioning "properly") and there's no formal rules about how long the warning interval must be except on Bellisseria.
  23. (I'm assuming "pop out" here refers to bringing up the Nearby Chat window.) I don't know BD, but I expect it's like Catznip and the Linden viewer: just hit Enter while mouse focus is on the world. Ctrl-T should work too, which thankfully was preserved in Firestorm, too. (On those infrequent occasions I use Firestorm, I'm forever forgetting I can't simply hit Enter to type in chat.)
  24. In addition to the repeated calls in the dataserver() handler, these ones in state_entry() and changed() will indeed be to kick-off reading or re-reading the notecard from the top. The reason it arises in changed() is usually to handle times when the notecard is edited or replaced, which is evident when the CHANGED_INVENTORY flag is set. (A notecard gets a brand new "key" or UUID every time it's saved, so that's a way of telling that specifically that notecard was the thing in object inventory that changed.)
  25. Yeah, llSetLinkMedia() establishes shared media for one face of an element in the linkset. (Of mostly historical interest, the llSetPrimMediaParams() does the same thing but only for the scripted link itself, so those functions share parameters such as PRIM_MEDIA_CURRENT_URL.) It is tricky finding viable URLs to feed these various functions (same problem for parcel sound, too), so it's not surprising that it doesn't like an .mp3 (which it will see as a file rather than a streaming format). I don't think playlists (.pls) will work either. I generally end up specifying a URL in the form of http:// <IP address> : <port number> for these streams, which are often found by persistent snooping around an internet radio source site. SomaFM, for example, calls these things "direct stream links" hidden under "alternative stream links for internet radios and other media players" and even then only the non-.pls, non-.m3u links seem viable. Maybe somebody else has a more rigorous way of finding working stream links. And yeah, shared media's range is problematic. Used to be even less predictable. If I really need to constrain streaming audio, I revert to the old PARCEL_MEDIA_COMMAND_AGENT and periodically check where the avatars are located, so they can hear for example different streams in adjacent "apartment" spaces. It's not that difficult, but a bit of a heavy lift for a first script, and requires some script processing time in contrast to merely leaving a URL on an object surface for the viewer to discover and pass off to an audio streaming library.
×
×
  • Create New...