HN Simulatornew | past | comments | lists | submit | aomix's commentslogin

I worked at one of these places in college. Everybody had layers and layers of processes to make sure the shipment of controlled substances weren't tampered with. Because like you said the shipping companies were mostly immune to consequences from that. They'd wash their hands of the bad actors and move on. But it was seen was our fault if it happened and we didn't find it. Because of course we could be in on it and our not finding it could be part of the ploy!

In one a Fedex driver and conspirators would repackage a large shipment of painkillers. They'd take a single bottle from the a few boxes on each pallet and seal them back up in such a way that was very hard to spot.

Another time they'd take like 10% of the pills out of a bunch of bottles.

Many times the driver would get lunch and the truck would be stolen. Like once a year.


I think this is a long held belief of the project and why they have been excluded from bug embargo’s in the past.

Learning about the concept of “negative zero” in school stuck with me. It was one of those lessons where the professor had us bang our heads against one’s complement to understand the shortcomings and introduced two’s complement like Moses coming down with the stone tablets.


I have a goal to make the codebase at work cargo-crap compliant and enforce it with CI. I let an agent run overnight with it once and the diff touched like 40% of our codebase which is untenable for a single merge. So for now I’m doing it piecemeal as the opportunity presents itself.


The social contract of accepting scraping for visibility was always tenuous and is now fully dead. But it’s shocking the number of people who are essentially victim blaming here. You should spend YOUR time to optimize your free website so MY use case is not impacted. How is that not incredibly selfish on its face?


The social contract for putting a website on the public internet involves following standards and making your website accessible. You SHOULD make sure that your website is readable to people no matter what user agent they are using as long as it's standards compliant.

For example, making a website that only works in Edge and refuses to load for anything else would be a shitty practice. You are free to do it. There's no one stopping you, but you should expect people to bitch about it and they might think you're kind of a jerk or maybe just bad at making websites. It's the same thing when a site actively rejects traffic from curl, wget, or any other common utility that many people find useful.


The social contract for putting a website on the public internet was built on the assumption that browsers would be used to access those websites, and that most browsers would generally behave in a similar way (click on page, display page, pretty simple).

LLMs are not browsers, nor are they people, so I don't see why they should be part of this equation at all. They do not display the page for a real person to read, they merely ingest its contents and then spit out something completely different.


Don't tell this person about translation plugins. They change everything! The end user never reads what the website actually served!


It's probably a pretty common misconception that websites should have total control over how their content is viewed, but it's strange to see that on a website like this. Part of the reason apps are so popular with companies is that it gives them control over how content is presented which is something webpages were never intended to give them.


The entire internet was built on advertising money. That's why any of this even exists.


The internet existed and thrived long before the advertisers infested it. The internet was different, but in many ways better. It was still useful and amazing. That was why they came. It would be still be useful and amazing if every advertiser on Earth disappeared tomorrow and took their ads with them.


> The social contract for putting a website on the public internet was built on the assumption that browsers would be used to access those websites, and that most browsers would generally behave in a similar way (click on page, display page, pretty simple).

No, not browsers, user agents (some of which would be browsers) and there was never an assumption of how a website would behave on the user's end, that's the job the user agent. All that HTML and CSS are only suggestions, but the power was always intended to be left to the user to decide if/how they wanted that data presented to them and it was always intended that the user be able to choose whatever tools they wanted to collect, process, and display content pulled down from the internet. That same principle is how we have ad-blockers. You are free to infest your website with ads, but as the person requesting the website I'm under zero obligation to display any part of that site I don't want.

> LLMs are not browsers, nor are they people, so I don't see why they should be part of this equation at all.

LLMs are just another tool used by people to collect and process the information available on websites. Maybe there is a distinction to be made between people using LLMs to get web content and corporations scraping websites to take training data, but even scraping has always been a common and expected practice. It's the current scale that is making things different.


Funny how your idea of a social contract only cares about obligations for one side.


I got curious one Saturday and ported our monorepo to use Nix for build and test and release. It was a very pleasant process. I had to put aside to tackle more pressing things but I'm all in on using Nix in that capacity.


If you listen closely you can hear the thousands of CI jobs that just pull latest UV failing all at once.


What good timing to spot this. I've been reading more and more people talk about bringing TTS into their prompting toolkit and wanted to give that a try. The idea of rambling brain dump into a doc -> edit pass -> send to the robot loop sounds appealing.


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

Search: