Joshe

Peace is overrated.

A mind that spins no stories about itself cannot be self-deceived.

Thanks! I'll share it if I ever complete it and remove all my personal info from it.

IQ is a few variables in a much larger picture. You have to look at configurations. Raw processing variables (what IQ primarily captures) Working memory capacity Processing speed Fluid reasoning / abstraction capacity Drive and orientation variables (what points the processing power) Need for cognition Systemizing drive Metacognitive access Epistemic drive Retrieval and processing style Linear vs. associative retrieval Convergent vs. divergent processing Receptive vs. acquisitive integration Epistemic and emotional variables Need for closure / comfort with ambiguity Openness to revision Intellectual honesty / epistemic humility Emotional integration Frustration tolerance Structural and contextual variables Crystallized knowledge base Domain breadth vs. depth Self-regulatory capacity Sensitivity to salience Social and environmental context Ben Shapiro has a high IQ, but it usually doesn't convert to intelligence for various reasons. "What is perception oriented toward in the first place?" determines a lot about how intelligence shows up and the particular shape of it. This is a badass project I need to finish.

Thread should be renamed to "Cultivating contempt for low conscious humans". "Let's start a mega-thread where we shit on idiots" Once you've processed 100 samples, the next 100 will be the same. To keep revisiting this topic is doing nothing but cultivating contempt. "Devilry" "Why do we make a habit of holding low conscious humans in contempt?" "What is the best way to accept conformity without making us contemptuous?" These types of questions cultivate development.

lol

That's because you whip its ass, lol.

The thought "she loves me" never did anything for me. Engagement or connection is love expressed, as opposed to stated. Some men want to be reminded they're loved, some want to be shown respect, and some want proof. IDK. It seems like happiness. The moment you start thinking about it, it's not there.

Emotion as guide.

Jesus Christ. This is the type of shit the banned folks were trying to keep at bay. lol

You seem like you just spent all day drafting an "I'd like to be a mod" letter to Leo. lol

I signed up to get notifications from Trump. Just got this: Live now.

Kimi K3 is no Fable but apparently it's not far off the mark. Tons of clickbait titles. Good video here though: Not super excited about sending my data to China either.

The recon didn't find any RSS feed. Yeah, the prompt intentionally omitted the scraping strategy so it could figure it out on the fly, as opposed to boxing it in early. I haven't tried lately, but pretty sure yt-dlp can download Vimeo vids. Works for my porn anyway, lol. Claude knows this is a GUI app with a backend. It knows it would need to track the markup to display it like like an actual blog post. You can't display videos and images with raw text. I mean, you could, but it wouldn't make sense because you'd need to style the content anyway. I'm pretty sure it would do recon and build a parser based on its findings and then reconstruct the markup based on user requirements. You wouldn't want to keep Leo's markup. It's probably shit, lol. Good idea about putting the OCR capture in the alt attribute, although not sure if that's beneficial for search. I'm no expert though.

I could think of some interesting use cases. Imagine if you took an aerial drone shot and mapped out dimensions of your entire property and house with all the rooms and gave it pictures and measurements of your entire space, along with blueprints and maps of your electrical and plumbing. "What is the shortest route to running a CAT5 cable from my router to my accessory building and how many feet of it do I need?" "I want to install a fence with 4x4 posts and welded wire. How many linear feet do I need to span the perimeter and how many 4x4s do I need if I space them 6ft apart? How much welded wire do I need and how many bags of concrete with 2 bags per post? Check Lowes or Home Depot for current pricing and give me an estimate for how much it's going to cost. Then use python to create an accurate diagram with all the posts in place." Pretty helpful.

IMO, you don't get to commit a violent crime and then have your death treated as a loss the world owes your family for. Absurd.

