Sabitlenmiş Tweet
sAd.sol 🎒 🐾
12.4K posts
sAd.sol 🎒 🐾
@nocoffeebreaks
🇵🇹 | building @playkindredxyz 🐾 banner is @playsolana proud @madlads holder
Katılım Nisan 2018
848 Takip Edilen1.7K Takipçiler
@Buddycrypto0 +15M de volume e 100k pontos não valeram nem 10k, triste mesmo
Português
Um dia vocês vão sentir saudades, dos poucos de verdade que se encontram nesse mercado, mas na época quem falava mal era invejoso ou hater.
Buddy@Buddycrypto0
Estava quase farmando Backpack, mas a palhaçada virou nível institucional. Desisti. Time não passa UM PINGO de credibilidade: Caso Frag? Liberaram o claim, foram os ÚLTIMOS a listar e… nada de perps. Exchange cai no meio da volatilidade. Recompensa? Pontos de consolação. Parece Black Mirror. Amigo meu colocou 100k lá, não conseguiu sacar. Solução: “compramos SOL e mandamos pra você ”. E se despenca 15%? Problema dele. Amigo enviou bbSOL por engano. Suporte: “não vamos devolver”. Só mudaram de ideia depois de serem expostos no X. E o mais bizarro? Tem gente empurrando referral como se fosse safe haven. Mas na real? Querem é lucrar nas suas costas. ⚠️ Não se iluda com thread bonitinha se der ruim, quem vai segurar a bomba é você. Não eles.
Português
I think disappointment is the lightest way of expressing any feelings around @Backpack
I was wrong and I am truly sorry for everyone that got burnt.
We are all in the same boat.
My DMs are open. Both here and on TG (same username). Please feel free to DM me or call.
English
English
"Rate @Backpack airdrop"
10/10. 🕺💃
Perfect execution. 💪
One of the smoothest airdrop mechanics crypto has seen.
• Sybils were punished in full, so they couldn't abuse system
• no liquidity issues - the Liquidity Engine passed the stress test
• clean distribution
• tokens landed directly in accounts and auto-staked, no extra clicks needed
Most importantly, Backpack proved again that an airdrop can be executed without:
• shady claim links
• wallet-drain bait
• bot front-running
• market maker games around distribution
That matters.
Users were protected.
Abusers were filtered.
The system worked.
Study Backpack.
Study how top-tier engineers execute.
Now back to buidling.
🧱 x 🧱
Next level for a reason.
Ferre@FerreWeb3
Rate the Backpack $BP airdrop out of 10. I’ll start: 2/10.
English
i got scammed on 10-10 by CZ in the range of mid-high six figures, backpack drop didn’t cover 1/2 of that 😵💫
staking it and forgetting about crypto
English
Backpack 🧱x🧱 Balkans
Mikel | Mad #9851 🎒@_mikel
More product, more markets or more community? "YES" 🎒 Backpack 🧱x🧱 Balkans
English
This is a viral engagement-bait post. The claims are fabricated:
- "600x faster" — made up number
- "ENABLE_LSP_TOOL" — doesn't exist in Claude Code's settings or environment
variables
- "50ms definition lookup" — not a real feature
- "auto-catches type errors after every edit" — not how it works
Claude Code uses ripgrep (rg) and glob for code search, which are already
extremely fast. The tool calls you see me make (Grep, Glob, Read) are the
actual mechanisms — there's no hidden LSP layer waiting to be unlocked.
These "hidden setting" posts circulate regularly on X/Twitter for engagement.
The pattern is always: "nobody knows about X" + impressive fake benchmarks +
just enough technical jargon to sound plausible.
English
claude code has a hidden setting that makes it 600x faster and almost nobody knows about it
by default it uses text grep to find functions.
it doesn't understand your code at all. that's why it takes 30-60 seconds and sometimes returns the wrong file
there's a flag called ENABLE_LSP_TOOL that connects it to language servers. same tech that powers vscode's ctrl+click to jump straight to the definition
after enabling it:
> "add a stripe webhook to my payments page" - claude finds your existing payment logic in 50ms instead of grepping through hundreds of files
> "fix the auth bug on my dashboard" - traces the actual call hierarchy instead of guessing which file handles auth
> after every edit it auto-catches type errors immediately instead of you finding them 10 prompts later
also saves tokens because claude stops wasting context searching for the wrong files
2 minute setup and it works for 11 languages
English
sAd.sol 🎒 🐾 retweetledi
One Kindred. Five biomes. The world is bigger than you think @solana 🐾
❄️ Snow
🌴 Desert
🌱 Grasslands
🏖️ Beach
🌋 Lava
Tag 2 friends you’d explore this world with, and get Discord access 👀
English
SQLite + Chroma + background HTTP service + Bun + uv just to remember context across sessions? if you have any project structure, a STATE.md file does this with zero infrastructure.
this ""solves"" what tools did claude call when the actual problem is what decisions were made and why.
plain markdown files + git > databases for session
context
Hasan Toor@hasantoxr
🚨BREAKING: Someone just solved Claude Code's biggest problem. It's called Claude-Mem and it gives Claude persistent memory across sessions. - You can use up to 95% fewer tokens each time. - Make 20 times more tool calls before reaching limits. 100% Opensource.
English
@nocoffeebreaks Looks like there’s a good chance we all will be there to see $8 again 😅
English
I was there when SOL went to 8$
I’m still here to see it dump 60% from ATH again 😂
English
@NapierHolland @cgtwts No. Game Studios will use these tools to reduce costs and decrease the size of it's teams which will lead to the same experience or even more blunt experience.
English
Google latest AI makes you generate games in a couple of minutes, that's insane.
This dude just made a Greenland version of GTA 6.
Gaming studios are cooked big time.
Google AI@GoogleAI
Last August, we previewed Genie 3: a general-purpose world model that turns a single text prompt into a dynamic, interactive environment. Since then, trusted testers have taken it further than we ever imagined — experimenting, exploring, and pioneering entirely new interactive worlds. Now, it’s your turn. Starting today, we're rolling out access to Project Genie for Google AI Ultra subscribers in the U.S. (18+). We know what you create will be out of this world 🚀
English