About this thread
Posts archived: 6 / 6 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
- Archived posts
- 6
- Discussion span
- →
- People posting
- 4
- Likes on archived posts
- 16
- Posts by staff, officers and moderators
- 1
- Authority score
- 41 / 100
- Historical score
- 29 / 100
- Story score
- 50 / 100
- Engagement score
- 54 / 100
Most-liked replies
- bogie [148747] Admin
· 2 likes ·
Closed, API TOS violations.
On the login page (or anywhere for that matter), there is no data policy explaining how the tool uses your API key. This is required by Torn's rules. So I'll start with the assertion right off the bat that you are breaking a rule there.
Secondly, you mention the keys are encrypted with AES-256. But why? What threat is this protecting against exactly?
"Not visible to anyone — not even us" - Ok I am going to call bullshit on this, unless you can adequately explain the mechanism behind this to me in a way which doesn't sound like ChatGPT to weasel out of it.
Given the absolute monstrosity of a script you also posted lately, I am guessing this is 100% vibe-coded.
For anyone reading this and wants my verdict: Wouldn't touch with a barge pole.
Asked the same question myself on the other thread he created for the same exact website lol
![[image: uploads.glasnost.dev]](https://uploads.glasnost.dev/2026-06-12-6cjpX6jpAxQeKW8F.png){kind=link}
Ah, seems you use FFScouter in the backend too using only your personal keys. Resolve the issues and answer the questions made above, and I will remove the ban.
![[image: uploads.glasnost.dev]](https://uploads.glasnost.dev/2026-06-12-ib6DkNVeULemr8TR.png){kind=link}
Closed, API TOS violations.