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.
What happens when you need to link a file that does not support comments like that? For example, something which stores its config as plain JSON.
Or how about when you want to symlink an entire directory? For example something like neovim, considering that you may want to split config into separate files for organization. My neovim configuration has an "autoload setup" so any lua files inside the config directory are automatically required.
Lastly, this approach does not appear to support running commands. My dotfile install script ensures that tmux plugins are installed, the terminal font I use is available, and some other stuff that you need to invoke a command or script to achieve.
I like that the approach is simple, but I do not think it can support even relatively common use cases very well.
A long time ago, I used CrashPlan for backups. They had support for Linux, and I had a Linux server at the time that ran ownCloud and some other services that needed backups. I pointed CrashPlan at the appropriate directories and let it roll.
Fast forward several years, I needed to restore something (non-critical) and it was a giant pain in the ass. I was able to get it done, but it wasn't immediately clear that I would be able to. Something about CrashPlan not retaining deleted files and some of my paths changing or something.
Anyway, I was so frustrated by the whole experience that I dumped CrashPlan.
I run Syncthing to provide file sync services. A Raspberry Pi acts as the "central server" on my home network. Once a night, an EC2 instance launches, syncs the data up, and then performs an offline backup to S3. I get a report e-mailed to me every night so I can keep tabs on stuff.
I did have to spend time building it out, but it costs something like $5 per month and it's been bulletproof.
Lots of love for Syncthing over here. It's been a champ.
I mean, sure. If you have the capability and the inclination, go for it. I live in a house that is quite large and I can't come close to fully populating a 24 port switch in a useful way.
I would not detract from your network going the extra mile. I suspect that for most people, the value-to-effort ratio of link aggregation just isn't there in a residential setting.
Maybe you and I have different opinions of "enthusiast" in this context. There is really only so much you're going to do on a home network. You set it up and once it's going, it requires very little maintenance. I would not consider running my own network gear a "hobby" any more than I would consider restaining my deck a "hobby". It's largely a one-time project.
I do have requirements beyond what the typical consumer does of their network, like PoE to run a couple of access points, PPPoE so that I can put my modem in bridge mode, the desire to configure extra DNS records, dynamic DNS since my home IP changes. Oh, and let's not forget some filtering/rewriting capabilities so that I can force modern smart TVs to respect the DNS server I provide them.
My network is much more usable having put the time into it. Yes, you could buy some off the shelf thing and get an OK experience, but that wasn't good enough for me.
Garbage was a bit of an indulgent word. It certainly is relevant and useful technology. It just isn't useful for home users, at least none that I've ever met.
Dark matter is a great example.
Our understanding of gravitation didn't cleanly apply at ultra-large scales so we had to add a massive fudge factor.
You can't "go faster" than the speed of light, but space in between things can expand faster than the speed of light.
It seems like things that are "settled" regularly get an "ope, but except for this special case..." treatment.