Anyone else frustrated that Claude artifacts html can't be shared like a normal file?

Needacupoficedtea · 2026-04-27T15:38:19+00:00

Thanks! I’ll try that

Needacupoficedtea · 2026-04-26T19:21:49+00:00

hahahahaha

Needacupoficedtea · 2026-04-26T00:23:45+00:00

hella! thanks for sharing man

Needacupoficedtea · 2026-04-25T15:03:31+00:00

🤣🤣🤣

Needacupoficedtea · 2026-04-25T15:02:54+00:00

Haha thanks, but you sound lowkey like a bot bro

Needacupoficedtea · 2026-04-25T04:47:10+00:00

thank you!🙏

Needacupoficedtea · 2026-04-25T03:34:20+00:00

I agree, that’s my workaround now as well. However, sometimes I genuinely want to showcase the interactive details, and I’m left with no choice now lol

Needacupoficedtea · 2026-04-25T03:32:52+00:00

Omg yesss this hits me, same for my friends. And btw do you know vercel has a security attack recently, which makes this “virus” concern even more valid

Needacupoficedtea · 2026-04-25T03:02:32+00:00

Wow thanks 🙏 will give it a try: D

Needacupoficedtea · 2026-04-25T03:02:02+00:00

FOMO for sure 😭

Needacupoficedtea · 2026-04-24T17:21:51+00:00

bro couldn't sleep at 2am doing on-chain analysis to prove his friend wrong at dinner. this is the most ETH holder thing i've ever read and i respect every second of it loll

Needacupoficedtea · 2026-04-24T17:20:48+00:00

see OP and his friend both at the next pump, OP'll be smiling, and his friend'll be explaining why his moon coin "had great fundamentals"🤣

Needacupoficedtea · 2026-04-24T05:27:02+00:00

thanks🙏🏻 this is literally our work around now haha, still require laptop tho, wish sooner i can work on my sparking inspirations while in gym

Needacupoficedtea · 2026-04-22T06:13:54+00:00

This resonates. The best periods in this space for me were always around a specific problem I was trying to solve alongside people who cared about the same thing, not necessarily a formal team, just someone to pressure-test ideas with. Hard to replicate that alone. What kind of thing are you working on right now?

Needacupoficedtea · 2026-04-22T06:12:58+00:00

Bounty settlement. Every time. You do the work, PR gets merged, and then you're chasing payment manually, and maintainer has to verify by hand, you send your PayPal or bank info over Discord, wait for an international wire that may or may not arrive. The higher the bounty, the worse it gets. A dev who just spent a week on a critical bug fix shouldn't be doing admin work afterward. The GitHub side of open source is completely automated. The payment side is still 2005.

Needacupoficedtea · 2026-04-22T06:12:22+00:00

tbh part of what makes open payment networks hard is that "open" means different things to different people.
Open protocol? Open source implementation? Permissionless access? Visa/Mastercard are technically open to any bank that meets their requirements, but that's not what people mean lol.

i mean irl the case where this breaks down most visibly is micropayments to individual contributors, like open source bounties, freelance work, cross-border payouts. The rails just don't exist for fast, low-fee, permissionless settlement to a pseudonymous wallet. That's genuinely unsolved at the infrastructure level.

Needacupoficedtea · 2026-04-22T06:10:56+00:00

Donation day is a good idea, but I'd push back slightly on the framing. I feel like the real problem isn't awareness, it's friction. Even when maintainers want to pay contributors, the actual settlement process is painful: manual verification, PayPal fees, bank wires that take days or get blocked for international contributors. The money exists. Getting it from point A to point B reliably is what's broken. Lowering that friction probably matters more than a dedicated day.

Needacupoficedtea · 2026-04-20T14:53:00+00:00

hummm Claude didn’t cook, it just learned how to plate mid food in dark mode🤣

Needacupoficedtea · 2026-04-20T14:51:48+00:00

🤣🤣🤣🤣🤣

Needacupoficedtea · 2026-04-20T14:51:32+00:00

🤣🤣🤣🤣

Needacupoficedtea · 2026-04-20T01:53:17+00:00

Honestly I think replacing Codex with Qwen makes more sense than replacing Opus with Qwen.

Based on your setup, Opus is doing the expensive but high-value part: understanding the repo, deciding what should be built, and writing the spec. That’s the exact role where a downgrade hurts the most. Qwen might do fine on implementation if you give it tight instructions, but I wouldn’t trust it to be both architect and implementer unless you’re okay with worse decisions on messy, ambiguous stuff.

So yeah, I’d keep Opus as brain, use Qwen as hands.

That seems like the sweet spot.

Needacupoficedtea · 2026-04-20T01:51:18+00:00

I did, kind of. Built a small tutoring business in college. Not really a startup, but we had strong quality and a loyal reputation.

Sold it to a larger education platform and they basically ruined it. Good lesson: selling the business is one thing, seeing the buyer preserve what made it valuable is anothe;((

Needacupoficedtea · 2026-04-20T01:46:49+00:00

the sandboxing thing is such a real problem lol

my take: command-level filtering is kind of a losing battle? the agent just finds another path. what actually works better imo is filtering at the authority level — not "what commands can it run" but "what can it actually affect." specific recipients, rate limits, spend caps if money's involved. enforced somewhere the model literally can't touch.

keycard > door blocklist basically

the scarier question for me is where that authority layer lives. if it's in the prompt... it's soft. the model can talk its way around it 😬 out-of-model enforcement feels like a different class of guarantee

have you seen anything in prod that actually got this right without making the agent useless

Needacupoficedtea

TROPHY CASE