Yog4a

Engineer & Developer, building things that work. Don’t ask me how, I’m still pretending it was intentional...

[Yog4a @Yog4a_]

Yes, but a non-technical team will fix the issue, since they’re already shipping production code… 🙃

[Watcher.Guru @WatcherGuru]

JUST IN: Coinbase crypto trading remains down for over 5 hours as outage continues.

[Yog4a @Yog4a_]

@Koossins @tayvano_ The guy who shot, and the seller who accepted to take the weapon back.

[Yog4a @Yog4a_]

No. Polymarket binary books are mirrored: YES 55¢ = NO 45¢ (YES+NO=$1). The cheap YES+NO < $1 claim is literally double-counting the same liquidity.

[Marlow @marlowxbt]

A Python script pulled $325K from the same price gap over and over.

It appears every few seconds. This bot catches it first.

I found distinct-baguette buried in a leaderboard. Another crypto bot grinding 15 minute windows. Almost closed the tab.

Then I saw the win rate. 80%. That is low for a profitable bot. Way too low. Something was off.

Turns out I was looking at it wrong.

→ Account: https://t.co/Zc9nyM2PDP

This bot does not predict anything. Does not care if BTC goes up or down. Does not read charts. Does not time entries. It just watches one thing: prices that do not add up.

Sounds weird until you see the trick.

Polymarket 15 minute windows have two sides. YES and NO. One of them always pays $1. So YES + NO should always equal $1. That is just math.

But when markets move fast, prices slip. YES at 48 cents. NO at 49 cents. Total: 97 cents.

The bot sees this. Buys both sides. Waits. Market closes. One side pays $1. Spent 97 cents. Keeps the 3 cent difference. Does not matter who wins.

The script checks Polymarket every few seconds. BTC. SOL. XRP. Anything with volume. The moment prices slip under 99 cents combined, it fires.

Three cents per trade. Repeat it tens of thousands of times. That is how you get to $325K.

The 80% win rate finally made sense. He is not trying to pick winners. He is locking profit before the bet even resolves.

Everyone else bets on outcomes.

This bot bets on broken math.

[Yog4a @Yog4a_]

@Koossins @raidenkrn Oops

[Yog4a @Yog4a_]

@Koossins Impossible

[Yog4a @Yog4a_]

@PasToucheAuCode @Purlins9 Jamais eu de problème perso, sur les noms de domaines + serveur dédié + vps. Hormis des problèmes que j’ai moi même créer et que j’ai du résoudre en passant par leur KVM qui bug parfois

[Yog4a @Yog4a_]

@melvynx Tu peux l'ajouter ici: https://t.co/FwkxyLUQLD

[Marc Lou @marclou]

Bye Bye fake MRR screenshots 👋

I built https://t.co/MZc8tG9xWi, the database of verified startup revenues.

1. Upload a read-only Stripe API key
2. Get a free page showing your verified revenue
3. And a nice dofollow backlink as a bonus

There's no way to game the system. It's all running on my server, and users can't edit the revenue data.

+ It comes with the leaderboard of startups with the most revenue in the last 30 days.

Go get verified!

[Yog4a @Yog4a_]

@LLCoolChris_ it's already the case if you're talking about their shitty animation

[Yog4a @Yog4a_]

@KaelCc T’as des sous modules qui auto retry, rate limit etc. C’est hyper facile à config.

https://t.co/AQBWCTw15R

[Yog4a @Yog4a_]

@KaelCc Je dis pas que tu mens mdr, je dis que tu as des limites aléatoires, sur deux groupes, qui reçoivent la même chose, parfois l’un fini bloqué et pas l’autre. Je souligne juste que telegram rate limit un peu aléatoirement. Et après GramJS je connais pas mais Grammy est top

[Yog4a @Yog4a_]

@KaelCc T’as des limites obligatoires peu importe le language / la lib. 1 message par seconde dans un groupe privé, 20 messages par minutes dans un groupe, pas de limite claire pour les channels. Si tu dépasses, tu finis par être bannis un moment (message envoye mais non reçu)

[Yog4a @Yog4a_]

@ShinraDeFi @studleemore No.

[Yog4a @Yog4a_]

@benjamincode Et c’est comme ça qu’on se retrouve avec des clés api directement lisible sur un front ou un back absolument pas sécurisé 🙃

[Yog4a @Yog4a_]

@Anthyra_dev Je suis pareil, j’en profite pour faire autre chose, perso j’vais au Sport / Courses / Coiffeur etc en début / milieu d’après midi

[Yog4a @Yog4a_]

@LLCoolChris_ Je préfère le do expressions perso

[Jamie Kyle is on 🦋 @buildsghost]

This is not yet a TC39 proposal but it's getting suggested again, and I find it very surprising that people want to take this from Go instead of following down the path of "do expressions" (with implicit returns) and having try expressions

[Yog4a @Yog4a_]

@ledevultime La limite de budget en soit bloque rien, puis il y a un délai entre l'alerte et le seuil. Mais je comprend, c'était juste pour savoir, si tu le faisais ça m'int��ressait.

De mon côté j'avais mis en place le nbre max d'instances sur les fonctions à 1 + app check et reCAPTCHA

[Yog4a @Yog4a_]

@ChrisSmiiic Rah ouai ça se balade en string dans le salon la pour tweet ça