Because I'm a Tease...

[RadioRob]

Ya'll saw some of the stuff I was doing before with the new review site, but had to put it on hold due to IPB5.  Well, it's out and I've been playing around with it in my test server.  This stuff is pure raw native Invision and not just custom pages databases.  It's truly built into the core system.  

And if you've scrolled this far...  I've got one more thing... I wonder if anyone is gunna catch it.   

 

[+ Vegas_Millennial]

5 hours ago, RadioRob said:

Ya'll saw some of the stuff I was doing before with the new review site, but had to put it on hold due to IPB5.  Well, it's out and I've been playing around with it in my test server.  This stuff is pure raw native Invision and not just custom pages databases.  It's truly built into the core system.  

And if you've scrolled this far...  I've got one more thing... I wonder if anyone is gunna catch it.   

 

I see you'll be asking for rent.men but not RentMen.eu (which many find easier to use and still work with the current Company of Men site).

[RadioRob]

1 hour ago, Vegas_Millennial said:

I see you'll be asking for rent.men but not RentMen.eu (which many find easier to use and still work with the current Company of Men site).

It’s a text styling issue. I actually support both. What happens though is I’m only going to take whatever you submit as a .eu value and process it through .men because the data mapping of results is better. The .men hands back info as a structured JSON object that can be more easily be read by machines so the site here can translate it to our website values. (We have to convert things like metric to imperial, change field values from their naming schema from their format to ours, etc)

But yes… I want to make it easier to import data so you don’t have to type it in. 

It basically is a “pre-fill” or suggest tool. On the next screen you can still see and change anything there. (For example you can change the age if you know it’s not correct.)  it will also try to automatically import pictures from the ad. 

I’m also building in a “Suggest a Change” feature where you can suggest fields about the record be updated. It will have an option to pull from the existing ad again to pull new information or to tell us there was a name change to X is now Y and we will change the name and add the old value to a field called “AKA”.  That means if you search for OldName, it will return the result and direct you to NewName. 

The first time a subject (escort, masseur, or venue) is created it will create a specific “master”  thread in the correct forum. The goal is over time the questions about that person will go there and we can start folding the multiple “411s on” to it and have a central spot for discussion. 

I’ve been trying to give this a LOT of thought to make it truly blended into the community here. Reviews that you have written have even been added to your profile. 

[RadioRob]

I've built reviews into the notification system here into the site as well.  

[viewing ownly]

Thank you for taking the time to do this. It will be a valuable help the more people contribute to hold the best weight with who is worth seeing, and who isn't. 

[savantsav]

Don't forget about the serial renamers. 

[RadioRob]

8 hours ago, savantsav said:

Don't forget about the serial renamers. 

I've thought about this already and have a workflow designed around it.  

All records will have a "Propose a Change".  That allows you to pick two options.  The first will be to propose a change to the record.  (Something is wrong such as the wrong city, or height, etc). The other will be to report a name change.

When you paste the link to the ad, it will try to grab the info necessary and then allow you to submit it to a moderator to review.  The moderator can then accept/reject, etc.  It even detects if the name is already in our database and will allow a moderator to merge a record if necessary.  

The outcome will be something like:

I've also built it in so if you search for BobJones, it will automatically map results to JudasE for example.  So both work in the search box.  We won't change the text in the reviews itself (so if someone says Judas was great, I won't change the text they entered to say "Bob was great").  This is by design.  The reviews stand alone and separate from the subject.  

And just to be clear...  the propose a change only applies to the subject itself (meaning to the escort, masseur, or venue).  NOT TO THE REVIEW!  Random people don't get to propose a change to someone's review. 

[+ JamesB]

I’m not sure if this would be considered TMI, but adding the provider’s phone number, which is publicly listed in the ad, could definitely help with detecting name changes.

[RadioRob]

3 minutes ago, JamesB said:

I’m not sure if this would be considered TMI, but adding the provider’s phone number, which is publicly listed in the ad, could definitely help with detecting name changes.

I'm trying to be very careful with that for now.  Phone numbers and emails are technically PII.  I have some thoughts, but I need to reason that a little more.  It absolutely won't be available to guests.  I'm wondering if it makes sense that it be only available to the Supporters group or something similar as a way to limit the blast radius. 

[+ JamesB]

8 minutes ago, RadioRob said:

I'm trying to be very careful with that for now.  Phone numbers and emails are technically PII.  I have some thoughts, but I need to reason that a little more.  It absolutely won't be available to guests.  I'm wondering if it makes sense that it be only available to the Supporters group or something similar as a way to limit the blast radius. 

You could use the phone number strictly on the backend for entity resolution and simply expose the relationship, such as “Linked to 2 other profiles,” without revealing the actual contact information

[mike carey]

4 minutes ago, RadioRob said:

I'm trying to be very careful with that for now.  Phone numbers and emails are technically PII.  I have some thoughts, but I need to reason that a little more.  It absolutely won't be available to guests.  I'm wondering if it makes sense that it be only available to the Supporters group or something similar as a way to limit the blast radius. 

My immediate thought would be that RM ads do not display the phone number when a profile is expired or the advertiser has paused them. They would be aware of this, and I'd have thought that in some, or even many cases they would be using that so that potential clients could not see the number when, for whatever reason, their ad was not active. I don't think we should be providing a way to circumvent that.

[mike carey]

4 minutes ago, JamesB said:

You could use the phone number strictly on the backend for entity resolution and simply expose the relationship, such as “Linked to 2 other profiles,” without revealing the actual contact information

There's a reasonable case for anyone (not just the moderators of a site) to use any public facing information to link two apparently separate ads. The case is less persuasive for someone to use information that is not currently available publically. There is probably no case for the site to use it to make such a link and publish it, and certainly no case to publish it where non-members can see it, or even as @RadioRob suggests, members who are not at least site supporters.

[RadioRob]

This is exactly why that specific topic is on the back burner for now.  A LOT to work through and consider more broadly.  In the meantime, there are much easier wins in terms of capabilities that can drive this.  So that's where I'm focusing on first.  

[Rayphactor]

Thanks for the work you're putting into it!

[RadioRob]

You can now track your contributions.  

Revising a review...

Checking for existing escort accounts (including showing former names if we know them)