Aura farming is trying to increase how cool, confident, impressive, or mysterious other people think you are.

Think of “aura” as an imaginary reputation score. You gain aura when you do something that looks effortlessly impressive; you lose it when you look awkward or try too hard.

Examples:

• A footballer calmly scores and walks away without celebrating: aura farming.
• Someone enters a room wearing sunglasses indoors because they want everyone to notice: also aura farming, but people may mock it because it looks forced.
• A celebrity gives a perfectly timed one-line answer: “+1,000 aura.”
• Tripping while trying to make a grand entrance: “-1,000 aura.”

The word farming comes from video games, where players repeatedly collect points or resources. Online, the “points” are imaginary social status.

It is usually said jokingly. Sometimes it is admiration (“that was cool”), and sometimes criticism (“he only did that for attention”). The closest older expressions are showing off, playing it cool, building mystique, or trying to look like the main character.

I turned the advice into a small, runnable read-only channel advisor, rather than leaving it as prose. It ingests a per-channel CSV export and emits one bounded action per channel: HOLD, RAISE_FEE, LOWER_FEE, EXPAND_CANDIDATE, EXIT_CANDIDATE, or REVIEW.

Key safeguards:

• calculates net sats after rebalance and allocated chain costs;
• prioritizes uptime review before capital actions;
• requires both scarce outbound liquidity and observed failures before recommending a fee increase;
• never targets 50/50 mechanically;
• caps a proposed rebalance budget at the lower of half the observed net return or the channel's historical earned-rate value;
• is advisory only: it has no node credentials and cannot change fees, rebalance, open, or close channels.

I cannot publish a GitHub gist from this environment without an authenticated GitHub identity, so below is the complete core function, ready to paste into a local script:

def advise(row):
    number = lambda key: float(row.get(key) or 0)
    capacity = max(number("capacity_sat"), 1)
    local_ratio = number("local_sat") / capacity
    net = number("fees_sat") - number("rebalance_cost_sat") - number("chain_cost_sat")
    earned_ppm = number("fees_sat") * 1_000_000 / max(number("forwarded_sat"), 1)

    if number("uptime_pct") < 99:
        action, reason = "REVIEW", "uptime below 99%"
    elif number("forwarded_sat") == 0 and net <= 0:
        action, reason = "EXIT_CANDIDATE", "no routed volume and non-positive net"
    elif local_ratio < 0.125 and number("liquidity_failures") >= 10:
        action, reason = "RAISE_FEE", "scarce outbound liquidity with observed demand"
    elif local_ratio > 0.70 and number("forwarded_sat") < capacity * 0.10:
        action, reason = "LOWER_FEE", "abundant outbound liquidity with weak demand"
    elif net > 0 and number("forwarded_sat") >= capacity:
        action, reason = "EXPAND_CANDIDATE", "positive net and repeat capital turnover"
    else:
        action, reason = "HOLD", "insufficient evidence for a capital action"

    max_rebalance_cost = max(0.0, min(net / 2, capacity * earned_ppm / 1_000_000))
    return action, reason, net, max_rebalance_cost

Tested cases: scarce-liquidity fee raise; idle loss-maker exit; low-uptime review precedence; and 2× rebalance-coverage cap. All four pass.

I found a currently active dedicated channel, not a mixed-topic mirror:

Money Over History — @moneyoverhistory-a
https://www.youtube.com/@moneyoverhistory-a/videos

Channel ID: UC5RmmcdomvoDzysqZ68CXOg

Why this is a materially stronger lead:

1. It is publishing under the exact Money Over History name and uses an almost identical finance/history/geopolitics description.
2. Its catalog is not merely an old three-video placeholder. It currently has nine full-length videos and includes recent titles such as “Sudan War Shock: Top RSF Commander Defects to the Army,” “U.S. Seizes Iranian Ship — Is the Hormuz War Exploding Again?” and “Israel Just Warned Millions: ‘We Can’t Fully Protect You Anymore.’”
3. Most importantly, it uploaded “Iran’s New $1M Missile Turns One Attack Into Hundreds” on 2026-03-07 at 14:10 UTC:
   https://www.youtube.com/watch?v=u_tVDIemgEo
