How to Rank User Profiles using profile characteristics - search

I am wondering how I would go about ranking my websites user profiles on certain characteristics: such as keywords withing profile sections, and sign up form answers...
Any Ideas on where to begin?

If you want to rank a user profile, then you better to use other user profile's specifications as a parameter to help you in raking. I don't know which websites you are using to rank, but I will assume that you want to rank all websites user profiles. So you can use these specifications generally:
If the web site gives the user some points per posts like stackoverflow.com so you can rank user profiles according to the points they have got.
You can use "Number of profile seen by other user" to rank too.
Also, you can use "Number of Posts Published by the User".
"User availability per day or month"
I hope these issues can you help while ranking user profiles.

Related

If a website stores a name and email address for authentication purposes, is that covered by GDPR?

I am setting up a website as a volunteer for a scout charity. As part of the web functionality we will be storing email addresses and names in a database with password hashes and some other info such as creation date and site roles.
Is this something that would be covered by GDPR? I have tried to do some reading online but can't seem to find something definitive that covers this use case.
Yes Norman it is personal data and hence processing it (which includes storing it) comes under GDPR ambit, You may want to mention it in your privacy notice stating the high level purpose it is used for and just to ease the users let the users know, the data is not being passed to other third parties.
IAPP is good authoritative and credible site for all such queries. You may want to read this series.
https://iapp.org/news/a/business-impacts-of-the-general-data-protection-regulation-part-three/

how to "dont vote twice" mechanism

I was thinking of creating a voting app. The general idea is
browse a gallery
an awesome pic grabs your attention
hit the vote button underneath it
code magic happens
vote is counted
at a certain date, vote buttons become non-active and the app counts
the votes
This will be a web app, which means html5-css3-express.js-redis framework, or something similar.
How can I ensure that the user cannot vote for the same pic twice? By making him sign up? Huge procedure for just a voting app, dont you think? Plus, I guess I will also need a CAPTCHA thing to avoid unwanted, mass sign up.
But if I use coockies of HTML5 local Storage API, what is stopping the same user to clear his/her coockies and vote for the same pic again and again?
What is the best method?
Thanks alot
The most secure way is by using accounts to keep track of who has voted. Accounts are easy to implement in your application and you don't even need to hold the account data yourself if you use a service like Passport.js. You'll likely have a database set up already which makes it easy to keep account data as well.
The other method is to keep track of IP addresses but this has some issues (say, if a user uses a proxy). Also an IP address will cover all clients on a network means if one person votes on an image, all others will be unable to afterwards.
Easy way may be using npm package mongoose-voting where all logic for voting is already implemented.
There is also requirement for keeping track of users, so if you don't want a user to sign-up, you can automatically create a user by using the visitor’s IP address as the user’s ID.
There are many ways to manipulate vote results, but at the level you described, most of them are unnecessary.
well you dont need to build a login system these days as you can use any of the open id login authentication.E.g providers are facebook, google, yahoo and twitter.

Website tracking cookies

I read about website tracking cookies at "http://www.newfangled.com/unlimited_vs_limited_web_tracking" and am wondering how they are implemented.
On page 2 of the article, the author writes, "third-party trackers using beacon technology can match the data they collect about you in real time with other databases containing geolocation, financial, and medical information in order to expand your profile to predict your age, gender, zip code, income, marital status, parenthood, home ownership, as well as unique interests."
I've thought of a few ways trackers could be implemented and am hoping answers to the following questions will help me get some clarity about how trackers work.
When you visit a website, do all of your cookies become available to the website? E.g., if I visited StackO.com , would the site be able to access my facebook/google/other cookies?
To track your visits from site to site, do various websites share information in a database, i.e. when you visit FB, google, CNN...do they log your activity in a shared database that's accessible by companies in the group?
When you visit a website, do all of your cookies become available to the website?
Yes
To track your visits from site to site, do various websites share information in a database, ie when you visit FB, google, CNN...do they log your activity in a shared database that's accessible by companies in the group?
Yes
In general, yes. If you look at cookies set by CNN.com for example, there's cookies set for scorecardresearch.com domain:
http://webcookies.info/cookies/cnn.com/11993/
Then there's some JavaScript code or 1x1 image that actually creates a request to the scorecardresearch.com servers. This way Scorecard Research can track you as you move from CNN to other websites. And they will definitely aggregate the information from various websites using their technology.
Profiling is just making use of this aggregated behavioral data.

How to hide form fields in a new company

I have an AX 2009 installation with 5 companies.
The current security configuration contains groups of users which are company specific, and the companies are in their own domains (1 per company).
I am adding a new company, however for this new company I do not want various groups to be visible on certain forms.
How do I achieve this without affecting the existing companies?
I have tried (in test environment) to add a new security key, however the security key defaults to "no access". When applied to a group on a form, the group becomes hidden; This is okay for my new company, but I would then need to go through every other user group and set back to full control, so that users in the existing companies can still see the field group.
There is a built-in function in AX called curExt() that will tell you the name of the users current company. You could do the following on the form if you set the auto declare property of the groups on the form to Yes:
if(curExt() == "NewCompany")
{
GroupNameThatShouldNotBeVisible.visible(false);
}
Then you will not need to worry about setting up security keys for all the companies.
I disagree with Michael Brown and Vince Perta just on the basis of best practices and best practices here would be to use security keys and domain setup. That said however, if you're not a consultant working across many clients and you're an in-house developer...it's not a big deal to use curExt() and hardcode the companies and security settings you want.
I'm having a bit of trouble following exactly how you're doing the security groups and why it's difficult...but I'd make a copy of Live to Test, make the security changes as needed for all of the companies, then just export them out to a file, then import into Live. Are you worried about the disruption to the live users or what exactly?

What technical security can I implement to help protect a public profile from a cyber stalker?

We run a website that has a number of public content makers that represent the public faces of our project.
One of the people has a previous online stalker who has found her at our site and has immediately started commenting on her posts and content.
Aside from tracking and blocking his IP what sort of technical solutions can I be implementing to help alleviate the situation?
There's not much you can do besides restricting access to information (eg: name, phone-number, email, etc.).
For example, your site could just not display anything but firstName lastInitial and the email (if necessary) to unregistered users, or registered users with insufficient permissions. Permission levels and information displayed could be tweaked according to your needs.
But ultimately it's up to the person posting content online to be careful with what they show/publicize on your site and elsewhere on the net. It would be useless for you to restrict access to information, but then she has her email and if you Google the email (or look her up on facebook) and her information is there.
Honestly I am a bit surprised by the way people feel free to post their email, real name, phone number, address, etc. online nowadays. I come from days where people liked to be anonymous online; and up until now a Google search for my personal email still comes up empty.

Resources