It's not an extraordinary claim, it's a mundane and plausible one. This is exactly what you get when you ask an LLM to write in a "engaging conversational" style, and skip any editing after the fact. You could never prove it but there are a LOT of tells.
"The key insight" - llms love key insights!
"self-contained corruption-free" - they also love over-hypenating, as much as they love em-dashing. Both abundant here.
"X like it's 2005" and also "Y like it's 2009" - what a cool casual turn of phrase, so natural!
The architecture diagram is definitely unedited AI, Claude always messes up the border alignment on ascii boxes
I wouldn't mind except the end result is imprecise and sloppy, as pointed out by the GP comment. And the tone is so predictable/boring at this point, I'd MUCH rather read poorly written human output with some actual personality.
ai detectors are never totally accurate but this one is quite good and it suggests something like 80% of this article is llm generated. honestly idk how you didn't get that just by reading it tho, maybe you haven't been exposed to much modern llm-generated content?
Much of the internet still does not support IPv6, so most providers will give you an IPv4 address. In fact only a few providers even support IPv6 at all.
Even with IPv6 it's not a huge problem. With a few samples we can know that a provider is operating in a given /64 or /48 or even /32 space, and can assign a confidence level that the range is used for VPNs.
Many websites including Soundcloud are still only accessible through IPv4, so this is moot, even if VPNs support IPv6 it's enough to block their V4 exit nodes for Soundcloud.
20 years ago, I used to consult with Fortune 500 companies that run Oracle and IBM products (web servers and Java frameworks).
These are distributed as enterprise binaries. It's common to face _at least_ one or two weird errors in production. Then you have to raise a ticket to support.
Would you like to know how it is discussing a binary-obfuscated error with Customer support? And then after few weeks being assigned to a newly joined fresher? And so on and on, where every person or layer every week says "you're doing it wrong" and you have to restart your proofing and explanation process from scratch?
Hint: After few weeks/months of this (or after 4 times of restarting your proofing process), you start questioning your sanity and life choices.
In those days, all I wished for is just "source-available", so that I can just debug myself what is going on and provide a concise bug report, instead of talking to support.
The weird part is, I'm pretty sure, on the other side, Oracle/IBM also LOST money in that same process. They had to hire an army of people. It was lose-lose on both sides.
Source-available means customers of that software can perform debugging themselves and file pretty good support tickets.
If you are an enterprise today, you would absolutely consider make it source-available to save on your own costs.
That's a great reason I steer clear of products like that. Oracle is not a DB I've used since 2005. There's no need. The market for closed sourced databases imploded to basically legacy products that predate when open source databases became a sane default choice. I guess some banks/insurers still might talk themselves into believing it's a sane choice for new projects.
I guess source available is better than source unavailable + hand wavy support from a company that's out to milk you for revenue for as long as they can get away with it.
But it's a weak substitute for proper open source that you can just fork and fix if you need to without having to beg some indifferent company to pretty please fix their legacy shit and offering to do free work for them. If it's open source, chances are that there are still some others around also using the same software and sharing your pain that can support you or benefit from your fixes.
I don't see the value of most shared source projects. Usually there are very decent OSS alternatives. And the lack of those usually just means one will pop up shortly and displace whatever it is you are using. Any benefit to these projects tends to be short lived. OSS developers like to copy what is good and add it to their own projects.
E.g. most nosql databases ended up having postgresql absorb whatever it was that made these things interesting. Several shared source things (mongodb) are at this point looking a bit dated and backwards. That's also exactly what happened to MS SQL, Oracle, DB2, and all those other long forgotten databases that people used to use last century. There's very little technical reason to use any of those at this point.
> But it's a weak substitute for proper open source that you can just fork and fix if you need
Many source-available licenses explicitly allow this, as long as you don't try to sell your fix commercially to others. You can certainly share it with others, it just has to be free of charge.
Technically correct but somewhat misleading. The app in question only asked for the following Google account permissions:
1. Manage your YouTube account
View and manage your videos and playlists
View and manage your YouTube activity, including posting public comments
2. View and manage your [YouTube] rental and purchase history
Your rental and purchase history may be displayed and accessible on this device.
Internet did not have enough devices to reach people. At the height of 2002 only a fraction of people worldwide had an already expensive computer and an internet to go with it.
I ran a e-commerce startup from 2005-2010. Having access to demand is a thing.
Today everyone has access in their pockets. Go to small city in Africa, India and China, and observe how they use AI. See how perplexity has put AI answers in hundreds of millions of people's hands before Google in a matter of months.
Forgive me for saying — but "Based on what" for comparing accelerated adoption between 2005 and 2025 — is discarding many huge elephants in the room, starting with that small thing you're reading this in your hand with, and the invisible thing that's sending you this comment.
You can thank them properly by submitting a comment on this matter and add your voice to the chorus so the proposed ruling gets shoved right back into the orifice it was pulled from.
reply