WIP: Boost
This is a Work In Progress proposal. It is open for discussion and subject to change.
The ad hoc boost system has got us this far, but it's abilities are limited. I am proposing a new boost delivery system.
The boost system needs the capability to deliver:
- Newsfeed Content
- Sidebar Content
- Channel Content
The boost system needs to respect the privacy of users:
- A user is assigned a boost identifier to allow anonymous tracking within minds.com
- All interaction with the boost system uses the boost identifier not the user id
- User can view all data associated with their assigned boost identifier at any time via boost console
- User can disassociate with a boost identifier and associate with a new one at will
- Explicit acceptance before any action that could compromise privacy is executed (e.g. user clicking a link to a third party site on a targeted boost could reveal their identity)
The boost system needs to use targeting to deliver relevant content and satisfy any regulatory compliance:
- Country level targeting (minimum requirement for compliance)
- User Age or some form of verification flag targeting filter (required for compliance for some categories)
- Hashtag allow/deny list
- Group allow/deny list
- Channel allow/deny list
The boost system needs to collect data to (im)prove ROI for advertisers and improve relevancy of content:
- Country of user (see above)
- Impressions (count + time duration)
- Interactions (expand/click/thumbsup/thumbsdown/subscribe/remind/comment)
The boost system needs to collect data to detect and prevent fraud:
- IP address
- GeoIP data obtained from IP address (country, connection type, proxy type)
- Device metrics for bot identification and classification (OS, Browser, Metrics collected from browser e.g. screen width, height, fonts)
The boost system will use a fully transparent algorithm to balance supply and demand.
There will be a level of revenue sharing between Minds and the creators of the content that boosted content appears alongside.
changed the description
mentioned in issue engine#1038 (closed)
added issue engine#1131 (closed)
closed
Moving to &73