✨ Feature Requests

  • Search existing ideas before submitting- Use support.secondlife.com for customer support issues- Keep posts on-topicThank you for your ideas!
Timestamp URI
Second Life Residents come from all parts of the world, however something that divides us is timezones. I propose a feature that will help unify us in that regard, and that feature being a Timestamp URI extension. The proposed implementation would allow for URIs such as secondlife:///app/timestamp/<unix timestamp>?timezone=SLT&format=H:m:s . Where <unix timestamp> is the standardized Unix Timestamp integer, which is based off GMT. (LSL has the ability to fetch the Unix Timestamp) By default, it will display SLT time, but timezone can be specified to show local or other timezones, such as GMT . The viewer already has timezone capabilities in it. Format can be a constant of full , short , time , or date , or a custom formatting such as H:m:S following a specification such as that laid out by python's strftime , which I believe is also the same used by PHP and Perl. This would allow us to share time and dates, while ensuring Residents' privacy is respected, as we do not have to request a user's timezone information. Notably, Discord has this feature, and it is used extensively by users to coordinate meetings, online times, and other information. (See this gist for examples) For example, a user may put a timestamp in their profile to show that "I am online between <timestamp a> and <timestamp b>" which shows local time. Residents on Second Life would be able to do the same thing by using this URI Extension. Some example use cases: * Specifying the start of an event, such as SLB or a shopping event. * Specifying online times. * Specifying event log times in local time.
6
Ability to selectively enable/disable device fingerprintng API of Media on each website
This is a request for a viewer Security featue (I could not find other requests about this...) I would like to request a new viewer option to selectively allow device fingerprinting by web sites through Media, based on url keyword matchs (i.e. *. google.com would allow " google.com " and all it's subdomains) so individual resident may choose to allow or disallow device fingerprinting or at least warn about potential indentity leakage when media is about to be used to show new website, and allow the resident to reject the access --- I accessed https://browserleaks.com from Media on a prim, and was able to see sepecifc information about my computer. I switched my login with an alt, and also could see the exact information. Next, I used VPN to see if the information would change, but it also did not change anything This means regardsless of the account or IP address used, the web sites on MOAP are able to capture specific unique information about my computer through the viewers. This would allow data collectors to capture device fingerprints of residents' computers just by placing an LSL object near them when the residents' media option is turned on. And finally, it also means that the data collectors can easily tie mutiple SL accounts operated on same computers I understand that Google and various other sites use this information for security (so new login from different fingerprint must to go through extra layer of authentication), and this might also be used for page rendering (i.e. streaming sites such as YouTube), so simply disabling fingerprint API would break many working media contents in-world... Since capturing screeen size by LSL function and some of the CEF's cookie was intentionally disabled to disallow fingerprintng by in-world data collectors for same safety consern, I would like to request this. I am guessing this is very poweful and accurate data collection I was unfortunately able to succeed to capture my computers fingerprints via LSL script and MOAP face in an experimets: Showing my signatures on MOAP: https://www.primfeed.com/otoa.kiyori/posts/2b175216-1392-4be1-91fb-693a3e5a2281 POC of data collection on LSL object in isolated private region: https://www.primfeed.com/otoa.kiyori/posts/b358a309-3493-485e-a1a1-63bc962a0aac
1
Load More