japers

DIY In-the-wall thin client would be an interesting video.
 
However there is an off-the-shelf option...
Can be PoE or have a barrel jack plugged into it. 

https://www.chippc.com/jack-pc.html




 
 

lmao
 
Dude says Floatplane 1080p > youtube 1080p
youtubte 4k > Floatplane 1080p
Floatplane 4k > youtube 4k
Clearly, A lie when this line states the videos are better on Floatplane

ok.
Why did they say LIE? When they could have just said discrepancy. OP is being inflammatory for the sake of being inflammatory, not because he has a smoking gun catching anyone in a lie.

In terms of AUDIO quality, reddit OP themselves found 320kbp/s audio in some of the floatplane videos. AKA what they are finding are what was uploaded. 

Youtube reencodes shit for standardization. Floatplane may just be taking the uploaded audio and going "ok seems good to me". And that is why there are some 96k audio files there you don't find on youtube. 
 
For SPOKEN videos, not music audio, 96k is MORE then enough. You do not go higher if you do not need to (like if your video had music)

They definitely do ask airlines for comment after a plane crash...

So youre saying disregard them if you want to take a jab at someone elses journalistic integrity without doing your own due dilligence.
Got it...

Steve essentially said he doesn't have to reach out if he feels you are guilty which is a far cry from a journalistic approach. 
 

So, after watching the first part of the latest GN video (the part focused on LTT since the rest is I believe irrelevant to this conversation), I'm still kind of mixed on how GN handled the situation. Steve saying "we didn't have to reach out" raises the question of "Yeah, but why didn't you?" Like it's an answer, but kind of a weird one in my opinion. Still, the fact that Linus didn't reach out to Billet until AFTER the GN video went up yesterday . . . @LinusTech I sincerely ask, why did you lie? This isn't even funny. It's just sad, and kind of hurts even me, and like I mentioned already, I don't watch LTT that often. I don't know, this just sucks all around.

So youre saying disregard them if you want to take a jab at someone elses journalistic integrity without doing your own due dilligence.
Got it...

Yes it is...Youre very wrong on this.
 
https://www.spj.org/ethicscode.asp
 
"Diligently seek subjects of news coverage to allow them to respond to criticism or allegations of wrongdoing."

https://www.spj.org/ethicscode.asp
 
Its not an opinion.
 
"Diligently seek subjects of news coverage to allow them to respond to criticism or allegations of wrongdoing."

Yeah man, I'm not saying I agree but this is what he means when he's talking about pitchforks being out. People are seeing this in a really personal, unhealthy way.

Not sure if this is the right spot for this, but last time I suggested a product from this company it became a video, the $100 hdmi cable with a processing chip in it.  Anyways here is a "Video card for your console"

I ended up tuning mine with the utility above and got within 5% of the base 5950 cinebench score 😄

I ended up tuning mine with the utility above and got within 5% of the base 5950 cinebench score 😄

Some tool has scraped the YouTube URLs when all the videos were un-privated and it included a few hundred unlisted personal videos
 
 
 
If any of the mods can reach out to someone directly to let Linus know, thats probably wise.

Some tool has scraped the YouTube URLs when all the videos were un-privated and it included a few hundred unlisted personal videos
 
 
 
If any of the mods can reach out to someone directly to let Linus know, thats probably wise.

How isnt it a fair comparison? Im comparing a potential DIY NAS solution with the same storage capacity but in SSD, with an off the shelf NAS with the same storage capacity but in HDD...
 
Thats what this whole thread is about. So in this case the DIY SSD NAS would be MASSIVELY cheaper than a 16TB synology NAS WITH SSDs (which afaik doesnt even exist). So i dont see what youre getting at. At All. 
 
My specific use case for faster NAS storage is that im a professional 3D Artist and have several terabytes of assets like textures and model files that i use. Every time i hit the render button, those assets get pulled into memory on either my desktop, or on my render farm.
 
Pulling lots of files from a HDD is noticeably slower in the rendering process than an SSD and ideally i want them all saved on a network device rather than the render farm needing to pull directly from my Workstation SSD over the network.
 
So in my specific use case, SSDs not only are worth the slight price increase over comparable drive size, but they have a noticeable performance impact.
 

I wonder if the new NUCs might be of use to you. Compact form factor, Lower voltage parts. Enough room for a full size GPU and expansion for your m.2. You can configure NUC's at time of purchase to suit your needs and then upgrade everything in future if you wanted to as its pretty modular.
 
Ive thought for a while that a nuc might be the ideal van life PC as ive recently found the potential need through my work to have a portable setup potentially in a van.
 
https://simplynuc.co.uk/9i9qnx-full/

The Biggest of oofs.

Summary
 
Intel suffered a massive data breach earlier this year and as of today the first associated data has begun being released. Some users are reporting finding hardcoded backdoors in the intel code.
 
Some of the contents of this first release (There will be further releases)
 
