RELLATTO @rellatto

Open letter to @Polymarket and especially @shayne_coplan: I've been trading on Polymarket for a long time. I am one of the biggest traders on the entire platform and I interact with it on a daily basis. And at this point I'm seriously questioning whether the team has simply given up. I'm not even trying to be dramatic. Wtf is actually going on? Has everyone made enough money that nobody cares anymore? Is the team completely overwhelmed? Are priorities completely broken? Is there no leadership? Is it incompetence? Because the current state of the platform is honestly embarrassing. Every maintenance seems to follow the exact same script: announce 10 minutes of downtime start 20 minutes late stay down for an hour deploy changes that break multiple existing systems leave the bugs in production for weeks And somehow nobody seems concerned. Example: ~1.5 weeks ago an update broke tick sizes. The matching engine started rejecting orders that matched the correct tick size after a tick size change was published. This was immediately visible after deployment. It's still broken. Nobody seems to care. Then for the last two days Polymarket's own RTDS feed, the feed used for all crypto markets, has been broken. The issue was marked "resolved" 10 hours ago. It still isn't resolved! Did anyone spend literally 5 seconds checking whether data was actually being published before closing the incident? Because it sure doesn't feel like it. Communication is somehow even worse than the bugs. Half the changes never get announced. The other half are hidden in random Discord side conversations. Major trading-impacting changes get silently rolled out with zero documentation. You ask support. They say they'll ask the team. Then you never hear back. Or you get the same canned response you've already received three times. The team keeps saying communication will improve. It never does. Then there's the rebate and fee situation. Taker tiers were supposed to launch on May 28. A week later they still weren't live. Nobody acknowledged the delay. The docs still said May 28. To this day there still hasn't been a single taker rebate payment. And the official position is apparently that missed rebates won't be back-paid. How is that acceptable? How are traders supposed to adjust strategies, thresholds, and risk when nobody knows what fees they are actually paying, what rebates they are actually earning, or how much of the promised rewards the platform simply decides not to distribute? That isn't transparency and it is clearly destroying trust. The craziest part is that every update creates fresh opportunities for exploiters. Just in the last couple weeks we've had: queue position jump exploits taker delay bypass exploits ghost fill exploits various matching and infrastructure bugs order spam exploits Millions of dollars have been extracted from legitimate users through platform failures. The response? Increase rate limits. Seriously. A huge amount of latency issues today are caused by order spam that is directly incentivized by broken infrastructure and exploitable mechanics. Fixing the root causes would help. Instead we get band-aids. Which raises another question: Does Polymarket have a testing environment? Does it have staging? Can updates be rolled back? Because from the outside it honestly looks like production is the testing environment. Every maintenance introduces new failures. Every maintenance gets partially reverted. Every maintenance creates more issues than it solves. This shouldn't be happening at a company valued in the billions. Meanwhile manipulation that has been repeatedly reported for months continues largely unchecked while manipulators keep extracting money from normal users. And surprise: Volume is declining. Prediction markets as a whole are growing. Yet Polymarket just posted its second consecutive month of declining volume. Meanwhile Kalshi has become the clear market leader in many categories and is now outperforming Polymarket by large multiples in areas where Polymarket used to dominate. Honestly? It's not hard to see why. Every serious trader I've spoken to says the same thing: Kalshi feels stable. Polymarket feels like you're one deployment away from disaster. I know multiple people who would happily trade Polymarket full-time if they trusted the platform. They don't. Not because of competition. Because they don't trust Polymarket itself. My trust in this platform is at an all-time low. And I genuinely don't understand what is happening internally. Maybe the response will be that the team is busy with the World Cup or other initiatives. Fine. Then stop shipping half-finished features. Stop deploying untested fixes. Stop breaking live trading. Slow down. Focus on fewer things. Do them properly. The most concerning part is that so many decisions feel like they were made by people with no actual trading experience. The product decisions show it. The infrastructure decisions show it. The market structure decisions show it. Building the future of prediction markets requires understanding how markets actually function. Right now it often feels like nobody is steering the ship. I want Polymarket to succeed. But from the perspective of someone who uses the platform every day, this is bordering on unusable. @Polymarket @shayne_coplan What is going on?

Claude Fable 5 vs Opus 4.8 👀

Claude @claudeai

a week ago

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.

5K 15K 105K 56.1M 22K

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.

Voyager 1 is 24 billion kilometers from Earth. It communicates with us using a 23-watt transmitter. Less than a refrigerator light bulb. The signal takes 22 hours to reach us, traveling at the speed of light. By the time it arrives, it's 20 billion times weaker than the power of a digital watch battery. NASA's Deep Space Network picks it up using 70-meter dish antennas cooled to near absolute zero to reduce electronic noise. The engineering required to hear a 23-watt signal from 24 billion km away is arguably more impressive than the spacecraft itself. Launched 1977. Still transmitting. Still being heard. We built something that works perfectly, 47 years later, in conditions no one has ever tested in. That's what engineering for the long term looks like.

