Man you should use a chatbot to talk to the other chatbots. AI all the way down

forgot to mention: I’m reporting this ad

Why did people upvote this ad?

Actual technical articles about LLM/diffusion would be interesting to read (I think?)… maybe something like [vibecoding]?

Actually, let’s make that generic and use [futurology], so that it may apply regardless of whether the incumbent revolution/menace is LLMs, low code tools, or stack overflow.

This isn’t a rant about AI.

I feared thus would be about AI, but… this might actually be interesting! I’m glad I started reading.

This time is different […] Previous technology shifts were “learn the new thing, apply existing skills.” AI isn’t that.

Well f*ck you and give me back the time I wasted on that article.

Guys, can we add a rule that all posts that deal with using LLM bots to code must be marked? I am sick of this topic.

There’s also .git/info/exclude, which is a per-repo local (untracked) .gitignore.

You can even add more ignore files via configuration (I don’t recall how).

thumbs.db FTW!

why on earth?

I think I like the idea, but I’m not sure I get what this is… could you share a couple pages?

A NAS is just a computer and TrueNAS is just Linux (ok, TrueNAS CORE is Bsd).

You can run zfs on any machine: they recommend loads of RAM for optimal performance, which you don’t need at home (or at work, unless your job is running a data center).

You can choose from a number of FOSS NAS-specific operating systems, plus all linux distros (since you post here, I’d assume you either can or aim to administer a home sever?)… why would you go with a proprietary OS?

There are several FOSS operating systems for network equipment too (keyword “NOS”), but as far as I’m aware none that work on small soho/edge switches. OpenWrt runs both my router (mikrotik) and WAPs (tplink), but the two 8-port switches I have at home (also tplink) run their proprietary firmware.

Se facciamo una manifestazione per quello, ci vengo pure io. Ma… non mi sembra sia questo il caso se si parla di “tre giorni di proteste contro le olimpiadi invernali”?

I really don’t get your reasoning, but I recommend helix (because I recommend it to everybody).

It’s a pleasure to use, and it’s… also not widespread or old enough to have any reported CVE ;)

Oh, it’s written rust IIRC, so it probably doesn’t suckless.

Don’t tear down your server just to have fun - setup a vm (or get one of those minipcs), call i “playground” and have fun there.

Redo your server after you’ve tried different things, and only if you feel like you found something that is worth it.

Experimenting with different distros can teach you a lot (especially if you try very different ones - mint and debian aren’t that much different) and I do recommend you do it, just don’t do it in production :)

I’d say it’s because:

1. the people who ask for recommendations won’t like (or understand) debian? (it’s just “old packages this” and “outdated that” for most people)
2. the people who do use and appreciate debian don’t read “I hate windows pls recommend me a distro” posts (or at least don’t reply as often as the <insert popular distro> fanboys)

And, no, I don’t use debian myself.

but when I finally switched over to Debian, everything just worked!

That’s most probably because you learned how to use your system without breaking it in the meantime :)

So I’ve been using it for a while! :)

What is the big deal about 4.4.0?

Is this the stable release of the rust rewrite?

Should I just learn how to use Docker?

Since you are not tied to docker yet, I’d recommend going with podman instead.

They are practically the same and most (all?) docker commands work on podman too, but podman is more modern (second generation advantage) and has a better reputation.

As for passing a network interface to a container, it’s doable and IIRC it boils down to changing the namespace on the interface.

Unless you have specific reasons to do that, I’d say it’s much easier to just forward ports from the host to containers the “normal” way.

There’s no limit to how many different IPs you can assign to a host (you don’t need a separate interface for each one) and you can use a given port on different IPs for different things .

For example, I run soft-serve (a git server) as a container. The host has one “management” IP (92.168.10.243) where openssh listens on port 22 and another IP (192.168.10.98) whose port 22 is forwarded to the soft-serve container via podman run [...] -p 192.168.10.98:22:22).

You don’t need to change distro in order to change desktop environment: just install gnome/kde/whatever if you want to give different ones a spin (you don’t need to uninstall your current desktop environment either - you can have multiple ones and choose which one to use when you login)

That just build t8plus becomes nixos-rebuild build --option eval-cache false --flake './nixcfg#t8plus' (the flake is at ./nixcfg/flake.nix).

Is MacOs “absolutely no cli”? It wasn’t when I was using it (admittedly, some 10yrs ago), except maybe for the basic things which any mainstream linux distro also provides.

What about Windows? Back in the day I would have paid to have a semi-decent CLI instead of being forced to use regedit (I hear regedit is still going strong, but I’ve not touched windows for an even longer period than MacOs)

The future is 3.0 quantum AI blockchain .com (also orchestrated application server RAD microservices enterprise edition, but TBH those fads weren’t as bad as the current ones)