kameshss

Billet sent us a quote. I don't know or care how they arrived at the value. If they're good, I'm good.

As for what steps we're taking, you're talking about an outlier issue that has happened once in 10+ years of operation. There won't be a new SOP to ensure we don't accidentally auction stuff. We just need to tighten up some documentation.

There won't be a big WAN Show segment about this or anything. Most of what I have to say, I've already said, and I've done so privately.

To Steve, I expressed my disappointment that he didn't go through proper journalistic practices in creating this piece. He has my email and number (along with numerous other members of our team) and could have asked me for context that may have proven to be valuable (like the fact that we didn't 'sell' the monoblock, but rather auctioned it for charity due to a miscommunication... AND the fact that while we haven't sent payment yet, we have already agreed to compensate Billet Labs for the cost of their prototype). There are other issues, but I've told him that I won't be drawn into a public sniping match over this and that I'll be continuing to move forward in good faith as part of 'Team Media'. When/if he's ready to do so again I'll be ready.

To my team (and my CEO's team, but realistically I was at the helm for all of these errors, so I need to own it), I stressed the importance of diligence in our work because there are so many eyes on us. We are going through some growing pains - we've been very public about them in the interest of transparency - and it's clear we have some work to do on internal processes and communication. We have already been doing a lot of work internally to clean up our processes, but these things take time. Rome wasn't built in a day, but that's no excuse for sloppiness.

Now, for my community, all I can say is the same things I always say. We know that we're not perfect. We wear our imperfection on our sleeves in the interest of ensuring that we stay accountable to you. But it's sad and unfortunate when this transparency gets warped into a bad thing. The Labs team is hard at work hard creating processes and tools to generate data that will benefit all consumers - a work in progress that is very much not done and that we've communicated needs to be treated as such. Do we have notes under some videos? Yes. Is it because we are striving for transparency/improvement? Yeah... What we're doing hasn't been in many years, if ever.. and we would make a much larger correction if the circumstances merited it. Listing the wrong amount of cache on a table for a CPU review is sloppy, but given that our conclusions are drawn based on our testing, not the spec sheet, it doesn't materially change the recommendation. That doesn't mean these things don't matter. We've set KPIs for our writing/labs team around accuracy, and we are continually installing new checks and balances to ensure that things continue to get better. If you haven't seen the improvement, frankly I wonder if you're really looking for it... The thoroughness that we managed on our last handful of GPU videos is getting really incredible given the limited time we have for these embargoes. I'm REALLY excited about what the future will hold.
 
With all of that said, I still disagree that the Billet Labs video (not the situation with the return, which I've already addressed above) is an 'accuracy' issue. It's more like I just read the room wrong. We COULD have re-tested it with perfect accuracy, but to do so PROPERLY - accounting for which cases it could be installed in (none) and which radiators it would be plumbed with (again... mystery) would have been impossible... and also didn't affect the conclusion of the video... OR SO I THOUGHT...
 
I wanted to evaluate it as a product, and as a product, IF it could manage to compete with the temperatures of the highest end blocks on the planet, it still wouldn't make sense to buy... so from my point of view, re-testing it and finding out that yes, it did in fact run cooler made no difference to the conclusion, so it didn't really make a difference.
 
Adam and I were talking about this today. He advocated for re-testing it regardless of how non-viable it was as a product at the time and I think he expressed really well today why it mattered. It was like making a video about a supercar. It doesn't mater if no one watching will buy it. They just wanna see it rip.  I missed that, but it wasn't because I didn't care about the consumer.. it was because I was so focused on how this product impacted a potential buyer. Either way, clearly my bad, but my intention was never to harm Billet Labs. I specifically called out their incredible machining skills because I wanted to see them create something with a viable market for it and was hoping others would appreciate the fineness of the craftsmanship even if the product was impractical. I still hope they move forward building something else because they obviously have talent and I've watched countless niche water cooling vendors come and go. It's an astonishingly unforgiving market.
 
Either way, I'm sorry I got the community's priorities mixed-up on this one, and that we didn't show the Billet in the best light. Our intention wasn't to hurt anyone. We wanted no one to buy it (because it's an egregious waste of money no matter what temps it runs at) and we wanted Billet to make something marketable (so they can, y'know, eat).
 
With all of this in mind, it saddens me how quickly the pitchforks were raised over this. It also comes across a touch hypocritical when some basic due diligence could have helped clarify much of it. I have a LONG history of meeting issues head on and I've never been afraid to answer questions, which lands me in hot water regularly, but helps keep me in tune with my peers and with the community. The only reason I can think of not to ask me is because my honest response might be inconvenient. 
 
We can test that... with this post. Will the "It was a mistake (a bad one, but a mistake) and they're taking care of it" reality manage to have the same reach? Let's see if anyone actually wants to know what happened. I hope so, but it's been disheartening seeing how many people were willing to jump on us here. Believe it or not, I'm a real person and so is the rest of my team. We are trying our best, and if what we were doing was easy, everyone would do it. Today sucks.
 
Thanks for reading this.

Technically, it should work without any issues.
 
I'll advise you on why it's better off installing the games on separate SSD.
Say for example that your OS is crashed etc and unrecoverable by a mistake you did or may be Windows being Windows etc. The size of games are quite big these days and its hard to download about TBs of Games when you re-install the OS.
 
So, one SSD for OS (250GB or 500GB) and 1TB+ for Games library as you wish. When you re-install the OS, you can just point your game launchers to where its installed and it should be able to recognise.
 
Completely not necessary. Just for fool-proofing.

Recently people discovered that a screw can cause a short with the PCB of the PCIe riser that is included with NZXT H1 cases. Gamers Nexus did two videos on this thoroughly testing this issue and they have found that is a certain fire hazard. Instead of me trying to explain, I will link the two videos:
 - Unsafe Computer Catches Fire: NZXT H1 Case & BLD Serious Problems - YouTube
 - NZXT is Irresponsible & Dangerous: H1 Riser Fire Hazard Should Be Recalled - YouTube
 
Now, I've searched out of curiosity to see if any other youtubers have made a video on this issue and I found this video from ShortCircuit that actually showcases one of the H1 cases:
- Don't wait for the Xbox Series X! - NZXT BLD H1 Gaming System - YouTube
 
I went into the comment section and I've seen people say that they have bought this case so that means they are at risk if not made aware of the issue. I replied to the ones that I saw, but as you can imagine not everyone that bought that case commented on the video.
 
Let's try to make someone from LTT aware of this so that they at least pin a comment on their video informing people of this issue. I have also sent an e-mail to info@linusmediagroup.com if it's of any importance.

1) crop the video and upload it to youtube
2) wait for it to be copyright claimed
3) get your answer

