u/Electronic_Resort985

My Jeep almost stranded me last fall because I drained the starter battery running camp gear overnight. That was enough pain for one season.

I kept the stock battery for starting and added a house battery in back. Went with Vatrer Power for that one. Its a 300Ah LiFePO4 at 12V, with self heating. Also installed a CTEK D250SA and a 2000W inverter.

It is not a tiny setup but now I can run fridge, camp lights, radio charging, and heater fan without babysitting voltage every hour. Typical day for me is around 40 to 55Ah used depending on weather.

Biggest lesson was wiring. I first used thinner cable on the charge line and saw annoying voltage drop. Swapped to thicker cable and it immediately behaved better. Wish I did that first and saved myself a weekend.

Took it to the Sierra last month, nights in the teens. Battery still charged in the morning once there was sun. For my use, this setup is way less stressful than one battery trying to do everything.

For folks running dual battery in a Wrangler, what did you do for tie down and crash safety in the cargo area?

For the past two years, our agency ran a quarterly SEO audit for each client that took roughly three weeks from kickoff to delivery. One person handled the technical crawl, another pulled backlink data and keyword rankings, a third built the competitive positioning matrix, and then someone stitched it all into a deck that usually landed a week late. About 60 billable hours per client, and by the time it shipped, half the data was stale.

Last quarter I scrapped the whole process and rebuilt it as a single continuous pipeline. The output is now a live interactive HTML report on a .mule.page subdomain. It covers technical site health (crawl errors, Core Web Vitals, indexation gaps), maps the client against five competitors across 14 dimensions like domain authority and content velocity, renders a radar chart so leadership can see relative strengths at a glance, and surfaces keyword clusters where competitors rank and we don't, filtered by traffic value so the content team gets an actionable list instead of 4,000 irrelevant terms.

I'll be honest about what flopped first. My initial attempt was to chain together three separate tools and stitch their outputs with a script. That broke constantly because one tool would update its export format or rate limit me mid crawl, and I'd spend half a day debugging before the actual analysis even started. Switching to a MuleRun agent that handles the scraping, normalization, chart rendering, and deployment in one pass on a cloud VM solved the reliability problem. I write a plain English brief, point it at the domain and competitor URLs, and come back four hours later to a live report. The first run still took a full day of tweaking that brief, though. Getting it to produce a clean deliverable rather than a data dump required several iterations, and I still adjust filters per client vertical.

The radar chart was a learning experience too. I originally used nine axes and the result was an unreadable blob. Five to seven axes (domain authority, content depth, backlink velocity, topical breadth, Core Web Vitals, local pack visibility) is the sweet spot for B2B clients. And the competitive positioning matrix ended up being the slide clients actually stare at. They skim the technical audit, but they spend ten minutes on the matrix, especially when the dimensions map to KPIs they already track internally.

First time I shared one of these reports, the client asked how many people worked on it. When I said one person plus an afternoon, the conversation shifted to "can we do this monthly instead of quarterly." That frequency upgrade increased our retainer value by about 30% because the faster cadence justified a higher fee while our delivery cost barely moved. We reallocated about 12 freed hours per client per quarter into implementation work, and average organic sessions improved roughly 15% within two quarters of the switch.

The part I'm still figuring out is whether monthly delivery trains clients to expect this speed as the default, which could compress margins over time. For now, the shift from "here's what's wrong" to "here's what we already fixed this month" has justified premium positioning rather than eroding it.

Hey, I have a really close friend who recently told me he’s gay. I’m really grateful that he trusted me with that, and I told him that I support him and that he doesn’t have to worry about what other people think.

Since then, I’ve been thinking about getting him a small gift. Nothing big or dramatic — just something that says “I’ve got your back.” With Pride Month coming up, I also want him to know that if he ever wants to check out LGBTQ+ spaces or events, I’d be happy to go with him, but only if he actually wants to. No pressure at all.

I saw a lightning-pattern piece from Cherrykitten while browsing, and it made me think of him, but I’m not attached to that specific brand or item. In my head, the lightning kind of represents courage and being yourself, but I also realize I might be overthinking the symbolism or projecting my own meaning onto it.

Would something like that feel thoughtful, especially with a short note explaining why I picked it? Or would it be better to keep things simpler and just continue showing support without making a big gesture?

I've been pulling prediction market trade data for the last few weeks trying to understand how quickly information gets priced into these markets compared to equities. What I found on the tariff-related contracts is genuinely unsettling.

