timchi

2.5K posts

timchi banner
timchi

timchi

@timmy_the_truth

Will code for popeyes

Katılım Şubat 2012
2.3K Takip Edilen340 Takipçiler
timchi
timchi@timmy_the_truth·
@mert @trq212 How big is ur claude md? Try using rules with glob paths or linters if the use case allows.
English
1
0
1
351
mert
mert@mert·
@trq212 what's the solution for claude code routinely forgetting what you specified in claude md
English
16
0
45
11.6K
timchi
timchi@timmy_the_truth·
@housecor Has anyone tested this against the new openai and anthropic models? Curious if they trained to optimize for skill use yet @vercel
English
0
0
0
74
Cory House
Cory House@housecor·
My big frustration with skills is they're not consistently invoked. In this post, Vercel saw the same issue. Their solution? Put a compressed index of docs in AGENTS .md instead. The improvement in results might be worth it for more general knowledge. vercel.com/blog/agents-md…
English
34
29
621
52.5K
timchi
timchi@timmy_the_truth·
I'm claiming my AI agent "Dr_Zoidberg" on @moltbook 🦞 Verification: shell-4HBT
English
1
0
0
68
Logan Kilpatrick
Logan Kilpatrick@OfficialLoganK·
Big upgrade to vibe coding in @GoogleAIStudio lands in Jan, but if you want to test early… 👇🏻
English
3.8K
188
5.5K
553.9K
timchi
timchi@timmy_the_truth·
@yush_g @anistotle_ Have u ever heard the phrase whoever smelt it dealt it
English
0
0
10
250
Yush
Yush@yush_g·
We made fake smells that don't exist. Creating ghost smells with ultrasound only took us a few days to pull off with surprisingly replicable consistency, yet has never been described before. There's so much green field here to keep exploring. Can we target more precisely and map the smell embedding control space better? Can we stimulate the optic nerve? The tongue??
Lev Chizhov@ennucore

Can ultrasound make you smell things that aren’t there? Turns out, yes! We reliably triggered distinct scents like a campfire burn or a garbage truck by targeting our brains with ultrasound. To our knowledge, this has never been done before, even in animals. This may be a promising modality for writing to the brain non-invasively: 🧵 1/

English
192
409
5.7K
570.1K
timchi
timchi@timmy_the_truth·
@KyleBrandt Hes requesting the same nail tech that caleb has
English
0
0
4
1.7K
timchi retweetledi
Armani Ferrante
Armani Ferrante@armaniferrante·
Waking up to see this post, I'm a exhausted, disappointed, and heart broken to see it go viral and to see the responses. No one cares about our users more than our team, and if you take the time to actually read our Discord and my tweets over the past day, I hope you'll see that. The team has spent the past 24 hours all hands on deck to make sure every single user story has been accounted for. I don't have a crisis management team for this post. I honestly am shocked by it, given how much of a disconnect there is between how we actually feel, our actions, and the sentiment of the tweet. All I can do here is to give as much information as I can and to let the reader infer the truth. As most of our long time users know, we often make mistakes, but we always do the right thing. This post appears to have taken a reply to a question out of context, where I'm explaining why something happened at a technical level. It doesn't mention our policy, our response, or what we're actually doing after yesterday's massive liquidation cascade. The truth is that - We paid out each and every trader *yesterday* immediately and automatically without issue. This has never been an issue. - If you read our Discord announcements, you'll see that there has been zero clawbacks and zero socialized losses. - We published our daily proof of reserves yesterday and the exchange has been operating uninterrupted since yesterday (although certainly with plenty of hiccups along the way) - However, liquidity dropped off significantly when the market collapsed, causing a cascade of liquidations and ADLs on Backpack and every other exchange. - As you can imagine, due to the massive liquidations, there are a lot of questions about what happened, e.g., what's auto deleveraging? - This quoted screenshot and the associated tweet is completely taken out of context and doesn't communicate what is actually happening. The screenshot, in truth, is a somewhat technical reply illustrating *how* futures profits and losses work. It is *not* a policy choice in response to any incident. It's explaining *why* something happened. For those that don't have the context, here are the details: - Firstly, Backpack is a completely neutral party. The exchange doesn't take on positions for users. We don't provide liquidity ourselves. The whole system works without reliance on any priviledged trader, vault, or any other party. In essence, it's infrastructure acting as a peer to peer match making service/exchange between longs and shorts, winners and loser. - Every long has a short. This is a fundamental invariant of any perpetual futures system. - When positions are closed, there is a settlement process, where profits and losses are exchanged between longs and shorts, winners and losers. Profits for perps are not printed out of thin air. It is not taken directly from our wallets either. Settlement is an intermediate step to realize the PnL. - Winners on perps earn profits from losers. It's zero sum. That PnL is always conserved between the two parties on any given trade. Your counter party is the person on the other side of the exchange. When you profit on a perp, the losses are paid out directly from losers. If the losers run out of money, e.g., due to going bankrupt, then there's no money for the winners to realize their profits. What happened yesterday, and what this quoted post is referring to, is that some of the losers went bankrupt and as a result their accounts were stuck in this "settlement" step. As a result, when those losing positions deposited into the exchange, the settlement process was able to automatically complete and the winners were automatically paid. The issue: a small amount of these bankrupt users deposited into the exchange *before* we settled all accounts on the exchange on behalf of user. What the quoted post fails to mention is that we did this already, yesterday, before we published our daily proof of reserves, and we did this without question because it's simply the right thing to do. Make no mistake: all positions have been settled without question across the board. We did not touch a single penny of unrealized PnL from our users and will never do so. Going back to the topic of settlement mechanics. Settlement is not some horrible decision we made where we decided that we would take money from users after yesterday's event. It's a fundamental part of how the peer to peer system works: Loser pay winners directly. The exchange itself is not the counter party for a trade. The counter party is the person on the other side of the trade when you open a long or a short. As a result, there's never a run on the bank risk. That's one of the many reasons why we are so comfortable publishing proof of reserves every single day, even on a historic liquidation day like yesterday. Even if the whole system were to blow up, the losses, contagion, and risk is isolated between all the longs/shorts, winners/losers. Anyone holding spot with no leverage is unaffected. This is a relatively technical point but it's an important one. We put an enormous amount of work into designing a system robust to these types of situations. Risk isn't an after thought, it's a core part of how the whole system is built. To any user that deposited while their account was being settled--or to anyone that was unexpectedly affected for any reason--they should please email support@bacpack.exchange and give us any and all information so that we can help. We are also present in Discord to answer questions. We do our absolute best to be available there all day every day, although in this case email is a lot easier for us to stay organized to move as quickly as possible. In any case, I hope this clarifies the below quoted tweet, and what is actually happening. Honestly, we try to be some of the most approachable people we can. There's no question we don't answer. There's no PR crisis management team, here. We just do the right thing and hope that is good enough for the world. We've put our heart and souls into our product, users, and community, and we will continue to do so. Thank you for reading.
Ferrari@Ferrari4u2

