pcislocked

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.

PS: I do not condone the use of this repo on Github. I think you should buy a legitimate license from Microsoft and do not use this repo from Github. I also think you should not buy an OEM key since they are technically not legal, but I do not recommend you to use this repo from Github either. Absolutely do not use this. This repo, like buying an OEM key, also not techincally legal.

I think you get the idea.

PS: I do not condone the use of this repo on Github. I think you should buy a legitimate license from Microsoft and do not use this repo from Github. I also think you should not buy an OEM key since they are technically not legal, but I do not recommend you to use this repo from Github either. Absolutely do not use this. This repo, like buying an OEM key, also not techincally legal.

I think you get the idea.

So let's recap.
 
- people in the management criticize the quality of her work, as they should be since it's their job
- she doesn't like it and starts complaining about her superiors
- they point out that their management is made up of accomplished professionals and she's a newbie that could be fired anytime
- she gets offended at the fact that they didn't fire all the senior management because she was complaining
- she alleges that she was "inappropriately grabbed" whatever it means
- she's perplexed by the fact that LTT cares about what public faces put in the video and weather they will stick with the brand

honestly you might as well go full pirate mode if it is not "technically legal". it's not like microsoft is going too hard on it anyways, if they did they'd start by taking down this repo from github, a site they own

try to learn what kind of WAN speeds you're going to get first - because going with a wifi 6E AP, 10Gbps and a 8 core pfsense box etcetc... won't be meaningful if you're going to get 250mbps dsl or something

In your head. Since you only need to remember one password from now on you should be able to remember even a pretty complicated one.

make a separate thread to ask this. this might get lost in the thread

@pcislockedThank you so much for the inputs, I'll go through all of your messages in detail in some time and I should be able to tweek out something.
I'll see all the analyser results and get back here.
if all else fails I think I'll stay home and record it on my i7 laptop with 2070. It should be able to record at 1080p 30 while encoding and decoding the Teams call in background

keepassxc + syncthing for serverless cloud sync. browser integration is a bit ohio-ish but if you import everything right it'll work great.
 
and backup your database to google drive for extra backup (+ maybe encrypt it with 7zip on gdrive for extra security)

Oof I had unsubbed last night thinking that I had somehow got subbed to a Tesla channel. 

> Discussion split off in to its own topic.
@Just Ori You may need to follow the topic to continue to receive notifications for new replies.

keepassxc + syncthing for serverless cloud sync. browser integration is a bit ohio-ish but if you import everything right it'll work great.
 
and backup your database to google drive for extra backup (+ maybe encrypt it with 7zip on gdrive for extra security)

Thanks for the concern everyone. We are still in recovery mode over here and working with YouTube to get everything restored. Will hopefully have a video (or at least an update on WAN Show) to share with you all ASAP, but we want to make sure we get the details right since smaller channels may rely on our experience to help harden their own security.

i am just hoping we get a deep dive on how this did happen and who is responsible for it. and i hope, again, no one gets fired. im logging out and i wish all the best for all staff, cya 

i am just hoping we get a deep dive on how this did happen and who is responsible for it. and i hope, again, no one gets fired. im logging out and i wish all the best for all staff, cya 

Good video about how this isn’t run by hackers or particularly intelligent people: 
Basically these people only care about a quick and dirty job. They want as little effort as possible and are never going to care about minor details that real victims wouldn’t notice anyway.
 
I very highly doubt there was any actual hacking involved at all.
 
 

That YouTube STILL hasn’t shut down the stream is freaking mind boggling. Who is the REAL problem here?

Thanks! That explains it for me then.

you can put single playlists in "shelves", the sections in your main channel page you can edit, at youtube studio > customization > layoutts i
 
When you press the add button, these are your options, and you can move them around.

 
So they add original tesla channel's playlists to make it seem like the channel they are editing/hijacking is legit.

Heard it here first, TeslaGate was an inside job!

Man imagine if this was done through a malicious ad. 

so at the end they arent that smart

you can put single playlists in "shelves", the sections in your main channel page you can edit, at youtube studio > customization > layoutts i
 
When you press the add button, these are your options, and you can move them around.

 
So they add original tesla channel's playlists to make it seem like the channel they are editing/hijacking is legit.