@IamProsperr@Farukbam1@Fznation01 you should have researched VALID TRACK RECORD for retail traders before responding ...it showsboth you and your idolos are ignorant
@hoshivri@forexblog9ja Please can you share the proof they have provided ? I can’t see a single myfxbook link on their profile but…but easily faked picture of how much they make is plastered all over
@Micosamo@forexblog9ja Not a single one of them has myfxbook link that people can verify their true trackrecord anywhere on their profile but they will gladly share easily faked screenshots of money everywhere … bunch of dishonest fools
@Ekeson__@Omolomo_o Lol... you should honestly ask GPT to evaluate your intelligence. . your question to the AI Model already gives us a pretty good idea.
@PRO_MISE@otienobria98322@KingFtpFx ...very easy to see ass lickers.... when they can't fault the TRUTH they deflect
lol so common with Furus and their Cronies
@KingFtpFx@khalifa_X001 If you won't feel hurt like majority of other furus that show only editted screenshot
You could share a valid track record: the myfxbook link to the account since you posted the performance screenshots ...why not back it up with valid evidence
MYFXBOOK LINK
@PRO_MISE@otienobria98322@KingFtpFx Screenshot is meaningless it could easily be edited ....they all know what is valid track record but they don't share it
Myfxbook link will expose all lies but they run away from it
This is numbers of motorcycle moving Lithium earth minerals from (Daba) Old Oyo National Park to Kishi or Igbeti, and each of this Okada riders charge 12000naira per bag, the individuals acting like a union for the motorcycle rake about 20-50million naira while those working for the union daily take home is 200,000naira.
The whole illegal mining stuff is a cabal and a organised crime.
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.