Yeah, I think people will lose their passkeys a lot. I think companies are happy to provide another service ("passkey syncing") that you will pay for for life. Back In The Day you could be a freeloader by remembering your passwords like a nerd. No longer. The loophole is closed!
That said, passwords are actually so bad that anything would be an improvement over them. While a stealable passkey vault sync'd to your malware-infested Windows laptop is not ideal for security, it's sure better than typing your bank password into your favorite forum because you don't understand that website administrators can see your password when you type it on their site. (Not to mention phishing.)
Apple, Google, and Microsoft already do passkey sync for free. They don't do exports, though. However, there are various third party solutions for synching passkeys that aren't tied to your computer manufacturer.
I don't think passkeys are going to replace passwords any time soon, and I don't think freeloaders are even part of the equation here. You can share a passkey through Bitwarden just as easily as you can share a password.
Freeloaders already need to jump through hoops to share passwords and even then they're getting off easy; if streaming companies actually cared about catching freeloaders, they could stop the practice all together. What they're doing now is just signalling them that you're not supposed to and adding very minor annoyances to the mix.
After you set up iCloud for Windows, you can use iCloud Passwords to access your passwords in Google Chrome or Microsoft Edge using a browser extension. You can also manage your passwords in the iCloud Passwords app.
This is a neat feature when it's your own device that you control, but not so great when they "disclose information generated by WiFi Motion to third parties without further notice to you."
I wanted to talk about how responsible WiFi router software authors can make things local-only (and I've done that in the past; no way to get this information even if I wanted it). But this is always temporary when "they" can push an update to your router at any time. One day the software is trustworthy, they next day it's not, via intentional removal of privacy features or by virtue of a dumb bug that you probably should have written a unit test for. Comcast is getting attention for saying they're doing this, but anyone who pushes firmware updates to your WiFi router can do this tomorrow if they feel like it. A strong argument in favor of "maybe I'll just run NixOS on an Orange Pi as my router", because at least you get the final say in what code runs.
A lot of these ARM boards use custom (read: outdated) kernels and proprietary boot methods, so I'm not really sure how applicable they are to people developing Linux distributions that work everywhere. NixOS, for example, is only supporting UEFI booting on ARM64 going forward. If Redhat has the same policy, then there is only a limited set of arm64 boards available. I researched this recently as I'd like to move my k8s cluster from renting expensive cloud machines to running them on cheap machines at home, and the situation is ... difficult. (I have tested the Orange Pi 5 Max and the Radxa Rock 5B+. Both required me to hack edk2-rk3588, but they do work well now that most rk3588 support is merged in Linux 6.15/6.16-rc1. But, this is an old CPU and is just now getting mainline kernel support, and that is always how arm has felt. It is, however, kind of neat to see a "BIOS" on an ARM board. I hope it catches on.)
I'm glad that people are mad about this. I got the ad, went on here to see if 1000 people were complaining, and nobody was. I was kind of surprised.
For me it's like "oh, I didn't know Wallet was an advertising app", I thought it was something I paid for with the purchase of my phone. But I was wrong. It's just adware. "We'll store your boarding pass if you'll let us spam you about movie tickets." Do not want. I disabled notifications. Now a year from now, I'll be searching for some pass in my wallet. Someone will say "don't you get a notification when you get to the venue"? I'll be like "no I've never seen that work". Multiply that by everyone, and suddenly the buzz is "Apple Wallet doesn't work. Trust my money and credit cards with something that doesn't work? No thank you." And now people are buying a Garmin watch for Garmin Pay instead of an Apple Watch for Apple Pay.
Really dumb. Huge mistake. It makes me sad that they don't care about their own brand. "We won the smartphone wars, let's cash in!" Winning is temporary, but losing is forever.
> Now a year from now (…) people are buying a Garmin watch for Garmin Pay instead of an Apple Watch for Apple Pay.
Talk about a slippery slope fallacy. No, that will not happen. At all. There’s a better chance that this year will be the year of Linux on the Desktop.
This kind of exposes how valuable reviews actually are -- likely not very. People like reviews, but some person you don't know using some unknown set of criteria to evaluate a product turns out to not actually offer any value. Taking the mean of this data ("4.5 stars on Goodreads!") also doesn't improve the quality of the data.
I'd disagree. Real, honest reviews are genuinely useful to me as a consumer particularly if the review outlines what type of person the reviewer is, too.
That is the whole point of the review scams - often I'm not an expert and I know it. I need some widget, and there are 10 choices. I want someone independent to review all 10 choices and tell me which is best so I don't waste my money buying a bad one. Lacking someone with the money and time to buy all 10, at least seeing the reviews of someone who has one is a suggestion on if that one is really as good as they say. Though if someone only has one they tend to review it well because nobody wants to admit they bought something that wasn't the best.
If the reviewer is consumer reports they for years were this independent reviews. (I've heard accusations they are no longer as independent - make your own decisions) They often don't know enough about the product to understand why long term the more expensive one might be better as opposed to just overpriced, so not perfect, but still better than buying everything yourself.
they have been doing this for decades. they fund themselves by selling a print magazine and paid online access. their reputation is so good that products that get good test results often use the result in their ads or print it on their packaging.
I don't think there is any desire to find a legitimate buyer. The bill wants to say "throw them into a landfill" but the architects are trying to sound thrifty. Stated reasoning: "Stop wasting the government's money on useless initiatives. Sell these white elephants and ask employees to use their own car!" Actual reasoning: "We need to burn more oil. There are campaign donations on the line and the midterms are going to be very tough for us. Big Electricity does not donate to campaigns and we can't take the money we save on fuel and use it for ads."
I agree with you. The dinosaur game in Chrome is the classic example; turned off because schools threatened to not buy Chromebooks if kids could play a game in the browser. At least it seems to be a setting now, so your individual locality can decide if fun is allowed.
That’s quite different from what we’re talking about though. That’s adding games or fun into your product whereas in this specific sub-thread we’re talking about naming code concepts (functions, classes, variables, enums, etc) funny things.
Not to mention even just this article exposed a just-for-fun API that ended up having a negative effect and had to be removed:
`isUserAGoat` ended up allowing any caller to determine if a specific app is installed on the system, which is a privacy violation and allows fingerprinting against the user's consent.
I get the desire to make the job more fun than just implementing a spec, but many of the things we work on are very important and very complex, with oodles of real-world consequences. That unfortunately means everything we do has to be well-considered and not off-the-cuff.
I think this is pretty well stated. I'll add that while nixpkgs isn't nix, nixpkgs is kind of the good part. I use NixOS and for the first time in my life, I'm using the latest version of the Linux kernel on release day. That's pretty excellent. While I've come to tolerate Debian Stable in my old age, it is always like stepping a few years into the past ;)
The Nix language is something I could criticize for hours without getting bored, but it is what it is. It's old and they did the best they could and it's probably not worth changing. The Nix build system feels awfully primitive to me, often rebuilding stuff that doesn't need to be rebuilt for no good reason. (For example, my NixOS installer ISO has a ton of the build depend on the cmdline I pass to the kernel [just console=ttyS2,1500000n8], and so changing the speed of my serial port requires about 3 minutes of build time. It's goofy and makes me laugh, I'm not going to stop using Nix because of it... but it's also something that I wouldn't let happen in MY build.)
Nix for Docker images is, in my opinion, what it's the worst at. A long time ago, I was writing some software in Go and needed to add the pg_dump binary from Postgres to my container image. The infrastructure team suggested using Nix, which I did, but our images blew up from 50MB of our compressed go binary to 1.5GB of God Knows What. pg_dump is 464K. I ended up doing things my way, with Bazel and rules_debian to install apt packages, and the result (on top of distroless) was much cleaner and more compact. My opinion with some actual Nix experience is that a Nix system always ends up being 1.4GB. My installer ISO is 1.4GB. My freshly installed machine is 1.4GB. That's just how it is, for whatever reason.
Finally, the whole "I would like to build a large C++ project" situation is a well worn path. s/C++/Rust doesn't change anything material. There are build systems that exist to make the library situation more tolerable. They are all as complicated as Nix, but some work much better for this use case. Nix is trying to be a build system for building other people's software, supporting nixpkgs, and lands on the very generic side of things. Build systems that are designed for building your software tend to do better at that job. Personally, I'm happy with Bazel and probably wouldn't use anything else (except "go build" for go-only projects), but there are many, many, many other options. 99% of the time, you should use that instead of Nix (and write a flake so people can install the latest version of Your Thing with home-manager; or maybe I'm just the only person that uses their own software day to day and you don't actually need to do that...)
That's strange, I never had problems building really tiny docker (release) images with nix, in fact it felt easier than doing it with alpine. You just get exactly what you specify, no more.
(OTOH, when developing in nix, I always end up with a huge /nix/store and have no idea how to clean it without garbage collecting everything and having to wait all over)
> I always end up with a huge /nix/store and have no idea how to clean it without garbage collecting everything and having to wait all over
FYI you can avoid things getting garbage-collected by doing `nix-store --add-root`; that makes an "(indirect) garbage collector root"[0]. Especially useful if you're using import-from-derivation, since that imported derivation won't appear in the dependencies of your final build output (which, to be clear, is a good thing; since it lets us calculate a derivation, e.g. by solving dependency constraints or whatever, without affecting the eventual hash if that calculation happens to match a previous one!)
I agree with that. Modern Unix is a 6-of-one-half-dozen-of-another type situation. Yes, terminal emulators and the termcap database are improved. But now, the traditional Unix user might be surprised at how things are done. I have accepted that ... systemd ... manages my networking now (ok, it's networkd or something I guess?). But if you can't accept that, it's good to have some option that just uses ifconfig.
But yeah, if you want fast storage just stick the SSD in your workstation, not on a mini PC hanging off your 2.5Gbps network.
reply