I think it would be difficult to find a majority of people who support minors having unrestricted access to pornography and shock content. The sticking point seems to be in the implementation details and true intentions of the people behind the initiatives that gives people pause.
I recently bought age restricted materials online and had to upload a picture of my photo id with a selfie to a 3rd party verifier. Similar to what crypto currency verification goes through.
I think the underlying disagreement/debate is whether or not these initiatives are in good faith. Any implementation of this is going to be imperfect and a motivated person will probably be able to get around this. So the debate, I think, is, if we implement this are we going to incrementally improve it? Or is it just a pretext to point to and say, hey look, this can never work perfectly, so we should ban x, y, and z.
My personal prediction is that llm powered search will be as terrible as google search once people figure out how to game it. In a way probably worse because it will only give one answer instead of a list of answers that you can pick through.
Assuming you’re pretty close to the hardware? As a standard backend web service dev os/library/device bugs are incredibly unlikely and usually defective application software is to blame. Not saying it doesn’t happen, but I can’t recall in recent memory this sort of thing happening as high up in the stack I work.
In addition to this I think picking problems that you don’t immediately know how to solve but is within your wheel house is important. Also sticking with a single problem or domain. Constantly starting and never completing things doesn’t expose you to the next iteration of challenges.
They haven’t included an amortized cost breakdown with depreciation of hardware including backup. Or the geographically local personnel required (data center remote hands or dedicated employee that gets the call?). Even still I suspect it’s still probably cheaper.
Also it looks like these are retail prices. You can get cost savings by negotiating but I’m sure there’s an NDA required.
The technical/organizational details around implementation of this and how it came to be realized would probably also be interesting to a readership as nerdy as hn. I think I’ve seen a few of these posts but can’t seem to remember them.
Or the side project you work on won’t be successful but you can reuse pieces of it for other projects. Code doesn’t stop working just because a product didn’t materialize.
Have they punished the total number of customer deposits? They keep saying they found $x billion in assets. But no mention of the liabilities or the delta between the two.
If he’s not exercising and is largely sedentary then 1400 calories for an adult male is a serious deficit, but not extreme. If he added in an hour of high intensity interval training or something that would be extreme and potentially hazardous.
Definitely had this happen in recent memory. Also the thing to be careful about here from experience is you still need to qa the contractors deliverables. Team had a contractor delivering features and it turns out what was “delivered” many times didn’t actually work. Wasted several months of my engineering time babysitting and validating said contractor. Net result was wasted time and money as we just ended up reimplementing ourselves.