- Intel ME Bringup guides + (flash) tooling + samples for various platforms
- Kabylake (Purley Platform) BIOS Reference Code and Sample Code + Initialization code (some of it as exported git repos with full history)
- Intel CEFDK (Consumer Electronics Firmware Development Kit (Bootloader stuff)) SOURCES
- Silicon / FSP source code packages for various platforms
- Various Intel Development and Debugging Tools - Simics Simulation for Rocket Lake S and potentially other platforms
- Various roadmaps and other documents
- Binaries for Camera drivers Intel made for SpaceX
- Schematics, Docs, Tools + Firmware for the unreleased Tiger Lake platform - (very horrible) Kabylake FDK training videos
- Intel Trace Hub + decoder files for various Intel ME versions
- Elkhart Lake Silicon Reference and Platform Sample Code
- Some Verilog stuff for various Xeon Platforms, unsure what it is exactly.
- Debug BIOS/TXE builds for various Platforms
- Bootguard SDK (encrypted zip)
- Intel Snowridge / Snowfish Process Simulator ADK - Various schematics
- Intel Marketing Material Templates (InDesign)
- Lots of other things
 
 

 
Quotes
 
 
My thoughts
 I hope this leads to more understanding about the internals of the Intel ME. Last few years have shown that it’s a tremendous security liability, and the best way to mitigate this is if we all get a better understanding of how it works.
Update: They used the password Intel123. They probably deserved it.
 
Sources (Original tweet and TH link)
https://twitter.com/deletescape/status/1291405688204402689
https://www.tomshardware.com/news/massive-20gb-intel-data-breach-floods-the-internet-mentions-backdoors

The Biggest of oofs.

Nobody: 
Dr Su: *Laughs in money*
 
*Aggressively eats popcorn while using AMD Ryzen CPU*

The Biggest of oofs.

Summary
 
Intel suffered a massive data breach earlier this year and as of today the first associated data has begun being released. Some users are reporting finding hardcoded backdoors in the intel code.
 
Some of the contents of this first release (There will be further releases)
 
- Intel ME Bringup guides + (flash) tooling + samples for various platforms
- Kabylake (Purley Platform) BIOS Reference Code and Sample Code + Initialization code (some of it as exported git repos with full history)
- Intel CEFDK (Consumer Electronics Firmware Development Kit (Bootloader stuff)) SOURCES
- Silicon / FSP source code packages for various platforms
- Various Intel Development and Debugging Tools - Simics Simulation for Rocket Lake S and potentially other platforms
- Various roadmaps and other documents
- Binaries for Camera drivers Intel made for SpaceX
- Schematics, Docs, Tools + Firmware for the unreleased Tiger Lake platform - (very horrible) Kabylake FDK training videos
- Intel Trace Hub + decoder files for various Intel ME versions
- Elkhart Lake Silicon Reference and Platform Sample Code
- Some Verilog stuff for various Xeon Platforms, unsure what it is exactly.
- Debug BIOS/TXE builds for various Platforms
- Bootguard SDK (encrypted zip)
- Intel Snowridge / Snowfish Process Simulator ADK - Various schematics
- Intel Marketing Material Templates (InDesign)
- Lots of other things
 
 

 
Quotes
 
 
My thoughts
 I hope this leads to more understanding about the internals of the Intel ME. Last few years have shown that it’s a tremendous security liability, and the best way to mitigate this is if we all get a better understanding of how it works.
Update: They used the password Intel123. They probably deserved it.
 
Sources (Original tweet and TH link)
https://twitter.com/deletescape/status/1291405688204402689
https://www.tomshardware.com/news/massive-20gb-intel-data-breach-floods-the-internet-mentions-backdoors

Summary
 
Intel suffered a massive data breach earlier this year and as of today the first associated data has begun being released. Some users are reporting finding hardcoded backdoors in the intel code.
 
Some of the contents of this first release (There will be further releases)
 
- Intel ME Bringup guides + (flash) tooling + samples for various platforms
- Kabylake (Purley Platform) BIOS Reference Code and Sample Code + Initialization code (some of it as exported git repos with full history)
- Intel CEFDK (Consumer Electronics Firmware Development Kit (Bootloader stuff)) SOURCES
- Silicon / FSP source code packages for various platforms
- Various Intel Development and Debugging Tools - Simics Simulation for Rocket Lake S and potentially other platforms
- Various roadmaps and other documents
- Binaries for Camera drivers Intel made for SpaceX
- Schematics, Docs, Tools + Firmware for the unreleased Tiger Lake platform - (very horrible) Kabylake FDK training videos
- Intel Trace Hub + decoder files for various Intel ME versions
- Elkhart Lake Silicon Reference and Platform Sample Code
- Some Verilog stuff for various Xeon Platforms, unsure what it is exactly.
- Debug BIOS/TXE builds for various Platforms
- Bootguard SDK (encrypted zip)
- Intel Snowridge / Snowfish Process Simulator ADK - Various schematics
- Intel Marketing Material Templates (InDesign)
- Lots of other things
 
 

 
Quotes
 
 
My thoughts
 I hope this leads to more understanding about the internals of the Intel ME. Last few years have shown that it’s a tremendous security liability, and the best way to mitigate this is if we all get a better understanding of how it works.
Update: They used the password Intel123. They probably deserved it.
 
Sources (Original tweet and TH link)
https://twitter.com/deletescape/status/1291405688204402689
https://www.tomshardware.com/news/massive-20gb-intel-data-breach-floods-the-internet-mentions-backdoors

This is release 1 and it contains confidential NDA code. Its NDA for a reason...
Even if its just trade secrets its damaging and their stock price will likely show it.