Jump to content

Kitty Barnett

Resident
  • Posts

    226
  • Joined

  • Last visited

Posts posted by Kitty Barnett

  1. Just for reference: Twitter actually outlines what you can/cannot do with automated data retrieval (in Twitter's case an API, in SL's case that would be LSL or reusing data interfaces intented for SL viewers) @ https://developer.twitter.com/en/developer-terms/more-on-restricted-use-cases .

    I don't see any reason why a similar document couldn't be drafted by LL to apply to SL Especially since part of the restrictions are of Twitter's own design, but other parts are simply rephrasing the various privacy laws that exist in different countries in a context that makes sense for what Twitter is about.

    I choose Twitter because it has a good mix of real and made-up identies who talk about personal and non-personal things or outright make things up and similarly to SL's profiles, chat and location data, just because you choose to share something with other Twitter/Second Life users, or because something needs to be available for the normal/expected use of the platform when used by human users doesn't mean it's a free-for-all-purpose datamine (or at least Twitter doesn't feel like it can get away with that claim).

    • Like 1
    • Thanks 2
  2. 8 minutes ago, Nadi Vemo said:

    Basically vendor shows one item to buy, it will only change that item when someone pays for it, and it will pick random new item from the list, vendor of course will lock to person who is currently using it so it will not allow any prize sniping. So that if a person decided to play longer next prize will always be their to pick first. it can also show what will come next, or it can be turned off to just show one item currently for sale.

    You're paying for the item *and* the chance of a lucky roll after payment has been received. If the next roll did not have intrinsic value there wouldn't be any need to (temporarily) lock it to the last person to pay the "slot machine".

    (In addition you even called the result of the random roll a 'prize')

    • Like 1
  3. 20 minutes ago, Deathly Fright said:

    as I understand it, an avi lock could be made where if in 1 minute the person who just purchased has a chance to buy more and only they can buy

    Lock-in would just prevent the automation from stealing someone's rare; someone will at some point leave up the common you want. Either because they don't want it, or because they've gotten it 5 times already and are fed up and let their lock-in time expire.

    It can then be bought, you get a roll of your own for one of the other items you want - including the rare - and then it goes back to sleep to wait for anything else on the list to become available.

    18 minutes ago, Kricket Calamity said:

    There are usually time limits at events, most big events would have the bot kicked out well before it could snipe things. I've been at an event camming around and was kicked out for inactivity after 30 mins. 

    Different scenario then: someone registers X amount of accounts to swap them in and out as the timer hits. They also advertise their service and for a small mark-up to be paid on delivery will attempt to get you the exact item you want. For diserable gachas the bot might grab most of the items since at least one person is a 'guaranteed' buyer of the item which gives the operator a very large amount of rolls for rares to sell at a heavy mark-up.

    People can get the item they want at the almost at-cost price without having to bother searching the marketplace and you can still get individual rares (for a mark-up) as is the case now.

    Which would actually be an improvement and I guess I'll stop arguing against it and wait for someone to set it up 😁.

  4. 3 minutes ago, Deathly Fright said:

    yes. so you walk up to what looks to be a normal gatcha vendor now and it has a small hovertext that says the key from the gatcha graphic. then when you buy that thing it randomly picks (just like it always has) and then the hovertext changes so that it says the new item's key. it won't help people who have a problem with gatchas, and there will be a problem of people camming to the gatcha and waiting for a rare to popup to get it, but I think it technically would be ok under the new rules.

    This will get automated fairly quickly: you point a viewer (or a bot) at the gacha vendor, you say which prize you'd like (hover text would be easiest since that's text but texture indicators will work too) and you leave an alt there AFK.

    If the next item isn't locked you could snipe rares, if the next item is locked for a limited time you can only snipe (un)commons - I'll assume that no one would pass on a rare, although you do get a roll of your own with ever common you snag up - but often you actively want specific common items too anyway and it'll just be a matter of time before someone leaves that common you want up.

    So go to bed, leave your alt at epiphany and by morning you'll have a good chunk of all the specific commons you wanted with no effort on your part. The only way for a real person to play would be to throw away their first roll on something they don't want.

  5. 7 hours ago, Lucia Nightfire said:

    In all fairness, I think LL needs to officially state whether this practice will be acceptable or not as it looks like a lucrative  alternative that could come into practice.

    The law can very well prohibit it, but so far with what Patch said on page 9:

    seems to be the focus and as long as what is pictured/expected is what you get upon payment, that part should no longer come into conflict with the change.

    Re-randomizing occurring AFTER expected product is paid for and receiving, might be an entirely different ethics/legal issue altogether.

    You're actually paying for two items: the item displayed *and* a random luck-of-the-draw outcome. Can you honestly say that no one will ever pay into it for an item they don't want just for the chance of being able to buy the rare on the next roll of the dice?

    Since gacha items have RL monterary value due to the thriving reseller market you essentially end up playing a slot machine knowing what the outcome will be, but mostly for the chance to win big if only you just feed it a little bit more money for one more spin to see what the next outcome will be... which to most people would feel like gambling.

    (I'm not arguing that it isn't allowed under LL's definition but just that it's as predatory as gachas and not an improvement over just selling the items in a regular vendor at fair value)

  6. I hated it when LL decided to discontinue Live Help and folded it into the mentor program since both had very different skillsets. I just don't have the patience to deal with newbies but I loved helping established residents with problems or answering questions (and of course nothing beat watching a Linden explain how SL genitals work 😇).

    In many cases resident volunteers also helped in ways that just aren't feasible for Lindens or support staff because of the time investment. My best memory is still a resident who started a Live Chat in full panic mode because they'd accidentally rezzed something and granted it debit permissions and the prim whisked away and was draining her L$ balance. She'd moved the remaining balance to an alt, but that account would be useless for as long as that prim was out there. So I teleported over to where she thought she rezzed it and we spent at least half an hour just flying around and eventually I found the prim and she deleted it. Account saved! 🥳

    It was at that point that a Linden who'd been silently monitoring the conversation jumped in, teleported to us, god teleported the scammer and kicked (banned?) them off the grid with a witty remark. LL can't dedicate that amount of time to helping a single resident, but by just monitoring us he could jump in at the right time and at least take some action (you still don't get your L$ back unfortunately).

    Another case was someone who'd lost a 'no copy' object (some kind of cuddly animal if I remember) after rezzing it and they were upset because it had sentimental value. This was at the time where items had a good chance of appearing at 0,0,0 so sure enough, I found it hiding there and selecting it made it return to their inventory. 10 minutes later I got a snapshot they'd taken with it as a thank you which made it feel really worthwhile.

    We also took care of concierge type questions for people who didn't qualify for concierge level, helped people sort out tier by calculating their group bonus, or just answered "why is there a box on my head?!" or directions to a "nude beach" 🙄.

    TLDR from the ex-Live Helper side, it did serve a big purpose. At the time LL support was somewhat lacking and it can't (and should have never been) a replacement for official support, but it definitely filled a void.

    • Like 8
    • Thanks 1
  7. 7 hours ago, Orion Pastorelli said:

    My first real encounter with SL fashion was The old "Naughty Designs" skins by Lost Thereian.  I remember he had a partner, but her name escapes me. I was like 2007 I want to say.

    I remember being wowed by the build of their in-world store. It looked like a real world mall. It generously made use of sculpts, with was the only way to import custom geometry at the time. This was before mesh.

    I remember that mall! It's one of the pretty places I used to show off LL's 'Shadow Draft' project (in the early days of shadows LL only did source code drops for it and didn't offer a viewer with it of its own).

    Hopefully this doesn't ruin your memory of it :) .

    2543894217_c98cc65c23_b.jpg

    2544721966_6098ac053a_b.jpg

    • Like 8
  8. 4 minutes ago, panterapolnocy said:

    the deploy plan message specifies that "function is restricted to being invoked by experiences that are enabled for all Residents" - and as far as I know not many experiences have such status - their owners won't risk losing them by disrupting user experience. Especially for newcomers, in newcomer friendly areas / Portal Park installations. For what purpose this function was actually created: "(...) New User Experience (which will rely on this function being present)."

    Grid-wide experiences were supposed to be generally available but so far it's only Linden experiences and I think a few residents who participated in the testing.

    That said, there are already 'shared experiences' out there where someone offers up their experience to the community at large, and which can then be used for griefing (one reason avSitter is banned from executing RLV commands).

     

    Even if grid-wide experiences end up being more tightly controlled by LL that then just shifts the risk to the security of the individual scripter. The in-world browser is old and not frequently updated so for force-opening URLs seems like a bad security move until that gets addressed and improved.

    I can unfortunately see blocking this functionality becoming an option on most TPVs, and then having it enabled by default which would limit its usefulness significantly and it would probably have been nice to have this discussion/announcement happen at the bi-weekly TPV meeting :(.

    • Like 3
  9. My first hair was a GuRL 6 hair because you got one for free if you were under 30 days old.

    Some I haven't seen mentioned:

    * Dazzle  (later rebranded as Last Call) was one of my favourite stores (unfortunately Ginny Talamasca passed away)

    * Republic Bay was probably not terribly well known but I got to know the creator (Lika Goodliffe) a little and he made a house I still have wonderful memories of (I later on found he'd also since passed)

    * TorridWear (Torrid Midnight) made the post iterations of my AO poses

    Starax Statosk was always a mystery name and I'd see it pop up with reference to the "Starax wand's magical abilities" - I don't think I ever got to see one

    17 hours ago, Rolig Loon said:

    I went looking for that gown in my inventory just now and I can't find it. It must have died in some ancient inventory dustbin fire.  I had a couple of those.  I still have a photo that shows the bodice, though.  It's maybe not as elegant as I remembered, by today's standards, but it was great at the time.  The hat wasn't Nonna's, but it went with the dress.

    I found this in a dusty corner of my inventory:

    image.png.11f88cadc47f91bebb10b8b579bf4efb.png

    • Like 6
  10. There's likely not many people who were around for this (or who remember, or who chose to be involved) but I wouldn't mind UI design documents opened up for resident comments again.

    Back in 2008 there was a landmarks/navigation redesign which I remember seeing and being asked to comment on before viewer work started ( https://jira.secondlife.com/secure/attachment/18733/LLSL-LandmarksEnhancements-FinalIA-08-0626.pdf
    note page 8 for the new landmarks floater and then https://jira.secondlife.com/secure/attachment/16995/SL_Viewer_Revised_Wireframes.pdf ).

    While far too heavily browser inspired there were really good ideas there (a 'Received Landmarks' floater would have been nice and prevented the OP mention of searching for landmarks being useless since we're literally drowning in them from spam / share-happy friends) and I think the only landmark related thing we ended up getting was a 'My notes' textbox that never had any follow up use.

    There have been some ambitious overhauls since then (CHUI comes to mind), but it often feels like very obvious things or existing use cases end up being completely overlooked which is why resident participation feels key and sharing documents like that helps prevent that before the code is committed and everything's set in stone.

    (EEP being the latest example: environment assets are a good thing, parcel-level control is a good thing, multiple-height levels is a good thing, a 'Personal Lighting' floater is a good thing. But the UI end-result however is very much not - in addition to coupling it with a rendering update that changes how the world looks)

    TLDR - I like that viewer UI is a focus point, but it would be even better if residents could get involved prior to being confronted with a 'done deal' where our feedback is largely pointless, because no one is going to hit the 'Undo' button and throw away months of work.

    • Like 4
    • Thanks 4
  11. 1 hour ago, Gabriele Graves said:

    If it could be known that scripts in products were calling home, even if only to find out about it after buying, it would make some people contact the vendor to ask why long before the unwelcome surprise of the product ceasing to function.

    Or just have LL implement permissions the same way Android/iOS apps have varying degrees of things they can/cannot do. In most cases people will simply not care, but at least it makes things visible when those functions are used in a script where you wouldn't reasonably expect them to be.

    Updo Hair, owned by you, would like to:

    * track your location (=llHttpRequest)
    * track the people around you (=llSensor)
    * listen to local chat (= llListen)
    * communicate/send information to a remote host

    [ Allow] [ Deny ]

    (Also updates can be done simply by redelivering an item to all people who have purchased it; no embedded scripts required)

    • Like 3
    • Thanks 4
  12. 3 minutes ago, LittleMe Jewell said:

     

    Off topic for the thread, but side note on the above comment about VAT:   VAT is not charged for Premium when it is paid yearly, but is charged for monthly & quarterly options.  It was the same before the price of Premium increased.  I don't remember how long ago LL started charging VAT on Premium memberships.

     

    No, it really wasn't. Quarterly wasn't subject to VAT until the price increase. (And support can't agree on what happens to my stipend if I change from quaterly to yearly with some saying I loose it, and the others saying it'll stay L$500)

    • Confused 1
  13. Is this why third-party L$ exchanges were banned all those years ago? So LL can now - already for the third time - keep on raising the cost of buying L$? 🙁

    The premium price increase doubled what I pay for premium (LL price increase + decision to start charging VAT on it which LL didn't before) and now the cost of buying L$ has gone up 10x from 40 cents to $4.20 (I tend to buy around L$15k/$60 at a time for a month's worth of shopping).

    "Whales will pay no matter what" works in games, but the (over)paying minority tends to at least get the "pay to win" brag rights but you're missing that piece of the puzzle in SL.

    The model where you (over)charge for basic platform services seems better than to just tax L$ spending residents with increasing amounts of RL money. For instance you have the "in-app purchase of $40 for a name change". Make extra options to wear 1 additional animesh attachments (basic has 1 currently, premium gets 2). Pay-to-win purchase for extra groups, or more picks, or an online status indicator,  or one time $40 to have 2FA, etc etc... .

    Anything that doesn't repeatedly make me feel punished for being part of the minorty that's already giving LL $US...

    • Like 2
    • Thanks 1
  14. 1 hour ago, Chaser Zaks said:

    You may not send unsolicited automated advertisements or subscribe a resident to automated mailing lists unless the resident has chose to subscribe or has directly interacted in a way that they may want to be subscribed.

    'Unsolicited' isn't really provable in an automated fashion so I'd personally really want the rule to be "You may not send automated advertisements....", period. That leaves groups as a means of allowed mass communication and people have to willingly join those so consent is implied (and annoying group invite spam bots would just fall under the same 'no go' rule).

    Not once have I ever clicked on any of the objects that spam me on a regular basis so it's very fair to assume that a large portion of stores with a "subscription kiosk" seed them anyway rather than people genuinely clicking them.

    In the last 7 days I've gotten 16 offline object messages and then every other day when I log in 2-5 are waiting for me to actually be online and then additionally offer landmarks and notecards.

    There's been a fun recent new one that's actually a full 33 lines of chat history text so yes, +1 for a no tolerance ban on spamming residents.

    • Like 1
    • Thanks 1
  15. I remember when you started and things are now much better for TPV devs than they were back then so thank you for all your dedication and hard work!

    I wish you all the best and we'll miss you. (Although hopefully we'll catch glimpses of an Oz Resident now and then 😀)

    • Like 7
  16. 5 hours ago, KjartanEno said:

    @arabellajones, it can be frustrating to wait. 🚏

    I don't think RLVa visual commands have been fully fixed for EEP yet, so that's another major consideration.

    I redid the WindLight RLV commands (with a few new EEP-specific ones) in RLVa back in May and it's gone out in several FS betas/nightlies since then and no one's poked me about any issues so if you know/think something's wrong/broken please do let me know.

    • Like 3
    • Thanks 1
  17. 7 minutes ago, Selene Gregoire said:

    @Kitty Barnett

    Will this be only in Catznip or will all TPVs have it at some point? Please note that I am not mentioning the clunker LL viewer.

    It's the proper emoji Unicode characters so really all any viewer (including LL's) needs to do is put the proper emoji font in its font folder. They will show as black/white emoji's but everyone will see them fine. Even without doing anything some of them will show up on all existing viewers (smiley face, sad face, etc) just because they're already in the current fallback fonts.

    My guess would be that if we release with it and it's actually popular then I'll probably just get poked to put it into Firestorm and then LL might poke to get it into the official viewer.

    Or it might fail and that's fine too 😃. Just using other chat proggies makes SL feel very old-fashioned with having to click imgur and gyazo links to see what they are in a program that isn't SL which is always disconcerting rather than just hovering over it and seeing it right there in the chat window.

    • Thanks 1
  18. You mean bringing SL communication up to semi-modern standards? It's already been done (or will be once the new Catznip releases) :).

    First was to just have proper link previews like anything else you use to communicate with (with the proper options to not have it on in groups and all that):

    DlEooYSXcAIkNJf.jpg:large

    And obviously, emoji's are a big thing (the current implementation looks a lot better than this - it was the original proof of concept from last year):

    DlKrGYJWwAAPco0.jpg:large

    And the only part that requires (new) viewer code is actually the colour emoji's (and having a way to look them up), you can do black and white emoji fonts right now just by dropping the font in the viewer's folder.

    • Like 1
  19. On 3/20/2019 at 9:15 PM, Whirly Fizzle said:

    But I get your point, having been in Kitty's house  :D

    Heyyyyyyyyyyyyyyy! I take offense to that! It looks great and pretty  *pouts*

    • Haha 3
  20. 17 hours ago, Qie Niangao said:

    Huh. I seem to recall that changing active group causes a bunch of (seemingly unrelated) stuff to update. I wonder how much lag is caused each time that @setgroup is called, and how much of it affects others as well as the changed-group agent.

    They aren't changing the active group, but rather changing the active role within the currently active group to get a different group title. That part is new since the last RLVa release; the ability to change the active group (without control over the active role) has been part of general RLV for many years now.

    As an aside, changing your active group shouldn't make that much of a difference. Access is independent of active group, placing prims is viewer dependent (which is how viewers can have a "rez under land group",  etc. Changing the role shouldn't do anything except broadcast the title string to everyone that has you on their interest list; which is less impact than a titler that keeps cycling its letters.

    ---

    That said, I've had some people poke with concerns; if I see things go out of control then I'll slap a throttle on it or remove it entirely as a failed experiment of introducing more "fun" things to play with.

    • Thanks 7
  21. 6 minutes ago, Whirly Fizzle said:

    NEW Stop Experiences having limitless access to RLVa by default

    • Added 'RLVaExperienceMaturityThreshold' and 'RLVaBlockedExperiences' debug settings.
    • Current default threshold is mature and higher
    • AVsitter is a compromised experience and blocked by default

     

    In addition to that RLVaEnableTemporaryAttachments setting has been around for a long while now precisely to limit the scope to only attachments you choose to wear yourself; which as a side-effect blocks all experiences related things too (since they're all temp prims).

    But that's really just intended to remove the surprise/undesired factor of having temp attached prims interacting with your RLV(a) when you know you never want them to. If someone is using an experience to grief, or step out of line, then the experience >creator< is ultimately responsible for how they allow their experience to be used and do abuse report that.

    • Like 4
    • Thanks 1
  22. 9 minutes ago, Innula Zenovka said:

    Thanks. Kitty.    That clarifies things a bit, but can I just focus on exactly what should or shouldn't happen?    Am I correct in thinking that the G experience will be able to temp attach something that is scripted to issued RLV commands (since I can't see how the viewer knows that the script might do before the object is attached) but, if the temp-attached object then tries to issue RLV commands, the commands will be ignored if the experience maturity rating is G?

    Yes, exactly, nothing about the experience is affected in any way. The viewer will simply add the object to the blocked list and not process its RLV commands, for example with KT's script I  see:

    [09:15] Object:  failed: @setrot:3.14=force (blocked object)

     

    • Thanks 4
×
×
  • Create New...