From my understanding and experience each device you’re logged into gets the hardware survey a few times a year.

The only Maui you should be using is the original https://mauikit.org/

The way I’ve been using it for a few years is that most of my machines can see each other and I have a shared folder and versioning setup. As I add things they move between the different machines and once an additional machine has it it is available to the others until everything is in sync

You can definitely do chain topologies which are useful for certain things with a single source of truth

TIOBE merely measures the number of questions asked about a particular language online, which is obviously not exactly realistic metric but people for some reason love to spout it

As a note, I believe that syncthing will actually scale up with more nodes as they will all share with each other if they know each other. If you’re doing this 1 to many then this is not the case of course.

Seeing as the XLibre fellows upstream commits were reverted because they were absolute dogshit, I don’t think that the fork has legs

Sidenote: I almost ended up working for the company almost a decade ago now lmao. The board was full of other characters we all know and love here. The €€€ offer was high for EU, but I still laugh at the growth potential of my 10000 dollars yearly equivalent in their tokens. The website was unique in that it scrolled… up. I think it’s still on archive dot org

I wonder why his 10000 agents haven’t done the work yet. It seems like such a straightforward plan.

Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below

[Unit]
Description=Loki

[Container]
Image=docker.io/grafana/loki:3.4.1

# Use volume and network defined below
Volume=/mnt/loki-config:/mnt/config
Volume=loki-tmp:/tmp/loki
PublishPort=3100:3100
AutoUpdate=registry

[Service]
Restart=always
TimeoutStartSec=900

[Install]
# Start by default on boot
WantedBy=multi-user.target default.target

You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.

Your ansible script will then call systemctl daemon-reload and then you can systemctl start loki to finish the example

The Kde store UI is a bit lacking the screenshot browser has arrows all the way at the edges.

I uploaded three screens two of the configuration and one of the widget on a panel, expanded with all the advanced controls.

Edit: Ive reuploaded the images with the expanded widget first

During my expirementation with some of these self hosted llms, I was attempting some jailbreaks and other things and thought would this be any good at ERP?

Only if youve never been with another human being.

The fork Ansel, is supposed to improve on the UI situation.

Unironically their greatest movie.

That is some terminal biz brain right there.

Kate has excellent lsp support nowadays as well.

Its a full linux os, so you can do literally anything that can be done with existing tooling. For example, I have syncthing installed on mine so i just have to drop files into a folder on another computer of mine and they show up.

The software folks have put together a decent experience in the last few years and its rather nice out of the box.

deleted by creator

Glad i did not go with these guys when i was e-reader shopping, the lack of gpl sources was enough for me.

Went with a pinenote because the timing was good, and while it has some corners I dont except the debian install to become a ccp mouthpiece 🙃

Pretty solid gameplay so far, threw a tenner at them for the work

Stack overflow now with the sponsored crypto blogspam Joining forces: How Web2 and Web3 developers can build together

I really love the byline here. “Kindest view of one another”. Seething rage at the bullshittery these “web3” fuckheads keep producing certainly isn’t kind for sure.