Issue: SoundCloud shows incorrect total number of liked tracks and reposts
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- api
Research direction
The report names no repository files, tests, or API entry point. Start by determining whether the public API exposes the liked-track and repost totals and lists described, then reproduce the mismatch and establish the expected behavior for deleted or private items before defining completion.
Written by the indexing model from the issue text.
Description
I am experiencing a problem with SoundCloud where the total number of liked tracks displayed (195) does not match the number of visible liked tracks on my Likes page (only 22 tracks are shown). Similarly, the total number of reposts also appears to include hidden or invisible reposts that do not show up in the reposts list.
It seems like there are "invisible" liked tracks and reposts that do not appear in the lists but still count towards the totals.
Possible reasons could be:
Some liked tracks or reposted tracks have been deleted or made private by their owners, so they are no longer visible but still counted.
Cached or outdated data causing the total counts to be incorrect.
A bug in the SoundCloud interface or API that results in mismatched like and repost counts.
There is currently no way to see or remove these invisible liked tracks or reposts from my account.
Request:
Please provide a way to:
View the complete and accurate list of all liked tracks and reposts, including those that are private or deleted.
Remove or unlike/unrepost tracks that do not appear in the visible lists to properly synchronize the counts.
This issue affects usability and causes confusion about the actual number of liked tracks and reposts.
Thank you!
- Dominant language
- JavaScript
- Stars
- 253
- Forks
- 53
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from soundcloud/api
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
soundcloud/api#593 · 6 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
soundcloud/api#592 ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
soundcloud/api#583 · 1 comment · 1 reaction ·
-
widget
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#557 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
soundcloud/api#548 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TheOdinProject/curriculum#31444 ·
Maintainers usually reply within 1 day
-
software-development-practices software-development-practices:nist-ssdf
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-cao#15860 ·
Maintainers usually reply within 1 day
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aiko-chan-ai/DiscordBotClient#380 ·