HN user
These are the kinds of interesting engineering challenges that were solved with human ingenuity and grit; I wish we were talking more about them to our youth to inspire imagination about what's possible.
Manipulation and misinformation on Wikipedia have been happening for many years (based on my personal experience trying to correct facts). I'm not referencing politics per se, though political views certainly impact Wikipedia since source material, these days, often has a political bias. I'm talking about business facts that get manipulated for that business's benefits.
How does that saying go? If you can't identify the mark in the room, you're the mark. Diligence and a good amount of skepticism serve you well before AI, and certainly post-AI.
I guess we've come full circle. It was just 20 years ago that my datacenters gutted DC in favor of AC.
This is pretty cool!
What's holding me back from AI repos and agents isn't running it locally though. Its the lack of granular control. I'm not even sure what I want. I certainly don't want to approve every request, but the idea of large amounts of personal data being accessible, unchecked, to an AI is concerning.
I think perhaps an agent that focuses just on security, that learns about your personal preferences, is what might be needed.
I agree with the sentiment of this article.
Sadly, I'm still disagreeing while crypto kiddies are driving past me in lambo's. If its the future of money, yes we'll get there eventually, but like every technology shift, there's a lot of money to be made in the transition, not after. *
* I sold all crypto a few years ago and I'm a happier person :D
The question I keep coming back to regarding the recent debate around age verification is "Why now?"
I'm 47, and I started using the internet in my early teens through BBS gateways. I've seen every age of the Internet, and there's always been widely available pornographic materials. Why all of a sudden is this a crisis?
Perhaps I'm missing something?
SLA’s usually just give you a small credit for the exact period of the incident, which is arymetric to the impact. We always have to negotiate for termination rights for failing to meet SLA standards but, in reality, we never exercise them.
Reality is that in an incident, everyone is focused on fixing issue, not updating status pages; automated checks fail or have false positives often too. :/
Im much more concerned with customer sites being down which indicates are not impacted. They are.. :/
I've been following this report for many years, but Backblaze, as a backup service (traditionally), has very different IO patterns than many users. They originally started with consumer drives, which we found to be far too unreliable. In my experience, the BER and write cycles have a dramatic impact on overall drive performance. The MTBF declines sharply as write cycles increase, both as a percentage of IO and overall IO.
Backblaze changed IO patterns with B2, but that would be the key data for me to make this more useful: failure rate as a percentage of bytes read/written, etc.
This is an interesting topic, but the ads overlaying the content make this very hard to read :(
* Please don't suggest I install an Ad blocker.
In my experience with OFCOM, Child Safety is just the gateway to a vague list bullet points including “terrorism” and “hateful” content (vaguely defined); what could go wrong??
I don’t understand all the FSD “disdain” in these comments. FSD 13+ on HW4 is amazing. I’ve basically stopped driving and it’s a marvel of technology.
It’s hard for me to understand how everyone doesn't geek out about it all the time.
These types of legal shenanigans, sadly, usually work; Politicians just keep attempting to pass the same provisions in different forms with slightly different language over a period of years until they slip, whatever it is, through.
This kind of reminds me of Instagram stories, somewhat ephemeral, the current state of being of people I follow, and things I'm interested in. I guess I like the federated timeline because it's a federated timeline of things I care about.
Somehow this has only gotten funnier since it was originally posted..
What the article doesn't say (well, there's a lot it doesn't say) is that this protocol was created by Anthropic but is being adopted more widely.
MCP reminds me of a new platform opportunity akin to the Apple App Store.
It's rapidly adopted, with offerings from GitHub, Stripe, Slack, Google Maps, AirTable, etc. Many more non-official integrations are already out there. I expect this will only gain adoption over the coming year.
I've been working with OFCOM on implementing the requirements of this act. They seem reasonable, and what they are looking for is mostly table stakes. That said, I wouldn't want to live in or run a UGC business in the UK right now.
Setting aside specific cases like DeepSeek, the tech trend is a consistent march towards cheaper, faster, and better solutions. This march is often fueled by new approaches in manufacturing, materials, and techniques, all part of the broader march of scientific progress. The result is usually similar or superior performance at a significantly reduced cost.
I agree with the OP that constraint is the biggest driver of this innovative trend, which is why disruption is the best form of innovation.
Thanks for the response. Do you mean by leveraging contacts or just by "existing" in it for a lengthy period (i.e., people see you as a more committed or more experienced option)?
The saying, “If it ain't broke, don’t fix it,” comes to mind. I’m all for progress, but Hacker News's simplicity and density are its major features.
I'm a woodworker, and i've suffered some injuries over the years (but not on a tablesaw). This seems like more of a political issue, those for and against regulation. I'm surprised to see this on HN and there is too much drama in this thread to otherwise comment.
I'm not a Meta fan, but it's hard to not look at how they have handled Llama and how well it's worked out for them and the "community." I think that OpenAI could also be playing a leading role in the science instead of selling subscriptions for Microsoft.
Why are all the example videos in slow motion?
In my experience, tipping culture first started to change with Starbucks, but it really seemed to accelerate with integrated tips in terminals like square and point of sale devices.
In short, when the checkout terminal asks you to round up your change for a donation to help kids, and the cashier is looking at you, nobody wants to feel like the jerk that says no.
I have to say, with all the discussion about how magnificent the JWST was going to be, and now it is, I expected a better picture. It puts into perspective just how far away Uranus is, which is hard to wrap my mind around...
Protrcting privacy worked out so well with these cookie banners, I cant imagine what could go wrong with this…
That may be more of a personality conflict. There's no more important choice than who you co-found with, and both parties should have high regard for each other's value to the business.
The inverse side of this is, that depending on the business, you may need another type of co-founder as well. Two technical co-founders aren't the right fit for every business.
This brings back a lot of memories, but I think what I lament the most is that this was really the end of American soup-to-nuts engineering in telecom. At the end of the 56k production and the start of G.Lite DSL, all this engineering started going to China to save money. Long gone are the days of Radio Shack and companies EE's designing, prototyping, testing, and manufacturing electronics. Sad.
Thank you for your response. Since I have your ear, I'll provide some direct feedback.
"We definitely care about abuse generated by Workers."
That may be the case internally but it's not as evident through support. I base this on their ability to answer security-related questions, diagnose odd behavior, or mitigate problems. FYI, we are paying for your highest tier of support.
"it should be treated as if they were running their bot on any other cloud provider and making requests across the internet."
Part of this is how Site Analytics and WAF analytics represent worker data (or don't). Even though the worker modifies the contents, the IP is passed through as the end-user IP (at least the way we use them). These analytics systems need to do a better job of identifying anything worker or tunnels related. If this were being done through AWS it would be evident. We can use various mechanisms to mitigate this, but I wanted to clarify why abuse through Workers is different for our implementation.
Also, the process to block non-zone workers was undocumented, and it took a couple of weeks for someone to dig it up and only after several trials and errors. Support wasn't sure it would work, and there was no other documentation (at the time).
We have yet to get an answer about the high volume of tunnel requests from specific goes.
Combine this with the opaque stack you have that causes odd situations. For example, I added a worker that automatically retries 500 errors from the origin. Simple enough. This breaks Zero Trust, though, and causes a redirect loop. There may be documentation somewhere, but there isn't a good breakdown of how Zero Trust fits into a customer-defined worker, and a redirect loop is undoubtedly a poor failure mode.
There is a world of difference between the information you have and may provide as the Technical Lead of Workers, and what I'm getting via support or raw documentation.
I could provide you more information offline if you want.
Edit: Let me just add the other recent thread [1] regarding redirect loops in verification is par for the course. We had the same issue and tried for weeks for progress or resolution. The issue was never resolved, nor could we get information on why the failure mode was so poor, etc. That ambivalence adds up to expecting general ambivalence or inability to make meaningful progress. At some point, you say to yourself, "Why waste my time talking to support and putting in much effort and getting the run-around."