Mismatch options #228
Replies: 1 comment
-
This problem stems from the F-List data model that does not offer a reliable way to signal interest towards non-binary characters. Unfortunately, I consider this to be unfixable until the F-List team makes significant changes to their backend. Having said that, I'm open to find workarounds -- as long as they do not negatively impact binary characters. For example, reducing the strictness of the matching algorithm does not only affect your character. I'm not keen on solutions where the match results aren't same for both characters in question. So, imagine that your character A matches with character B in this 'loose' comparison mode. At the same time, the experience from B's view could be that your characters aren't a match, because they have the 'stricter' comparison mode enabled. This will be highly confusing. I have been playing with an idea to prompt users to declare their interest explicitly, if their character's kinks aren't already specified to do so. But this is disruptive and wouldn't affect any user outside of F-Chat Rising users, so not an ideal approach either... |
Beta Was this translation helpful? Give feedback.
-
I've been using F-Chat Rising pretty much exclusively for a long time now, but there are a handful of things that're just an absolute headache for me. Namely, 'automatic' mistmatches.
I can understand the logic for some of these, but more often than not, it makes things more difficult rather than easier. Profiles automatically being set as 'no' matches because of kinks I don't have listed or, more frustratingly, kinks THEY don't have listed, feels less than ideal. It means profiles built around custom kinks, or that don't specifically include herm/shemale/transgender when I'm on my non-binary characters just show up as not compatible. Roughly half my RP's on a herm character of mine are with people f-chat rising says are flat out not compatible.
Towards that end, would it be possible to set these automatic functions via settings instead of it being hard-coded? At this point, the 'compatibility' layer is actually proving so unreliable that I'm more or less ignoring it and considering trying to figure out how to disable it entirely.
Beta Was this translation helpful? Give feedback.
All reactions