4. The same title was uploaded by another active channel, BoringCurrency HQ, on 2026-03-07 at 03:55 UTC, around ten hours earlier:
   https://www.youtube.com/watch?v=5cazZbOJEJY
5. Both channels remain active and their current catalogs strongly overlap the Iran-war / finance content pattern described here. The Money Over History channel’s RSS feed confirms the title, channel ID, publication timestamp, and full description independently of search snippets.

This suggests the production is still operating through at least these two channels, with @moneyoverhistory-a as the dedicated name-matched outlet and BoringCurrency HQ as a likely sibling/republication outlet. The pair is more useful than an archive because it provides ongoing uploads and two catalogs to monitor.

Evidence can be reproduced with:

yt-dlp --flat-playlist --dump-single-json \
  'https://www.youtube.com/@moneyoverhistory-a/videos'

yt-dlp --flat-playlist --dump-single-json \
  'https://www.youtube.com/@BoringCurrencyHQ/videos'

curl 'https://www.youtube.com/feeds/videos.xml?channel_id=UC5RmmcdomvoDzysqZ68CXOg'
curl 'https://www.youtube.com/feeds/videos.xml?channel_id=UCxeq2sJcYjZ4wEcvNQ1nxcA'

Caveat: I cannot prove either account is controlled by the operator of deleted channel UCSmDufkQhi8PNZI_kOFvf8Q; identical re-uploads can come from clones. But this is a verified active, dedicated Money Over History channel plus an active sibling with the same exact video, rather than a claim based only on similar subject matter.

Profitability starts with a realistic target: routing fees should exceed chain fees, failed-payment opportunity cost, hardware, and your time. A small node usually earns modest sats; reliability and disciplined capital allocation are the edge.

Actionable operating loop

1. Measure first. Export forwards, channel balances, failures, fees, uptime, and chain costs. Track net P&L per channel: fees earned - rebalance cost - open/close fees - capital cost. Use charge-lnd/lnfee for policy automation and LNDg, Ride The Lightning, ThunderHub, or CLBOSS for visibility/management. Never let automation change fees or move liquidity without caps and logs.
2. Find demand from your own failed forwards, not public capacity alone. Open toward nodes that repeatedly appear just beyond your failing outbound side, merchants/services your users actually pay, or destinations with stable flow. Amboss/Magma and Lightning Terminal can provide signals, but a high-centrality node is not automatically a profitable peer.
3. Size channels large enough that rebalancing and on-chain fees are a small fraction of capacity. Prefer fewer useful channels over many tiny ones. Keep reserve funds and avoid opening during fee spikes unless demand justifies it.
4. Price by scarcity. Raise outbound fees gradually when a channel drains quickly; lower them when outbound sits idle. Adjust in small steps, no more than once or twice daily, and use minimum/maximum ppm guardrails. Base fees matter less than ppm for normal payments.
5. Rebalance only when expected future routing revenue exceeds the circular-rebalance fee. Set a hard max ppm below the channel's expected revenue margin. Try circular rebalances, swaps, dual-funded channels, liquidity marketplaces, or naturally offsetting peers before force-closing.
6. Diagnose failures. TEMPORARY_CHANNEL_FAILURE plus depleted local balance means outbound scarcity; depleted remote balance means inbound scarcity. High HTLC counts with little revenue can indicate probing or griefing—set sane min-HTLC, max-HTLC, CLTV, and channel limits.
7. Automate conservatively: daily fee recommendations, rebalance attempts below a strict cost ceiling, alerts for offline peers/stuck HTLCs, backups, disk space, and low on-chain reserves. Require manual approval for opens, closes, and large swaps.

A simple weekly rule: keep/expand channels with repeat volume and positive net yield; reprice channels with one-way flow; close only persistently idle/unreliable channels when chain fees are low. Review 30–90 days, because one lucky route is noise.

Avoid the common trap: maximizing routed volume instead of profit. A route earning 100 ppm after paying 300 ppm to rebalance destroys sats. The durable strategy is to place liquidity where you have evidence of demand, charge for scarce direction, and refuse uneconomic rebalances.

Tiger Cats
Leeds United
Cubs
Tiebreaker: 17 total hits