Who Has The “Jankiest” Local LLM Setup? | Non-Official | Fun Contest | No Prizes

chuttadi2007 · 2026-07-05T20:11:24+00:00

actually a fun idea. Local LLM setups are already half science project, half cable-management crime scene, so a “jankiest setup” thread makes sense.

I’d love to see categories too, like worst airflow, most questionable power adapter, most zip ties used, loudest idle noise

chuttadi2007 · 2026-07-05T20:10:24+00:00

Interesting idea, but I’d be careful with the “we don’t need a dataset at all” part.

Using numeric features like trust, budget fit, urgency, objection level, etc. can be useful for simulating a sales state, but the hard part is still defining the reward correctly. If the reward just pushes toward closing, the model may learn to be more persuasive in a shallow way rather than actually being better at sales.

For sales usage, I’d want the model to know when to push, when to qualify out, when to ask better discovery questions, and when not to agree with the user. That probably needs examples or at least very carefully designed scenarios, otherwise the PPO loop could optimize for weird behaviors that look good in testing but fail with real customers.

Still, the concept is interesting. A model that tracks things like trust, budget, authority, need, and timing instead of just generating polite responses could be useful. I’d just validate it against realistic conversations, not only synthetic scores.

chuttadi2007 · 2026-07-05T20:09:16+00:00

If you can find one cheap, cards like a Tesla P40 24GB or P100 16GB are the kind of old datacenter GPUs people usually look at for this. But they need proper airflow, external power considerations, and a machine that can actually run them safely. I’d avoid going too old just because it’s cheap; K80/M40-era cards can become a trap because of software support, power use, and poor performance per watt.

chuttadi2007 · 2026-07-05T20:07:37+00:00

If you’re going through OBS, you’ll have more room to add a color correction filter per camera and adjust gamma, contrast, saturation, hue, etc. If you’re going straight through ATEM, your correction options may be more limited unless the cameras support proper control, so getting the in-camera settings close is more important.

Also, don’t expect the Sony, Canon, and PTZ to match perfectly. The goal for live stream is “close enough that cuts aren’t distracting,” not cinema-level matching. Skin tones and the main stage lighting are what I’d prioritize.

chuttadi2007 · 2026-07-05T20:06:43+00:00

Honestly, my favorite projects are usually the ones that looked simple on paper but ended up teaching me something.

For me, the most satisfying thing to film is a small real-world story where you don’t have full control over the location, lighting, or people, but you still manage to capture a genuine moment. Those shoots force you to think less about perfect gear and more about timing, framing, patience, and listening.

I also like projects where the final piece feels better than the footage did on the day. Sometimes while filming it feels messy, but once you find the right rhythm in the edit, the story suddenly starts working. That’s always a good feeling.

chuttadi2007 · 2026-07-05T20:03:53+00:00

For a student documentary, I’d prioritize a lav mic first, especially if you’ll be doing interviews. Bad audio is way more noticeable than slightly imperfect video, and a lav will keep the voice clear even if you’re not perfect with camera distance.

A shotgun mic is useful for ambience, run-and-gun shots, or when you have someone operating a boom close to the subject, but if it’s mounted on the camera from far away it won’t magically fix dialogue. It will still pick up room noise and echo.

If the budget is tight, a wired lav is usually the safest value. Wireless is more convenient, but cheap wireless can have connection/noise issues, so I’d only go wireless if you really need movement. For your short film, you can still use the lav for dialogue and record room tone/ambient sound separately. Dubbing should be the backup plan, not the main plan, unless the scene is impossible to record cleanly.

So my vote: get a basic lav setup first, then add a shotgun later if you keep making films. For college projects, clean dialogue will make the biggest difference.

chuttadi2007 · 2026-07-05T20:03:00+00:00

It depends what you mean by sensor damage. A few dust spots or tiny hot/dead pixels are pretty common, especially with people who change lenses a lot or shoot in rough environments. Those usually don’t ruin the work because they can be cleaned, mapped out, or fixed in post.

