brucethemoose

Also, if you have a more specific question about memory types, I can try to answer them.

But honestly my knowledge getting dated too. For example, I don’t know much about the specifics of GDDR7 (RTX 5000 memory) off the top of my head.

Like a primer? I don’t know anything off the top of my head, but all this stuff is literaly 1st-year computer engineering in college. The basic of ISAs, circuits, low level programming and computer design are all kinda background you need to understand why RAM trace length is so important.

There are definitely college courses you can look up and read for free.

Most “guides” you’d find on Google repeat outdated information; watch out for that. That’s why the Apple “memory on the CPU” thing keeps persisting; most discussion isn’t even updated to account for CAMM modules. But ECE focused magazines are good about covering and explaining commercial memory tech:

semiengineering.com

www.eetimes.com

Yes.

Actually, it’s everything: en.wikipedia.org/wiki/Random-access_memory#Memory…

…But also, your friend is wrong. And its complicated.

First some background. There are a couple of “regular” types of RAM basically every product uses under the hood. And every one is a set of tradeoffs: bandwidth, latency, capacity, power efficiency, trace lengths, expense, and so on. A few of types:

• “Regular” DDR. This is what you see on sticks for desktops, laptops, and servers.

• LPDDR. Its power-optimized at the expense of some latency and trace length, but its specs are otherwise similar to DDR. This is what smartphones (and Macs) use.

• GDDR. Optimized for bandwidth and cost over everything. Guzzles power. Used on gaming GPUs.

• HBM. Low speed, requires extremely short trace lengths, but low power and latency. Uses an exotic bus with exotic manufacturing techniques. This is what you see on more exotic server accelerators.

But the packaging is also really, really important too. For example, regular DDR5 can come in:

• Unregistered RAM sticks, for your desktop.

• As registered RAM, for servers.

• As SODIMM, for laptops.

And these all have long traces, since they have to come in sticks. They’re “far” from the CPU. Laptop SODIMMS, in particular, have a really poor path to the CPU, and start to run into huge scaling issues at DDR5 speed.

…In other words, laptop DDR5 SODIMMS are particularly slow, because the socket they sit in simply cannot keep up with their speeds.

As for LPDDR5: its specification assumes a shorter, higher quality trace or “wire” to the CPU, hence it can only come soldered, and sitting right next to the CPU:

Samsung graphic

But electrically, it’s almost the same as DDR5! It’s not wider-and-slower like HBM, or more tweaked like GDDR5: it’s just regular old cheap DDR5, massaged to work better soldered to the motherboard.

This is what Macs use.

They’re not using “special Apple RAM” like is the popular perception. They’re using smartphone RAM. Its a bit faster becase it is “closer” to the CPU, but this is misleading, as its nothing like more exotic standards that really take advantage of that proximity. If you read this, its much closer to GDDR5 than HBM: graphicscardhub.com/gddr5-vs-gddr5x-vs-hbm-vs-hbm…

In practice, Apple RAM is faster and “closer” to the CPU, but its more because of business design choices than a particularly exotic memory specification:

• Apple uses very wide buses for their CPUs. Typical laptops are 64-bit or 128-bit, Apple stuff can be 192-bit to 512-bit. This is more expensive, and you pay for it in the sticker price.

• Regular laptops use swappable SODIMM sticks, which have a tremendous speed cost. Apple doesn’t have to worry about this.

• Apple pays a premium for fast, binned LPDDR5, regular OEMs do not.

But it doesn’t have to be this way.

Some laptops already use swappable LPCAMM modules, which for all practical purposes are just as fast as Apple’s RAM, and just as “close to the CPU” from an electrical perspective:

LPCAMM module

Framework was very close to implementing this for AMD’s 256-bit Strix Halo CPUs. They could quite work out the electrical gremlins before release.

TL;DR

Apple RAM is “closer to the CPU” in the existing market, but there’s no technical reason PCs have to be any different.

Apple uses off-the-shelf smartphone RAM, basically.

An AMD Strix Halo laptop, with 2 LPCAMM modules, would be just as fast as Apple memory, and just as “close” to the CPU. Some PCs already do this on a smaller scale.

So strictly speaking, your friend is correct. But its misleading. All that really matters is the memory specification laptop/desktop manufacturers choose.

I am taking another stab at Rimworld, after a long hiatus. Putting together a mod pack for multiplayer.

At risk of going off-topic, Halo’s fall is really sad.

Like, I still imagine everything Infinity could have been as a franchise-reboot, clean slate, high budget, open world game, and it just felt so… underwhelming? Conservatively developed, yet not quite right either?

It feels like it could have been a Halo 3 fan mod, like they didn’t even leverage the format. I know that’s technically not true, but still.

That makes sense. The host is pretty unreliable.

Which is the second issue. No image hosts even support JXL or AVIF, except catbox.moe. It’s infuriating.

What platform is that, out of curiosity? Im pretty sure everything should load an AVIF.

Om Android, or iOS?

JXL is working alright for me.

As an example with a lot of dynamic range, here’s a JXL:

JXL

AVIF:

AVIF

Both render in my desktop and iPhone browsers, just fine. I bet at least one renders for you. And I made them from RAWs from a really old camera!

The problem is, as you say… arbitrary lack of support. As an example, I can’t upload either file to Lemmy. Brand new social media software, and it doesnt’ recognize JXL or AVIF as valid image types, even though they should render just fine? Most image hosts wont take JXL either, hence I had to upload them to litterbox since catbox is down!

An HEIF, on the other hand, has basically 0 support outside of Apple:

HIF

