You're "literally surrounded" by cafes built into the first floor of your apartment complex? Because that's what I was very clearly talking about. Not shops within walking distance.
(I didn't ask and don't care if you think your cheap meal's "very delicious," by the way. That's not the main indicator of quality. Many Americans would call a Big Mac "very delicious.")
Where do you live that this is so bizarre? Multi story buildings with retail space on the bottom and residential space at the top are very common in cities.
> I didn't ask and don't care if you think your cheap meal's "very delicious," by the way. That's not the main indicator of quality. Many Americans would call a Big Mac "very delicious."
What’s the point of this? This is just needlessly rude.
> You shouldn’t ignore a problem when you’re in a position to help.
is incompatible with
> not put emotional investment into it
I'll only help because I care (maybe it's the person, the larger goal, etc). To me, everything behind the experience that I call "care" is an emotional one. If I don't care, then that means it doesn't matter to me, which literally means there's no emotional response/motivation to do it. Is this odd?
Even in startups, sometimes you’ve just got to let the consequences of the things you’ve warned about happen.
I’ve lost too much sleep and fought too many battles and lost too much clout over the years trying to make sure bad things didn’t happen. “Nobody could have foreseen this” is still said, even if there’s a ton of evidence, recommendations, pleading, etc, to keep it from happening.
Yeah, I’m sure it happens everywhere. And I’m no expert, I worked in state government, fed R&D, big tech and a startup and I feel like the big tech environment was a lot more of the “I need an audience to make my point” in a big staff or strategy meeting vs the small swarms where we just need to get this thing working environment. But it depends on the startup and depends on the people. I’m sure the same goes for teams in big tech but I assume the politics plays more in survival there.
I’ve tried Spruce Beer before and my brain rejected it for similar reasons - it tasted like house cleaner. If they’ve got anything that has that scent that’s dangerous, I imagine the brain wires similarly :D
They give you a key and only if you have a higher tier account. The act of doing that requires that there is a step in the process where they know you’re requesting a key and who you are. They could bind them in the backend if they wanted, before giving it to you.
You’re still trusting them. Not to mention they could round them all up by IP or browser fingerprinting.
There is still some level of trust.
I happen to trust them enough for that; but it is still trust.
I am not an expert in the underlying cryptography, but the claim is indeed that the cryptographic approach makes it impossible for them to link the key to the queries in the backend.
Sure! But there is a stage where they generate those keys for you and give them to you. You need to be logged in to get that page. That is trust there.
No, issuer-client unlinkability is a feature of the design. The token is finalized by the client using private inputs so Kagi never actually sees the redeemable token (until it's redeemed).
Using the example doc you’re citing from kagi.com - though not the RFC, I don’t have the time to dive into that one at the second, I see that a session token plus some other stuff is passed in and a token comes out.
Where does it show that on the Kagi backend they couldn’t, theoretically, save the session key before performing the token response?
Sure, they probably do. Doesn't matter because neither the session key nor the token response can be linked to the tokens.
If you're not going to make an effort to understand how it works, don't make assertions about how it works. Ask your favorite LLM about the RFC if you have any further questions.
On the contrary, companies building things is *constantly* under scrutiny for local building plans. That’s literally what the NIMBY / YIMBY movements are all about - using political clout and power (especially including voting) to affect what can and cannot be built.
That's not quite correct. There's a lot of NIMBY pressure in cities, where land is scarce and there's lots of people to attend planning meetings to block building.
However, if you want to build a datacenter, you don't need to build it in downtown Manhattan. You can build it anywhere, and some places make it easy to build data centers.
By definition local restrictions apply locally. If you want more housing in Manhattan then Manhattan nimbyism really matters. But if you want to build a data center somewhere you have a lot of options. There's no nationwide vote on allowing datacenter construction.
While that’s true, and there are several locations that are using their local authority to perform those actions; but, *all* of that is power wielded by elected officials. The smaller the location the less “who voted for this” likely means anything because the decisions that are made that impact all of us are made by a smaller and smaller number of people with less and less authority, but it is still voted for.
> Electricity prices near data centers go up, right?
I hear this a lot, but the most comprehensive study I've seen found the opposite -- that retail electricity prices tend to decrease as load (from datacenters and other consumers) increases [1].
The places where electricity prices have increased the most since 2019 (California, Hawaii, and the Northeast) are not places where they're building a lot of new datacenters.
What fixed costs of the grid? In Northern Virginia, we’re constantly adding substations and transmission lines because the grid isn’t a fixed cost when you’re building data centers constantly; it quickly becomes a variable cost.
Sometimes you might need to operate on a result from an external function, or roll back a whole transaction because the last step failed, or the DB could go down midway through.
The theory is good, but stuff happens and it goes out the window sometimes.
Before sealed classes and ultra-robust type checking, sometimes private functions would have, say, 3 states that should be possible, but 3 years later, a new state is added but wasn’t checked because the compiler didn’t stop it because the language didn’t support it at that time.
Thank you for that wording.
reply