👻 A Snapscore tracker that reports various metrics such as time differences, score increases, snaps sent and received, snap rates per minute, hour, and day and much more
Report Bugs
Troubleshooting
| Date | Time Difference | Snapscore | Increase | Increase Difference | Snaps Sent | Number of Snaps Sent Since Last Time | Snaps Opened | Number of Snaps Opened Since Last Time | Number of People Snapped | Number of People Snapped Since Last Time | Snap Rate / min | Snap Rate / hour | Snap Rate / day |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024-06-13 18:46:00 | 179396 | 0 | 0 | 0 | 0 | ||||||||
| 2024-06-13 18:50:00 | 4 minutes | 179400 | 4 | 4.0 | 2 | 2.0 | 2 | 2.0 | 2 | 2.0 | 1.0 | ||
| 2024-06-13 19:04:00 | 14 minutes | 179405 | 5 | 1.0 | 2 | 0.0 | 3 | -1.0 | 2 | 0.0 | 0.3571428571428571 | ||
| 2024-06-14 14:29:00 | 19 hours, 25 minutes | 179512 | 107 | 102.0 | 53 | 51.0 | 54 | 51.0 | 53 | 51.0 | 0.0918454935622317 | 5.883347421808961 | |
| 2024-06-14 15:40:00 | 1 hours, 11 minutes | 179514 | 2 | -105.0 | 1 | -52.0 | 1 | -51.0 | 1 | -52.0 | 0.028169014084507 | 1.6901408450704225 | |
| 2024-06-14 15:46:00 | 6 minutes | 179518 | 4 | 2.0 | 2 | 1.0 | 2 | 1.0 | 2 | 1.0 | 0.6666666666666666 | ||
| 2024-06-14 15:56:00 | 10 minutes | 179523 | 5 | 1.0 | 2 | 0.0 | 3 | -1.0 | 2 | 0.0 | 0.5 | ||
| 2024-06-14 16:08:00 | 12 minutes | 179531 | 8 | 3.0 | 4 | 2.0 | 4 | 3.0 | 4 | 2.0 | 0.6666666666666666 | ||
| 2024-06-14 16:18:00 | 10 minutes | 179534 | 3 | -5.0 | 1 | -3.0 | 2 | -4.0 | 1 | -3.0 | 0.3 | ||
| 2024-06-14 16:18:30 | 30 seconds | 179537 | 3 | 0.0 | 1 | 0.0 | 2 | 0.0 | 1 | 0.0 | |||
| 2024-06-14 16:52:00 | 33 minutes, 30 seconds | 179543 | 6 | 3.0 | 3 | 2.0 | 3 | 3.0 | 3 | 2.0 | 0.2727272727272727 | 24.507042253521128 | |
| 2024-06-14 17:11:00 | 19 minutes | 179549 | 6 | 0.0 | 3 | 0.0 | 3 | 0.0 | 3 | 0.0 | 0.3157894736842105 | ||
| 2024-06-14 17:18:00 | 7 minutes | 179551 | 2 | -4.0 | 1 | -2.0 | 1 | -2.0 | 1 | -2.0 | 0.2857142857142857 | ||
| 2024-06-14 17:28:00 | 10 minutes | 179552 | 1 | -1.0 | 0 | -1.0 | 1 | -2.0 | 0 | -1.0 | 0.1 | ||
| 2024-06-14 18:10:00 | 42 minutes | 179562 | 10 | 9.0 | 5 | 5.0 | 5 | 6.0 | 5 | 5.0 | 0.238095238095238 | 14.615384615384617 | |
| 2024-06-14 19:07:00 | 57 minutes | 179564 | 2 | -8.0 | 1 | -4.0 | 1 | -4.0 | 1 | -4.0 | 0.0350877192982456 | 165.6986301369863 |
python3 main.py -h
usage: Snapscore Tracker [-h] -u USERNAME -s SNAPSCORE [-t TIME] [-a AVERAGE]
👻 A Snapscore tracker that reports various metrics such as time differences,
score increases, snaps sent and received, snap rates per minute, hour, and day
and much more.
options:
-h, --help show this help message and exit
-u USERNAME, --username USERNAME
Snapchat username to track
-s SNAPSCORE, --snapscore SNAPSCORE
Snapscore to log
-t TIME, --time TIME The time you want to log the Snapscore in Y-m-d H:M:S
format. Example: 2024-06-15 12:00:00 will log the
Snapscore at 12:00:00 on June 15, 2024. If not
provided, the current time will be used. Use this
feature if you want to log the Snapscore at a specific
time. WARNING: Current time can be inaccurate by an
hour: 2024-06-15 12:00:00 will log the Snapscore at
11:00:00 on June 15, 2024. Using this parameter will
fix this issue.
-a AVERAGE, --average AVERAGE
Calculate the mean of a column from the logs
Contribute: https://github.com/ibnaleem/snapscoretracker
$ git clone https://github.com/ibnaleem/snapscoretracker.git
$ pip install -r requirements.txt
$ mkdir logs
$ touch ibnaleem_logs.csv # replace {username} with the username of the Snapchat account you're tracking
$ python3 main.py -u {username} -s {snapscore} -t {time in Y-m-d H:M:S format}
Date- the date you logged the SnapscoreTime Difference- the difference between the previous datetime and the new datetime (eg. a difference of 5 minutes will be reported if you log another snapscore 5 minutes later)Snapscore- the SnapscoreIncrease- the increase since the previous snapscoreIncrease Difference- the difference between the previous increase and the new increase (a negative increase implies the person is snapping fewer people than before)Snaps Sent- the number of Snaps sentNumber of Snaps Sent Since Last Time- the difference between the previousSnaps Sentand the newSnaps Sent(a negative implies the person has sent fewer snaps than before)Snaps Opened- the number of Snaps openedNumber of Snaps Openeed Since Last Time- the difference between the previousSnaps Openedand the newSnaps Opened(a negative implies the person has opened fewer snaps than before)Number of People Snapped- the number of people they've Snapped; equivalent toSnaps SentNumber of People Snapped Since Last Time- the difference between the previousNoPSSLTand the newNoPSSLT(a negative implies the person has talked to fewer people than before)Snap rate / min- the number of Snaps sent per minuteSnap rate / hour- the number of Snaps sent per hourSnap rate / day- the number of Snaps sent per day
⚠️ OnlyIncrease Difference,Number of Snaps Sent Since Last Time,Number of Snaps Opened Since Last Time,Number of People Snapped Since Last Timecan hold negative values; if any other column contains negative values, you've likely entered a Snapscore less than the previous (e.g entering 170,000 instead of 180,000)
💡 Calculate Average of a column
To calculate the mean value of a column, find the column name in the
.csv file and append it to the -a or --average argument:
$ python3 main.py -u {username} -a Increase
You may need to wrap the column name in quotes ("") if it contains spaces:
$ python3 main.py -u {username} -a "Snap rate / min"
Snapscore increases by a point under one of the following conditions:
- you opened a snap (+1)
- your snap was opened by someone else (+1)
- you posted on your story (+UNKNOWN)
Usually, a Snapscore increase of 2 means the person sent and received a snap; similarly, an increase of 16 means the user sent and received 8 snaps. This calculation does not show the number of people the person has snapped but indicates the maximum number of people they could have snapped, which is increase // 2. So, a Snapscore increase of 16 implies the maximum number of people they've snapped is 8.
If the increase value is even, the number of snaps sent and opened is the same. For example, with an increase of 16, 16 // 2 yields 8 for both snaps sent and received. However, for an odd Snapscore increase, such as 17, the formula 17 // 2 yields 8. Applying this to both snaps sent and opened gives a total of 16, missing one value.
✅ Even Snapscore Increase
Previous Snapscore: 40,000
Current Snapscore: 40,004
Increase: +4
Snaps Sent: Increase // 2 = 4 // 2 = 2
Snaps Opened: Increase // 2 = 4 // 2 = 2
Increase = Snaps Sent + Snaps Opened = 4 ✅
❌ Odd Snapscore Increase
Previous Snapscore: 40,000
Current Snapscore: 40,005
Increase: +5
Snaps Sent: Increase // 2 = 5 // 2 = 2
Snaps Opened: Increase // 2 = 5 // 2 = 2
Increase = Snaps Sent + Snaps Opened = 4 ❌ (sum of Snaps Sent and Snaps Opened should yield 5)
To address this, a new formula is used for Snaps Opened: (increase // 2) + (increase % 2). If the increase is even, increase % 2 is 0, so it doesn't change the result of increase // 2, yielding the same value for snaps sent and received. If the increase is odd, increase % 2 will add the remainder to the floor-divided value.
✅ Modified Formula: Even Snapscore Increase
Previous Snapscore: 40,000
Current Snapscore: 40,004
Increase: +4
Snaps Sent: Increase // 2 = 4 // 2 = 2
Snaps Opened: (Increase // 2) + (Increase % 2) = (4 // 2) + (4 % 2) = 2 + 0 = 2
Increase = Snaps Sent + Snaps Opened = 4 ✅
✅ Modified Formula: Odd Snapscore Increase
Previous Snapscore: 40,000
Current Snapscore: 40,005
Increase: +5
Snaps Sent: Increase // 2 = 5 // 2 = 2
Snaps Opened: (Increase // 2) + (Increase % 2) = (5 // 2) + (5 % 2) = 2 + 1 = 3
Increase = Snaps Sent + Snaps Opened = 5 ✅
You did not install the dependencies:
pip/pip3 install -r requirements.txt
As per PEP 668, "Python-specific package management tools should neither install nor remove packages into the interpreter’s global context, by default, and should instead guide the end user towards using a virtual environment" (Thomas et al.). Therefore, you must create a Python virtual environment to install Python packages so it does not conflict with global packages installed on the OS.
$ python/python3 -m venv ~/myvenv
$ source ~/myvenv/bin/activate
(myvenv) $ pip/pip3 install -r requirements.txt
This is due to daylight savings, sometimes datetime.datetime.utcnow() reports a time one hour earlier than the current time. To mitigate this, manually type the datetime in %Y-%m-%d %HH-%MM-%SS format.
For example, if you want to log for 26/06/26 @ 21:13 (that's 09:30PM):
python3 main.py -u {username} -s {snapscore} -t "2024-06-26 21:13:00"
Indeed, you must use 24-hour time.
This repository is under the MIT License
I welcome contributions from the community and appreciate the time and effort put into making SnapscoreTracker better. To contribute, please follow the guidelines and steps outlined below:
Note: Your pull request will be closed if you do not specify the changes you've made.
Start by forking this repository. You can do this by clicking on the "Fork" button located at the top right corner of the GitHub page. This will create a personal copy of the repository under your own GitHub account.
Next, clone the forked repository to your local machine using the following command:
$ git clone https://github.com/yourusername/snapscoretracker.gitNavigate to the cloned directory:
$ cd snapscoretrackerBefore making any changes, it's recommended to create a new branch. This ensures that your changes won't interfere with other contributions and keeps the main branch clean. Use the following command to create and switch to a new branch:
$ git checkout -b branch-nameNow, you can proceed to make your desired changes to the project. Whether it's fixing bugs, adding new features, improving documentation, or optimising code, your efforts will be instrumental in enhancing the project.
Once you have made the necessary changes, commit your work using the following commands:
$ git add .
$ git commit -m "Your commit message"Push the changes to your forked repository:
$ git push origin branch-nameHead over to the original repository on GitHub and go to the "Pull requests" tab.
- Click on the "New pull request" button.
- Select your forked repository and the branch containing your changes.
- Provide a clear and informative title for your pull request, and use the description box to explain the modifications you have made. Your pull request will be closed if you do not specify the changes you've made.
- Finally, click on the "Create pull request" button to submit your changes.
2024 7EC0 23F2 769E 6618 1C0F 581B 4A2A 862B BADE