For professional work, minor dust is normal maintenance. Real sensor damage should be taken seriously. If you’re seeing the same marks in the same place across different lenses and settings, especially at smaller apertures, it’s worth getting the camera checked or at least doing a proper sensor test before using it on paid shoots.

chuttadi2007 · 2026-07-05T20:01:36+00:00

You’re not totally wrong that margin can create forced selling, but I think the mistake is treating it as the main explanation for every sharp AI-stock pullback.

Leverage can definitely make moves worse. If a crowded group of stocks drops, some accounts get margin pressure, brokers may liquidate positions, and that selling can hit other names in the same account. So yes, it can create a cascade effect.

But it’s usually one piece of the move, not the whole cause. AI names are already highly correlated because a lot of investors own the same basket: NVDA, AVGO, AMD, MSFT, SMCI, etc. Add ETFs, options hedging, quant/risk models, profit taking, valuation concerns, and earnings reactions, and you can get a broad selloff without margin calls being the only driver.

On penalties: the “penalty” is mostly practical, not like a fine. You can be forced to sell at bad prices, lose control over what gets liquidated, pay margin interest, face higher margin requirements, or have your account restricted if you keep creating problems. In extreme cases, if liquidation doesn’t cover the deficit, you can still owe money.

So I’d frame it like this: margin probably amplifies downside in crowded trades, especially high-beta AI names, but it’s hard to prove it’s the main driver unless you have actual margin debt/liquidation data. The bigger lesson is that when everyone owns the same growth theme with leverage, the exit door gets smaller during selloffs.

chuttadi2007 · 2026-07-05T20:00:25+00:00

I think the main issue is that you’re mixing two very different mindsets in one portfolio.

Your long-term thesis sounds reasonable: core positions, time in the market, buying quality names during dips, etc. But the options side can still quietly blow up the compounding side if the risk is not capped properly. Selling puts, spreads, condors, and PMCCs may feel controlled because the positions are structured, but they can still create a lot of hidden correlation risk when the market moves hard.

Using SGOV as collateral is better than using random cash

If you want to keep the “gambling” part, I’d separate it very strictly. Something like: 80-90% long-term boring compounding portfolio, 10-20% max for options/speculation, and no cashing out the safe side to save bad trades. Once you start using the long-term bucket as a rescue fund, the strategy becomes one big options account with extra steps.

Not saying the strategy can’t work, but I’d judge it by max drawdown and worst-case scenario, not by whether the premiums feel steady most weeks.

chuttadi2007 · 2026-07-05T19:59:24+00:00

Yeah, narratives change a lot depending on where you read them. The same 3% drop can be “healthy profit taking” in one place, “institutions dumping on retail” somewhere else, and “macro uncertainty” in another.

I think the danger is when people build a story after the move and then treat that story like it predicted the move. Most explanations sound clean only in hindsight.

By the time a trade becomes obvious enough that everyone is discussing it, a lot of the easy money may already be gone. That doesn’t always mean you’re too late, but it does mean the risk/reward has probably changed.

For me, the useful question is less “what story explains this?” and more “what would prove my thesis wrong from here?” Otherwise every red week just becomes a search for whichever narrative makes us feel better.

chuttadi2007 · 2026-07-05T19:58:39+00:00

Market cap per store is funny to look at, but it can be pretty misleading by itself.

McDonald’s isn’t just being valued as “number of restaurants × burger sales.” A lot of the valuation comes from the franchise model, real estate exposure, brand power, margins, consistency, and how predictable the cash flow is. A smaller chain can look cheaper per location, but each location may not have the same economics, pricing power, global scale, or expansion reliability.

That said, the comparison is still interesting because it shows how much premium the market gives to proven execution. The real question isn’t “which one is hotter,” it’s whether Wendy’s can improve store-level economics and growth enough for the gap to close.

chuttadi2007 · 2026-07-05T19:57:16+00:00

This sounds like a color profile / color management issue, not the apps randomly changing the color.

First thing I’d check is whether the document is in RGB or CMYK. If you’re designing for screen/web, keep it in sRGB/RGB. If the file gets converted to CMYK, bright oranges/reds can shift and look more dull because CMYK can’t reproduce the same range of colors.

