Richard Young

@tehseowner Go on :-)

Wow

@iamrofe @lr_jordan When I was a lad you read the fresh air spray can and were thankful.

@lr_jordan I think she’d prefer Peppa pig

The no screen time rule for under two year olds is all fine and dandy. Until you’re on your own with your kid and you need to take a shit. How else are you meant to keep them distracted.

@corememunlocked I can even remember the music. :-)

I keep seeing WWIII trending. This is proof it’s all a scam. We’re already on eleven!

@thePhilRivers Example please.

Everyone says "let the data decide" on welcome-series A/B tests. Discount-depth tests are mechanically rigged — the deeper offer always wins the 7-day window and almost always loses 90-day LTV. The data isn't lying. Your test is just measuring the wrong thing.

Ha! Oh yeah, it makes stuff up.

@RtHonBTaplow @ZackPolanski @EssexPR youtu.be/PFLaCUSJUDY?si…

@ZackPolanski @EssexPR Is @ZackPolanski Jewish, @EssexPR? I know his real name is David and he changed his name to sound more Jewish! Like Jimmy McGill in Better Call Saul does changing your name make you Jewish?

None of this is ok. But as a Jewish man yourself, I can’t seem to find your tweets on the countless synagogue attacks recently?… Or churches being burned down ? Why is this ? You’re a Party leader, I’d thought you would be consistent?… Or do you rely on a certain vote ?…

@RepairBritain Feels like this is a wind up. Nobody is that daft?

"Today on St George’s Day" 🤔....

@fba Why have you not gone static? Lean and clean.

Installing SEO agents for my own wordpress and webflow's has been mind blowing. This allows me and my editor do our most creative work since AI is doing all the SEO heavy lifting. DM me if you want to learn how to do this.

@fba @AleksejAros Link to the posts and get them index surely.

@AleksejAros 😂

Easiest SEO hack in the world (with LinkedIn) > Open ahrefs > Site explorer = linkedin dot com > Filter by "keyword contains phrase (put your Keyword)" > Check top results > Ask the owner to add your link / promote / affiliate / etc. 2nd Easiest: rank your own page there

@GrindstoneSEO Move somewhere sunny for more action. ;-)

This plus a timer on my phone to come check 4 Claude instances every 15-20 minutes.

We can send MFs around the moon and my internet goes to and from space but we can’t make rice packets open without splitting. I blame the Iranians. Someone has to be responsible.

You have to keep checking and cannot trust the machine fully at the moment. Sure enough, I was correct.

@myeyesshine_ @GrindstoneSEO I almost always say please and thank you just in case they remember. Unless it’s being a fucking idiot then I tell it so.

@GrindstoneSEO Wait until it can parse X. Then you’re f*cked

Claude turned effort down to Medium across all instances in my setup, that's why it's running like shit today. Back to max, lazy robot. Inb4 Mythos is just Opus but running on max by default.

New Ubiquity switch installed and network setup. Top of the list is that it is pretty. 😂

@GrindstoneSEO But I could try and decode your skills. Send em over 😂

@ukgimp Love this. People are always asking me to 'share my skills and tools'. They're built for me, the way I do things. They wouldn't be plug and play for anyone else, even if they are better.

You can just do things. 🤖 PAI ALGORITHM ═════════════ MINIMAL — Summary request PAI Distributed Memory System Problem: Single-file memory index (234 lines, truncating) with no concurrency support. Growing at 12 files/day, accelerating. Can't run multiple Claude Code instances without data corruption. Solution: Domain-sharded, inbox-buffered memory with tiered retrieval. Architecture memory/ ├── MEMORY.md # Auto-generated catalog (134 lines, was 234) ├── _index.json # Machine-readable manifest ├── _domains/ # 13 domain directories │ ├── reil/ # Client-specific memories │ ├── wordpress/ # WP patterns & gotchas │ ├── seo/ # SEO learnings │ └── ... # 10 more domains ├── _inbox/ # Conflict-free write buffer └── _ops/ # Merge logs & audit trail Key Innovations Inbox Pattern — No instance writes directly to memory files. All writes go to _inbox/ with unique filenames. Zero conflicts, ever. Tier 1+2 Retrieval — Domain matching narrows 1,000+ files to ~100, then keyword scoring against frontmatter picks the 5-12 files that actually matter. <100ms, no LLM call. Instance-Scoped State — Each Claude Code session gets its own state file (instances/{session_id}.json). No shared singleton = no race conditions. What It Enables 3-6 concurrent Claude Code instances on the same machine Separate projects (Instance 1 on LLM_visibility, Instance 2 on FSBO) — each loads only its domain Same project splits (Instance 1 on Grindstone blog, Instance 2 on Grindstone pillar pages) — both write safely Cross-machine sync via git (inbox is local, domains are the sync unit) Scale Runway Files Timeline (6 instances) Per-Instance Load 85 (now) Day 0 ~15K tokens 500 ~1 week ~25K tokens 1,000 ~2-3 weeks ~35K tokens 2,500 ~1-2 months ~45K tokens 5,000+ ~3-4 months Add Tier 3 (LLM) Built Today 3 CLI tools (memory-migrate.ts, memory-merge.ts, memory-index-rebuild.ts) 2 new hooks (MemoryMerge at SessionStart, MemoryLoader at UserPromptSubmit) 7 modified hooks (instance-scoped state across the work tracking system) Updated /save-memory command with inbox protocol Inspired by ByteRover's research paper (arXiv:2604.01599) — their hierarchical context tree approach validated, adapted for file-based multi-instance use 🗣 PashaAI: That's the shareable version. The ByteRover paper gave us the theoretical backing, the inbox pattern gave us the concurrency, and the tiered retrieval gives us the runway. System's live.

But on limitations. On Thursday I built a callback tracking system for cold emails. Getting people to sign up. It works my way. No need for pixels, just direct custom API calls to track. It’s just insane. Built for me only, exactly as I need it. It’s awesome even if I do say so myself 😂

@ukgimp luckily my retard brain has limitless imagination

@GrindstoneSEO Haha. I’d pay for access. 😂

@jdevalk @hellemans I know many people moving to uber fast flat file systems instead of WP. I now would not use it. Things are changing fast as you know. WP will die if they don’t do something.

OK, EmDash is making us have good discussions. #WordPress is delaying 7.0 over a single database table for a feature most users don't need. Meanwhile, one developer at Cloudflare built an entire CMS from scratch. The problem isn't engineering talent. It's priorities 1/2