HN user
That is not a rare threat model. Many people use iPhones and Windows computers. Fortunately, Apple has released iCloud Passwords which lets you access passwords and passkeys from a Windows computer.
That is what they actually deployed. They were planning on performing client-side scanning of all images uploaded to iCloud for CSAM and reporting it to the authorities, but backpedaled after public push-back.
A spouse that marries a homeowner, for example. It would be "better" if they broke up and owned their own separate homes.
No, if you look at the first example explaining how the two metrics are calculated, it is clear that both spouses are considered homeowners for HPOP.
Both Firefox containers and multi-account container extention described in that link have been around for years. Nothing in that page describes what is new/changed in Firefox 153.
I don't think the font can actually do that - I think it is a hand-crafted example of the idea. The later examples all have random letters for the decoy text.
It wasn't option for the first 20 years of SQLite's existence.
Yes, BSD licenses are compatible with AGPL meaning BSD licensed code can be combined with AGPL licensed code while complying with both licenses. However, it does not give you permission to relicense the BSD code (or derivative works) as AGPL. The author is free to license any new code they write as AGPL, however the license for the machine translated code is another question. If it is considered a derivative work (which I think it should be) then it must remain under the Postgres license.
If it is not a derivative work, then for copyright to apply at all then it must be an "original work" which has "at least a modicum" of creativity applied by malisper in the translation. If this is satisfied then malisper could choose any license for the translated code they want, compatible with Postgres or not. If it isn't satisfied then no license applies, because it isn't eligible for copyright - essentially it is public domain.
The safe and polite thing to do is to keep the same license when performing machine translation.
I think you are saying the same thing as benced - just because Zig source code is verbose is no reason to assume the binary should be larger.
About 250k devices were getting GrapheneOS security updates two years ago[1], so it is approaching the number of official (and opt-in reported) installs of LineageOS.
[1]https://discuss.grapheneos.org/d/12281-how-many-grapheneos-u...
Wow LineageOS really is a bazaar, and not a cathedral.
* 74% of installs are unofficial builds, not ones released by LineageOS.
* 2/3 of US installs are on non-phones (waydroid, nintendo switch, rpi, etc)
* Most of the installs on actual phones are in China, Brazil and Vietnam
* Less than 21% of installs are on versions that receive security updates, and less than 9% of installs are on the latest version (mostly because device's binary blobs don't support newer android versions?)
The relationship was different. When Id licensed an engine, they threw the code over the fence, and games that used it often heavily modified the engine for their purpose. In contrast Epic put a ton of effort into making the UT engine a polished development tool for creating games.
That is neglecting network effects. Less than 10% of the US population is vegetarian, but if a restaurant doesn't have any vegetarian options they lose business not just from that 10% but from any party that has a single vegetarian. Likewise, if a website has any social network effect, disregarding a portion of the population will decrease use from a much larger percentage than those directly affected.
Furthermore, even if your site functionality has no social networking component itself, all business are subject to the network effects of word of mouth. People are much more likely to share negative experiences that positive ones, so if 1/50 of people find your site to be broken, then a considerable amount of feedback online will be negative and will harm your reputation for the entire market, not just that 2%.
Finally, in business you have to work hard to win over even a small portion of your total addressable market. Artificially decreasing your TAM can be fine if it is an intentional strategic decision to focus on a specific market, but pointless to exclude people without good reason. Not having vegetarian options at BBQ restaurant in Texas is harmless - no one goes there for that, but if you are running a more general restaurant it would be foolish not to have a few vegetarian options. Excluding people because your web developers are too lazy to use approaches that have worked fine for the last 20 years and need to use the new shiny is even more foolish.
What is frustrating is that even when you buy physical games, often what you get is a buggy beta release of the software that isn't playable without GBs of day-one patches. I have little confidence that 20 years from now I will be able to play console games I bought today, without resorting to "pirating" and console mods or emulators. I'm pretty sure that the Switch will be my last console because of this.
At least with PC I have the actual files for the game I am playing, and can backup and mod them as I wish.
Yeah, that seems grossly unrealistic. They are growing. Neutron is almost complete, and I'd expect significant growth in their launch revenue from that, and their space services are also doing well. So I could easily see their revenue increasing 5x over the next 5 years, maybe 10x. But that market cap can only be justified by the space market as a whole growing 100x, and RL maintaining a significant portion of it with strong competition from SpaceX, Blue Origin, and others.
I think they mean that rather than have the RGBI splitter hardware, have a full-signal splitter that displays the same full color image on each monitor, then put a color filter sheet on each monitor to only pass a specific color.
It would have the benefit of working with NTSC, PAL, composite, and other output signals that don't breakout RGBI components on separate pins. But it would have the downside of only supporting 3 monitors instead of 4 (can't color filter on intensity). And of course each monitor would look red, green, or blue according to their filter.
On my Roku the ads aren't just off to the side. When I go to the home screen there are now "recommended" shows above and below my channels, and they are initially selected, so I have to scroll down past them to get to my actual channels.
The existence of loyalty clubs are fine. If you use the service a lot, then it is a better deal, and the company gets the benefit that you are more likely to consolidate your spending with them rather than shop around. Win-win.
It is the fact that you can't do anything without them being pushed down your throat that is infuriating. Every interaction with a company these days is an attempt to up-sell. When a small number of retail stores started that, I stopped doing business with them. Now they all do it.
If you travel a lot for work and would prefer to use Waymo over Uber or renting.
This is not an example of that. It is perfectly within US jurisdiction to prevent US companies from doing business with sanctioned countries. That is the point of a sanction, and US is in good company in choosing to use sanctions as a diplomatic tool.
It is more of an example of how the internet/software industry is too consolidated to the US, and thus other countries are too dependent on the US in those areas. If the internet infrastructure was well distributed, then people in sanction countries could simply get certificates issued by a different CA, and in some cases they can. However, this is complicated by the fact that the list of trusted CAs is dominated by US organizations (Google, Mozilla, Apple, Microsoft). If you want to reach western audience you must use certs from a CA approved by them.
Who says Go's handling of the corner case is incorrect? The original IPv6 RFCs didn't address the case at all. Then in 2013 RFC6874[1] clarified that the % in the zone identifier MUST be percent encoded when used in a URI, just like Go requires. Then in 2025 this RFC was obsoleted by RFC 9844, which only talks about UI behavior and says nothing about URIs, basically reverting things back to the undefined state prior to 2013. What a fucking mess.
It looks like it does, which depending on your goal is either helpful or part of the problem. By default processes should inherit their parent's oom_score_adj. If I exit out of firefox completely, then start it up (with no saved tabs), this is the behavior I see:
$ firefox-esr& PID=$!; choom -p $PID -n 42
[1] 105360
pid 105360's OOM score adjust value changed from 0 to 42
$ for p in $(ps --ppid $PID -opid --no-headers $PID); do printf "%3d" $(</proc/$p/oom_score_adj); ps -opid,comm --no-headers $p; done
0 105360 firefox-esr
0 105425 Socket Process
167 105451 Privileged Cont
0 105456 RDD Process
100 105495 WebExtensions
0 105524 Utility Process
233 105534 Web Content
233 105542 Web Content
233 105549 Web Content
The funding isn't going towards some hypothetical future practical quantum processor, it is going towards existing approaches that we know have different technology, manufacturing processes, and most importantly different applications than the Chips Act was targeting. Funding quantum computing research might be a good thing, but it doesn't make us any less dependent on foreign silicon manufacturing for the countless uses of computer chips across existing industry, which was the purpose of the Chips Act.
And that mindset makes this move even more risky. If people move away from Chrome to DDG, Brave, or Kagi Orion browsers which block tracking by default, then that will harm their ad income even more.
Setting aside the corporation part, is there precedent for allowing people to vote in multiple residences? In my experience, when you register to vote in one location you are no longer allowed to vote where you were previously registered, regardless of how many places you own houses. Some places cross-reference voter registrations to enforce this, and others don't really check, but it has been the rule everywhere I have lived.
Seconded. What Realtors value in a contractor is someone who will respond quickly and do a job that looks good on the surface to avoid delaying closing. For the most part they don't know whether the job was well done and will hold up over time since they are already on to the next house.
Not the same. What email client you chose doesn't fundamentally change how you wrote the email, or require any additional context that people reading the email should keep in mind. AI codegen does. It should be disclosed, and co-authored-by is good convention for doing so.
Syncing is a huge part, UX is another. I was using KeePass on my desktop for several years before I met my wife, and having her use it was a complete failure. She did not like the workflow. Having to open another another tool, login, search for the correct site, and copy/paste the password was too much friction. And that was when things worked.
Syncing was an utter disaster. Inevitably something would cause syncs to be delayed, and then there would be a conflict and one of our changes would be silently lost. We were constantly going to lookup a password we entered, and finding it was not there anymore, at which point I would have to dig through sync conflict backup files and manually reenter the passwords that were lost, or go through the password reset flow for the sites. It was a giant mess, and that was just with two desktops and a laptop. I was using btsync at the time but all the issues I encountered apply to any file based synchronization, like syncthing, nextcloud or dropbox. Performing whole database file synchronization is simply not the right approach for password safe.
I eventually switched over to self-hosted BitWarden with the browser plugin and it has been much smoother.
The encyclical is for the Pope to express the church's view on AI and its impact to society to other Catholics. My guess for why Christopher Olah is there is to signal that Anthropic is the ethical AI company.
For a random blog you have never visited before and have no reason to trust. It could attempt to do all the malicious things that you are worried a man in the middle would do.
The bug reports are helpful! Many Linux developers including Linus, Greg Kroah-Hartman, Andrew Morton, Chris Mason, and Willy Tarreau have all commented positively on all the legitimate problems that are being found with LLM. Here is just one example article[1].
This is just a workflow issue. In the past it was very rare for multiple people to find and report a security vulnerability at once, so it made sense to keep the discussion private until they were ready to release a fix. With AI that is happening all the time, so it makes more sense for the discussion to be in public to avoid duplication. So they changed the policy accordingly. That is it.