✨ Feature Requests

  • Search existing ideas before submitting- Use support.secondlife.com for customer support issues- Keep posts on-topicThank you for your ideas!
Malicious links filtering system
Currently if someone types [SOME_UNSAFE_URL SOME_SAFE_URL] into an IM they can convince a person to click a malicious link that looks entirely safe visually. I propose a way to correct this: A new Preferences -> Chat -> Chat Windows checkbox called Enable URL Filtering. When unchecked it disables the Allowed URLs button. A new Preferences -> Chat -> Chat Windows button called Allowed URLs. When this button is clicked a filter list similar to the Firestorm Media Filter list pops up allowing the user to add or remove allowed domains. By default the following domains should be allowed: secondlife.com firestormviewer.org phoenixviewer.com discord.gg discord.com youtube.com youtu.be This way users can perform basic operations like connecting to friends on Discord, visiting support help links on firestorm or secondlife's website, visiting the marketplace, and viewing youtube links. Beyond that if someone needs to visit additional domains, they need to add them to the allowed filter list. Then if someone were to attempt to hit them with a malicious link, it wouldn't work by default. I think this would be a quick and efficient way to fix the problem for the most users. I understand this would make things more difficult for any url not on the list, but people could just display those urls as plaintext and users could copy and paste them if they truly want to visit them. And, in this way, they wouldn't be concealed by a malicious clickable link. And, any links added to the filtering allow list would become clickable if desired. A checkbox which is on by default, could be provided for unchecking to turn off the security feature. But, it should be on default for all users, unless the user chose not to use it. With a warning that pops up when attempting to uncheck explaining why that might not be a great idea that they could then ignore and even "don't show me this warning again."
31
·
tracked
Make Local Chat Range configurable (Project: Voices Carry)
Back in Spring/Summer of 2020 there was work being done to make the common chat channel (channel 0) definable by region owners. This work was done under the project name "Voices Carry". During the May 15, 2020 TPV Developer meeting, the new simulator chat range capability was discussed in that it'd: a) require viewer-side UI support, which had yet to be completed. b) The range set for a region would be reported to the viewer by the simulator as a part of the region information. c) and that the server-side support will be appearing real soon now™. Then at the May 26, 2020 Simulator User Group meeting this was further explained that: "a new ability is being developed to allow region / estate owners / managers to set the open chat range on a region (see BUG-228333). This update is only intended to affect nearby chat channel 0 (the default open chat channel)." And there followed at that time some clarification discussion with Rider Linden and Oz Linden addressing some of the inter-region concerns arising from this. In June of 2020, server release 2020-06-05T19:36:41.543337 "includes work in the simulators to eventually allow per-region values for Shout, Say, and Whisper distances. NOTE: Currently these values are read only, and can be accessed via the Sim Console." Which sparked similar discussion on the Second Life Server sub-forum. Not long after, but I'm not sure of the time frame the scripting function llGetEnv() had data for "whisper_range", "chat_range", and "shout_range" added as a return for scripts to be able to dynamically find out what the channel 0 chat ranges had been adjusted to. All of this was done during the cloud migration work and I assume by necessity was a lower priority. But then, nothing ever came of it. I know that projects get abandoned all the time for various reasons, but I wonder if this one simply fell through the cracks and might be something that can be re-looked at as a possible feature for Region/Estate managers to update on their own. (I'd be nice if it could be a parcel level setting but also understand why that might be desirable or even feasible.") In addition to extracts from the official Release Note and server forum, some of the detail extracts from the meetings come from Inara Pey's blog "Living in a Modem World", and full links can be provided on request. Thanks.
2
·
tracked
Load More