IMO, yes. I think it would make people more, rather than less, inclined to comment on a cross-post made in a smaller communities, since then their comment would be more visible.

The main concern I can see being raised is potentially leading to brigading? I’m not sure if that’s much of an issue on Lemmy and I would assume being able to de-federate would mitigate that substantially.

I believe you set env vars on Windows through System Properties -> Advanced -> Environment Variables.

I believe you just need to set the env var OLLAMA_HOST to 0.0.0.0:11434 and then restart Ollama.

What OS is your server running? Do you have an Android phone or an iPhone?

In either case all you likely need to do is expose the port and then access your server by IP on that port with an appropriate client.

In Ollama you can expose the port to your local network by changing the bind address from 127.0.0.1 to 0.0.0.0

Regarding clients: on iOS you can use Enchanted or Apollo to connect to Ollama.

On Android there are likely comparable apps.

I hear more complaints about Windows from Windows users than from people who solely or primarily use other OSes. Unless you count “Okay… so why don’t you do something about it?” as a complaint, that is.

I think that makes you “the guy who really likes to talk about Linux.”

From https://wiki.servarr.com/

Welcome to the consolidated wiki for Lidarr, Prowlarr, Radarr, Readarr, Sonarr, and Whisparr. Collectively they are referred to as “*Arr”, “*Arrs”, “Starr”, or “Starrs”. They are designed to automatically grab, sort, organize, and monitor your Music, Movie, E-Book, or TV Show collections for Lidarr, Radarr, Readarr, Sonarr, and Whisparr; and to manage your indexers and keep them in sync with the aforementioned apps for Prowlarr.

See also https://wiki.ravianand.me/home-server/apps/servarr

Servarr is the name for the ecosystem of apps that help you run and automate your own home media server. This includes fetching movie and TV show releases, books and music management, indexer and UseNet/Torrent managers and downloaders.

The original Switch was constantly sold out. I assume there were supply issues. It’s likely that it would have outsold the Switch 2 if they’d had the same supply.

I’m a professional software engineer and I’ve been in the industry since before Kubernetes was first released, and I still found it overwhelming when I had to use it professionally.

I also can’t think of an instance when someone self-hosting would need it. Why did you end up looking into it?

I use Docker Compose for dozens of applications that range in complexity from “just run this service, expose it via my reverse proxy, and add my authentication middleware” to “in this stack, run this service with my custom configuration, a custom service I wrote myself or forked, and another service that I wrote a Dockerfile for; make this service accessible to this other service, but not to the reverse proxy; expose these endpoints to the auth middleware and for these endpoints, allow bypassing of the auth middleware if an API key is supplied.” And I could do much more complicated things with Docker if I needed to, so even for self-hosters with more complex use cases than mine, I question whether Kubernetes is the right fit.

You can store passkeys in (and use them from) a password manager instead of the OS’s secret vault. I think most major password managers support this now - Bitwarden definitely does.

Can’t Keepass also generate TOTPs?

Proton doesn’t know that your password is 64 characters long because the hash will be the same length regardless. They also don’t know if you’ve reused your password on other sites.

Do you have two factor authentication set up? A lot of sites - Proton included - institute stricter security measures if you do not have 2FA enabled.

You have it backwards.

• Day 2 Purchase
• Day 1 “Theft”

Chronologically, the “theft” comes first. And you can easily purchase something you previously stole.

Theft is in scare quotes because piracy isn’t theft and I’m assuming OP isn’t going to actually steal someone’s Steam Deck, Switch, or Switch game cartridge… but maybe I’m wrong.

(Also you could “steal” it after purchasing it by buying on one platform and pirating it on another, but that’s a separate matter.)

Just be aware that you need a 2230 M.2, not the much more common 2280 size.

I’m not a lawyer, but I believe that if the Lemmy instance’s ToS indicates where disputes will be resolved, and either the site owner resides there or is an LLC that is registered there, that you could sue Meta in that location.

Meta is big enough that they are most likely conducting business there (even if digitally) and you could also show that the harm suffered was suffered there.

By chance did you make her unintentional malapropism a canon part of the history of the company’s name? Like Google’s backstory (it may be an urban legend, but I heard they’d intended to name it “googol” but didn’t know how to spell the word, and misspelled it as “Google” when submitting their application).

Strange, I suddenly want to have an Italian-inspired, high class restaurant in my game called “Bone Apple Tea”

Claiming that GTA is responsible for mass shootings is an example of what pro-gun activists do in order to deflect the blame off of guns.

In fact, Redot has had 13 releases since the project started late last year.

With an absolutely massive number of commits since then.

An absolutely massive number of commits that were originally made to Godot, sure. Redot has 118 more commits than Godot as of the time of this writing (76,344 vs 76,266). That’s not even 1 original commit per day.

I genuinely don’t understand why people here are taking it so hard that I wish the Immich devs were using semver.

Because you didn’t say that; you said “Breaking changes in a point release? Not cool” and later “I’m basing this off the guidelines at semver.org.”

I’m paraphrasing your comments from memory, to be clear, so apologies if I misquoted you.

It certainly felt to me like you were assuming that this project was using semver and was not following it well, not that you wouldn’t want to use a project that receives this many breaking changes / that doesn’t follow semver. Those complaints both make a lot more sense to me - and I’ve seen many people say similar things about Immich in the past. In fact, it’s a big part of why I haven’t migrated from Photoprism to Immich myself - in this regard they’re complete opposites.

I don’t think there’s any room to argue that announcing a 1.x with a change the developers say is a breaking change, which is what Immich have done, fits within the semver.org guidelines.

That wasn’t the argument.

Following semver is optional. If a project doesn’t explicitly state it is following semver, it shouldn’t be assumed that it is. With regard to Immich in particular, a cursory review of their documentation makes it clear that they are not following semver. Literally, go to https://immich.app/ and read the text at the very top of the page:

⚠️ The project is under very active development. Expect bugs and changes.

Go to the repo and you’ll see the README, which states at the very top:

• ⚠️ The project is under very activedevelopment.
• ⚠️ Expect bugs and breaking changes.

If you can read that, see that they’re on major version 1 with a minor version over 100, and you still think they’re using semver, then that’s on you.

The devs have stated they won’t be using semver until they consider Immich production ready, and that moving to a 1.x version from 0.x was a mistake made some time ago. If you want to think about it as though it is semver, consider the major version to still be 0. See https://github.com/immich-app/immich/discussions/5086#discussioncomment-7593227 for example.

As this project is clearly not following semver, the semver guidelines aren’t applicable and haven’t been violated.

I don’t think there’s any room to argue

Even if semver were applicable, in this case, I would still disagree. The text from semver.org states:

8. Major version X (X.y.z | X > 0) MUST be incremented if any backward incompatible changes are introduced to the public API.

It doesn’t state that any backward incompatible changes, period, require a major version increase, only changes to the public API. I would personally argue that the deployment configuration is part of the public API, but not all project owners agree with me. Even if they do agree, they might say that this was not a documented deployment configuration and thus not part of the public API, and that it therefore doesn’t necessitate an increase to the major version, but as they knew that people were using that configuration, anyway, they included a note about a potentially breaking change as a courtesy to those users.