Try mixing 1 tbsp cocoa powder, 1 tbsp brown sugar, and 1 tbsp of peanut butter into 1/2 cup oats + 1 cup milk. Tastes like an energy bar.

If you just pulled the default version of qwen3.5 from ollama’s repo you downloaded a mediocre one that only uses ~6GB.

Check ollama show qwen3.5 and see if you get something like this in the result:

  Model
    architecture        qwen35    
    parameters          9.7B      
    context length      262144    
    embedding length    4096      
    quantization        Q4_K_M 

This is the default version I got when I first tried using ollama without any experience. It worked, but it’s a heavily quantized, lower parameter version of the model – i.e. it’s pretty dumb – compared to what you can actually run on your hardware.

I started running LLMs a couple months ago on my own hardware. I have a Framework Desktop that I ordered last year and also recently picked up a refurbished 24GB AMD RX 7900 XTX which I’m doing some performance testing against. The dGPU is much better for dense models, and slightly faster for MoE if I’m willing to run them at a lower quant – but uses more power and has annoying coil whine. The Framework Desktop uses ~100W under load, is quieter, and for the MoE models already runs them fast enough for most of my needs – so most of my LLM use happens on that system still.

For software: I’m using ollama on the Framework currently, but I want to replace it with just using llama.cpp directly eventually. I’ve been using llama-cli for testing the dGPU. I wrote my own chat client to interact with ollama as well as a few other programs for specific tasks.

I’ve been using the LLMs for a mix of research (both personal and professional), entertainment, practical coding tasks (mostly debugging and brainstorming, plus a bit of UI prototyping, automatic generation of sequence diagrams for documentation, and light scripting), as well as automation of tedious tasks.

As an example of the latter, people often send me requests to prepare data sets by email but don’t specify the sources they want precisely so I have to go match the name against the real name in our archives; LLMs are great for mapping the imperfect name – with typos, missing prefixes, incorrect addition of spaces, addition/removal of hyphens, etc. – to the exact name I actually need to pull the data off disk when given a lookup table to compare against.

As far as models go, I’m mostly using various Qwen 3.6 and Gemma4 variants. I have multiple versions of each for different purposes. llmfan46’s uncensored Qwen 3.6 35B-A3B @ Q6_K (from Hugging Face) is my default model currently.

Huh. I hadn’t heard of that before. I do know that keeping it in the fridge overnight changes the texture though (which can make it better for some dishes like fried rice and worse for others). Thanks for the tip!

Looking back through your history, that’s a post by a user local to your instance. You can see it because you’re on the same instance.

If I understand how federation works correctly, posts don’t go directly to the instance a community is on when they are made. They are created locally on your own instance, and then federate out if/when they can. Since you’re both on the same instance, you can see the post and interact with it, but the post and your comments are (presumably) stuck in a queue trying to federate to the now defunct instance. Since lemm.ee is gone, it can’t federate out, so other people don’t see the post/comment on their instance.

I think that’s what’s going on.

BlueSky uses AT Protocol which is similar to how you break things down: https://en.wikipedia.org/wiki/AT_Protocol

Should be trivial to set up something like that if you’ve got parts you want to work with. Any desktop with an automatic background switcher should be able to cycle through images in a directory you specify on a timer. Set up your favorite remote access software (SSH, Samba, NFS …) and you’re done. If you want more control over the behavior, you could script up something custom with a little more effort – but it’s still not particularly hard to implement something like that.

Watch out for burn in on the screen if you’re leaving it on all the time.

Instances go down a lot – often permanently. e.g. kbin.social, lemm.ee, etc.

When an instance goes down, it takes out all the user accounts and communities on it, and it’s hit or miss if you can find copies of the posts on other instances.

By “legacy” they probably mean that they work with the older process technologies, not that the fab itself is old:

The acquisition includes an existing 300 mm fab cleanroom of 300,000 square feet and will further position Micron to address growing global demand for memory solutions

In its May 2024 ’Hooray, we’re open!’ announcement, PSMC said it invested more than NT$300 billion (US$9.5 billion) on the facility, and that it had capacity to produce 50,000 12-inch wafers per month under 55, 40 and 28 nanometer technology nodes.

Those kinds of chips are still very useful for things like cars and washing machines and such where you don’t need bleeding edge chip tech.

I haven’t tried Nostr, so have no opinions on what the experience of actually using it is like, but cryptographic identity seems like it’d be a better way (technically speaking) of doing things than AP; tying everything to domain names has worked rather poorly – as we’ve seen repeatedly every time an instance goes offline…

I ended up on AP after jumping ship from reddit. I was on kbin first (since it was readable w/o JS and I liked the UI), and then later using the mlmym interface for lemmy as kbin because more unstable and eventually went offline.

reddthat is an instance hosted in Australia; so the answer to “how will the ban affect it” is “we already have an age limit in place”. That’s my point.

We discussed it in the community posts back in Dec 2024 when the law passed – February is when the sign up change happened and March was when the announcement went up. The UK’s bullshit may be what prompted the announcement happening then though.

On reddthat, we got this notice in an announcement back in March 2025:

Age Restriction

Effective immediately everyone on Reddthat needs to be 18 years old and futher interaction on the platform confirms you are over the age of 18 and agree with these terms.

If you are under the age of 18 you will need to delete your account under Settings

This has also been outlined in our signup form that has been updated around the start of February.

Wow, I didn’t realize. How time flies. 😲️

Thank you!

The fifth instance denied my application with, “read the coc and reapply”

Don’t know what instance that is specifically, but if their application process is anything like reddthat’s lemmy application process, there’s probably a bit in there about something specific you’re supposed to include in the application so they can weed out bots.

This won’t fix parents just buying a device to palm off to their kids, because if setting up parental controls is beyond them, setting up an account for them properly likely will be too.

Sure, but this limits companies liability if they make a good faith effort to comply; idiot parents being idiots and not setting up a kid’s account are no longer their problem, legally speaking, if they follow this law and respect age signals.

It’s already happening. California passed a law to require OS vendors and online services to support this functionality last month.

How is device-based age verification different?

You put your device in child safety mode, and it tells sites “I’m a kid, treat me like a kid” – otherwise the site can assume you’re an adult with full rights. Done. No intrusive ID requirements. No face scanning. No third-party payment shakedowns. Parents, in theory, can still stop their five year olds from accidentally accessing PornHub or other content that would disturb them by just clicking a button when they set up an account on the device.

It’s, frankly, the sane way to do this if we’re going to have age restrictions.

It looks like the connector is U.2 so I’d look for motherboards that indicate support for that explicitly. From a quick search, it looks like SuperMicro makes some. This is getting out of my area of expertise though; I just know the crazy drives exist…