Yeah, I remember in the early days, when I installed Spotify it would scan my computer for music and upload everything it found. I imagine this is basically how they bootstrapped
But you can't look it up anonymously. You have to authenticate with your national ID number, and the person will be notified about who looked up their income.
Actually addresses being public are causing issues. Sweden has a lot of problems with gang violence, and gang members often register their public addresses to other peoples addresses, causing innocent people to be killed. The address you enter is in no way being verified beyond it needing to be a valid address.
Yes, you are right - I misremembered this detail. My problem at the the time was I didn't want to commit my flake.nix to the repository in one of my previous work places (for political reasons). So I had to unstage and restage it every time I created a new commit.
My use case here is not using pkgs.fetchgit etc - but rather when developing a package locally and rebuilding it.
Let's say I'm working on a huge monorepo locally, with GBs of code and data in it, most of which I want to ignore in my nix build. Let's say the files I actually care about are also not in a single subfolder. Then I can't just move the flake.nix to that subfolder either.
Building third party flakes takes forever since every flake uses its own version of nixpkgs. If you don't pin your third party flake urls they might also change under your nose as you run the same command again a day later.
Flakes are coupled to git. You need to remember to stage changes whenever you do Ctrl+S in your editor before rebuilding. I've wasted more time than I'd like to admit wondering why what I'm building doesn't include my latest change.
Flakes copy the entire directory into the nix store. This is terrible for mono-repos - and especially if it contains any large files. There is an issue about making the copying of the entire directory into /nix/store lazy - though this doesn't really address the problem. It just treats some common symptoms.
This kind of copying would likely be a lot more acceptable if it was specified explicitly in flake.nix, rather than implicitly. Then you could also use your own filters for ignoring files, rather than relying on the coupling to git and its staging area.
I feel like looking at the first working versions of a big successful project is a great way to understand how it works.
Usually it will only contain the most important core features without a lot of abstractions/generalizations. So it is actually manageable to read through all of the code in a couple of days.