That is the video title, but I think it should be paraphrased here to be more correct given our highly technical audience. The politician is actually reading an unedited AI response, which includes "editors notes" or maybe you could call it meta-content.
- it creates the file if it does not exist, not merely truncate. as a tutorial kind of blog post this incomplete description matters IMO.
- it would work the same without the colon (similar for default variable assignment examples). we generally strive not to have "extra" things, like useless use of cat.
- educationally it's useful to demonstrate that redirection, like parameter expansion, works before the command executes (the null command in this case), but the article doesn't explain that at all!
otherwise i <3 this article. some uses of colon i had never thought of or seen before. like file truncation, not sure i'd use them but it was cool to see them.
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.
> 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.
> 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'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.