Where in the US do you find it's difficult for people to get an ID? Where is it not? What percentage of the population has an ID in a place where it's difficult to get one vs somewhere it is easier?

What constitutes an ID being expensive?

Nearly every country in the world requires proof of citizenship to vote. How is the rest of the world dealing with this problem? Do you think that their democratic processes might be compromised because of it?

I am talking about American support for a working legal immigration process, and enforcing that process. Not everyone agrees about exactly what it should look like.

I'm not talking specifically about the actions Trump is taking or the job ICE is doing currently. The current sentiment around ICE is very negative.

That's been happening for a long time in the US. Staggering military industrial complex. Tens of billions lost in COVID relief. Billions lost in Minnesota due to unchecked privatized social welfare fraud (which has been known about for a decade).

Some mistakes will happen. What we have is unacceptable. If the government can't handle the money responsibly, it has no business collecting the money.

If people immigrate to America, the arrangement should be mutually beneficial.

We are not, and should not be, the self-appointed saviors of the world.

Traefik really is awesome once you can get your head wrapped around the configuration.

I appreciate that you revised the docs, but I still found it quite difficult just to get started. My experience was poor enough that I almost switched to Caddy. The thing that kept me from doing that is that Caddy requires a custom container build for DNS-01 ACME challenges which I didn't particularly want to deal with. I found Caddy's documentation much easier to grapple with, so that could serve as some inspiration.

I have some feedback I'd offer of my own, too:

1. I'd recommend you take a look at the Divio documentation system: https://docs.divio.com/documentation-system/. Your documentation aligns to this vaguely, but I'd recommend reading about the different doc types and applying that feedback throughout the docs.

2. Traefik's tutorial and how-to docs are very dense and feel overwhelming. [1] Related to my first point, I think you're trying to provide too much information in the wrong places. Tutorials and how-to guides should be very focused and limit explanation to only that which is absolutely necessary.

3. Reference and understanding docs are mixed together. I'd recommend using an approach more like Caddy's, where the config reference (https://caddyserver.com/docs/json/) shows prominently what the expected config schema is, and all of the fields are explained briefly. If there is very nuanced behavior for a particular option, consider moving that to a separate reference or explanation page.

4. Having a few How-To guides for the most common patterns which include complete configurations would be helpful.

[1] Here are some concrete examples:

- On https://doc.traefik.io/traefik/setup/kubernetes/, there is a whole introductory session about setting up Kubernetes and I have to scroll before reading anything related to Traefik. It's not only unnecessary -- it's noise. Nobody is going to consult Traefik's docs for setting up Kubernetes, so just omit it.

- https://doc.traefik.io/traefik/setup/kubernetes/ and https://doc.traefik.io/traefik/getting-started/kubernetes/ are different pages which seem to explain mostly the same things. They both include too much irrelevant information, like overly explaining what Helm commands do. Similar to the previous point, it is not the job of Traefik's documentation to explain Helm to me.

Like all genres, games within the roguelike genre (or what some people call "traditional roguelikes") have some variance. But if you played two games in the "traditional roguelike" genre, you'd definitely feel the similarities.

These days if you pick two random games on Steam with the "roguelike" tag, you're going to get two experiences which are not even reminiscent of the other.

I have a repo with some code that generates a credential and writes the credential to a location specified in .gitignore so it isn't picked up by version control.

I used `jj edit` to roll back to a change before the credential path was added to the ignore file to make an unrelated change.

The result? jj instantly started tracking the credential and I didn't notice it before pushing to GitHub.

Fortunately I did figure it out pretty quickly, but that could have gone very poorly.

See also https://github.com/jj-vcs/jj/issues/7237.

I bought one. It lasted less than a year. One day I pulled it out to use it and it just stopped booting. It had been barely used up to that point. No drops or anything like that.

Support was giving me the runaround, too -- by not using info I provided them, not answering direct questions, and asking me to provide info I had already provided.

Do some research on Framework support. You'll find it is atrocious.

The idea is absolutely amazing and I hope it succeeds. The expansion cards are an AMAZING feature. The problem is that the quality bar just isn't being met, yet.

https://pyinfra.com/

You probably just cut all the people out of your life who disagree with you.

That is the liberal way, these days.

Donald Trump, among the worst presidents the US ever had, won the 2024 election. This kind of nonsense was absolutely a factor.

It is 2025. bash is present almost everywhere. If, by chance, your script is run somewhere that doesn't have bash then guess what?

Your POSIX script probably won't work anyway. It will be a different system, with different utilities and conventions.

Line count is not a good reason to choose or avoid bash. Bash is quite reliably the lowest common denominator.

I dare say it is even the best choice when your goal is accomplished by just running a bunch of commands.

All that said, bash is gross. I wish we had something as pervasive that wasn't so yucky.

If a minority were sharing their perspective about whatever their lived experience was with regards to racism, would you respond this way?

I'll answer that: no, you wouldn't.

Which very quickly lifts the curtain. The movement is not about empathy or understanding. It's about empathy and understanding for people you deem worthy of receiving it.

Consoles have historically not done so well with backwards compatibility (at most one generation). I don't do much console gaming but _I think_ that is changing.

There is also something to be said about catalog portability via something like a Steam Deck.

The left moved further left.