On Polymarket, the "US-China tariff reduction by Q3" contract sat between 22-26% probability for nearly two weeks straight. Flat. Boring. Then on May 11th starting around 2:14 AM UTC, a cluster of wallets began aggressively buying YES shares. Over the next 19 hours, roughly $47M in notional value flowed into YES positions across three related tariff contracts. The probability shot from 24% to 67% before any mainstream outlet had reported a word about the Geneva talks producing a framework.

Here's where it gets interesting. I cross-referenced the Polymarket activity with Kalshi's equivalent tariff contracts. Kalshi saw a similar spike, but it lagged Polymarket by about 4 hours. The Polymarket whales moved first, and the Kalshi flow followed. One wallet alone accounted for $8.2M in YES purchases across both platforms within a 6-hour window.

I used Surf to run SQL queries across their prediction market tables — they have something like 934M+ rows of trade data indexed across both Polymarket and Kalshi with cross-platform market matching. Pulled the orderbook snapshots leading up to the move and the bid-ask spread compression was textbook. Someone was lifting every offer available, not trying to get a good fill, just trying to get positioned.

The Geneva tariff pause was publicly reported 19 hours after the initial cluster of buys. By then the contract was already at 71%.

This isn't the first time. I found three other instances in the last 90 days where prediction market whale flow preceded major policy announcements by 12-48 hours, with position sizes ranging from $11M to $47M. The pattern is consistent: sudden volume spike on Polymarket first, Kalshi follows within hours, public announcement comes later.

Prediction markets were supposed to be the great democratizer of information. Transparent, on-chain, open to everyone. Instead what we're seeing is that the transparency just makes it easier to prove that some participants consistently have better information than the rest of us. The difference from traditional markets is that nobody is investigating this because prediction markets sit in a regulatory gray zone.

The data is all there if you know where to look. Every trade, every timestamp, every wallet. The irony is that the same transparency that was supposed to level the playing field is now just documenting the information asymmetry in real time.

Been working for about 2–3 years now and lately i've been feeling pretty drained. nothing is "wrong" exactly, but every week feels the same and i don't feel like i'm building anything for myself. I've been thinking about trying something on my own, maybe a small side thing first. Problem is i don't really have a clear idea, and the more i sit there trying to figure out the "right" direction, the more i end up doing nothing. So lately i've been thinking maybe i should just pick something and start somewhere. Like instead of overthinking ideas, just look at what's already out there, talk to a few suppliers, see what exists and what might work, and let that guide things a bit.

I know myself though… i tend to think through everything before starting, and that usually just slows me down even more. Not sure if this approach makes sense or if i'm just trying to justify not having a real plan.

Not sure why this made such a difference but yeah.I finally got a proper nightstand from Colamy instead of just putting everything on the floor or stacking stuff on my desk.And somehow my whole room feels more like an actual adult space now.Before it was just bed + chaos.Now with the nightstand and a chair in the corner , it feels a bit more intentional.Like i actually have a place for things instead of just "put it wherever".Weirdly makes me want to keep the room cleaner too.Didn't expect that kind of chain reaction from one small piece of furniture.

Spent the last month dialing in a workflow for printing AI generated miniatures on my Saturn 3. Figured I'd share what works and what doesn't since I wasted a lot of resin figuring this out.

Generate the model in Meshy. I use image to 3D mostly because I can control the pose better by uploading concept art. Text prompts give me random poses that usually don't work for tabletop.

First thing in Blender is check for non-manifold edges. There's always some. Select all, mesh cleanup, make manifold. Then check wall thickness, anything under 1mm gets thickened or it'll break during printing or post cure.

Weapons are the worst offender. Swords, staffs, spears all come out way too thin. I usually just delete them and kitbash replacements from free STL weapon packs. Faster than trying to fix them.

Scale to 32mm in Chitubox, add supports manually. Auto supports miss overhangs on AI models constantly because the geometry is irregular. Manual supports take longer but save failed prints.

Print settings: 2.5s exposure, 0.03mm layer height for detail. Standard grey Elegoo resin.

Success rate after dialing this in is about 80%. The 20% failures are usually models with too many thin floating bits that I missed during cleanup.

Total time per mini from generation to printed: about 45 min of active work plus print time. Not counting the learning curve which was painful.

Worth it for custom campaign minis. Not worth it if you just want generic fantasy stuff, there's better STL packs for that.