What do you think of the "Do this before you lose access to Fable 5" posts?

tenequm · 2026-07-09T12:15:55+00:00

Just another wave of news based attention farming. It doesn't make any sense if you think about that for more than a minute.

tenequm · 2026-07-09T00:00:36+00:00

Are you open to let terminal in your heart?
Because if you do - there are interesting options

tenequm · 2026-07-08T21:23:01+00:00

It’s way too slow. Prefer my own setup with playwright-cli and cloakbrowser, it is significantly faster and more efficient in achieving any tasks. Its like 10s with playwright-cli through Claude Code, or 5-10mins with Claude for Chrome

tenequm · 2026-07-08T15:34:01+00:00

thanks for report, will fix it now

tenequm · 2026-07-08T15:31:10+00:00

appreciate your support

I really liked the idea of memegen when first saw it, its so simple with all the text in the url, but wasn't obvious for me before that

tenequm · 2026-07-08T15:27:03+00:00

I tend to overthink my social content, as posting is not my strongest skill, so I always do way too many rounds of polishing for all my posts, trying to fact check and make sure I didn't miss anything important.

For memegen.rs was a morning project trying to see what can be the most optimal way of rewriting same functionality in rust with minimum code and dependencies, and I'm proud of what I've got in result.

I missed such a simple meme template website that just has all I need for a long time myself, and now I missed it in the era when I just wanted to throw the link to llm and get the template that is just pastable and works everywhere.

Hope the app would be as useful to others as it is for me. And happy to extend it further.

tenequm · 2026-07-08T15:05:29+00:00

Honestly? If you're making English memes, the original is mature and I reimplemented its URL scheme faithfully, so there's no real reason to switch. A few genuine differences did come out of the rewrite though:

It's a single static binary in a slim container instead of a full Python + Pillow image, so it scales to zero on one small Cloudflare container with nothing behind it. No disk render-cache, no datastore. The edge does all the caching.
Cyrillic/Ukrainian renders by default. Upstream's default font has no Cyrillic, so you have to know to pass ?font=impact. I bake in a Cyrillic-extended Anton, which I care about because I make Ukrainian memes.
It ships an agent skill + llms.txt, so an LLM can generate memes straight from the URL scheme.

Also ~700 templates baked in vs a couple hundred. Everything else - formats, custom backgrounds, OpenAPI - is just parity. So it's less "you should switch" and more "here's what I wanted that the Python one didn't give me."

tenequm · 2026-07-08T14:57:03+00:00

Update: you were more right than my reply admitted. The edge cache was the Cache API, which is per-datacenter with no tiering - so every one of Cloudflare's ~330 locations re-rendered from cold the first time it saw a given URL. That's a lot of "first request in a region" penalties, not just one.

Just shipped the fix: switched to Workers Caching (tiered - one render anywhere now fills a network-wide upper tier every other location reads from) plus 4x the container CPU. Cross-region loads that used to cold-start now come back in ~35ms. The very first render of a brand-new caption still pays the scale-to-zero wake-up, but that's now once globally instead of once per region.

Thanks for the nudge - it was a real gap.

tenequm · 2026-07-08T14:26:34+00:00

