Hacker Newsnew | past | comments | ask | show | jobs | submit | pylua's commentslogin

The correct name depends on your context. I know it’s unpopular but it’s true.

True!

And the correct name in all contexts that matter is "Lake Ontario".

It's almost as if people don't know that "Ontario" is not a Canadian name, it's a native American one, and the province is named after the lake, not the other way around.

It was called "Lake Ontario" before Canada or the US even existed.


I completely understand and respect that , but the reality is that the U.S. governments opinion matters, even if you don’t like the leadership.

One thing that does seem to be incorrect is that Google has a single name on the lake - Lake America, when surely that only applies to the American half. The US-Canadian border runs down the middle of the lake, so unless I'm missing something Trump's renaming only applies to the American half, and the correct way for Google to show it would be with different names for each half of the lake.

That's ridiculous! How do you rename half of a lake!

I say that there are two lakes. It remains for future generations to decide how the two lakes are apportioned. Perhaps each of them are coterminous, with the same boundaries, size and volume, but one is named "Lake America" and one is not. One is a lake in US waters, and the other is in some foreign country.

Perhaps of the two lakes, they are split in twain, and there is an international border running through the middle of these two distinct bodies of water. Perhaps vessels will littorally obtain right of passage in international waters, and undergo customs inspections before they can cross over the somewhat amorphous border between Lake Ontario and Lake America, and vice versa.


That's not really how local naming works. I call Germany Germany but the Germans call it Deutschland. There's not two Germany's, there's just one and I have a different name for it. It really doesn't matter if a geographic object is completely inside, partially inside, or completely outside a country's borders, they have an official or de facto name for it that could differ from what you call it.

1) Whoooooosh!

2) You really had to choose that country? https://en.wikipedia.org/wiki/East_Germany


If Google maps, or anyone else, is just going to label things in other countries according to the whims of Trump, then where does it end?

If Trump tells Google, and spends taxpayer money, to "officially rename" Ottawa itself "Poopietown", then should they do it?

Maybe we need a constitutional amendment to remove the president's power over place names, given that the founding fathers only considered a malevolent president, not one with the brain of a 5 year old.


You joke, but of course that is exactly the direction we're heading in, where a previously friendly border, both on land and in the water, becomes a hostile one where full border formalities do apply.

I remember years ago driving across the border at Niagara Falls, and just being waved though, no passport required, when I said I was just on a day trip.


It gets it wrong a lot and is automated. How would you feel about being falsely accused or misunderstood ?

Also, it lays the groundwork to absolutely crush dissent in the future .


The software industry should be ashamed by the number of exploits that ai can find in software. It’s really an embarrassment.

The software has to be built better.


I'm curious if you are a coder and have used an LLM to review your code. It is like something like shining a black light around a hotel room, and that seems to be the case even for highly regarded software.

It is really easy to have tunnel vision while coding. LLMs have a working memory with a capacity an order of magnitude greater than ours. I wouldn't trust an LLM to write the code, but at this point it is malpractice not to use one for review.


I have been, yes. For a field that has engineering in the name there sure has been a lot of critical mistakes.

You have to call a spade a spade — the profession accepts this sort of tradeoff in the name of speed and cost.

A well designed system would have never allowed those mistakes to occur. I feel like using an llm to catch these sorts of things is just because it wasn’t built right in the first place.

I think ai systems will be able to build systems of abstraction that are formally verified, and we won’t be needed(eventually).

Right now it’s being used as a bandaid.


Formally verified against what spec?


The one liner leadership keeps asking for.


Every single software engineer in the industry agrees with you.

Every single project manager disagrees.

Don't blame the engineers, we were specifically instructed and paid to build things fast and cheap, and every time we argued for good we were shouted down.


True. It has been a race to the bottom for lowest cost as long as the quality meets the bare minimum. LLMs can go through and find all the nails sticking out pretty easily.


At the end of the day it hurts U.S. consumers to not have Chinese cars mainstream in the market. We lose out on features and stagnate on innovation because we are not pushed to compete.

I can’t imagine this would be any different — banning open weight models would hurt us in the long run. The point is to beat the competition, not suppress it.

There should be no limits on open or custom models. Too often safety is a synonym for surveillance and control. It’s a natural consequence, intended or not.

I am curious… why can’t distillation be stopped?

As a side not Im not against protectionism, but it has to be across the board and the same in all industries with no excrptions. We’ve let all these industries die on the vine due to cheap cost in foreign countries. It could very well happen to ai.


This is the real answer to the op.

It’s incredible how overblown these sorts of things can become


If the customer can run the scanner and find the vuln, that means they can log in, right? Which means they can RCE.


Not always, it can be run at static code analysis or the container repository (not the prod one)?


Yes— they spy on every pic and text upload. They literally are big brother.


I uploaded a picture to Google Maps once. They told me they needed to access my photos to be able to upload the picture.

A week later I get a notification “hey do you want to upload this photograph of a restaurant you took at location x?”. So Google Maps was busy rifling through my photos while I was going about my day-to-day business.

Creepy, gross and repulsive.


GrapheneOS has storage scopes which make the app think it has full folder/file access but in reality you can choose the exact files or folders to give access. It helps keep invasive apps in line.


So does iOS. That's why this caught me by surprise. Does Android not have this built in?


On iOS, it tells the app you only gave it limited access, and that causes some apps to badger you for full access or refuse to work without full access.


On iOS, there's the picker for access. It doesnt trick the app into thinking it has full access. All apps should just be forced to use the private picker style which is convenient and private.

This feature is to make privacy-invasive apps, that want to snoop and degrade functionality if they don't, behave.


Yes, they scan your photos and text and look for reasons to report you to a government agency. They can completely misinterpret or fabricate what you have with no real controls other than good faith.

For somethings I think they are legally obligated to do this. It is creepy.


You mean mortars ?


Does anyone know why we write code anymore? Why not pass through to an llm that generates the page on the fly (ssr)?

Is it cost ?


Yes: cost, speed, and reliability.

But all of those things are improving at shocking speeds, so I think we’re on a path where code is losing value quickly.


Yeah, I agree. It will be like serverless but for code : codeless.

It’s a disconcerting future.


Why disconcerting?


Seems like the reshaping of an industry and is disconcerting for those of us who work in it.


Just post to the database then asynch send to message queue. Messages should still be idempotent by the consumer but at least this follows rest and is transactional.

It’s simple and easy to follow. At scale use multi tenancy.


Every time I send a work email I leak my pii. We should all use government issued uuids on linked in / facebook.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: