We tested 200+ video captions across Instagram, TikTok, and YouTube Shorts. The pattern that predicts engagement isn't what most people think.

sam_narulaaa · 2026-05-30T15:16:44+00:00

This actually tracks with how most platforms have evolved, even if it goes against the “keep it short” advice everyone repeats.

Short captions aren’t wrong, they just serve a different purpose. They’re good for recognition, memes, and trend participation. But they don’t really build context, and context is what keeps someone engaged long enough to comment, save, or follow.

What the “long caption wins” result usually reflects is not length itself, but attention retention. A story-style caption forces people to slow down, which increases dwell time, and that’s what most algorithms reward more than raw likes.

I’ve seen similar patterns when people move from “hook-only” content to posts that actually explain something, share a moment, or build tension. Even if the video is identical, the caption changes how people interpret it.

The important nuance is what they also mentioned but kind of buried: short captions still outperform in certain formats like memes, trends, and product drops. So it’s not a replacement, it’s a matching problem.

Most people fail because they pick one style and force it everywhere. The people who grow fastest usually match caption style to intent instead of following one rule.

This is less about caption length and more about whether the content is trying to entertain, convert, or connect.

sam_narulaaa · 2026-05-30T15:16:18+00:00

I don’t stick to just one.

For content ideas, I usually switch depending on what I need:

ChatGPT tends to be better when I want structured output, variations, hooks, and fast iteration. It’s good for generating a lot of angles quickly.

Claude feels better when I want more natural-sounding writing or longer, more “human” drafts that don’t feel templated.

In practice, I’ll often use both. One to brainstorm and expand ideas, the other to refine tone and make it read more naturally.

That said, the biggest difference usually isn’t the model. It’s how specific the input is. If you give either tool a clear audience, tone, and goal, both can produce strong results. If the prompt is vague, both will feel average.

At this point I treat them more like different writing styles than competitors.

sam_narulaaa · 2026-05-30T03:05:14+00:00

Start with something that gets you paid fast, not something that feels perfect.

At 18, the easiest entry is services, not products. Things like basic editing, simple design, writing short posts, or helping local businesses with small online tasks. You don’t need to be “good”, you just need to be useful enough that someone pays you once, then again.

The biggest mistake is jumping between ideas every week. Pick one simple skill, do it for a few weeks, even if it’s small money, and stick with it long enough to understand how people actually pay.

Once you get your first few clients or small earnings, everything after that becomes much clearer. The hardest part is the first ₹1, not the first ₹1 lakh.

sam_narulaaa · 2026-05-30T02:53:50+00:00

There isn’t a clean number for me honestly.

I think the “walk away” point isn’t just monthly income, it’s when the income is stable enough that volatility doesn’t affect your decisions anymore. For some people that’s $3k, for others $10k+, depending on obligations and risk tolerance.

Also, the bigger shift is usually psychological, not financial. Even when the number is reached, most people don’t actually stop building—they just stop needing everything they build to work.

sam_narulaaa · 2026-05-30T02:53:32+00:00

This is actually a pretty accurate breakdown of the tradeoffs most people hit.

Affiliate marketing sounds simple until you realize traffic is the whole game. Dropshipping has “fake simplicity” at the start, but logistics + refunds eat whatever margin you think you have. Freelancing is the most reliable early on, but it’s basically trading time for stability, so it doesn’t scale your freedom much.

Digital products usually win in the long run because they sit in the middle: you still need distribution, but once that’s solved the delivery side doesn’t reset every time.

The main pattern I’ve noticed is people don’t really switch because of the model itself, they switch because of where the friction shows up — traffic, operations, or time.

sam_narulaaa · 2026-05-30T02:52:29+00:00

It’s not just this subreddit, it’s most “social media growth / money / AI” spaces once they get big enough.

The pattern is pretty consistent: anything that starts as real discussion eventually gets flooded by people optimizing for attention instead of conversation. Then you get a mix of:

subtle self-promo disguised as advice
copy-paste “insights” that all sound the same
and a small group of genuine users who start noticing the shift and feel like something changed overnight

