Substance Use Risk Tracking and Scoring System #889

theimperious1 · 2024-11-14T20:17:23Z

theimperious1
Nov 14, 2024

Context: Expanding TripBot's functionality on Discord with a focus on private, real-time substance tracking, risk assessment, and harm reduction.

Commands like /dose would provide reminders and guidance throughout the session, including:

Time to Onset: Reminders for when effects may start.
Hydration and Self-Care: Prompts for hydration and helpful self-care actions.
Comedown Tips: Tips for managing the comedown.
TripSit Channel Reminders: A gentle nudge to visit TripSit channels for extra support if needed.

The bot would privately track and score users’ substance use patterns, assessing risk levels based on:

Frequency: How often the substance is used.
Dosage and Tolerance: Amount taken and level of tolerance.
Combinations: Risk scores based on dangerous combinations, such as:
- Staying awake on meth for 5 days: High risk score.
- Repeating high-risk behaviors within a short timeframe: Exponentially higher score.
- Mixing cocaine and alcohol: Moderate risk score.
- Combining opioids and benzodiazepines: High risk score.
- Using opioids, benzos, and stimulants together: Massive risk score.

Monthly Overview: Risk scores reset monthly, allowing users to track changes in behavior and risk.
Yearly Summary: A yearly tally provides a long-term visualization of the user’s risk habits.
Trend Awareness: Monthly carryover without additional increases from repeated actions, helping users maintain or improve their habits over time.

Color-Coded Scoring:
- Green = Low risk, Yellow = Moderate risk, Red = High risk.
Anonymous Leaderboard:
- Displays anonymous risk scores for a general comparison, offering users insight into their habits relative to others.
- Users may feel encouraged to lower their score to improve their ranking.
Behavior Comparison:
- Helps users identify that certain behaviors they view as “safe” may carry the same risk as behaviors they know are dangerous, offering perspective on their habits.

Data Encryption: User data would be encrypted and associated with a user-generated password.
No Command Logging: Commands wouldn’t be logged, and data would only be accessible through the user’s password.

Example Commands:
- /idose drug: [substance], dosage: [amount], additionalInfo: [details], key: [password]
- /drugoverview key: [password] (for a monthly summary)

This concept is a work-in-progress and may evolve with further feedback and consideration for privacy.

Feedback and further ideas are welcome!