And he's looking at you... and me?

Lttstore.com tattoo (Y) 

what is this color grade? someone forget  put on the wrong one at the start?
Seems overexposed

Thanks for the kind words guys ?

in a world where nothing is constant, i feel so much joy in knowing 99% of the Staff at LTT are still working at LTT all these years later, and Linus hasn't been involved into any sort of outrage or any controversy that he can't back out of, remember how enraged was the "can't use this word because someone will report it" warriors attacking linus for stealing a tampon in that amazon video, that's as close to any controversy he's been in and youtube even defended him in a tweet. i'm just glad the channel exists and ever growing. 

gonna leave this comment from 2015
 
  
  
 

Okay, please hire her. like please.
 
Amazing video, @LinusTech!

Okay, please hire her. like please.
 
Amazing video, @LinusTech!

I'll show you a laptop with 4100 MHz

I'll show you a laptop with 4100 MHz

Or fsck
 
Which can't actually be filtered because FSCK can be several things including a linux file checker

Seinfeld by yourself, Friends with your girlfriend.

damn 5700XT looks like Linus dropped something on the mold and AMD couldn't afford to replace it.

B&H is selling LG OLED 55" inch OLED TV for $999. GET IT! Go
 
https://www.bhphotovideo.com/c/product/1417949-REG/lg_oled55c7c_55_uhd_smart.html
 
Looks like it's a Commercial edition TV and the year is 2017. More here https://www.theverge.com/good-deals/2019/6/12/18662664/lg-c7-oled-4k-hdr-tv-b-h-photo-sale-deal?fbclid=IwAR2GGQlsYOmHzT3Z8TwHXheAniEfd6Gz0NtH5CJFtCFSQRt38XvdGDjNvlA

360p squad!

360p squad!

I have done something like this before. But, your best place for this to search is tonymacx86. They might have some step by step solutions for that. Clover EFI is the base where you need to start from. Unless you're booting on a Legacy BIOS, you need to search differently.

RMA. Bad drive. It happens. If you want data off of it, use something like this https://www.amazon.com/Sabrent-2-5-Inch-Adapter-Optimized-EC-SSHD/dp/B011M8YACM/ref=sr_1_3?ie=UTF8&qid=1545883675&sr=8-3&keywords=2.5+inch+to+usb+3 and try attaching it as external drive and see if it detects. If not you're out of luck. Pretty sure you can RMA the drive.

RMA. Bad drive. It happens. If you want data off of it, use something like this https://www.amazon.com/Sabrent-2-5-Inch-Adapter-Optimized-EC-SSHD/dp/B011M8YACM/ref=sr_1_3?ie=UTF8&qid=1545883675&sr=8-3&keywords=2.5+inch+to+usb+3 and try attaching it as external drive and see if it detects. If not you're out of luck. Pretty sure you can RMA the drive.