Would use it a lot but not as frivolously. People are already preparing for and figuring out how to “tokenmax”. My current monthly usage would likely cost somewhere between 5 and 10k, which I’m getting for $200. But the labs offset this because most users are not heavy users like me. Power users are factored into their current pricing. Based on what I've read, these labs are not losing money on inference/compute - they're already profitable there. Some models are really cheap and the best models are crazy expensive. If prices go up, usage would require more effort to match the task or inquiry to the appropriate model. Some tasks and inquiries could be handled by cheaper models fine, so you’d have to understand the various model’s strengths and weaknesses and route appropriately. Interesting finding published the other day that if you take a screenshot of text and send the screenshot image instead of actual text, the model consumes far fewer tokens, which is really counter-intuitive. The DeepSeek lab found that by using images instead of text, you cut token use by up to 10x. Also, it's not as expensive as I thought. Google's Gemini Flash is super cheap. If you do 250k tokens in and 1 million out, which is a deep work session, it's would cost you 65 cents and Google profits from that.

I think it's possible Trump and the Project 2025 people are planning an actual hostile takeover and won't even try to cheat in 2028. If you know what the Heritage Foundation is and how it operates, and how deeply embedded in our political system it is, when you hear it's leader say "The revolution will be bloodless if the left allows it to be.", and when you realize that dude is serious as fuck and has serious plans in the works, backed by billions of dollars, that statement reads to me like a direct confrontation. Not some slow soft coup. Just a theory, but it seems possible they just outright say "we're taking over, no more democracy". I know it sounds crazy and hard to imagine how they'd pull it off, but these people have the deepest pockets and influence and a vast network of operatives (tens of thousands), and they're building underground bunkers with mini cities inside them. Maybe not likely but I'm keeping it on the table.

I considered that, haha.

I'm sure there's going to be a massive response to this. It'll be interesting how it plays out. Basically, this is a huge pressure campaign to change voting laws before the midterms.

You gotta download Claude Code CLI and then just send it that. It will build it for you.

lol, the solution to your problem.

I would also include an instruction to have it run OCR on all the scraped images so you could search the image posts as well.

