A great response to a complex issue.
Hope to see more fantasy on this topic, with any real equivalents being obviously separate from a story/tease/game.
- - -
mistressamber wrote: ↑Wed Jan 17, 2024 10:44 am
I'm thinking of my next tease idea, also blackmail themed, but more on the 'clear consent' side.
...
Teasing kisses,
Mistress Amber
Look forward to it!
- - -
@seraph0x - I'd like to make few minor suggestions;
seraph0x wrote: ↑Wed Jan 17, 2024 7:28 am
Planned Eos Changes
- Improved handling of Unicode content, taking into account recommendations from the UTS 36 / UTS 39 reports. Invisible characters should only be allowed in contexts where they are necessary. All messages should be single-script. Existing content should be reviewed to ensure these changes have minimal impact on existing, legitimate content.
- Any use of the clipboard (copy/paste) will trigger a warning. (Something like: "Any link or text copied from Eos may contain information that you have entered during the course of this tease or previous sessions with this tease. This information may be cleverly hidden and a pretext for copying may be used to mislead you. By continuing, you understand that you are trusting the tease author with your data and that Milovana cannot protect your data once it leaves our site. Are you sure you want to copy from this tease?")
- We may start to allow clickable links, but clicking them will trigger a warning. (Something like: "You are about to leave Milovana and any information that you entered into this tease could be sent to [website] or other third parties, are you sure you want to continue?")
- We will think about ways that we can bring certain popular types of content in-house such as videos, puzzles, etc. to reduce the need for external links in the first place. Reducing the demand for unsafe practices is an important aspect of secure design.
- We will consider creating additional safety information around subjects like BM that can be attached to teases by the author or a moderator.
- Please avoid creating an popup interrupt situation.
These have become highly tedious, where every act and click we do online/in-app's requires secondary clicks to do precisely what the UI provided.
A non-interrupt warning appearing in the corner would achieve mostly the same result.
- Although the text input function provides some great teasing opportunities, the frequency that tease authors now demand a input of [name] / [other details] before you can (pre-)view the tease is getting ridiculous.
Instead, each time a text input is requested, would it be reasonable to have EOS require a [default] input available (chosen by author), quickly selectable of-side.
Added bonus, debugging tease save-data would be easier as their defaults could be set to always allow a tease to work as intended by author.
Overall, really interesting discussion topic.
Stay Sexy!