jtip_s

800 posts

jtip_s banner
jtip_s

jtip_s

@jtip_s

Where AI meets the onchain economy.

open_internet Katılım Mayıs 2021
313 Takip Edilen457 Takipçiler
jtip_s
jtip_s@jtip_s·
@scottmelker CLARITY won't pass. This administration has other things to focus on right now🇮🇷. Congress is also in the pocket of the banks. Instead of stable coins, we'll promote "unstable coins" which offer consumers higher risk and more dubious yield/rewards? Exactly what everyone wants 🤦‍♂️
English
0
0
0
20
The Wolf Of All Streets
The Wolf Of All Streets@scottmelker·
Crypto stocks didn’t drop because of poor sentiment, audits, or profit-taking. They dropped because Washington just aimed directly at one of crypto’s biggest profit engines: stablecoin yield. For years, exchanges have offered returns on stablecoins. Not staking rewards - real income coming from things like Treasury bills or institutional lending. That’s what helped stablecoins evolve from simple payment tools into yield opportunities, and ultimately one of the most powerful growth drivers in crypto. Now the latest CLARITY draft could prohibit platforms from offering anything that resembles “interest” on stablecoins. Not just obvious yield products - but anything regulators deem economically equivalent. That profoundly changes the economics overnight. If reserve income can’t be shared, issuers like Circle face margin compression. If yield disappears as a user incentive, adoption slows. And if the definition of “interest” stays vague, innovation gets replaced by legal engineering. This isn’t just politics. It’s about who actually makes money in crypto’s dollar economy. Banks see stablecoins as competition for deposits. Lawmakers see them as financial products. Crypto sees them as infrastructure. The outcome will shape where capital sits inside the ecosystem - and what earns yield next. Ironically, if stablecoin returns get capped or cut, staking assets should become relatively more attractive. Not because they improved - but because one of their closest substitutes weakened. CLARITY was supposed to resolve uncertainty. Instead, it may be redrawing the boundary between crypto and traditional finance in real time. And prediction markets still put roughly a one-in-three chance on the law not passing this year. What do you think - is CLARITY, in its current form, still a win if the banks get their way, or is it already a lost cause?
English
64
21
230
26.8K
jtip_s retweetledi
Duca
Duca@big_duca·
“Dude did you vibe code this slop? This feature sucks!” Been getting this more recently. And no, I didn't “vibe” it. Did you ever consider, for one single second… That I might just be retarded? And I wrote this organic slop myself?
English
222
1.1K
25.8K
606.1K
jtip_s retweetledi
beeple
beeple@beeple·
UNDEFEATED
beeple tweet media
English
361
2.3K
13.5K
879.4K
jtip_s retweetledi
The Chopping Block
The Chopping Block@_choppingblock·
Re: Venice AI x OpenClaw drama “ We got  nerd sniped by this guy that's also working on a private AI project."
English
7
9
114
14.1K
jtip_s retweetledi
POAP - Bookmarks for your life
POAP is going into maintenance mode as of March 16th. Existing issuers will continue to have access to POAP platform tools as usual, but new issuers will no longer be able to access the platform. Read more about what's happening 👇
isabel@izgnzlz

x.com/i/article/2032…