Friday Update - Week of June 1st, 2026: - CLOB performance: long-awaited taker-delay fix landed in production this week as part of broader execution-path improvements, together with a new trading gateway. Large latency reduction and better stabilization under load. More architectural work continuing - World Cup launches: final testing pre-release next week - Beacon Deposit Wallet: new version launching 6/11 (moved from 6/8), for new users - Taker Rebates: prod rollout started, tier badges live on leaderboard, expanding across the UX next week - Market Resolution upgrade: large improvements in consistency and speed - Perps: continuing access rollout to users; taker delay, reduce-only, and TP/SL shipped to production testnet; Limit Close on open positions, trading directly from the chart, and mobile UX improvements - In-house indexer: preparing for full production rollout, big performance gain on high-traffic endpoints - TS SDK: RFQ support released; World Cup feature support and docs wrapping next week

Пишет @Emokwx: «Кто-нибудь когда-нибудь видел облака, междугородными трассами? Сегодня утром кучевые облака (Cu) развились идеально вдоль основных междугородных автотрасс вокруг Хьюстона. Немного шокирующе видеть такие идеально выстроенные облака». Хьюстон создаёт облака? Как город запускает конвекцию — buymeacoffee.com/nadvorie/houst…

We've reset 5-hour and weekly rate limits for all users on Pro and Max plans. We fixed an issue that caused some Claude Code sessions to spawn excessive parallel subagents, burning through usage faster than expected.

We reported a critical loss of funds bug to @Thorchain (32M TVL, 150M FDV) They silently patched it and told us their bug bounty program is permanently retired. We have more Thorchain chain halt DoS vulns. We intend to release them (open disclosure) in the coming few days

keyboard_arrow_left Previous keyboard_arrow_right Next

@0x_Punisher пиздабол это разные графики да еще и на 1 месяц 😄😀😃

⚡ Microsoft Releases KB5089573 for Windows 11 to Fix Patch Tuesday Install Issues Source: cybersecuritynews.com/microsoft-kb50… Microsoft has rolled out a new cumulative update, KB5089573, for Windows 11 versions 25H2 and 24H2, targeting a critical installation failure that affected users following the May 2026 Patch Tuesday release. The update brings OS builds to 26200.8524 and 26100.8524, respectively, resolving a widely reported error that prevented many systems from completing the monthly security update. The May 2026 Patch Tuesday security update (KB5089549) triggered installation failures on a subset of Windows 11 devices, with error code 0x800f0922 halting the process. #cybersecuritynews #windows11

Felicidades al PSG por la consecución de la Liga de Campeones y a Luis Enrique por sumar un nuevo título a su palmarés.

🔴🔵🤣 @KMbappe

Congratulations to PSG on winning the UEFA Champions League, and to Luis Enrique on adding another title to his list of achievements.

Friday Update - Week of May 25th, 2026: - Perps live in production: launched with 5 tradfi pairs and 1 crypto pair (BTC); more instruments and user access upcoming - World Cup pages live: Globe/Map, Bracket and standings shipped - World Cup launch features in final testing - CLOB performance: Order Book consistency improvements shipped this week, with deeper architectural changes underway and a release next week to address queue congestion - SDKs open-sourced: TS SDK with runnable examples, Python SDK with improved public docstrings, multiple beta feedback items addressed - Unified API: kicked off, first Gamma endpoints wrapped - Gamma: tighter keyset pagination and indexes on high-traffic read paths, production correctness fixes across users, profiles, comments and sports summary

Opus 4.8 is insane guys. It one shotted my session usage limit.

100 litres of water was used to create this

加密圈的又一大奇闻：一共5笔转账，共107枚BTC，转向了销毁地址。超过800多万美元的BTC就这样被永久销毁。 转入的销毁地址是著名的地址：1111111111111111111114oLvT2 目前上面躺着807.23892159枚BTC，价值超6100多万美元。 发送者地址来自2014/15年的休眠老钱包。 为什么这么做？ 似乎不太可能是误操作，5笔交易是独立的，金额加起来正好是107枚BTC，很难想象，一个人连续5次都手抖打错地址。 至于真实原因是什么，只有发送者知道。

keyboard_arrow_left Previous keyboard_arrow_right Next

> Ele comprou 107 Bitcoins em 2014 > Viu o BTC ir de US$ 500 para R$ 125.000 > Observou uma valorização de 24.900% Então, nessa segunda-feira, ele enviou os 107 BTC para o endereço “1111111111111111111114oLvT2” e LITERALMENTE QUEIMOU R$ 41 milhões. Quais são as teorias? Por que alguém faria isso? 😳

Scheduled CLOB maintenace tomorrow, May 27 at 12:10 UTC. - Intermittent trading for ~5-10 min during the window. - Brief post-only mode after restart (~2 min) before normal matching resumes. Stay updated, subscribe at status.polymarket.com

JUST IN: Someone just sent 107 BTC across 5 transactions to a well know "burn address" 🤯 $8.3 million GONE.