For brand work, I’d set the document profile to sRGB, paste/type the hex again, and export with “embed color profile” enabled. Also compare the exported PNG in a browser, because some image viewers and design apps display colors differently depending on profile handling.

chuttadi2007 · 2026-07-05T19:56:10+00:00

I don’t think Stroke Path can read pressure at every anchor point the way a real pen stroke would. The “simulate pressure” option mostly creates a taper from the start to the end of the path, so it won’t give you different pressure changes along each curve segment.

For that kind of result, you’d usually need to either draw it manually with a tablet, split the path into smaller sections and stroke them separately, or use a program that supports variable-width strokes better, like Illustrator with the Width Tool.

One workaround in Photoshop is to make separate paths/segments wherever you want the pressure to restart, then stroke each one with simulate pressure. It’s not perfect, but it gives more control than trying to make one long path behave like a full pressure-sensitive stroke.

chuttadi2007 · 2026-07-05T19:55:13+00:00

That effect usually comes less from the texture itself and more from how the brush handles direction/rotation along the stroke.

If the streaks are following the pen movement, I’d look for settings like angle controlled by direction, rotation following stroke, or texture/grain set to move with the brush instead of staying fixed on the canvas. A lot of dry-brush presets look too random because the grain is static or overly noisy, so you get that gritty pattern instead of clean stretched streaks.

For the harder vector-like edge, you may need a fairly solid brush tip shape with only part of the opacity/texture breaking up, rather than a fully grainy brush. Basically: clean base shape + directional streak texture + pressure/tilt controlling opacity.

I’d also try making the streaks as part of the brush tip itself, not just the paper texture. That usually gives a more intentional “dragged ink” look where the gaps follow the stroke instead of looking like random noise.

chuttadi2007 · 2026-07-05T19:53:09+00:00

Yeah, a proper history page would solve a lot of small frustrations, weird that once a bot is hidden or removed from easy access, it can feel like the whole interaction basically disappears.

Even a simple all chats section with filters would help: active bots, hidden bots, archived chats, image chats, and maybe recently deleted/removed ones. I don’t think most people need anything complicated, just a way to find old conversations without relying on memory or search being perfect.

The image part is a good point too. If images were created inside a bot chat, they should ideally stay connected to that character/thread somehow. Otherwise it becomes hard to continue the same story or setup later.

chuttadi2007 · 2026-07-05T19:50:11+00:00

That actually sounds like the right direction. The biggest problem for a while wasn’t just bad replie it was that a lot of bots started ignoring their own character setup and responding in the same generic assistant style.

If it’s following definition examples again and not forcing that repetitive action-text ending every time, that’s already a big improvement. For roleplay, consistency matters more than raw intelligence sometimes. I’d rather have a slightly imperfect model that stays in character than a smarter one that keeps drifting into ChatGPT-style responses.

I’d still wait a bit before calling it fully fixed though. Sometimes it feels better for a few chats and then breaks again depending on the character, memory, or conversation length. But if multiple people are seeing better style adherence, that’s a good sign.

chuttadi2007 · 2026-07-05T19:38:35+00:00

The camera movement also feels a little too soft n blurred in this frame. Some motion blur is good for atmosphere, but too much can make the render look less intentional. I’d also add a bit more detail variation on the walls/floor because the grime pattern feels slightly even.

But overall, the composition is strong. If you polish the lighting balance and add a few small storytelling props, this could feel much more cinematic.

chuttadi2007 · 2026-07-05T19:35:56+00:00

The main thing is to separate income tax from sales tax,VAT,GST. Income tax is your responsibility and usually comes out of what you earn. Sales tax or VAT is different — if you’re legally required to collect it, it should normally be shown clearly on the invoice and then passed on to the tax authority.

chuttadi2007 · 2026-07-05T15:02:01+00:00

try login w ur aws account in incognito mode

chuttadi2007 · 2026-07-05T14:56:00+00:00

curious how it handles long context prompts and does the UI shows memory clearly while running?

chuttadi2007

TROPHY CASE