Just have Claude Code do it for you. Here's a prompt that should get you an app to fetch the blog daily and let you search it, all hosted locally: # Build prompt: Actualized.org blog reader Build me a GUI app that lets me read and search every blog post from https://actualized.org/insights — a local, offline archive with full-text search that stays current on its own. Start with the backend: getting all the posts off the site, stored durably, OCR'd where the content is locked inside images, and kept up to date via a daily automated check. The GUI comes after. You own the architecture. Everything below is reconnaissance and constraints, not instructions — make your own engineering calls, and tell me if you disagree with any framing here. I'm not a developer, so flag tradeoffs in plain terms. ## What I already checked (verified 2026-07-16 — don't repeat these dead ends) Every convenient structured-data route is closed: - **WordPress REST API: unavailable, and WordPress doesn't render these pages anyway.** A WordPress install *does* exist at `/wordpress/` — it serves the blog's images — but the public site is not WordPress-rendered. Evidence: `/wp-json/wp/v2/posts` 404s at the root; `/wordpress/wp-json/wp/v2/posts` 404s; the permalink-independent fallback `/?rest_route=/wp/v2/posts` returns the homepage HTML rather than JSON or a JSON error, meaning nothing WordPress-shaped handles requests at the root; and a sample post page carries no WordPress fingerprints (no generator meta, no `wp-includes` scripts, no `api.w.org` REST link, no `wp-block-*` or `postid-N` classes). Don't burn time looking for a WordPress-shaped door — there isn't one. - **RSS: useless.** `https://actualized.org/rss` is a valid feed but only carries 10 items, description excerpts only — no `pubDate`, no `content:encoded`, no post bodies. - **No sitemap anywhere.** `/sitemap.xml`, `/sitemap_index.xml`, `/wp-sitemap.xml`, and `/sitemap-index.xml` all 404. `robots.txt` contains no `Sitemap:` directive. So HTML scraping is genuinely the only path. Post URLs must be enumerated by walking the pagination at `/insights`, which runs to roughly 274 pages. ## Site structure - Index with numbered pagination at `/insights`, ~274 pages. - Individual posts at `/insights/[slug]`. - **Canonical host is `www.actualized.org`.** Post links on the index are absolute and include the `www.`, though the site also answers without it. Pick one form and normalize, or you'll end up with duplicate records for one post. - Each post has a title, a publication date, body content, and social share buttons (Facebook, Twitter, Pinterest, Email) that are chrome, not content. **The site's age matters.** `robots.txt` disallows `/includes/`, `/Templates/` (capital T), `/flash/`, `/downloads/`, `/wordpress/`, and several hand-listed `.php` files under `/pages/misc/`. Combined with the total absence of WordPress markup on the public pages, this reads as an old hand-built PHP site with a WordPress install sitting in a subdirectory doing something behind the scenes — plausibly the media library and/or an authoring back-office — while custom code renders the front-end. I never established what WordPress's actual role is, and it doesn't matter for this build: you're parsing hand-rolled HTML either way. The implication is what matters — assume post markup varies across eras, and verify that early rather than trusting page 1 to represent page 274. ## Content characteristics - Posts are short and structurally simple: usually a single headline followed by rich text. - YouTube embeds appear throughout, sometimes several per post. These need to survive into the archive and be playable/visible in the app. - **Roughly 30–40% of posts are just an image, and the image is almost always text.** Not a photo or a diagram — an image containing the actual written content of the post. For these, the HTML body is nearly empty and everything I care about is pixels. That's a large minority, not the majority — most posts are ordinary rich text — but it's far too many to treat as an edge case or handle by hand. See "OCR" below; this is core scope. - Images are hosted under `/wordpress/wp-content/uploads/`. ## Constraints - **Respect `robots.txt`, with one decided exception.** `/insights` and `/insights/[slug]` are not disallowed — that's the content, and it's fair game. `/wordpress/` is disallowed, so don't crawl or enumerate it. However, post images live under `/wordpress/wp-content/uploads/`, and OCR requires downloading them. I've decided that's fine: those are assets embedded in pages I'm permitted to read, and fetching them is the same request my browser makes when I read the post normally. Fetch images **only** by following `src` URLs found in posts I've already legitimately retrieved. Never traverse, enumerate, or spider `/wordpress/` itself. - **Be a good citizen.** Personal-use archive of one site I read. Throttle politely; there's no reason to hit the server hard. A slow crawl is fine — run it in the background. - **Fetch each post once.** The initial crawl should be a one-time cost. See "Keeping it current" below. - **Fail loudly, not silently.** A post that doesn't parse should be recorded as a failure with its URL, not written as an empty or half-empty record. I'd rather see a list of 40 problems than discover hollow posts in six months. - Windows. Assume nothing else about the stack — recommend what fits. ## OCR For roughly a third of posts, the image *is* the article. If the archive only stores the HTML body for those, it stores nothing, and they're invisible to search — a third of my archive would be a hole, which defeats the point of the whole app. So: **Size this properly before choosing an approach.** If the archive turns out to be ~2,700 posts, 30–40% means somewhere around 800–1,100 images to OCR — and every one gets re-processed if I later want a better pass. That's enough volume that per-image cost and total runtime are real design inputs, not rounding errors. Tell me what your approach would cost me in both, and if it's a paid service, what the bill looks like for one full pass. - Text extracted from post images must land in the database and be **searchable on equal footing** with regular post text. If I search a phrase that only ever appeared inside an image, that post has to come back. - **Track which text came from OCR.** I need to know whether a given post's text is authored HTML or machine-read pixels — it affects how much I trust it, how it should be presented, and whether it's worth re-processing later. Don't blend the two into one indistinguishable blob. - **Assume the first OCR pass won't be good enough.** OCR engines vary a lot on this kind of content, and I may want to re-run everything with a better one later. Re-processing must not require re-downloading anything from the site. - **Bad OCR must be visible, not silent.** An image that yields zero text, or obvious garbage, should be flagged as a problem I can review — not written to the database as if it were a legitimately empty post. - **These are quote cards, which is good news.** Confirmed image filenames follow the pattern `leo-quote-<slug>-01.png`, e.g. `leo-quote-life-is-not-a-physical-process-01.png`, `leo-quote-my-work-is-10-percent-wrong-01.png`, served from `/wordpress/wp-content/uploads/`. So these are machine-rendered text on a background — clean, high-contrast, probably consistent typography — not photographs or scans. That's the easy case for OCR and should push accuracy expectations up. Verify the consistency holds across the archive's full history before relying on it. - **The filename is a free sanity check.** The slug in each filename is a human-readable rendering of the quote itself. It's not a substitute for OCR — it's truncated and lossy — but it's an independent signal you can compare OCR output against to catch a pass that's silently producing garbage. Worth storing regardless. - Still sample real examples across the archive before committing to an approach. The `-01` suffix hints at multi-image posts or variants; I don't know what that means. ## Keeping it current The archive needs to check for new posts **daily**, unattended, and pull anything it finds into the archive without me doing anything. Constraints that make this harder than it looks: - **The machine is a personal Windows desktop.** It sleeps, it gets shut down, it won't be on at any predictable hour. A schedule that silently skips its window and waits for tomorrow is not acceptable — missed runs need to catch up on the next opportunity. Days may pass between runs, and the archive still needs to be complete afterward. - **The daily check must be cheap.** Re-walking all ~274 pagination pages every day to find the zero-to-two posts that are new is wasteful and rude to the server. The daily path should cost far less than the initial crawl. - **New posts need the full treatment**, including image download and OCR. A daily sync that grabs an image-only post but never OCRs it has archived an empty post and won't tell me. - **Silent failure is the main risk.** This runs unattended, so the realistic bad outcome isn't a crash — it's the site changing its markup, the scraper quietly finding nothing, and me not noticing for months while believing the archive is current. I need to be able to tell at a glance whether the sync is actually working. Surfacing "last successful sync" and "last error" somewhere I'll see matters more than clever recovery logic. - Don't let a failed or interrupted run corrupt the existing archive. A bad sync should leave yesterday's good data intact. ## Things I don't know - Whether I want to be **notified** when new posts arrive, or just have them appear silently in the app next time I open it. Raise this with me — don't assume either way. - Whether the daily check should also catch **edits to existing posts**, or only genuinely new ones. Same — ask me, and tell me what it costs to do both. - The real post count. ~274 pagination pages; posts-per-page unconfirmed. - How many distinct markup variants exist across the site's history. - Whether publication dates are reliably present and parseable on every post. - Whether pagination is stable enough to enumerate cleanly (new posts shift it). - The 30–40% image-post figure is my rough estimate from reading the site, not a count. Confirm it while you're sampling. - Whether the quote-card format is consistent all the way back. I only saw recent ones; the oldest posts may look nothing like them. - What WordPress is actually doing at `/wordpress/`, beyond serving images. I didn't establish this and don't think it affects the build — but if you find a legitimate, robots-respecting structured route into the content that I missed, I'd rather use it than parse HTML. - Whether OCR'd text should be **shown to me as readable text**, or only used behind the scenes to make image posts findable by search. These have very different accuracy bars. Show me sample OCR output before I decide. ## What I want from you first Before writing the full scraper, show me what you actually found: what the markup looks like at both ends of the archive's date range, how many variants you're dealing with, and what your storage plan is. Then build it once we agree.

His work would be much more appealing and people would want to see where it could go if he wasn't so weird. Point is, it's not primarily about the work. The work is not what people are repulsed by, at least not most. You have the whole anti-transhumanist crowd, but that's not most people.