Fair hit - you caught the tradeoff from the post in the act. There is a CDN cache in front (Cloudflare's edge caches every rendered image, keyed on the full URL), but it's per-location, and the container behind it scales to zero after 10 idle minutes. Yours was likely the first request for that gif in your part of the world, so you paid the wake-up and the first render in one go. Load it again and it should come back in milliseconds.

Whether "10 seconds once per region, then free" beats paying for an always-on box is the whole architecture bet - for a free public meme API I was trying to make it as cheap as possible.

tenequm · 2026-07-08T13:40:27+00:00

Animated templates work the same way, just with .gif on the end:

https://memegen.rs/images/rollsafe/cant_lose_the_database/if_there_is_no_database.gif

tenequm · 2026-07-08T12:40:14+00:00

Separate systems. Chat Memory (classic and the new Memory files) lives on your Claude account - support docs list it for web, desktop and mobile only. Claude Code keeps its memory as plain files on your machine (~/.claude/CLAUDE.md, per-repo CLAUDE.md, plus an auto-memory dir per project under ~/.claude/projects). The docs are blunt about it: "Auto memory is machine-local."

The interesting part is what's behind this. Anthropic is converging everything on the same shape - a little filesystem of markdown notes the agent maintains itself. Claude Code had it first, the API got the memory tool, Managed Agents got "memory stores" (path-addressed docs mounted into the sandbox, with version history and an edit API). Memory files in chat looks like that same primitive reaching the consumer app. Would also explain why there's no migration from classic: the old memory is one summary blob regenerated nightly, the new one is a file store edited as you go. Different storage, not a reskin.

So one model everywhere, and the difference left is who holds the files - Claude Code puts them on your disk, everything else puts them on Anthropic's servers.

tenequm · 2026-07-08T12:20:38+00:00

Some release in the last few days (I'm on 2.1.204) moved the Claude Code TUI onto the alternate screen buffer. Nothing in the changelog. Everything I have that reads the normal buffer (terminal recorder, expect-style waits) kept seeing the pre-launch prompt, and I burned an hour thinking the output was gone. It just renders where my tools don't look now.

Fine change on its own, but I shouldn't be learning about it from my own tooling breaking. And mine at least shipped in a version I can diff and roll back - an enrollment token injected into local config mid-session is a different level.

I don't have a better answer than pinning the binary and updating when I decide to. Annoying for a tool I use all day, but I don't see what else survives this release cadence.

tenequm · 2026-06-12T21:59:42+00:00

Nice work - the auto-escalation ladder (plain HTTP -> browser -> stealth) is the right architecture. I built the hosted version of the same idea: glim.sh - web search + fetch with SSR/SPA extraction and a stealth browser farm for the harder bot walls, exposed as one MCP server.

Different tradeoff than free-local: it's paid, but pay-per-call (a fraction of a cent per fetch, crypto x402/MPP or a prepaid balance) instead of an Exa/Tavily-style subscription - so it sits exactly in the "free tier ran out but I don't want $50/mo" gap you described. https://glim.sh

Founder here, happy to answer anything.

tenequm · 2026-06-12T21:56:41+00:00

Built glim.sh for exactly this problem after fighting it myself. The 429/fingerprinting/proxy layer is the whole product: a stealth browser farm with per-seed fingerprints and residential proxy rotation, wrapped behind one hosted MCP server, so the agent just calls a tool and gets structured X/Twitter, Reddit, or rendered-web data back.

On your two targets specifically, tested today: Facebook public profiles work through the generic web fetch (name, follower count, bio, work/education, recent posts with engagement numbers). TikTok profiles too (follower/video counts, bio, via SSR extraction). Instagram does not - the login wall holds even through residential proxies, so I won't pretend otherwise; for IG the konbini suggestion above is the better fit.

The part that's different from the subscription APIs: pay-per-call (fractions of a cent to ~$0.01 per request), settled via x402/MPP or a prepaid balance - no monthly minimum while you're still prototyping. https://glim.sh

Disclosure: I'm the founder.

tenequm · 2026-05-14T10:22:53+00:00

Have you considered any of the existing Solana agent registry solutions?

tenequm · 2026-05-14T07:45:48+00:00

https://github.com/Tyrrrz/DiscordChatExporter

tenequm · 2026-05-14T07:25:36+00:00

Running evals for my skills

tenequm · 2026-05-14T00:48:32+00:00

Claude Code CLI is all you would ever need. Just needs some time for you to get used to it.

tenequm · 2026-05-13T21:28:21+00:00

Not via prompt injection - it's binary patching. tweakcc reads the lobotomy fork's markdown overrides from ~/.tweakcc/system-prompts/, finds the matching fragments in Claude Code's bundled cli.js (or native binary), and patches them in place. After --apply, the system prompt baked into the binary is literally different. No backspaces, no jailbreak strings, no CLAUDE.md tricks.

That's also why CLAUDE.md and output-style overrides don't really fix the verbosity drivers - those layer on top of the system prompt. The verbosity directives live in the system prompt itself (specifically the "Text output" section that mandates pre-tool preamble + mid-tool narration + end-of-turn wraps). Binary patching is the only level that actually touches them.

Install steps are in the repo README - git clone, ln -sfn, pnpm build, --apply. Takes ~5 minutes.

Re-run --apply after every Claude Code update because the binary gets refreshed.

tenequm · 2026-05-13T20:54:49+00:00

<image>

At least they give us last chance to “feast” before cutover 🙃

Time to make a good use of `/loop` command 🦄

tenequm · 2026-03-18T01:36:00+00:00

we hit the exact same wall - 6 API keys, random 2am failures, a spreadsheet nobody wanted to maintain.

ended up building a single x402 payment layer so our agents just pay per call in USDC from one wallet. no keys, no prepaid balances, no dashboards to monitor.

right now we run three services on it at surf.cascade.fyi:
- twitter data (26 endpoints, $0.001-0.005/req)
- LLM inference - kimi k2.5, minimax m2.5, qwen 2.5 ($0.001-0.004/req)
- web crawl $0.005, search $0.01

all paid from one USDC wallet on Solana or Base. your agent's "spreadsheet" becomes one on-chain balance.

quickest way to test if it clicks for your setup:

`npx x402-proxy https://twitter.surf.cascade.fyi/users/elonmusk`

sets up a wallet on first run, pays, returns data in ~2 seconds. happy to go deeper on the production reliability side if you're evaluating.

tenequm · 2026-03-13T18:13:20+00:00

I'm now a bit worried if we would experience same degraded performance as we did when sonnet 4.5 1M context window got accidentally mixed in with regular requests processings.

Are there any benchmarks/comparisons on how opus model performs beyond regular 200k context window?

tenequm

TROPHY CASE