

It’s being downvoted with relatively little discourse because it’s an insult with no relevance to the topic, in addition to supporting a comment from someone who is either trolling or has no idea what they’re talking about
I joined Lemmy back in 2020 and have been using it as @qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.


It’s being downvoted with relatively little discourse because it’s an insult with no relevance to the topic, in addition to supporting a comment from someone who is either trolling or has no idea what they’re talking about
Have you tried Tweakers Vraag & Aanbod yet?
It’s not that bad. A lot of our servers at work use Windows. It certainly took some getting used to as someone who has been using Linux on all their devices, but it does work.


It’s a field in the users database on your own device. You can change it yourself. If something stupid like that would happen you could bypass it entirely by just setting the field to something else.

It seems like you’re referring to dotfiles. You can manage these using a git bare repo.

You could use something like Kopia and only include the files you want
Assuming reliability is the priority I would suggest going with Tailscale Funnels or a cheap VPS acting as intermediary.
I don’t have a lot of experience with dealing with GCNAT, but perhaps you could look into some solution with UPnP or RFC 6887.


object_store does indeed also support WebDAV among a variety of other protocols, Apache Druid or Apache Pinot probably would be better examples. My only experience with WebDAV is with Nextcloud and hasn’t been that great because it has been very slow, probably should look into it sometime.
EDIT: Apparently it supports CAS, and even has a locking mechanism


Scaleway, Exoscale, Cyso, Contabo, UpCloud, and others too


Many cloud providers offer S3-compatible storage, so it’s a common protocol to use in applications. There are even some databases like SlateDB that fully rely on object storage for everything. Supporting more API’s is extra work (unless you’re using OpenDAL) so most people pick S3 compatible API’s because they’re the most widely supported across all cloud platforms.


S3 isn’t just an AWS thing anymore. It has kind of become the standard object storage protocol, and almost every cloud provider uses it aside from a few the made their own API’s (e.g. Azure Blob storage)


Many cloud providers offer S3-compatible storage, so it’s a common protocol to use in applications. There are even some databases like SlateDB that fully rely on object storage for everything. Being able to have local S3 compatible storage is useful if you want the storage of your local machine while still doing so over a widely compatible protocol.
I tried that and my account got randomly deleted
There is Cockpit which allows you to manage the server and has simple management for containers. However, I recommend using something like Dockge with compose because it makes it easier to change the configuration of containers without recreating them manually.
And podman runsias user, not as root.
Both Podman and Docker have rootfull and rootless options
I personally use Node-RED for several automations myself. Is it worth switching to n8n?


I think it’s because it’s entirely unmoderated (at least it was the last time I checked) and while they claim that defeats censorship they also realize that having CP everywhere ain’t a good look


Typescript’s string pattern types are quite neat though
Deepseek recently published a paper in which they describe that vision tokens contain more information than text tokens and that this can be used to compress context.
It reminds me of LLM caveman speak, it used to have another option to use Chinese instead of English. A language like Chinese is seemingly better at encoding information in fewer tokens and I think this is the same mechanism why OCR tokens work so well.
That said, I also doubt that voice messages are more efficient than text prompts, but it’s best not to waste too much time engaging with these sorts of LinkedIn posts (and LinkedIn in general).