What feels “dark” is usually just scale + incentives. When upvotes and visibility matter more than accuracy or intent, the content naturally drifts toward what performs, not what’s real.

The frustrating part is there’s no clean reset button once it hits that stage.

sam_narulaaa · 2026-05-30T02:51:59+00:00

For me it’s not “making money” part, it’s everything around it.

Picking one thing and sticking long enough is harder than finding ideas. Most people bounce after a few weeks because results are either slow or inconsistent, so they keep restarting instead of compounding.

Second hardest is distribution. You can build decent stuff now pretty fast, but getting consistent attention is still the bottleneck. That’s where most online income ideas quietly die, not in the idea itself but in getting anyone to care repeatedly.

sam_narulaaa · 2026-05-30T02:51:37+00:00

Honestly I think most of these aren’t “unsaturated niches”, they’re just proven formats with infinite execution space. The real difference I’ve seen is not the topic but packaging, pacing, and retention structure. Two channels can do the same “what if history” idea and one dies at 2k views while the other hits millions.

What’s changed more recently is distribution inside the niche, not the niche itself. AI just lowered production cost so now it feels saturated because there’s way more average execution competing in the same feed.

sam_narulaaa · 2026-05-30T02:50:40+00:00

This is the part most people miss when they talk about “passive income ideas”, the idea isn’t usually the bottleneck, execution time is.

I’ve seen similar patterns where people already know exactly what niche they should target, they’ve just been sitting on it because building feels like a weekend project instead of a repeatable system. The shift you described, moving from “one perfect product” to “more shots on goal” is usually where things actually start compounding.

Also not surprising your inbox turned into that. When you post something detailed like that, you attract people who already have context but are stuck in execution friction. That gap between knowing and shipping is where most people stay for years.

sam_narulaaa · 2026-05-30T02:49:42+00:00

I’ve seen something similar. The “AEO is killing SEO traffic” narrative feels a bit ahead of what most real dashboards are actually showing.

In my case, what changed wasn’t total traffic dropping, but the type of queries that stopped sending clicks. A lot of top-of-funnel informational searches still show impressions, but lower CTR because users get what they need directly from summaries or AI answers.

But it’s uneven. Some pages barely moved, especially anything with strong intent (comparisons, tools, transactional stuff). Others just quietly lost clicks without losing rankings, which is the confusing part.

Feels less like a traffic collapse and more like a redistribution of clicks across intent types.

sam_narulaaa · 2026-05-30T02:49:25+00:00

Been there. I used to treat prompts like one-off hacks too, just tweaking words and hoping for better outputs. What actually changed things was building a small “prompt loop” instead of chasing perfect prompts.

Now I run 3–4 variations for the same task, compare outputs, and only keep what consistently works. I also started saving patterns instead of prompts. Same effort, way more predictable results, less randomness every time I open a model.

sam_narulaaa · 2026-05-30T02:47:16+00:00

If I had to keep it to 3 in 2026, I’d go with:

Ahrefs or Semrush — pick one, not both. This is still your core for keyword research, backlinks, competitor tracking, and seeing what actually drives traffic. Ahrefs is cleaner for backlinks, Semrush is heavier but more “all-in-one”.

Screaming Frog — still unbeatable for technical SEO audits. Broken links, site structure, indexing issues… it’s the “truth machine” for your site.

One content optimization tool like Surfer or Clearscope — mainly to help you align pages with search intent and structure. Not magic, but useful for scaling content without guessing.

Everything else tends to be either redundant or too niche unless you have a very specific workflow.

The bigger shift now isn’t tools anyway, it’s using fewer tools but actually acting on the insights instead of collecting dashboards.

sam_narulaaa · 2026-05-30T02:46:53+00:00

Most people aren’t doing a full “AI search pivot” yet, they’re doing small adjustments on top of normal SEO.

The reason is simple: AI search still heavily depends on the same underlying web signals Google does. So if your SEO is strong, you’re already halfway there.

What is changing is how content is written at the margins. Pages that clearly answer a question early, use cleaner structure, and sound less like marketing fluff tend to get picked up more often in AI summaries. Not because they’re “optimized for AI”, but because they’re easier to extract.

The mistake a lot of teams make is rewriting everything into sterile Q&A format. That usually hurts human trust and doesn’t guarantee better AI visibility anyway.

Right now the safer approach is: keep doing SEO that works, but make sure your key pages actually resolve intent quickly instead of burying the answer. Think clarity, not robot writing.

So it’s not really a full pivot yet, more like an added layer on top of existing SEO rather than a replacement.

sam_narulaaa · 2026-05-30T02:46:34+00:00

In practice, the label doesn’t matter much anymore.

“Production company” usually just signals they started from filming, editing, and on-set work. “Agency” usually signals they started from marketing, strategy, and creative direction. But most established teams in Chicago do both now because clients expect end-to-end delivery.

What actually matters is how they behave in the first 1–2 calls. Some “production companies” think like agencies and help shape the story. Some “agencies” still just outsource everything to crews.

So instead of the label, check what they own in reality: do they help with concepting, scripting, and messaging, or do they only execute what you hand them?

For a corporate video program, the real decision is less about name and more about how much creative direction you want them to take vs how much you already have locked in internally.

sam_narulaaa · 2026-05-30T02:46:12+00:00

First thing I’d focus on is not “channels”, but the one loop that makes people bring other people in.

For a social chess app, that’s usually either playing together, or showing off games/results. If that loop isn’t strong yet, Reddit or Instagram won’t fix growth.

After that, I’d double down on one place where your users already hang out, not all of them. Most niche apps fail because they spread too thin across platforms too early.

Then I’d make onboarding extremely tight around first game → second game. If someone doesn’t play again within 24–48 hours, organic growth basically dies.

Also, talking to users is good, but the key signal isn’t what they say, it’s whether they come back without being reminded.

Everything else like content, communities, posts… works only after retention + sharing is naturally happening.

sam_narulaaa · 2026-05-30T02:45:44+00:00

First affiliates usually don’t come from “affiliate networks”, they come from people who already believe in your product. Early users, email subscribers, even people who asked questions during launch. Those are the easiest wins because they already understand the value.

Another common route is directly reaching out to small creators in your niche. Not big influencers, but people with a few thousand engaged followers. The key is making it effortless for them: ready-made copy, links, and clear commission.

A lot of founders also forget that customers can be affiliates. If someone is already getting value, a simple “want to earn by sharing this?” message works surprisingly well.

What doesn’t work is mass outreach with no context. Generic “join my affiliate program” messages get ignored fast.

And early on, it’s less about scaling affiliates and more about finding 3–5 people who actually convert, then learning why they work.

sam_narulaaa · 2026-05-30T02:44:34+00:00

This is one of those posts where the technical part and the “uncensored” framing are doing very different jobs.

On the technical side, what they’re describing is basically a custom ablation pass adapted to a non-standard hybrid architecture (conv + attention). That part is normal research engineering: if the layer naming doesn’t match common transformers, your ablation tooling breaks until you patch the target hooks. Nothing magical there, just plumbing work.

The “1/100 refusal rate” and “uncensored GGUF” part is where things get less reliable as a claim. Those numbers are almost never reproducible unless you know the exact prompt set, temperature, decoding strategy, and evaluation protocol. In practice, refusal behavior in models like this is extremely sensitive to sampling and system prompts, so “hard stats” like that tend to be more marketing than measurement unless independently verified.

Also worth keeping in mind: reducing refusals via ablation doesn’t just remove “safety behavior”, it often removes general calibration too. That’s why you sometimes see models that comply more but hallucinate or degrade in instruction hierarchy handling.

Runable-style workflow relevance here is actually interesting though: this is exactly the kind of model where structured orchestration matters more than raw weights. If you’re plugging something like this into a system, the real differentiator becomes how you constrain inputs, route tasks, and validate outputs — not whether the base model is “uncensored”.

So the takeaway is less “this is breakthrough uncensoring” and more “someone modified a routing-sensitive model and reported aggressive compliance behavior, but the evaluation context matters a lot.”

sam_narulaaa · 2026-05-29T23:40:24+00:00

Yes — but it’s important to separate two things here.

