So I think there were a few issues.

• the original pinephone was basically too slow to be usable
• there were a few hardware quirks that had to be fixed in software but made mainlining drivers for it difficult
• the lack of community updates (and you could argue overall community management) caused some developers to move away while also impeded pine64s ability to attract new developers
• the lack of any sort of funding for developers made it difficult for people to work on as any more than a hobby (not necessarily pine64's fault, but it's the reality)
• poor battery life (better idle and sleep support would have been software issues but the hardware was designed to be cheap instead of really useful)
• daily driving Linux on a phone is a poor experience - not pine64s fault but there's a bunch of support missing in Linux that needs to be developed before early adopters can really use Linux phones. Modem power management, audio switching between Bluetooth and speaker, MMS support, camera support, etc.

The Dev stated he's been working on it for 10 years and says its time to move on

Man that's a hard sell when the starlite is going for $627 https://us.starlabs.systems/pages/starlite

$70 cheaper with better specs is a no brainer

Like many others, I have mixed feelings on this. If anyone is stopping by and doesn't want to read through the linked forum thread, this is frameworks goal:

This isn’t a program to get people to go to conferences and rep Framework, it’s a program to give people who are already going to conferences and showing off their Framework some swag and opportunities to talk with the team. It’s not assigning work, it’s just saying thank you to people who are excited about Framework and active in the Linux community.

The command was rm -rf $pathvariable

Bug in the code caused the path to be root. Wasn't explicitly malicious

Did you expose your router login page to the open internet? How'd they get access? Why are you chmoding anything to be 777?

It's disappointing to see so many commentors arguing against you wanting to do this. Windows has it through bitlocker which is secured via the TPM as you know. Yes it can be bypassed, but it's all about your threat level and effort into mitigating it.

I am currently using a TPM on my opensuse tumbleweed machine to auto unencrypt my drive during boot. What you want to do is possible, but not widely supported (yet). Unfortunately, the best I can do is point you to the section in the opensuse wiki that worked for me.

https://en.opensuse.org/SDB:Encrypted_root_file_system

If you scroll down on that page you'll see the section about TPM support. I don't know how well it will play with your OS. As always, back up all your files before messing with hard drive encryption. Best of luck!

The "real" way needs the corresponding Wayland protocol in order to work. The protocol is under development/review, but involves a lot more moving parts that requires coordination and approval from multiple people. This "fake" way was able to be implemented faster and by fewer people as a stop-gap measure

Theres no such thing as "real stainless". Stainless steel 304 is corrosion resistant, it's the cheapest and most common. 316 is better at corrosion resistance and is "marine grade" since it will hold up better to salt water. 316L is some of the best at resisting corrosion, it's more expensive than 304 and is used in lab and surgical equipment. There are a lot of other types, like 309 for higher heat applications, etc.

Cybertruck is probably made from 304.

Definately not supprised that cybertrucks are having this issue. Especially with road salt in the winter. I'm sure the engineers at Tesla saw this coming too.

Well prepared to be failed again https://www.digitaltrends.com/computing/opera-sold-600-million-chinese-consortium/

With temps that high in Linux and Windows, it almost sounds like the AIO water block is falling off the CPU.

Plasma 6 is built using QT 6, currently plasma 5 is using QT5. This is a huge effort to move the code to the new version of QT but it brings many improvements behind the scenes. Once this is done a lot of the code is going to be cleaner and more maintainable, which should translate to a smoother user experience.

Here's the plasma 6 wiki: https://community.kde.org/Plasma/Plasma_6#Work_that's_been_decided_on_but_not_implemented_yet