Tjay Wicken

This appears to be the case. What's shown here in this thread is only a small sample of the strange, unfinished, untested changes. I'm fairly certain that there's no testing or staging environments - or if there is, they are not using them, direct commits to production all the way!

English is secondary for me as well. First language is Danish but having lived in Spain and now Sweden for the past many years I'm fluent in both of those as well. I also communicate fairly well with norwegians, but I tend to use some kind of mix between Danish and Swedish when speaking depending on where in Norway the person is from. My father was of Polish descent so I was taught quite well by my grandmother growing up, but at this point I can just about have a small conversation going, it's fading as I am not using it at all. I also speak, read and write French fairly well thanks to it being my second choice back in school, but definitely not fluent.

When I wanted to change my surname (was "Oh" before "Wicken") I had to lodge a ticket to get it done as well, so there may be something to it. Either way, a ticket is the way to go for her, they can force through the change from their end.

Looking back, Jonas Quinn was actually a decent replacement. Wouldn't have been the same without his arc.

Version 1.0.6 has been submitted to the extension stores. Full changelog can be found on github This is just a minor hotfix as Linden Lab made some changes to the product pages on the marketplace yesterday causing the posting date and tags no longer being injected as they have modified and given new names to div containers. Since they also added some additional width constraints to the layout, the extension is now also applying the same to avoid overflowing outside the main container. The update for Firefox should be available in the next few minutes, Chrome within a day or so and Edge within a week. Edit: As of this evening, LL renamed some of the div elements again. I will continuously push out updates as I notice any breaking changes, but won't update this thread unless there's a significant update. The github repo will always be updated with these minor hotfixes as they happen.

It's quite clear that the marketplace is being updated to better support mobile devices, that means larger buttons and proper modal popups instead of inline input fields, which is not inherently bad, although seeing UI become "mobile friendly" is never a pretty experience to go through. The issue I think is whenever functionality is reduced. The gift option is a good example of this, as the auto-complete functionality was not carried over in the change and at the end of the day that just becomes a regression of functionality. I expect we'll be seeing more, similar, changes across the marketplace in the coming weeks and months, and hopefully at some point some QA testing from a desktop user perspective as well to avoid too many functional regressions.

It looks like Linden Lab has made some changes to the search filters on the marketplace. Specifically, they have renamed the "Do not show" parameters and as a result you will now see an error message if you attempt to search if you have enabled either "limited quantities" or "demo items" under advanced search filters in the extension settings. I'll release a hotfix tomorrow to address these changes. Edit: Version 1.0.5 which addresses these changes has been submitted to the extension stores. As always, the updated version is likely available for Firefox in the next half hour or so, while Chrome takes about a day and Edge up to a week for reviews to take place.

Some data is available through the official data feeds. api.secondlife.com/datafeeds/lindex.txt api.secondlife.com/datafeeds/homepage.txt Collected over the course of this month:

This is a very good point and something which really should be addressed at a ToS/Policy level by LL. There may be legitimate reasons to use an external server to validate things, such as for subscription-based products or those relying on external servers for core functionality. However, it should be an absolute requirement for creators to make potential customers aware of this external dependency and provide realistic expectations that the product may cease to function in the future. I don't see any way of ensuring this outside of a ToS change that requires creators to indicate dependencies on external servers. Creators using this functionality maliciously should have their accounts terminated/closed.

That feature nearly made it this release! I need to do a little bit more testing as I saw some strange behavior when testing it, so I moved it out of this release. Should be there in the next update.

@AmeliaJ08 @Flea Yatsenko I have now submitted version 1.0.4 to the Chrome, Edge and Firefox extension stores. Firefox appears to already be live, however Chrome usually takes a day or two, and Edge takes up towards a week before the update passes through validation. I have added initial support for advanced search filters. I tried a few different approaches, and I believe the current implementation works pretty well. If enabled, it should apply to all searches and when browsing categories persistently with the exception of store pages, since I believe that is the one place where it is still nice to be able to browse the categories without filtering being applied. I can perhaps add a toggle for that in a future version. Thanks for all your feedback and suggestions! Version 1.0.4 - August 7, 2024 4---------------- 5🚀 New Features 6 7- Added a new set of options for advanced search filters which are applied across all search and category links on the marketplace. 8 9✨ Enhancements 10 11- Complete overhaul of the settings popup. Settings are now categorized in tabs for a better overview. 12- The extension settings can now be accessed through the extension contextual menu inside "Manage extensions". 13- For Firefox, the extension is now automatically pinned for all new installations.

That sounds like a really great idea. I will look into this!

In my initial test I did have a separate settings page as well, but ended up removing it as I figured the popup would be suffecient. I will reintroduce that in the next update as well, it would just take a few minutes to pull back in. Several ways of being able to reach the options is not necessarily a bad thing in this case as I wouldn't want people to somehow not be able to find the options. I will give the options a small overhaul later today and do some initial testing. Edit: and thanks for the feedback!