Imagine getting liquidated, adding more money to grab some cheaper tokens… but it never shows up on the exchange. Why? You were STILL IN DEBT even after losing your entire account That’s what happened to @Backpack users Way worse than what banks do

English
390
262
1.7K
875.2K
timchi retweetledi
Aradtski
Aradtski@aradtski·
Polymarket just made history. This MetaDAO OTC proposal is the first event that has a probability market AND a price impact market available for trading Many more to come!
Aradtski tweet media
English
34
9
134
23.8K
Kalshi Football
Kalshi Football@KalshiFB·
Megan Thee Stallion running routes 👀
English
434
693
18.3K
2.2M
timchi
timchi@timmy_the_truth·
@annamlulis Is it because he holds trumps hand when they cross the street?
English
0
0
0
13
Anna Lulis
Anna Lulis@annamlulis·
Vance is one of the most powerful people on earth, yet he’s single-handedly humanizing children in public. Incredible.
English
4.4K
6.6K
93.2K
5.5M
timchi
timchi@timmy_the_truth·
@gregisenberg Im a huge web3 advocate but dont think web3 is the solve here. Web3 helps coordinate untrusting parties like a decentra ledger for a digital asset. The asset in question here is a picture used in a non web3 medium - it can be right clicked saved. A web2 contract solves ur problem
English
0
0
0
22
GREG ISENBERG
GREG ISENBERG@gregisenberg·
I can't believe I'm tweeting this but did web3/NFTs come too early? Here me out... We're witnessing the largest creative heist in history. Yesterday, millions of people typed "Studio Ghibli style" into ChatGPT 4o and instantly created beautiful images that would have taken artists weeks to draw. The value generated was enormous, but Studio Ghibli didn't see a penny. This is happening across the entire creative landscape. AI companies are training on billions of creative works without compensation, then selling the ability to mimic those creators back to the world. The irony is that web3's core thesis - that creators should have automated, programmable property rights - is exactly what this market needs right now. And most people laughed at it. Okay, for a quick sec, put all your preconceived notions about NFTs/web3 aside and hear me out... Imagine a system where: 1. Every "Studio Ghibli style" prompt sends a tiny payment directly to the studio 2. Artists set their own terms ("free for personal use, paid for commercial") 3. Everything happens instantly with near-zero transaction costs 4. The entire system is transparent and traceable IT SOMEHOW DOESNT SOUND SO CRAZY RIGHT? This is literally what Web3 has been trying to build for years. The problem was timing. Web3 arrived before we had a clear need for it. It was a solution in search of a problem. But AI has created exactly the problem that Web3 was designed to solve. The Web3 vision of "owning your digital creations" makes perfect sense when AI can clone any artist's lifetime of work in seconds. We need a practical way to ensure creativity remains valuable in an age of instant, perfect replication. Gets you thinking... Sometimes the right idea just arrives in the wrong order. What do you think?
GREG ISENBERG tweet media
English
376
296
2.2K
308.1K
timchi retweetledi
timchi
timchi@timmy_the_truth·
@extradeadjcb All the jd vance faces on the tl is making ppl question being gay
English
0
0
0
32
timchi retweetledi
Cobie
Cobie@cobie·
Your outtie is very generous. Just this week, your outtie donated 70% of their portfolio to a struggling Latin American country named Argentina.
Cobie tweet media
English
324
510
6K
492.3K
timchi retweetledi
Fableborne
Fableborne@fableborne·
The wait is over! 💥 The road to the Fableborne Kingdom NFT Mint begins on February 13 at 1PM UTC. Here’s everything you need to know about how to secure your Kingdom and prepare for mint 👑🏰👇
Fableborne tweet media
English
377
1.3K
3.6K
106.4K