jiveturkey

looks like a response to https://news.ycombinator.com/item?id=48445834

DACs are copper, and they're happy.

Well come on. GP really means category cable (twisted pair copper) is not happy at 10Gb distribution lengths (so-called horizontal cabling, although in a home it may span multiple floors without IDFs). That's kind of obvious context.

DACs are not category cable; they are twinax, short, and bulky.

JWTs can do that (delegate) and such capability is already well defined.

entropy check, for one

TL;DR: Don't overthink it, just send a verification email.

pretty bad advice, if taken only as written, without adding more flavor on top.

the major email providers will penalize you if you generate too many undeliverable emails. thus, if you just send a verification email without any pre-validation, it's pretty easy to get into a DoS situation where current/valid users don't get important email sent to them, or that email is significantly delayed, plus incur huge operating cost to resolve the problem.

some form of rate limiting is needed, plus IMHO it's better to use a verifier service or your own heuristic or ML model to test for email validity including valid but fake/spammy/disposable addresses.

sorry, but we are way past the point of being able to have nice things, esp. when we're talking about email.

the "lies" part of the content is great. people do assume all those wrong things. however the TLDR is just wrong, and potentially harmful.

oooh. i have an original. it doesn't have the 'Collector's Edition' etching. Does that make it a fake?

But the chatbots/aggregators do, and they accept the reports as fact.

As is noted in the conclusion.

Instead of releasing our results all at once, we're going to focus on one report at a time. This approach both prevents individual examples being overlooked and allows us to illustrate the negative impacts of vibe citing on research quality and public trust.

Not to take away from the actually great reporting here, but what they mean is, This approach allows them to milk it for as many clicks as possible.

why is that? you'd run yt-dlp from the same device you generated the cookies on (with a real browser). yt-dlp will have the bare cookie and also be able to refresh the cookie just like the browser.

There was a secondary sale in April.

There's a newish term for this: RLO, Recurring Liquidity Opportunity. These are tender offers at some recurring interval. Even some companies that have a shorter lifespan (say 7 years) offer this.

We are still in the short-half-life phase of GPUs. If a 2x faster GPU is on the horizon, why wouldn't OpenAI already be in line to buy? They aren't buying just 1, they are buying multiple datacenters' worth. So they wouldn't be a low priority, back of the line customer.

A short half-life means you are going to quickly dispose of what you have now, anyway. In fact most current datacenters can't even handle Vera Rubin, so I don't think there's short term risk here.

  BOOBS

Residents, not just citizens.

Since when does a commission in the EU get to tell the entire World how to treat Personal Data?

Ah! Curse your sudden but inevitable betrayal!

well, you're complaining about an ad.

Liability.

Going off on a tangent, I wish there were more awareness of how this concentrates power to Cloudflare.

Leaked to different parties.

Assuming you don't have ECH, you leak the question (in practical terms) to your ISP, and you leak your question to the DNS provider. With ODoH you plug the latter leak. Plugging that first leak is then still a problem (solved separately) but it's orthogonal to the second.

Even with ECH, where you plug the TLS leak, you have many more holes to plug. IP address might not be shared or might be shared across too few properties, and then traffic profile after the initial connect (to retrieve all the sub-resources) can identify destinations.

If relay and target are operated by the same provider, there is no collusion. Collusion occurs between 2+ parties. You have stipulated that they are the same party.

Why isn't github in the list of self-hosted options?

They are losing money.

They have $4b in cash and Q1 FCF $84m, and 70% gross margin. They can become profitable anytime they want.

Which is a F500 company.

It’s not DNS

There’s no way it’s DNS

It was DNSSEC

It doesn't mean that. A Co-Authored-By header isn't a legal signature or legal assertion of AI generated code.

I guess one could argue that flat pricing is actually quite expensive, and more akin to ssotax than real value. I guess it depends on the median team size that adds this feature.

yes, i understood, and i am saying you are wrong.

the enterprise tax also always includes other features (often you don't care about those -- acknowledged and that's why we call it ssotax because "we" only want the sso portion), and is priced per-seat. it's particularly vile when removal of dark patterns is also gated behind the ssotax/enterprise tier. such as advertising to every user.

the vercel offering is a flat price per month and doesn't bring in other stuff you don't care about. it's very well priced and you pay for just the value you want. it's unfair to lump it into the concept of ssotax.

no, with vercel it's an independent add-on. unique AFAIK.

GPS antennas typically need power. GPS receivers expect to be the sole power supplier. Simple, cheap signal distribution won't handle this. There are splitters that can allow one downstream port to supply power, but that fails when that single receiver fails. There are other splitters that are active-active. I guess you're claiming that the boxes from Time Machines are such active-active devices.

Those are not cheaper than an antenna! Although from the photo I'm not sure he bought the cheap antennas.

Speaking from experience deploying stratum-1. Not stratum-0, but the same GPS concerns.