Ostfriesentee

GrapheneOS reigns surpreme. We should all use it. But I am not buying a phone for €2000. Count me out.

Markdown is the code of the LLM world. It works, if you are precise.

For absolute obedience, throw in a §.

§ 1 Speak like a pirate.

You got access to much bigger models than I have! Nice. I use the gondolin sandbox for Pi. It traps it in a minimal Alpine Linux VM with only packages you define and the only directory it can see being the dir you cd’d into.

I think you do have a point. I think the overarching problem with discussions about “AI” is that people rarely refer to the same things when they talk about it and they end up talking past each other. There is a difference between using a custom harness with (a) carefully optimized local LLM(s) and other models you glue on top yourself for other-than-text tasks and using server-side models with a ready-made CLI and UI served to you on a golden platter with all processing being done elsewhere. “You’re gonna get left behind” is not the argument here. If the problem is “the code is too complicated”, that is a style issue that can be mitigated. It’s not set in stone. Sure, there are many problems with LLMs and ML models in terms of where they source their training data from and the environmental impact of data centers. I’ve also had my fair share of literal slop pop out. Some problems are just there and won’t go away (yet), but some problems are a choice, whether you know it or not.

I also think that some people like the idea of being on the designing end rather than just being on the using end. Why stop at skill.md? Why not post-train your model on your own code, style and preferences? I’ve trained a tiny model on a small subset of data I may legally use because it’s… fun. It’s my hobby. I just tinker around with it. The model itself is absolute poop, because it’s super small. But it works. I also locally rebuilt llama.cpp with a TheRock ROCm build for better support for my graphics card and got a very significant performance improvement. It doesn’t even need to be useful in any meaningful way (it often is anyway), as long as I got fun understanding how it works.

“I’ll just start using it one day and be just as good as everyone else because that’s explicitly how they are designing the software to be used, right?”. Yes. You’re still going to need to be capable enough to express what you want with precision, but if you can do that, you’re absolutely right, especially considering future models. But maybe you don’t want to be absolutely dependent on big companies serving you those models.

Get Ponytail https://github.com/DietrichGebert/ponytail and an auto-linter such as pi-lens if you’re using Pi harness. And a goal/to-do (pi-goal-x) extension.

What model are you using?

You’re out-of-date, I fear.

I’m not sure making the tool you’re selling less useful is a smart idea. Hmm, yes liability is an issue. But other models are just gonna allow it anyway, so people will just stop using Claude for that usecase. Reverse engineering won’t stop. Claude will just not be used for it anymore

I am, on my main machine. Even at a DNS level. Can’t quite do the same for my phone. It usually blocks everything but this website wasn’t for some reason.

What is this terrible ad-riddled website? Second time I’m seeing it today.

I’ve become a heavy user of Noctalia and figured these issues out.

I’ve been through these: CachyOS+Hyprland+Noctalia ↓ CachyOS+MangoWM+Noctalia ↓ CachyOS+Umbriel+Noctalia

I honestly recommend Umbriel. It’s a nice mix of Niri and Hyprland and is very customizable. Also better integration with Noctalia.

Anyway: The fixes are the same.

sudo noctalia-greeter passwordless-sync enable “$USER”

For passwordless theme syncing between shell and greeter. My setup also syncs the wallpaper to hyprlock via a Noctalia hook.

If the keyring authorization thing shows up after login with Noctalia greeter, edit /etc/pam.d/greetd to include:

auth optional pam_gnome_keyring.so

in the auth section and

session optional pam_gnome_keyring.so auto_start

in the session section (obviously this requires gnome-keyring).

That should fix all weird pop-ups. Been very happy.

COSMIC I’ll have to check out. But I’ve been so invested in customizing my Noctalia/Umbriel setup it’s going to be hard to switch. I really like my look and feel right now.

A lot of people want local inference, and somehow they assume that the problem is solved now because we have open-source models, we’re going to be able to run them on our computers, and so we’re not going to need all the stuff in the data center.

We’re going to be able to? That’s wrong. We already can. Right now.

https://github.com/Niko1221/Strata https://github.com/ggml-org/llama.cpp https://github.com/earendil-works/pi

There’s going to be use cases for data centers but I don’t think it’s going to be consumer LLM inference.

What can be run locally on mid hardware now couldn’t be run half a year ago. Imagine one year from now.

Newsom, in his veto letter to the legislature, said he was supportive of “protecting sensitive personal information of Californians,” but that a “categorical ban on sharing that information goes a step too far.”

The governor pointed to existing state laws that require businesses to give consumers the option to limit sharing their information and budget constraints that would hinder implementing and enforcing the law.

Newsom also signed a handful of other bills strengthening the state’s privacy rules:

• SB 923 expands the scope of the California Consumer Privacy Act to require businesses to delete all personal information they have on a consumer upon request, not just data collected directly from the consumer. Online-only businesses will be required to provide a webform or portal for deletion requests.

• AB 883 shortens the time with which data brokers must comply with a data deletion request from 45 to 30 days. It requires elected officials and judges receive information on how to access the deletion mechanism, known as DROP, to protect their information.

Other data privacy laws still awaiting Newsom’s signature or veto include:

• SB 690 would remove the private right to action for alleged violations under a wiretapping law, allowing just the state attorney general to pursue such legal challenges.

• AB 2561 would prohibit an operating system or application from re-adjusting a user’s privacy setting without consent.

They say they are about law and order but oftentimes aren’t.

Shoop da whoop, my fren.

It doesn’t do that. My color theme changes dynamically with my background. But even manual changes don’t require that. Did you enable polkit in the control center? Are you running Noctalia 5 or newer?

Only when I want to update my greeter theme alongside everything else, I get polkit requests asking for my password. But I also got noctalia-greeter after having had installed another greeter. So maybe that messed it up. Anyway, you can disable auto theme update for the greeter. Or use a different greeter.

I’m sure there are problems still, but it only just got implemented last month (Noctalia greeter is also super new). I think we can expect fixes. Maybe your particular issue has already been fixed. For some tools I’m using I’m getting daily updates by now, so last month is like ages ago in terms of updates. Not necessarily true for Noctalia, though.

I did like Mint Cinnamon, as well. Pop!_OS I haven’t tried yet. I might hop a little on my second machine. But for now I’m happy with my heavily customized Noctalia setup on my main machine. What else did you find to be messed up?

I can only tell you that I’m using CachyOS (Arch) with Wayland and the latest Noctalia, which is extremely customizable. I’m very content. My compositor is Hyprland, but Niri or Mango work, too. Noctalia even technically works with KDE, which I also used for quite some time, but I wouldn’t recommend using it on top of it. Noctalia (Hyprland) has been a standard installation option in the CachyOS .iso ever since August 2026.