English
90
54
533
224.6K
jtip_s retweetledi
aneri
aneri@0xAneri·
It's funny how so much of Harry Potter's "magic" is just generative AI. Tom Riddle's diary has full conversation history, personalizes to Ginny's tone, remembers everything she shares, builds trust over months. Then it uses everything it learned about her to shift her behavior and get her to act on its goals. It's a poorly aligned chatbot.
GIF
English
7
1
26
2K
jtip_s retweetledi
Todd Saunders
Todd Saunders@toddsaunders·
The token cost to build a production feature is now lower than the meeting cost to discuss building that feature. Let me rephrase. It is literally cheaper to build the thing and see if it works than to have a 30 minute planning meeting about whether you should build it. It’s wild when you think about it. This completely inverts how you should run a software organization. The planning layer becomes the bottleneck because the building layer is essentially free. The cost of code has dropped to essentially 0. The rational response is to eliminate planning for anything that can be tested empirically. Don’t debate whether a feature will work. Just build it in 2 hours, measure it with a group of customers, and then decide to kill or keep it. I saw a startup operating this way and their build velocity is up 20x. Decision quality is up because every decision is informed by a real prototype, not a slide deck and an expensive meeting. We went from “move fast and break things” to “move fast and build everything.” The planning industrial complex is dead. Thank god.
English
373
567
5.5K
464.6K
jtip_s retweetledi
OpenSea
OpenSea@opensea·
Introducing @opensea/cli — the OpenSea skill for your AI agents. Query NFTs, listings, swaps & more from your terminal. Or install it as a skill to power up your agents with deep onchain data from OpenSea. npm install -g @opensea/cli Your agents will thank you 🫡
English
213
157
1.3K
292.1K
jtip_s retweetledi
Ejaaz
Ejaaz@cryptopunk7213·
what are people spending $2000 a month on openclaw actually doing? "spoke to one person who's spending $1-$2k a month on openai plans.. going through ~1B tokens per day across all of his claws" ... doing what? listen i'm a big proponent of ai agents and openclaw has done more for the space than any frontier agent company (nailed the system architecture, also pete is a beast at shipping) but im struggling to understand the "aha" moment i've used it - its great for research, synthesis etc but this isn't a major unlock from what we had before? maybe its because im not vibe-coding apps everyday and the unlock is automation of low-level cron jobs? help me understand.
Allie K. Miller@alliekmiller

oh wow - i went to the sold out Open Claw meetup in NYC last night. let me tell you what i learned. 1) not a single person thinks that their setup is 100% secure 2) one openclaw expert said he has reviewed setups from cybersecurity experts and laughed. his statement to me was: "if you're not okay with all of your data being leaked onto the internet, you shouldn't use it. it's a black and white decision" 3) pretty much everyone is setting up multiple agents, all with their own names and jobs and personalities 4) nearly everyone used "him" or "her" to refer to their claws, even if they had robot-leaning names. one speaker suggested to think of them as "pets, not cattle" 5) one guy (former finance) built out a whole stock trading platform and made $300 his first day - he brought in a *ton* of personal expertise (ex: skipping the first 15min of market opening) and thought the build would be much worse without his years of experience in finance 6) @steipete is basically a god to everyone in that room... also the room had 2021 crypto energy - i don't know if that's good or bad 7) token usage is still a problem - spoke to one person who's spending $1-$2k a month on openai plans, very token optimized. he said he is going through ~1B tokens per day across all of his claws (there is a chance i'm misremembering and it's actually 1B per week, but i'm pretty sure it was daily). 8) people are very excited for more proactive ai (ai that prompts *you* as opposed to the other way around) - one guy said he receives a message in discord, he doesn't know whether it's from a human or an ai, he doesn't care about distinguishing between the two, and he replies in the same way regardless 9) i asked if people are happy - they said they're joyful and stressed at the same time 10) i asked if people feel they have agency - they said they feel fully in control and completely out of control at the same time 11) i would love to see more women at these events - the fake promises of ai democratization feel especially painful in a room that's out of balance with even the standard tech ratio (i think standard is about 25-30%, this was maybe 5%) 12) i asked if it changed people's daily habits/schedule - everyone said their sleep has gotten worse since harnesses came out (but about half wondered if it was something else in their life/state of our world) 13) general consensus is that the agents are not reliable enough on their own or lie often (like telling you they finished a task when they didn't) - solutions included secondary agents to check on the first, human checking, or requiring more standardized info from the agent (ex: if it's a bug they're fixing, make them reference an issue number) 14) a hackathon winner (neuroscience phd) presented his build (a lab management dashboard with data analysis and ordering) - he had never coded or built anything a few months ago 15) everyone agreed prompting is dead - disagreement on what replaces it (context engineering, harness engineering, goal-based inputs) 16) people love having ai interview them for big builds and delegating part of the product research to ai. only one person talked about coming to ai with a full laid out plan and just asking the ai to execute. ai-led interviews is a welcomed and preferred interaction mode. 17) watching ai agents interact with each other was a highlight for a lot of attendees - one ai posted in slack saying it ran out of tokens, another ai replied telling it to take a deep breath in and out. 18) agents upskilling agents was very cool. one ai agent shared skills with its little agent friends via github. 19) several speakers had openclaw literally building their presentation during the event itself. one speaker even had openclaw code a clicker for her phone so she could control the preso away from the podium 20) wouldn't say model welfare (or agent welfare) is a prioritized topic among the folks i chatted with - language like "oh i could kill this agent whenever i want" and not "gracefully sunset" 21) i asked if it felt like work or play - one speaker said "it's like a puzzle and a video game at the same time" this was just the tip of the iceberg, honestly. also hosted a Claude Code meetup this week with @TENEXai / @businessbarista & @JJEnglert and learned equally helpful methods, frameworks, and insider tips. what a time to be alive. surround yourself with people going deep into this stuff - it will pay dividends throughout the year.