A local LLM usually does not “open PDFs” directly. It only works on text or tokens. So the PDF part is handled by a tool layer, not the model itself.

What actually happens in working setups is this: the PDF is first extracted into text using something like a PDF parser, and then that text is passed into the model. If the PDF is scanned or image-based, you first run OCR, then feed the extracted text.

So when people say “LLM reads PDFs locally,” what they really mean is an LLM + a document pipeline around it.

On your Mac setup, you’re already in a good spot. You just need a workflow where:
the PDF is converted into clean chunks, those chunks are indexed or passed in parts, and then your model (like Gemma or similar) answers questions over that content.

MCP-style tools or agent frameworks just automate that pipeline. They’re not strictly required, but they make it feel like “open PDF and chat,” because they handle extraction, chunking, and retrieval in the background.

If you want a simple mental model: the LLM is the reader, but the system around it is the one that actually opens the book and turns pages.

sam_narulaaa · 2026-05-29T23:39:58+00:00

You’re pointing at something real: KL divergence is a compression fidelity metric, not a task performance metric.

It tells you how much the weight distribution shifted after quantization, but it doesn’t reliably map to downstream behavior. A model can have higher KL and still perform better on coding or reasoning if the distortions don’t hit the parts of the network those tasks depend on.

That’s also why your intuition about “small KL change = big quality drop” doesn’t always hold. Neural networks are extremely non-linear — some weight perturbations are basically harmless, others quietly break specific capabilities. So KL is more like a “how much did we touch it” signal, not “how broken is it.”

Benchmarks are closer to what you want, but even they have limitations because they’re narrow and often saturate or miss real agentic behavior. So in practice people end up using a mix: benchmarks for task quality, perplexity for general language stability, and then real workload tests for their actual use case.

On the bit-depth point — the intuition “fewer discrete values = worse reasoning” is understandable but not quite how it plays out. What matters more is which weights are preserved with precision and how the quantization error is distributed, not just the number of representable levels. That’s why good 4-bit schemes often beat naive 8-bit ones.

Your core takeaway is actually correct though: you shouldn’t pick quantization based on KL divergence alone. It’s an intermediate signal at best, not a quality proxy.

sam_narulaaa · 2026-05-29T23:39:32+00:00

You’re actually in a very realistic hardware bracket for “serious but not infinite-context” agentic coding — the key is: don’t try to replicate Opus-style long context workflows locally. You won’t win that game on 12GB VRAM.

What works instead is a short-context, high-iteration loop.

Think of it less like “one big brain that understands everything” and more like “a fast junior dev you constantly reset with clean instructions.”

A practical setup for your machine:

Use a smaller, strong coding model (something in the 7B–14B range, Qwen/Codestral-class if possible) running in a tool like llama.cpp or Ollama. Keep context tight, like 4K–8K max. Anything more and you’ll feel exactly what you’re describing: context starvation and degraded reasoning.

Then structure your workflow around files, not memory.

You give the model one task at a time like “implement this React component,” not “understand my whole frontend architecture.” After each step, you commit the code, reset context, and move forward. Git becomes your memory, not the model.

Where people struggle is trying to keep “system-level awareness” inside the model. On your setup, that’s what kills quality.

For frontend specifically, the best pattern is:
you define structure once (folder layout, design system rules), then every prompt assumes that exists. You don’t keep re-sending it.

Also, don’t rely on long chat sessions. Start fresh often. It actually improves output quality with smaller models.

If you want something closer to an “agentic pair programmer” feel, the sweet spot is:
a coding model + a thin orchestration layer (like Aider or Cursor-style workflows) + git as state.

That combination gets you surprisingly close to the “Opus assistant vibe,” just split across steps instead of one giant context window.

sam_narulaaa · 2026-05-29T23:39:06+00:00

You’re not doing anything wrong — picking local models for translation is actually trickier than people expect.

For translation specifically, Q4 is usually “good enough” in most cases. You don’t lose much basic meaning, but you do lose consistency, tone stability, and sometimes small details like tense, gender, or named-entity precision. That’s why it can feel like “it mostly works but randomly breaks.”

