Interesting idea but this seems woefully inadequate for password management.
The first thing that came to mind for me: how do you change a single site's password? The article doesn't say. It only mentions that changing the master password would require changing all passwords. That also seems like a complete non-starter.
There is an array of useful functionality that modern password managers provide, too: password sharing, saving select file content securely, password history, storage of security questions and answers, storing username (when you use something atypical for anonymity).
I can't help but feel like this idea is a dud. It's neat in an academic sense but it can't seriously compete with what already exists.
> but also have places where getting to a government office to get such an ID is difficult or expensive
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?
If it's their vehicle and the vehicle wasn't stolen, the owner should know who was driving it. Courts do compel people to testify sometimes (when it is not self-incriminating).
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.
When a significant share of the taxes you pay are mishandled or lost to fraud, yes it is a punishment.
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.
Hi there. I'm a brand new Traefik user. It's bundled with k3s, so I set it up for my homelab on a single node cluster. I'm a technology professional who has worked in infrastructure and software roles for more than 15 years.
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.
No, it wasn't always nebulous. Roguelike was a well-established genre for decades before it got hijacked and now means nothing.
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.
The meaning degraded much earlier than just a couple years ago. People thought it was cool so they latched onto it. It seems like that process started 7-8 years ago, maybe even a bit further back.
I ran into one thing with jj that I would say is pretty bad. I love it other than the way it bit me in this one case.
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.
I would strongly recommend you _don't_ get a Framework.
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.
So many businesses are pushing AI hard. People with varying levels of job (in)security want to be seen as "leading the charge" into a post-AI era.
LLMs can do some really impressive things, don't get me wrong. But I regularly find massive blunders in the code it produces.
And that actually makes sense if you understand how LLMs operate and the quality of software on GitHub.