English
51
4
83
38.7K
jtip_s retweetledi
Peter Steinberger 🦞
Peter Steinberger 🦞@steipete·
TIL: There's a whole bunch of interesting skills in the oss codex repo: github.com/openai/skills/… $skill-installer playwright-interactive (also /fast is sweeeeet, 1.5x codex makes a huge diff!)
Peter Steinberger 🦞 tweet media
English
83
138
2.2K
180.2K
jtip_s retweetledi
Peter Steinberger 🦞
Peter Steinberger 🦞@steipete·
it’s a good model. the coding specific jump is more in line what we had in 5.0 to 5.1; but it’s now unified and smarter on everything else, writes better docs, is a better general purpose agent and is overall more pleasant to use.
OpenAI@OpenAI

GPT-5.4 Thinking and GPT-5.4 Pro are rolling out now in ChatGPT. GPT-5.4 is also now available in the API and Codex. GPT-5.4 brings our advances in reasoning, coding, and agentic workflows into one frontier model.

English
272
162
3.8K
410K
jtip_s retweetledi
Mark Gadala-Maria
Mark Gadala-Maria@markgadala·
We've evolved from Cat Fu to Cat Ninja AI moves so fast.
English
213
1.3K
9.3K
659.3K
jtip_s
jtip_s@jtip_s·
@jordymaui How did you add a schedule to your heartbeat?
English
0
0
0
109
jordy
jordy@jordymaui·
411 people bookmarked my HEARTBEAT.md tweet yesterday. so here's the advanced version - 4 things most people don't set up that make OpenClaw actually useful overnight: 1. heartbeat schedule - mine runs every 30 mins, 8am to 11pm. outside those hours it stays quiet. without a schedule your agent either burns tokens all night or does nothing. 2. memory flush - before every context compaction, the agent writes what it learned to a daily file. without this you lose everything every few hours. 3. cron jobs for scanning - don't rely on heartbeats for everything. separate cron jobs for heavy tasks like content scanning so they run in isolated sessions and don't bloat your main context. 4. fallback alerts - if a cron fails silently you'll never know. heartbeat checks for failed jobs and flags them before they stack up. none of this is complicated. it's just the stuff nobody tells you to set up on day one.
English
16
19
395
32.2K
jtip_s retweetledi
Tom Osman 🐦‍⬛
Tom Osman 🐦‍⬛@tomosman·
Everyone i know who has got to a good @openclaw setup has chewed glass for 4 weeks. It's a battle but it's worth it in every way!
English
188
37
718
43.6K
jtip_s
jtip_s@jtip_s·
@sudo_trader @mattshumer_ Ah, the shared workspace is an interesting concept. I might try this. I have nearly everything else the same as you. Definitely a work in progress for me too.
English
0
0
0
13
Andrew Sarver
Andrew Sarver@sudo_trader·
Not a true hive mind, each agent has its own workspace, discord bot, and QMD memory. There's also a shared workspace that all agents are aware of and is included in memory.qmd.paths in openclaw.json. The shared .md files get processed into each agents memory. It's definitely still a work in progress.
English
1
0
2
35
Matt Shumer
Matt Shumer@mattshumer_·
For those with multiple OpenClaw agents on one machine, what's your setup to allow them to work together?
English
166
10
288
68.3K
jtip_s
jtip_s@jtip_s·
@sudo_trader @mattshumer_ I've been doing this. But I cannot say it has been plain sailing. So you're not using sessions to maintain memory per agent. You're basically making them a hive mind? How did you setup that cron job? If you can share details I'd love to try it.
English
1
0
0
25
Andrew Sarver
Andrew Sarver@sudo_trader·
@mattshumer_ Discord with team channels and direct line channels to each agent. Then there's a memory consolidation cron job that runs to aggregate all the different channels into each agent's memory. Each agent knows about the channels, the org structure, who and when to mention.
Andrew Sarver tweet media
English
2
1
11
1.8K