pacman -Ss ollama | wc -l                                                                                                              
  16
  pacman -Ss llama.cpp | wc -l
  0
  pacman -Ss lmstudio | wc -l
  0

> New users were signing up but not doing anything, they weren’t creating an org, a project, or a deployment, they just left an account sitting there.

Surely the LLM version is:

> New users were signing up but not doing anything; they weren't creating an org, a project, or a deployment—they just left an account sitting there.

You also have code comments, docs in the repo, the commit message, the description and comments on the PR, the description and comments on your Issue tracker.

Providing context for a change is a solved problem, and there is relatively mature MCP for all common tooling.

Is there an established name for this LLMism?

I don't need a "Reality Check" or a "Hard Truth". The thought can be concluded without this performative honesty nonsense or the emotive hyperbole.

This probably grates me more than any other.

... 1000 plays in a year?

We're taking a handful of people (Close friends? A proud mother? The artist themselves?) listening a few times a week.

If an artist has no following, and creates music that listeners consider substitutable for AI slop or low-effort shovelware, then they are hobbyists with no reasonable right to renumeration?

Losing free Actions doesn't particularly bother me, and I have no issue with paying what is most likely a negligible amount, but I don't really want to have a credit card on file which could be charged some unbounded amount if somebody gets into my account. I've shut down my personal AWS for similar reasons.

Is there any way of me just loading up a one-time $20? That will probably last well into 2027, and give me the peace of mind that I can just let it run. If my account's compromised, or I misconfigure something that goes wild, I am perfectly happy to write off that amount and have my incredibly-low-stakes toy projects fail to build.

My suspicion is that fairly simple heuristics of age estimation, combined with social graph inspection, are probably enough to completely disrupt the network effects of "social media" for kids, and achieve the stated objectives well enough that I never have to.

Maybe it turns out that I'm wrong, but why even risk it? If the true policy goal is extending mass-surveillance, why waste so much political capital on such a round-about approach which might yield nothing, or even set back your existing capabilities.

MyID (myid.gov.au) already exists, and could easily have been mandated, or "recommended", or even offered as a means of age verification now. But it wasn't.

Could you elaborate further on how preventing a sizeable proportion of its citizens from communicating through these established spy-nets, causing them to disperse out to unpredictable alternatives they might not be able to control, increases mass surveillance?

Aside from YouTube I don't particularly engage with any of these often, but my Google, Facebook, Discord, Twitter, Bluesky, (current) Reddit, Slack, Telegram accounts all seem to be BAU without new requirements.

If the 80% of us currently holding unambiguously-over-16 accounts are exempt, and it only affects future over-16 users as they're onboarded, then it is a very blunt and very slow form of data harvesting which won't yield useful results until years/decades after all of the relevant decision-makers have moved on, retired and/or died. So this seems unlikely?

Set up your preferred self-hosted web interface (OpenWebUI or whatever, I haven't looked into this for a while), point it at ollama, and then configure it in Firefox:

browser.ml.chat.provider = http://localhost:3000/

At home I point this at Kagi Assistant, at work I point it to our internal GenAI platform's chat endpoint.

Two main reasons:

1. This laptop up was set up with flatpak versions of all GUI applications, including Firefox, and the browser plugin just doesn't work. I persisted with the work-around of `pass -c ` from the run command prompt for a while to paste into the browser, but its not ideal.

2. I realised that the Android app was archived. There's at least one fork, but who knows how that will be maintained going forward. https://github.com/android-password-store/Android-Password-S...

For now I'm content with hosting vaultwarden and using various Bitwarden clients.

> Trump has made tariffs a central campaign pledge in order to protect US industry. He has proposed new 10-20% tariffs on most imported foreign goods, and much higher ones on those from China.

I've moved my credentials over from pass to Vaultwarden about a month ago (after discovering the pass Android app was abandoned and pulled off app stores), and spent the last two weeks since discovering Pocket ID migrating a few self-hosted services to OIDC.

When Pebble died I decided that I'd rather less smart and more battery than more smart and less battery, so I got a Withings watch and have been reasonably happy since.

But this looks really good now and I'm happy to support it even if it doesn't win over my wrist space.

Hopefully they sort out Health Connect support on the Pebble Android app by January so that I can at least sync steps between watches if I'm switching between them.

Which ones?

My Alira X from a couple of years ago is currently talking directly to Home Assistant over WiFi. For a year or so I've been unable to update firmware without losing the functionality, but it looks like the community has a fix pending verification: https://github.com/home-assistant/core/issues/99251

I have another old unit that I'll have to replace eventually, and ideally it could be Daikin and would work natively without involving external hardware.

Looking forward to giving this a try.

Work provides me with tooling and requires that I stick to approved AI tools, and my hobby-coding alone is just not important or regular enough to justify a paid subscription.

It's been a little annoying that I can have ollama running locally, enable ollama and configure it in my IDE, but still (seemingly?) not be able to make use of it without activating a paid AI Assistant license.

It makes perfect sense that cloud models would require payment, and that JetBrains would make some margin on that.

But I'm already paying for an IDE whose headline features have recently been so AI-focused, and if I'm also providing the compute, then I should really be able to use those features.

The only viable business model ... while the incumbent (IE, now Chrome) is allowed to give the product away for free in service of some other predatory agenda.