All the HEIC files from my camera are still busted :(.

To be fair, its a tricky issue. Its camera makers’ fault for using a format no one else wants to touch, and rendering them as HDR files instead of SDR with gain maps, as is standard practice for smartphones.

…But still, its annoying. They render fine on my iPhone, on Windows, or KDE Linux, out of the box. But they’re completely garbled in Immich :(

Vibecoded self promo is a growing, specific spam problem though.

And a appreciable fraction of Lemmy/Piefed is “anti AI absolutist.”

I think that’s pretty unique.

Be sure to try the ik_llama.cpp fork. Basically, it specializes in MoE CPU offloading on Nvidia cards, and more efficient quantization types than mainline llama.cpp:

github.com/ikawrakow/ik_llama.cpp/

And see this repo for specific 3090 configs: github.com/noonghunna/club-3090

Honestly I should just write up my general setup in this community too.

So is this a leak?

Because, with a cursory glance, it doesn’t always look like spam.

A classic example I see starts with “I built a…” in the title, has a wall of text in the description, and actually promises to do something interesting. Only upon deeply inspecting the code (or trying it yourself)… it becomes clear it’s hallucinated nonsense.

And it’s not always malicious, either. A lot of devs get deep in AI psychosis as truly believe there building something revolutionary with their vibe coding agent.

And sometimes these projects are interesting!

Hence it would be EXTREMELY helpful to have this tagged, up front. To me, an [AIP] is gigantic red flag to warrant extra caution, but not necessarily a smoking gun, and would help “regular” homebuilt projects stand out from the vibecoded ones.

And [AIT] is just nice to have. Some users don’t want to see any AI in /c/selfhosted, period. It gets reported as spam because people interpret it as that, and this gives would prevent that while giving those users a way to easily filter them out.

Normally I’d agree, but the tagging rule won’t affect the majority of posts. I think it’s an acceptable complication, in this case.

Especially with how much vibecoded spam is in the horizon.

Vibecoded spam is deliberately engineered to look “high effort,” so even with the vagueness of such a rule, it wouldn’t cover the spam so well.

Failure to provide a disclosure after using the tag would mean removing the post. It could be locked, but I would have to assume the majority of the spam-type postings that happened to make it past the rule 7 criteria are the ones who will not provide the requested disclosure. I think it makes for a good filter this way, but please comment if you think otherwise.

Sounds reasonable to me!

I think the major choice is for y’all (the mod team), as enforcing a tagging system is going to increase the moderation workload.

I have no recommendations for a bot.

…You could use an embeddings model for a little extra automation though.

This is a pre-LLM thing, but basically you could feed a script new untagged posts, use a embeddings model to compare the text of their bodies to a keyword (“AI”?), and spit out a number as a rough “similarity” metric. If it’s above a certain threshold (eg if the post seems AI related), send a message to the moderation team to check it, or maybe even post a rules reminder in the comments.

And FYI, embeddings models are tiny, so it doesn’t need extra resources to run or anything.

I have a single 3090!

And I have 128GB RAM. So the best model I can run is MiMo 2.5 (a 300B model) at around 10 tokens/sec, using hybrid CPU inference.

…But that’s the worst-case scenario, for speed. It’s an IQ3_KT quant (with is a high quality quantization type but very slow on CPU), with a model that barely fits in my RAM+VRAM combined, with no DFlash or any kind of speculative decoding turned on. I could tune it to be much faster, but I mostly just want “max quality, fast enough.”

For speed, or prompts with lots of thinking or context, I just run Qwen 3.6 27B now. That would fit in your 3090 no matter how much CPU RAM you have, but you just have to be smart about the backend and quantization you pick. If you just use Ollama, it’s gonna tell you it won’t fit, or use some horrible default that spits out garbage.

You don’t even need Claude anymore. GLM 5.2 API is good enough for 95% of the same things and vastly cheaper.

MiMo 2.5 Pro and Kimi are also very good. And then there’s Cerebras API if you just want simple things done quick.

Oh, both! Yeah. I didn’t even think of that, but [AIT]/[AIP] as separate tags makes sense.

I guess two tags runs the risk of “overcomplicated rules,” but that’s more of a moderation load question. I got no say in that, heh.

For what it’s worth, I asked my self-hosted LLM (MiMo 2.5), and it came with [AIT] (AI-Topic). Not bad.

I’m not consistent about it yet, but because of exactly this, I’m trying to differentiate the two when I talk.

Responsible automation? I use ML or machine learning.

The grift consuming the world? A Tech Bro? “AI”

I think one of the saddest things is the conflation between the two, like you can’t even talk about one without invoking the other.

Yeah. Just not sure what it should be, heh.

I will say, if it still has “AI” in the tag (like [LAI] or whatever), it would play nicer with keyword filters.

TBD indeed. But it will effectively ‘downrank’ posts and their visibility. I’ve seen highly negative scores across the board in more machine-learning focused subs, and that’s without a tag that catches the eye so easily.

Also:

Anything with an [AI] tag in the title will have a drive-by downvote issue.

Not sure how to deal with that, or if its even a concern.

There already are.

I’d argue that Lemmy and piefed need a “sub community” or community taxonomy strucutre, but that’s kinda out of scope here.

+1

Home-AI oriented channels like Reddit’s localllama are filled with self promotion garbage, and it will trickle here over time. I’m not even against self promo or heavy coding assistance, but 4 out of five times the linked repo is nonsense, or straight-up fraudulent. And being obviously vibe-coded is a common tell.

Good to get ahead of this.

Also, +1 on driveby insults. If the post is tagged up front, there’s really no need. That bieng said, it should be okay for users to call out an obviously a grift, or a “nonsense repo” that’s actually pure slop.

Poland remembers.

The moment the Ukraine invasion happened, they weren’t waffling like the rest of the world, they were:

Image

Are they?

They seem to accept credit cards. And: www.usatoday.com/story/money/2025/…/77932811007/

I’ve heard of the payment processors trying to dictate what isn’t and isn’t allowed on OF, which is of course scummy. But I really think they’re having their cake and eating it here.

Yeah, fuck the payment processors.

They don’t bat an eye at OnlyFans but turn their nose up to smaller fish like Patreon? They have NO leg to stand on.