Solar Legion

Bah, no worries. As noted above, short on patience today. I hate rainy/stormy days and so does my head.

Yes, that is part of what I mean and the expanded version of what I said. Brand recognition and the fact that the option to send to it is right there, showing that brand name. Heh, you're having a brain fog day and I've got a case of weather based irritation. Apologies on my tone.

Oh for .... Read. What. Was. Said. Flickr was there by name. That is the difference. It has nothing whatsoever to do with extra steps. As for the incorrect information regarding how to send it to Snapzilla ... To Send a Postcard you have to ..... Send it Via an E-mail. The option is labeled differently depending on the Viewer used. Seen below - to further drive home the primary point (which you either did not get or simply ignored) and further negate that rather incorrect information (while showcasing the difference in naming conventions between Viewers) is how the Snapshot Window appears on Firestorm when you are chosing how to save the Snapshot, followed by the Send to E-mail section. Out of curiosity I looked at the Share to Flickr dialog option and found it had several text entry boxes as well. So once again, it has nothing whatsoever to do with saving any time and everything to do with one option being named directly in the floater and one using a generic function.

Yes and no. Flickr was marked by name. Snapzilla requires you use Send to E-mail. Therein lies the difference for easily led around users. Which was - I thought - quite obvious given the way I'd phrased my post.

The answer is even simpler: Flickr was directly integrated into the snapshot window as a Save option (among others). This was done during the time when there was a push for broader Social network integration (excuse me while I void the contents of my stomach). That's it. That's all.

I do not use and have not used Windows for many years now. The closest thing to it I currently use is Proton and WINE. The closest thing to it I will use in the future will be ReactOS (once it properly catches up). There is no reason whatsoever to require the average end user to enable Developer Features, least of all to circumvent something that should not even be there in the first place. Android has a similar problem with functions that should not even be behind such a 'wall' having been placed in the Developer Options (among other issues). It is not all that hard to understand and is (part of) why I stated that I cannot roll my eyes hard enough. The other part is that a program "signed" by Microsoft is not intrinsically more "trustworthy" - such has been the case since the early days of their OS and company.

You answered your own quandary: They're called .... Clients.

Ah yes, because all programs that are "signed" by that Microsoft Certificate are - in fact - trustworthy .... I cannot roll my eyes nearly hard enough ....

People that insist on pretending program differentiation terminology serves no purpose ...

And another typical response ....

You mean "sanitized".

Ah yes, it was only a matter of time before someone showed up to spread their usual BS ....

The thread(s) concerning the world Map can be found here. Also, there is no such thing as the Second Life browser, they are Clients or Viewers and no update to such will fix the map - that is all server side.

As for the topic of the thread ... Keep your username(s) and password(s) in a safe place in the event something like this happens again. In my experience, once such a change occurs you cannot simply restore the saved password file.

There's a reason I quoted you directly ya know - my response was to you. The upload/third party bit related to the changes made in the API, which hit some earlier than the 15th. Chrome itself would be utterly unaffected by the change.

If what you were using was a third party add-on/plug-in to do the uploading, it is possible that it was affected by the recent blocking of certain Chrome API functions in Chromium based browsers - which is what powers Brave.

Control (CTRL) + Shift + Enter - as noted in two of the above posts - does actually force such a break if using Firestorm. The trick is remembering to do it.

What you are seeing is normal IM behavior and has been the normal behavior for as long as I have been using Second Life, with no way to change it either. Local Chat has an automatic cutoff point wherein it automatically splits a longer message up - much like AOL (and other, older services) did, even if you used third party tools to allow you to type more text than the normal entry box allowed for. The Instant Message system in Second Life has no such function. So if you want such line breaks, do as Rowan said above and actually hit enter every now and again.

Yeah ... no. Thread older than you're comfortable with being "revived" posted to? Move on. Can't be arsed to actually look at the date? Your problem. Then again, I go through the categories that I like to read, one at a time and don't use any of the activity feeds. For exactly this reason.

You're going to get very mixed responses here, some incredibly biased as well. On general RAM usage: More is often better as it allows for more and more multitasking and can compensate for resource hungry OSes. The rest seems to be pretty nice and will allow for a lot more than just Second Life applications/usage.

The Continent Names do not show up anywhere outside of image files around the Grid - they were never a part of the region or Map Server data.

And your point is .... What? Someone responded, others are now responding.

Loophole: No one was directly named and no name is present in that reposting.

I cannot roll my eyes hard enough at that .... Have your friend strip out the IP Address information if they're that concerned. There is nothing in the information being asked for that can facilitate her directly getting a virus.

Oh for ... Sit. Down. The only way it will be "dead" is when such proposed legislation is properly defeated and ceases to ever be introduced again.