Jump to content

New Review Site - A Call to Arms!


RadioRob
This topic is 947 days old and is no longer open for new replies.  Replies are automatically disabled after two years of inactivity.  Please create a new topic instead of posting here.  

Recommended Posts

As I progress with building the new review database, it's time for us to start building a team that is going to help manage/operate this new tool.  

In the past, this was done by Daddy, who:

  • Built/maintained the site
  • Reviewed all submissions and edited them as needed for grammar, etc.  
  • Verified the submissions with both the poster as well as the provider.
  • Gave the provider an opportunity to have the last word on any posted review.  

I'll continue to support the website and the tool itself from a technology perspective, but I honestly don't have the time or the interest in all of the efforts needed to verify reviews for approval.  If it's going to be done RIGHT, it will require being someone's primary attention on this site.  

So this is a call to arms...  if you want to see NEW reviews, we need a few people who will help document guidelines on how to verify reviews and once in place, handle verification of all new submissions.  It's most likely best served for me to remain focused on maintaining the site and overseeing our overall direction/vision.  

I have simplified the process of actually getting reviews "published" once approved... it's just a couple of clicks now.  The biggest efforts are going to be around verifying the data submitted and getting feedback from the provider.  

In addition, we're going to be separately looking for people to help us "migrate" reviews from the archive site over into the new review database.  This effort should be significantly less overall effort and not require any sort of long-term commitment.  Essentially it's a data entry role where someone is simplying copy/pasting data.  In this role, someone would take an existing published review from the archive and create the provider if they did not already exist and submit each review associated with the person.  (There will be a special account that can be used so each review does not show up linked to the person copying it.)

If you are interested in EITHER role, please send me a private message and indicate which you're interested in.  I will collect all of the names and work with the moderators to pick a couple of people to lead the new area.  Given the potential sensitive nature of the review, we only expect to have a couple of people selected.  There can be several people who help with the data migration.  

Link to comment
Share on other sites

Bumping this as we still are accepting nominations for both roles.

If we don't end up with an Editor, we'll end up with "Garbage In/Garbage Out".  

Everyone has told me the review site is important to them and that they find it a valuable source of information...  let's keep it that way.  

Link to comment
Share on other sites

  • 1 month later...

