OnlyOffice, not OpenOffice. This is a different suite entirely. Might be better for people coming from MS Office, since it looks practically identical. Also supports opening multiple files as tabs.
DupaCycki
joined 1 week ago
I'm a huge fan of Pine64, but I wouldn't expect the PinePhone to be a great replacement for an Android smartphone. Personally I have quite extensive experience with PineBook Pro, PineTime and PineBuds Pro. I haven't had the chance to try the PinePhone, but I'd definitely go for the Pro.
Even then, prepare for a junky experience and forget about lixuries such as good camera, nice screen, smooth UI/UX. Their devices are great, and the ideas behind them more so. But unfortunately they rarely work well, perhaps with the exception of PineBuds Pro.
Good point. Sometimes it helps to read properly
no more locked bootloader
Likewise modifying the bootloader requires unlocking it - which means no more secure boot and anyone who takes your phone can happily boot whatever they like on it. This is also bad.
Except for Graphene. The last step in the installation is locking the bootloader back, and the phone clearly says it's locked.
As of right now, it's looking like GrapheneOS will be unaffected, and Google has yet to lock down the bootloader. So this should remain a valid option for at least 2 years.
Other than that:
- Any smartphones with an unlocked bootloader + any ROMs without gapps
- Chinese smartphones with non-Google Android builds
- Linux smartphones
- Bonus: Huawei is about to release their own non-Android OS, but I wouldn't expect it to be privacy-friendly
Honestly there probably isn't any good, long-term solution. Personally I'm somewhat shocked we've gone this many years with reasonably open smartphones. Next step is probably closing bootloaders in new laptops, as part of the switch to ARM (which is already undergoing).
It's very likely that no amount of negative feedback will change anything. Why not waste some of their time anyway? Write to them, call them, spread the word. This is the only thing we can do. Even if it goes through regardless - at the very least we can make it as unpleasant as possible.
Two things especially worth noting from the article.
If you have a non-Google build of Android on your phone, none of this applies.
This means that at least GrapheneOS will be unaffected for now. Other ROMs without gapps will be unaffected only as long as you don't install gapps. Since Graphene has a sandbox for them, I'm assuming it'll be fine. That is, unless Google decides to lock the bootloader entirely.
In September 2026, Google plans to launch this feature in Brazil, Indonesia, Singapore, and Thailand. The next step is still hazy, but Google is targeting 2027 to expand the verification requirements globally.
So most users worldwide still have at least 1.5 years until it's implemented. Plenty of time to get a Pixel and install Graphene on it. Or to figure out some other plan.
Don't get me wrong - this is insane, unreasonable and horrible news for everyone. We should push back as hard as physically possible against it. However, at the very least we still have some time to figure things out before the policy rolls out.
This is the law in all EU member states. What the article is discussing is different. Technically, a deepfake of you is not a photograph of you, unless you can reliably prove that a photograph of you was used to create it. Of course, it had to be, but a court will never accept "that's how deepfakes work" as evidence.
The new Danish law is forbidding anyone from making anything that closely resembles you, meaning nobody can make a deepfake of you, regardless of whether or not it's proven that a real picture of you was used. Just like you cannot create anything that closely resembles any other copyright-protected content, regardless of whether or not you use any of the original creator's material in the process.
(...) it was all avoidable.
It really wasn't. Everything in American politics for long years has been leading to this point. It was always bound to happen, sooner or later. Sure, by choosing another president you could have potentially delayed it by a few years. But later it would have happened anyway. This is not a 'Trump issue'. This is a 'USA issue'.
I think Americans are the only ones who haven't seen this coming. And I don't mean that in a hostile way. Your education system has been sabotaged for decades, so it's no wonder the people are uninformed and ignorant to what's going on. The only ones to blame are the psychopathic politicians and billionaires who deliberately made this happen over the last 200 years.
(...) if Russia can't even win against Ukraine how would they ever fight against the EU, our army is both larger and much better equipped then Ukraine.
The problem is, the EU isn't united nearly enough to fight a war together. If, for instance, Russia attacks, it'll be mostly Poland, Lithuania, Latvia and Estonia defending. Maybe Romania too, and maybe with some support from the rest of the EU. As it stands right now, the EU is divided on many issues, with some countries (notably Hungary) intentionally sabotaging it from the inside.
Even if - and that's a big if - all or at least most of EU member states can come to agreement and cooperate in a conflict, our militaries aren't very well prepared to work together. This would require years of cross-border military drills between all of the member states. Especially considering the fact that the vast majority of all EU soldiers have never seen any real combat. Russia may be losing a lot of soldiers in Ukraine. But those who survive become extremely valuable assets for the military, since real world combat experience is infinitely more useful than textbooks or casual training exercises.
You're also massively wrong about DirectX on Linux, DXVK and VKD3D both work to run various versions of it on Linux.
I very clearly wrote that Linux does not support DirectX. Which is 100% true, no matter how you look at it. Just because there are translation layers, it doesn't mean Linux 'supports DirectX', because it doesn't. It supports Vulkan, which DXVK and VKD3D translate DirectX API calls to.
Let's say you can't read Spanish, but you hire a translator to translate a text for you. Now you can read it. Does that mean you can suddenly read Spanish?
view more: next ›
One of the most cozy setups I've ever seen. Except whatever it is surrounding the cable in the top right. Kinda disgsuting looking.