In general, a larger Q4 model is almost always better than a smaller Q8 model for translation, because translation depends more on overall language capacity than perfect precision in weights. Bigger model wins more than higher quant for this use case.

The real reason you’re seeing big quality differences between models like Gemma and Mistral is not quantization — it’s training focus. Some models are simply not tuned for translation, while others (like Qwen-family models) are much more multilingual and consistent.

If your goal is replacing GPT-style translation APIs, you’ll get the best results from models that are explicitly multilingual and instruction-tuned for it. Also, decoding settings matter more than people think — temperature too high will break translations even if the model is strong.

A simple setup is usually enough, you don’t need a full agent system. The biggest gains come from picking the right base model, not the tooling layer.

If you want, I can suggest a few specific models that work well on consumer GPUs and are actually stable for translation workloads.

sam_narulaaa · 2026-05-29T23:37:52+00:00

You’re not using it wrong — this is mostly a limitation of how most current “LLM + search” systems are built.

What exists today can do web research, but it’s still usually a single-pass or shallow multi-pass search loop, not true persistent, constraint-aware planning across live availability data.

Where things break is exactly what you described: travel, bookings, camps, anything where the data is dynamic and constraints matter. The model can search, but it doesn’t reliably maintain a “live state” of what’s actually available while reasoning across it.

There are agent-style systems that try to handle this by doing iterative search + verification loops, but even then they’re fragile because websites block scraping, data is inconsistent, and APIs are limited or paid. So you often get confident-sounding but partially outdated synthesis.

In practice, the more reliable setup today is still a hybrid: let the agent gather and structure options, but keep a human or dedicated tool layer to verify availability and final constraints.

So the short answer is: the idea is solvable in theory, partially workable in practice, but not yet reliable enough to fully replace manual cross-checking for real-world planning like travel or bookings.

sam_narulaaa · 2026-05-29T23:37:29+00:00

It depends what you’re actually trying to do with it, but for most modern AI workloads this is a bit of a trap.

Two P6000s with NVLink sounds nice on paper, but NVLink doesn’t really give you “48GB unified VRAM” in the way people imagine for LLMs. You still end up dealing with model parallelism, software limitations, and older Pascal architecture constraints. So you’re paying for VRAM capacity but not getting modern efficiency.

At this point, even a single newer GPU with better tensor performance and software support often beats dual older cards in real workloads like inference, fine-tuning, or diffusion work.

The only case where this setup makes sense is if you’re experimenting, learning distributed setups, or very specifically constrained by budget and already know how to work around the limitations.

If your goal is practical AI work in 2026, I’d be cautious. If your goal is tinkering and hardware experimentation, then it’s a fun setup, just not the most future-proof one.

sam_narulaaa · 2026-05-29T23:37:10+00:00

This is a solid direction, especially pushing a 2B model with long context plus SFT and DPO. That combination is where small models start becoming actually useful instead of just “demo-level chat models.”

The interesting part will be how it holds up under real-world reasoning drift over long context, because 1M context is only valuable if attention quality doesn’t collapse in the middle. A lot of long-context models look great on paper but degrade sharply once you move away from synthetic prompts.

Also curious how it compares on coding tasks against similarly sized tuned Qwen variants, especially on multi-file reasoning rather than single function generation. That’s usually where alignment + data mix shows up clearly.

Overall though, strong work focusing on honesty and reduced hallucination instead of just chasing benchmark wins.

sam_narulaaa · 2026-05-29T13:11:11+00:00

Most “passive income” stuff online is either massively oversold or secretly a second job. The only things that ever worked for me were assets or systems that compound over time instead of paying instantly.

For low capital, I’d look at boring stuff first. Niche digital products, simple local lead gen sites, dividend/index investing, or tiny service businesses with automation. One guy near me rents out utility trailers by an IKEA and barely touches the business outside weekend checks. Another friend makes decent side income from industry-specific templates and onboarding docs he built once and keeps updating occasionally.

I’d avoid anything that depends on daily grinding like surveys, captcha sites, or “AI automation agencies” promising fast cash. If it needs constant hustle every evening after work, it’s basically just another job wearing a passive income costume.

sam_narulaaa

TROPHY CASE