maybe it's too late, and I also apologize if I (or somebody else) brought these items to your attention, but here are my other thoughts / feedback about the databases:

  • Provider DB
    • General
      • What would be the process for ensuring there is only one account for a provider across multiple platform sources (e.g., RentMen, Hunqz, PlanetRomeo, others)?
      • What is the verification process for creating a provider account? Can anybody just create one?
      • What if the provider decides to change their screen name(s), do those get pulled into the same account (e.g., having 'akas')
      • Will there be verification for when accounts or profile URLs no longer exist or have since been retired?
      • I can't remember if we mentioned something about having a different escort vs. masseur vs. other type of DB, but based on the information collected, doesn't it seem like we'd just be collecting the same info? Mea culpa if I totally misunderstood this.
      • Should all of these fields be public fields, or could there be an option for keeping some of these non-public (e.g., private or for forum members only)
    • Fields, Keys
      • Is Home Location needed? I know it's not a required field, but I would think location would be mostly used for when the encounters happened, right?
      • Should there be an option, in addition to the required profile URL, to add other profile URLs for the same provider?
      • Are VoIP numbers accepted values for the phone field?
      • Should there be a gender field - with Unknown, Male, Female, Non-Binary, Transgender - Male, Transgender - Female, Other, as options?
      • For height and weight, should we have options for the metric system. For example, the drop down could be 5'9" (1.75 m) for height, and for weight, we could do 171 - 180 lbs (77 - 82 kg)
      • For build, what's the difference between defined and swimmers? Is an "athletic" build more defined or more swimmers?
      • For hair, should we have an option for 'Bald' or do we assume folks would just put 'Other'?
      • Is facial hair needed? I feel like this field can change a lot and often - I wonder how much updating and potentially LOE this would entail to manage in the future.
      • It is probably just me, but we may have overdone it with the hair categories - we got head hair, facial hair and body hair. I wonder how much of these data points folks feel are relevant to search or filter. I would suggest just getting rid of facial hair category (since of the 3 categories, facial hair tends to change more frequently on guys), and simplify Body Hair category to the following options - naturally smooth, light hairy, hairy, very hairy, and shaved.
      • I would prefer the addition of the following:
        • Smoking: Non-Smoker, Social Smoker, 420-Friendly, Heavy Smoker
        • Drinking: Non-Drinker, Social Drinker, Heavy Drinker
        • Tattoos: Yes/No
        • Piercing: Yes/No
        • Conversational Language: 
    • Non-Public / Limited View Fields - I wonder if it's possible to add the following fields:
      • Endowment Size - Unknown, Small (less than 5"), Average (5" - 7"), Large (7" - 9"), XL (over 9"), Other
      • Cut or Uncut
      • Fetish
      • S&M: Full, Soft S&M, No S&M
      • Position: Unknown, Top, Versatile Top, Versatile, Versatile Bottom, Bottom, Other
      • Safety: Unknown, Safe Only, Anything Goes
      • HIV Status: Unknown, Negative, Positive, Undetectable, Other
      • STI Status: Unknown, Negative, Positive, Other
      • Service Offering:
        • Massage - Deep Tissue
        • Massage - Sports
        • Massage - Sensual
        • Massage - Erotic
        • Companionship
        • Escorting
        • Videos
        • Modeling
        • Boyfriend Experience
      • Preferences - Giving: Anal, Feet, Latex, ..., Kissing, Water Sports
      • Preferences - Receiving: Anal, Kissing, Oral
      • Payment Methods: Cash, Venmo, Zelle, ...
  • Review DB - [i'll add/edit tomorrow]
Link to comment
Share on other sites

18 minutes ago, JoeMendoza said:

maybe it's too late, and I also apologize if I (or somebody else) brought these items to your attention, but here are my other thoughts / feedback about the databases:

  • Provider DB
    • General
      • What would be the process for ensuring there is only one account for a provider across multiple platform sources (e.g., RentMen, Hunqz, PlanetRomeo, others)?
        • The unique factor is the person, not what platforms they're on.  I *could* potentially make the name field unique, but we have times where there is two different providers that have the same name.  Daddy handled this by just adding a number after the name.  (Jake, Jake #2, Jake #3).  If someone creates a new provider account for one that already exists, editors will remove the duplicate records.  (People can report duplicate records also.)
      • What is the verification process for creating a provider account? Can anybody just create one?
        • Creating a provider record can be created by anyone.  We're not doing any initial validation of the record, however editors can and will make changes as needed.  If someone is abusing creating records, they can have that ability removed.  Editing a record can only be done by an editor.  If any records need updated, someone would just report the record and note what needs corrected.
      • What if the provider decides to change their screen name(s), do those get pulled into the same account (e.g., having 'akas')
        • Report the post.  Editors can change the name to the new alias and will add the old one to the "Old Alias" record field.  
      • Will there be verification for when accounts or profile URLs no longer exist or have since been retired?
        • There is nothing that checks for the profile to load.  However if the profile is reported, a provider can be flagged as inactive.  
      • I can't remember if we mentioned something about having a different escort vs. masseur vs. other type of DB, but based on the information collected, doesn't it seem like we'd just be collecting the same info? Mea culpa if I totally misunderstood this.
        • Once I finalize the major features of the escort database, my plan is to clone the system to also support masseurs, venues, social profiles (JFF/OF), etc. 
      • Should all of these fields be public fields, or could there be an option for keeping some of these non-public (e.g., private or for forum members only)
        • What fields will be public, member only, or limited to "subscriber only" is something that can be supported, however specific determinations on exact permissions have not been decided.  
    • Fields, Keys
      • Is Home Location needed? I know it's not a required field, but I would think location would be mostly used for when the encounters happened, right?
        • Yes.  It's needed to support finding a provider by location.  In order to find a provider by location, the provider record needs to have it.  Individual reviews also need a location to handle travel scenarios.  
      • Should there be an option, in addition to the required profile URL, to add other profile URLs for the same provider?
        • I'll think about this later.  
      • Are VoIP numbers accepted values for the phone field?
        • Yes
      • Should there be a gender field - with Unknown, Male, Female, Non-Binary, Transgender - Male, Transgender - Female, Other, as options?
        • If we end up with enough interest in this later, I can add it.  
      • For height and weight, should we have options for the metric system. For example, the drop down could be 5'9" (1.75 m) for height, and for weight, we could do 171 - 180 lbs (77 - 82 kg)
        • I asked about this and there was not a lot of interest from the community.  In looking at stats, 90% of our site activity comes from the US.  So this could be something to add later.  
      • For build, what's the difference between defined and swimmers? Is an "athletic" build more defined or more swimmers?
        • Good question.  I copied the options from Daddy's drop down.  I could remove one of the fields, but then again someone will ask for it to be added if I do.  haha
      • For hair, should we have an option for 'Bald' or do we assume folks would just put 'Other'?
        • Again, copied from Daddy's.  However I added Bald as an option.  
      • Is facial hair needed? I feel like this field can change a lot and often - I wonder how much updating and potentially LOE this would entail to manage in the future.
        • I asked this earlier and people indicated it was important to them.  If there are changes it would need to be reported by someone.  Editing a record is only a few seconds.  If it matters to someone enough to go looking for it and reporting a change, we can spend the 10 seconds to update the record or just note that it just changes frequently.   
      • It is probably just me, but we may have overdone it with the hair categories - we got head hair, facial hair and body hair. I wonder how much of these data points folks feel are relevant to search or filter. I would suggest just getting rid of facial hair category (since of the 3 categories, facial hair tends to change more frequently on guys), and simplify Body Hair category to the following options - naturally smooth, light hairy, hairy, very hairy, and shaved.
        • Again, I tried to cut these down but there were several people saying it was important to them.  We're not going to please everyone here!
      • I would prefer the addition of the following:
        • Smoking: Non-Smoker, Social Smoker, 420-Friendly, Heavy Smoker
        • Drinking: Non-Drinker, Social Drinker, Heavy Drinker
        • Tattoos: Yes/No
        • Piercing: Yes/No
        • Conversational Language
    • Non-Public / Limited View Fields - I wonder if it's possible to add the following fields:
      • Endowment Size - Unknown, Small (less than 5"), Average (5" - 7"), Large (7" - 9"), XL (over 9"), Other
      • Cut or Uncut
      • Fetish
      • S&M: Full, Soft S&M, No S&M
      • Position: Unknown, Top, Versatile Top, Versatile, Versatile Bottom, Bottom, Other
      • Safety: Unknown, Safe Only, Anything Goes
      • HIV Status: Unknown, Negative, Positive, Undetectable, Other
      • STI Status: Unknown, Negative, Positive, Other
      • Service Offering:
        • Massage - Deep Tissue
        • Massage - Sports
        • Massage - Sensual
        • Massage - Erotic
        • Companionship
        • Escorting
        • Videos
        • Modeling
        • Boyfriend Experience
      • Preferences - Giving: Anal, Feet, Latex, ..., Kissing, Water Sports
      • Preferences - Receiving: Anal, Kissing, Oral
      • Payment Methods: Cash, Venmo, Zelle, .
        • I'm thinking about including non-public fields.  This sort of data could potentially become a premium type feature.   Again though...  the more fields we have, the longer and more effort it will take to submit.  

 

Link to comment
Share on other sites

On 8/17/2021 at 9:20 PM, JoeMendoza said:

maybe it's too late, and I also apologize if I (or somebody else) brought these items to your attention, but here are my other thoughts / feedback about the databases:

  • Provider DB
    • General
      • What would be the process for ensuring there is only one account for a provider across multiple platform sources (e.g., RentMen, Hunqz, PlanetRomeo, others)?
      • What is the verification process for creating a provider account? Can anybody just create one?
      • What if the provider decides to change their screen name(s), do those get pulled into the same account (e.g., having 'akas')
      • Will there be verification for when accounts or profile URLs no longer exist or have since been retired?
      • I can't remember if we mentioned something about having a different escort vs. masseur vs. other type of DB, but based on the information collected, doesn't it seem like we'd just be collecting the same info? Mea culpa if I totally misunderstood this.
      • Should all of these fields be public fields, or could there be an option for keeping some of these non-public (e.g., private or for forum members only)
    • Fields, Keys
      • Is Home Location needed? I know it's not a required field, but I would think location would be mostly used for when the encounters happened, right?
      • Should there be an option, in addition to the required profile URL, to add other profile URLs for the same provider?
      • Are VoIP numbers accepted values for the phone field?
      • Should there be a gender field - with Unknown, Male, Female, Non-Binary, Transgender - Male, Transgender - Female, Other, as options?
      • For height and weight, should we have options for the metric system. For example, the drop down could be 5'9" (1.75 m) for height, and for weight, we could do 171 - 180 lbs (77 - 82 kg)
      • For build, what's the difference between defined and swimmers? Is an "athletic" build more defined or more swimmers?
      • For hair, should we have an option for 'Bald' or do we assume folks would just put 'Other'?
      • Is facial hair needed? I feel like this field can change a lot and often - I wonder how much updating and potentially LOE this would entail to manage in the future.
      • It is probably just me, but we may have overdone it with the hair categories - we got head hair, facial hair and body hair. I wonder how much of these data points folks feel are relevant to search or filter. I would suggest just getting rid of facial hair category (since of the 3 categories, facial hair tends to change more frequently on guys), and simplify Body Hair category to the following options - naturally smooth, light hairy, hairy, very hairy, and shaved.
      • I would prefer the addition of the following:
        • Smoking: Non-Smoker, Social Smoker, 420-Friendly, Heavy Smoker
        • Drinking: Non-Drinker, Social Drinker, Heavy Drinker
        • Tattoos: Yes/No
        • Piercing: Yes/No
        • Conversational Language: 
    • Non-Public / Limited View Fields - I wonder if it's possible to add the following fields:
      • Endowment Size - Unknown, Small (less than 5"), Average (5" - 7"), Large (7" - 9"), XL (over 9"), Other
      • Cut or Uncut
      • Fetish
      • S&M: Full, Soft S&M, No S&M
      • Position: Unknown, Top, Versatile Top, Versatile, Versatile Bottom, Bottom, Other
      • Safety: Unknown, Safe Only, Anything Goes
      • HIV Status: Unknown, Negative, Positive, Undetectable, Other
      • STI Status: Unknown, Negative, Positive, Other
      • Service Offering:
        • Massage - Deep Tissue
        • Massage - Sports
        • Massage - Sensual
        • Massage - Erotic
        • Companionship
        • Escorting
        • Videos
        • Modeling
        • Boyfriend Experience
      • Preferences - Giving: Anal, Feet, Latex, ..., Kissing, Water Sports
      • Preferences - Receiving: Anal, Kissing, Oral
      • Payment Methods: Cash, Venmo, Zelle, ...
  • Review DB - [i'll add/edit tomorrow]
  • Review DB - 
    • General Feedback
      • Do we need the 'Unknown' option for either communication or matched description? Could we potentially default the drop down to a blank value but disallow submission unless the reviewer actually replaces the blank default value with a non-default one (1 thru 5)?
      •  
    • Fields / Keys
      • What does 'other' represent for encounter type?
      • Rate: we probably meant <$100 for the first value in the drop down.
      • Rate: would suggest to continue the $100 increment through $2K. 
      • Rate: would suggest adding $2000-2499, $2500-$2999, $3000-$3499, $3500-$3999, $4000-$4499, $4500-$4599, >$5000
      • Like in RentMasseur - any way we could differentiate between time booked vs. actual session time?
      • Time: does it make sense to have < 1 hour in the drop down, if we are going to have < $100 as a rate option? Can we also add 5 hours as an option?
      • Time: should we quantify what we mean by the following options - afternoon, evening, day, extended?
      • Could there possibly be 1-5 rating for whether services were rendered as advertised (maybe a field for 'Satisfaction'?)? Also, another for hygiene.
    • Non-Public / Limited View Fields
      • Similar to RentMen, I wonder if there is also a free text field for a reviewer to note something specifically for the moderators / review editors but not necessarily for publication.
      • Perhaps also having an option for forum members to see other nsfw feedback (i.e., stuff that someone would discuss via PM).
      • Any chance there could be a limited view field for the types of services / preferences were rendered during the encounter? or give an option for the reviewer to multi-select options of what activities were involved with the encounter with obviously an option for 'prefer not to disclose'? maybe this is too much but was just thinking it might give a forum member a much more informed context of seeing a 5-star review for just an oral session (which could very well be what the client wanted) vs. the entire end-to-end BFE or fantasy experience.
Link to comment
Share on other sites

As far as rates are concerned personally I’m not convinced of the benefit of having this as a drop down field rather than a numeric (or free text) field that records the actual price paid for the session, particularly if this is primarily being done in order to try supporting searching by price the same way as other attributes.

There are a considerable number of factors that can influence the price of a session (or hour):

  • incall, “incall” where the escort books a hotel room etc rather than use their own place vs outcall
  • duration:some escorts give a significantly discounted rate for multiple hours/overnight… others simply multiply their hourly rate by the length of session, it therefore isn’t possible to work out what a provider will charge for one hour based on the price of a longer session
  • Location: “average” rates vary considerably from city to city and from country to country and a travelling escort may or may not adjust their rates to reflect their current location
  • Activities: some providers charge extra depending on what has been requested whilst others charge a fixed price based purely on time
  • loyalty discounts/grandfathered rates which regulars may get that aren’t offered to new clients
  • Location of advert/method initial contact (I’ve heard of a few providers that vary their rates based on where they are advertising)
  • When the encounter occurred… due to inflation prices from 5-10 years ago aren’t directly comparable to prices being charged now
  • Currency fluctuations (where the session wasn’t originally paid for in US$).  A change in exchange rates may change which band a price maps to even if the provider hasn’t actually changed their rate at all

This all makes it extremely tricky to produce a single value that is comparable between reviews and therefore useful for a search

As someone who doesn’t live in the US I’d also much prefer to see prices shown in the local currency for where the encounter occurred than in US$ as this minimises the amount of currency conversion needed to figure out what a similar session might cost and what the equivalent might be in my own currency and it is much easier and less prone to error for a reviewer to report what they actually paid than worry about converting the amount to US$

In my opinion the fixed sized bands also don't work very well as they fail to distinguish sufficiently between different prices at the lower end (Eg: in cheaper markets) and don’t go high enough for longer multi day sessions in more expensive markets….  As an example until recently in the UK £150 was fairly average whilst £200 was quite high yet both fall in to the same $200-$299 band when the prices are converted to US$.

Having the price of the session shown alongside all of the other details of the review does provide some useful context for the review even if it isn’t a good way of carrying out an initial search,

If a searchable field giving an indication of price is desired then an extra field recording a simple rating of how the provider compares against other providers in the same market might be more useful than the current price bands, as long as the actual price paid is still recorded and shown in the search results.

Link to comment
Share on other sites

On 8/18/2021 at 10:24 PM, JoeMendoza said:
  • Review DB - 
    • General Feedback
      • Do we need the 'Unknown' option for either communication or matched description? Could we potentially default the drop down to a blank value but disallow submission unless the reviewer actually replaces the blank default value with a non-default one (1 thru 5)?
      • Have we considered how reviews work for a single encounter with multiple providers (e.g., threesome, group play)? just wondering how the associated rates would work (would it be for the entire encounter, average rate per provider). if the review is intended to be for each individual provider, I wonder how it could work in situations when each provider have different rates for a session. for example, provider A charges $350 per hour or $1800 overnight and provider B charges $200 per hour or $1200 overnight.
    • Fields / Keys
      • What does 'other' represent for encounter type?
      • Rate: we probably meant <$100 for the first value in the drop down.
      • Rate: would suggest to continue the $100 increment through $2K. 
      • Rate: would suggest adding $2000-2499, $2500-$2999, $3000-$3499, $3500-$3999, $4000-$4499, $4500-$4599, >$5000
      • Like in RentMasseur - any way we could differentiate between time booked vs. actual session time?
      • Time: does it make sense to have < 1 hour in the drop down, if we are going to have < $100 as a rate option? Can we also add 5 hours as an option?
      • Time: should we quantify what we mean by the following options - afternoon, evening, day, extended?
      • Could there possibly be 1-5 rating for whether services were rendered as advertised (maybe a field for 'Satisfaction'?)? Also, another for hygiene.
    • Non-Public / Limited View Fields
      • Similar to RentMen, I wonder if there is also a free text field for a reviewer to note something specifically for the moderators / review editors but not necessarily for publication.
      • Perhaps also having an option for forum members to see other nsfw feedback (i.e., stuff that someone would discuss via PM).
      • Any chance there could be a limited view field for the types of services / preferences were rendered during the encounter? or give an option for the reviewer to multi-select options of what activities were involved with the encounter with obviously an option for 'prefer not to disclose'? maybe this is too much but was just thinking it might give a forum member a much more informed context of seeing a 5-star review for just an oral session (which could very well be what the client wanted) vs. the entire end-to-end BFE or fantasy experience.

 

Link to comment
Share on other sites

This topic is 947 days old and is no longer open for new replies.  Replies are automatically disabled after two years of inactivity.  Please create a new topic instead of posting here.  

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...