mirror of
https://github.com/Rafiuth/Soggfy.git
synced 2026-04-25 07:05:58 +03:00
[GH-ISSUE #46] Any reason to think that Spotify would even know that a track was being downloaded if played at normal speed? #43
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Soggfy#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dtronvig on GitHub (Sep 9, 2022).
Original GitHub issue: https://github.com/Rafiuth/Soggfy/issues/46
I have Soggify up and running, and it's brilliant, but I'm considering your warning that an account could get banned for using it. I suspect that Spotify would notice if someone were "playing" a track at 10x speed, but if playing at normal speed is there any way that Spotify could even guess that you are reconstructing the original file as you're playing it?
If there's really no way for Spotify to see anything out of the ordinary, when you are playing (and reconstructing) at normal speed, you might just update your Notes to reflect that,
Thanks,
Drew
@SmilerRyan commented on GitHub (Sep 9, 2022):
Honestly, normal play/download speed should be fine and undetectable assuming they don't add in checks later.
At any point, they could make an update which would detect code changes, the injection, etc and ban the account.
I would agree that adding onto the warning (possibly like this) would be a good idea though:
Your account could get banned by using this. Consider using alt accounts, keeping backups (see Exportify and SpotMyBackup) or keeping the playback speed at 100%.
@Rafiuth commented on GitHub (Sep 10, 2022):
I agree with @SmilerRyan, it's highly unlikely that they can detect Soggfy currently, unless they add intrusive client-side checks or complicated server-side heuristics.
Adding on that, the normal Spotify client logs pretty much all player state changes: when a song starts or ends, volume, and yes, playback speed. Though these logs alone don't seem to trigger a ban, Soggfy blocks them by default via the "Misc > Block Telemetry" option. Because of that, I think it would be pretty unfeasible for them to implement a server-side detection heuristic based on just client behaviors (especially if you keep playback speed at 1x), downloaders just aren't that widespread for them to bother much.
It also seems that they use bans more like a scare tactic, saying that you can get unbanned by apologizing: https://www.reddit.com/r/Piracy/comments/x37e50/spotify_now_checking_for_piracy
@dtronvig commented on GitHub (Sep 13, 2022):
Yeah, this all makes perfect sense.
Thanks @SmilerRyan and @Rafiuth.
@AlexandreGagner commented on GitHub (Oct 19, 2022):
Hi,
I already had my main account banned using software that was implementing a similar technique (Sidify - look's like a Soggfy fork with UI that they sell). But the ban was after few month, like a manual batch lunched from Sportify.
Now I use Soggfy, but never on my main account. I just login using premium trial on alias email account, on LTE network and virtual VISA card that I delete after.
Also, I use always use full speed but I never for now received a ban message on my fake (alias) email account.
Bisous
@RealUlix commented on GitHub (Mar 28, 2024):
Just found this tool and it works nicely. Very cool. I have questions: