We’ve lived through an entire internet without age checks, why is it different now? There aren’t more creeps

I think the big difference is ease of access. For millennials growing up, accessing the internet basically required being at the family desktop in the middle of the living room. Phones weren’t connected to the internet, and cell phones weren’t even common yet.

And kids still got groomed, even when their only access to the internet was in a shared family space. And that began to get more prevalent as devices became smarter and more portable. Now, any 8 year old can get groomed in their own bedroom, while simply playing a video game.

I actually disagree, because hardware-level verification is basically the most privacy-conscious method of accurately verifying a user’s age. Rather than fighting age verification entirely, I think it’s more productive to start assuming users are under 18 until proven otherwise… Age verification is inevitable, (if you don’t like it, tor is always an option), so we should at least figure out secure and private ways of doing so. Rather than resisting it outright, present them with secure and safe ways to do it. The internet is a dark place full of a lot of creeps, and services like Roblox have proven that they will enthusiastically become nesting grounds for predators unless they’re forced to add safeguards.

Sure, it’s easy to say “just monitor your kids” but no parent can be present 24/7. And in fact, oftentimes parents end up using screen time so they can do other things like chores, without needing to watch their kid. So the “just watch your kids” argument is diametrically opposed to the reality of why parents tend to rely on screens. Sometimes you just need 15 minutes to wash the dishes, without a kid demanding your constant attention. Even I, a child-free person, can understand that. And it becomes increasingly difficult to monitor them as they grow into teens and (reasonably) start expecting their own privacy.

I’ve been saying for a while now that we need to shift to hardware verification. Your device (or for shared devices like desktops, your user account) verifies your age once. And then it doesn’t need to do so again. All of the various sites and apps can simply ask your device “hey, is this user over {age}?” And the device responds with a simple true/false. You’re not needing to give your PII to every single site you visit, and the device isn’t needing to report back to the government every time an age verification check happens. It’s all done locally. The handshake could even be cryptographically secured, to prevent tech-savvy kids from MITM’ing the age check. And then protecting kids online is as simple as not age-verifying their device (and protecting your own password on shared devices). Hell, devices like cell phones could even have the age bracket set by the parent directly, since the phone would be on the parent’s phone bill. Similarly, parents could create child accounts on their shared devices, so kids can access age-appropriate content. It won’t stop kids from getting a prepaid phone, but it’ll at least prevent them from easily verifying that phone.

And it’s also the most elegant for the user experience. As far as the adult user is concerned, they never even see an “are you over 18” verification when they visit a porn site. They simply get access to the site. And kids simply get redirected back to Google’s home page (or more realistically, a page on the porn site saying “hey you failed the age check. If you’re over 18, be sure you do that with your device before trying again, because this is the only page you’ll be able to access until then. Or if you’re under 18, click here to return to where you were before” explanation) as soon as the age check fails.

Hardware age verification is basically the best of every world. You don’t rely on a third-party service to verify your PII (which will inevitably leak it, like Discord did). You don’t need to verify with every single individual site and service. The government doesn’t get a record of every site that asks for verification. And kids are automatically prevented from stumbling across adult content.

I agree that Colorado democrats are typically the “if we cozy up to the right they might stop being mean to us” candidates. I think this bill is a poor implementation, but it’s at least done under the right premise. If we could force hardware manufacturers and/or OSes to support native age verification, it would solve a lot of the current issues that we have.

Yeah, Tailscale’s “zero-config” idea is great as long as things actually work correctly… But you immediately run into issues when you need to configure things, because Tailscale locks you out of lots of important settings that would otherwise be accessible.

For instance, the WiFi at my job blocks all outbound WireGuard connections. Meaning I can’t connect to my tailnet when I’m at work, unless I hop off the WiFi and tether to my personal cell phone (which has a monthly data cap). Tailscale is built on WireGuard, and WireGuard only. If I could swap it to use OpenVPN or IKEv2 instead, I could bypass the problem entirely. But instead, I’m forced to just run an OpenVPN server at home, and connect using that instead of using Tailscale.

Yeah, this is my preferred way of doing it. That way I always have a nice compiled list of IP addresses, and if I ever need to change any of them, I have them all in a single menu instead of needing to access each device individually. Just let the server use DHCP, then assign it a static IP in your DHCP server.

Appeals aren’t an infinite thing. Each appeal goes to a higher court, and eventually will reach the SCOTUS. And at any point, the respective appellate court can refuse to accept the appeal, essentially saying that they agree with the lower court’s ruling and leaving it in effect.

Each step of the appeals process basically asks if the lower court applied the corresponding laws correctly. And if they did, the appellate court looks at whether or not that law is constitutional. If both are true, (the law is constitutional and was applied correctly) then the appeal fails. Appeals are actually fairly hard to win, especially for laws that have lots of precedent. If a law already has lots of precedent and the lower court was simply applying the law the same way that other cases did, the appeal will almost certainly be shot down.

That’s why lots of the big landmark “court strikes down law as unconstitutional” cases are from laws that were recently passed. There is no long-standing precedent for the recently passed law, so the lower courts have to set the precedent, and the appeal is actually what is deciding whether or not the law is constitutional.

Yup. My local shooting range doesn’t need RAM. The archery target in my back yard doesn’t need RAM. The park where I go jogging doesn’t need RAM. My local food bank always needs volunteers, and they’re not handing out RAM to hungry people. My local theater always needs volunteer ushers, and you get to see a show for free.

Yes and no. The hardware companies have already said that they’re not interested in expanding production. They know it’s a bubble, and don’t want expanded production now to cause a glut in the future when the inevitable pop happens. So prices may not actually drop, (even after the pop), because the companies still won’t be producing more hardware than they currently are.

My best guess is that we’ll have some dark data centers sitting around collecting dust, but the hardware they bought won’t actually flood the market and crash prices. If anything, since the US dollar’s value is essentially tied to Nvidia and OpenAI’s market share, a pop will only make the dollar less powerful and will counteract any potential drops in prices that may have otherwise happened. The companies will get a trillion dollar bailout when the pop happens, (because they’re too big to fail) then nothing will change about the current hardware prices.

Yup, they’re 100% trying to shift towards cloud computing. It has already been happening with gaming, and many players have decided that they’re okay with a slightly worse experience if it means they can run their games on a potato PC. Tech companies see the blood in the water, and know that there is money to be made in cloud computing. Everything is shifting to SAAS, so it only makes sense that hardware will be a subscription next.

It’s actually not pornographic, and the photo shoot didn’t involve any nudity. But it definitely uses some pornographic poses and camera angles, so it looks like it’s from the start of a porn video, or from a porn photoshoot.

The funny part is that votes are public, to ensure they get counted correctly during federation.

That’s how you charge the Apple Mouse. They intentionally designed it so you couldn’t use it while it was charging, because Steve Jobs demanded a cord-free desk. He hated the cords leading to his mouse and keyboard, and didn’t think devices should stay plugged in all the time. So he forced the engineers to design a mouse that couldn’t stay plugged in.

It really is the epitome of Apple’s “I know better than you” design philosophy

Probably worth noting that FlareSolverr hasn’t actually worked to bypass Cloudflare in a while. They got noticed by CF, and CF started actively preventing their solvers from working. However, several trackers still require FlareSolverr to run before they’ll even try to connect.

In some cases, you can visit the site directly, and then manually solve the CF captcha. That will usually allow it to work, even when Solverr is broken.

Yeah, it feels like a “loose lips sink ships” situation… But on the other side of the same coin, there’s no way the TV providers were ignorant of this. They undoubtedly already knew, so it’s not like this article is going to bring anything new to light. If anything, it may put a target on the backs of some of the people who were quoted in the article for litigation, but that’s not going to actually stop the boxes from being sold in the long term.

The original quote was saying that he could shoot a man in the middle of 5th street and not lose any votes. But yeah, he probably could rape a child on the street, and he would have apologists lining up to justify it.

I’ve been saying this for literal years now. They should release a publicly searchable database of every single SSN, name, and DOB. Force organizations to stop using those as a form of ID, because they’re not secure and never have been.

Give it like a year of lead time. Like announce “March 1 2027, we’ll post the database” and then that gives institutions a full year to figure something new out.

In late 2025 and 2026 there is a huge surge in demand for hardware. There’s a shortage of hardware, and factories don’t get built out overnight. So prices skyrocket, pricing out many users to the point where demand at the new price point matches the available supply. But as production capacity increases, that will also ease.

And this is where your entire idea falls apart… The manufacturers have openly stated that they have zero interest in expanding production. They’re trying to avoid a supply surplus after the boom ends, and they know that expanding production now means crashed prices later. Why expand production, when you can simply not spend that money and charge higher prices anyways?

Ah yes, the College Sophomore technique: Don’t eat all day, so the party beer gets you absolutely wasted when you’re drinking on an empty stomach. That’s just efficient use of resources.

I mean yeah, but that’s a little like saying “computers all have WiFi capabilities these days, as long as you only buy motherboards with built in WiFi.” It’s a pretty large limitation to place on the user’s choice. Especially when Linux users like to meme about certain distros being better or worse.

For IEMs, the price difference typically goes towards comfort rather than sound quality. As a professional audio technician, a custom-molded IEM will be infinitely more comfortable than a cheap set. But not everyone can justify spending $2000 for custom molds, because they don’t use them for work every day.

It really depends on how low the bitrate is. A change from 320kbps (the highest “near-CD” bitrate that .mp3 supports) to 128kbps (standard .mp3) won’t make a huge difference, but a change from 160 to 75 will likely make a big difference… Bitrate tends to be a game of diminishing returns, where a difference between 96kbps and 128kbps is typically noticeable, even by laypeople… But a difference between 320kbps and 640kbps is harder to hear, (or makes no difference at all), even though it’s a much bigger jump between numbers. As the bitrate continues to increase, you get fewer and fewer benefits while your file size begins to balloon.

To be clear, there is a lot of snake oil in the audiophile world. I’m not denying that. I work in audio, (peep my username), and spend a lot of time dispelling snake oil myths as part of my job. My current audio rig is easily a quarter million dollars, and is located in an acoustically treated room, because it’s built for an entire audience. I’ve also worked in recording and system design. So I’m probably fairly qualified to speak about this specific topic…

Like lots of snake oil, the bitrate conversation is built upon grains of truth; Just enough to be convincing to someone who only has a surface level understanding of the underlying principles. And audiophiles tend to focus a lot on hardware and manufacturer’s claims, instead of studying what makes that hardware work… Which makes them particularly susceptible to snake oil myths, oftentimes perpetuated by the manufacturers to sell more expensive products to unsuspecting customers. An extreme “low vs lower” bitrate difference is one of the few things that laypeople will be able to identify when presented with an A/B test. In fact, low bitrate comparisons are often used by scummy audiophile companies as a bad-faith “here’s what our competitors sound like, vs what we sound like” example. And to be clear, reducing from ~160kbps to ~75kbps is an extreme difference.

I want you to think of the most crunchy and heavily compressed “downloaded from limewire on the family computer for your iPod” .mp3 file you’ve ever heard. Full of artifacts, absolutely no high end, sounds like it was recorded with a landline phone, and it crackles when the kick drum peaks. That was probably at least 96kbps, because that’s the lowest bitrate that .mp3 compression supports by default. And that’s after the mp3 compression algorithm has done its lossy “eh, people probably don’t care about this particular frequency” thing. 75kbps is crazy low, and you’ll undoubtedly hear the compression as a result. But again, increasing bitrates will have diminishing returns as the number continues to climb. Going from 75kbps to 160kbps will be a marked improvement, but going from 160kbps to 320kbps will be a much smaller change.

The reason audiophiles tend to have difficulty with (or even completely fail at) identifying different bitrates is because audiophiles live in a magical land where going from 1200kbps (high-end FLAC quality) to 1411kbps (uncompressed CD quality) makes a noticeable difference. In 99.9% of cases it doesn’t make any difference at all, (because again, diminishing returns) but audiophiles will swear that the 1411kbps sounds better simply because the number is bigger. Again, the snake oil is built upon grains of truth, (differences in low bitrates are immediately noticeable) but only enough to be convincing to people who don’t understand the underlying principles, (at a certain point, bitrate stops impacting audio quality and only makes your file size bigger).

All of this is to say that yes, the posted bitrate of 75kbps is laughably low. And even laypeople will absolutely be able to hear a difference between the two in an A/B comparison. Because as the bitrate approaches 0, the differences get more and more apparent. And (at least when compared to things like FLAC and CD quality) 75kbps is remarkably close to 0.