Thanks, I did not think of that! I believe in Chrome based browsers it is no longer possible to pin by default, but it looks like it still is for Firefox. I will test, and if possible, include that specifically for Firefox in the next update. For Chromium based browsers we can perhaps show a small "getting started" window after the extension gets installed the first time and show how to pin the extension.

Out: Summer In: Fall At least that's what it has felt like in the past week or so here a few hours drive away from the arctic circle.

Sorry to hear that it was a rough time for you. Addictions comes in many shapes and forms, and we as humans are really bad at self-reflecting in the moment of the heat so to speak. I suppose the important part here is that you got to learn something new about yourself once you did have the time to reflect - and you came to terms with it, that's a great take away at the end of the day. Hope you're getting along with your retirement well!

I'm not really sure why you are being so hostile, the only thing I did was point out that the paragraph you were questioning has been in place in the Tilia ToS for several years, and most likely it has been there since Tilia was formed. Whatever change there may have been, if any, is not related to that. Who am I representing? me! - a satisfied SL resident since 2006. It has never taken more than 2-3 days for me to withdraw through LL (and I live across the atlantic) And for what it is worth, I'm glad that you have had a nice experience with PayPal and Venmo - personally, when I was using PayPal for my business, it would not be uncommon for them to randomly freeze/put a hold on my funds, sometimes for a month for no reason at all, each time having to re-send the same company registration forms. I would personally never use them for anything business critical ever again.

Sorry, should have been clearer, I was just pointing out why I didn't point it out in the other thread, as my only focus was what had changed. 30 days is something you will often see with payment processors, or really anytime any firm needs to make transactions and transfers (that is, unless they are the ones who should be paid, of course! 😂), that statement is there to cover them in the event that something goes wrong, or they are for some reason unable to complete transactions. Terms of Services will often read extremely hostile for customers reading them but as with any legal speak it is important to pay attention to the leading words, in this case "but may take up to", which is them saying (and I am paraphrasing here) "We aim to have your funds with you within 5-10 business days, but In the rare event that we are somehow prevented from completing the transaction, we still make sure that you have the funds within 30 days".

I'm not sure why it would be mentioned in the other thread as it is not new. In fact, this paragraph has been present in the TOS since at least May 2022, possibly much longer than that, but the May 2022 version is the oldest archived version on archive.org. You can see the same statement appearing in this version of the page cached in December 2022.

Before we go all doomsday, it would be best to also take into consideration that the datafeed stopped updating concurrent users on the 27th of July

It is worth to note here that Intel claims the oxidation issue is only present on early models of the 13th gen, and it is not present on the 14th gen at all. This is two separate issues with one only affecting the 13th gen series. So far everything points to voltage being the definite factor in terms of the WHEA errors and my guess is that the microcode patch coming out later this month will be addressing the problem specifically by limiting the vcore voltage.

I think your question has already been answered well by others in this thread, so I won't repeat what has already been said. I would personally be very careful to suggest that theft is taking place unless you know with absolutely certainty that this tattoo was in fact a 100% original creation by the creator. A vast majority of the smaller/less complex tattoos you see are just ripped straight from Google, fitted to the UV and then uploaded to SL - and while I am not suggesting that is necessarily the case here, it could very well be that both of them simply sourced it from the same place.

In all honesty, if you go by your "work persona" name and even include your workplace name in your handle, you cannot expect people to treat it as a personal account.

I have been using userscripts to display marketplace tags and item listing dates for a long time but wanted a little bit more flexibility, especially in terms of deciding where to display additional information. I ended up making a small browser extension for myself and figured it could benefit other people than just myself, so I have decided to publish it for the Firefox, Chrome and Edge browsers (although if you have any chromium-based browser, you can install it from the chrome web store as well) So far, I have added a couple of fundamental features: Added tags and listing date to product pages. Added listing dates for items appearing in search results, category browsing and on store pages. Added an option to hide featured items containers (disabled by default). Every option can either be enabled or disabled independently from each other from the extension settings (just click the icon for it to pop up). Privacy comes first for me, and honestly, I have no reason or desire to know anything about the users, so nothing is collected or sent anywhere. The extension does store your settings in your local browser storage, but that is and will ever only be used for saving and applying your settings. Last but definitely not least, I have made the extension fully open source under MIT, so if you want to have a look at the code or package it yourself, you can just head over to the github repo (pull requests are always welcome too!) You can find the extension on the Chrome Web Store, Firefox Add-ons page, and the Edge Add-ons page. For additional install instructions and an always updated changelog history, you can either check out my blog page, or the github repo Suggestions, bug reports and anything in-between is always welcome and appreciated!

The change is most likely just to streamline internal processes, here's the exact wording that was removed: My guess is that removing this provides Tilia increased flexibility (it now has more discretion in how it handles refused transactions) and the old language was very committing. This essentially reduces the liability in some sense - the risk of a user claiming breach of terms if a suspension isn't lifted has now been lowered. It could also just be as simple as them just simplifying the terms, not having this specific language in place allows them to better handle things case-by-case.