Last time i tried plasma mobile it was unbearably slow (even slower then the normal unbearably slow) so i switched to phosh, but I would like to try it again so let’s see if these updates made it any more usable.

UPDATE: Honestly i’m impressed, it might be because currently im not running waydroid beside it like i did on my previous Phosh install but it feels very responsive. With the angelfish browser providing a way better experience then firefox. The battery life is still very bad but outside that this could be used as a regular phone.

And I’m on NVIDIA, so no Wayland for me yet.

4090 user here with nvidia-open and wayland works fine?

My first distro was debian and why I switched was that I wanted up to date packages.

I would suggest Arch with KDE plasma, I don’t have a stylus so can’t vouch for it personally but I’ve seen it mentioned in the update notes alot.

That was a huge rant, i also don’t like the microsoft authenticator so guess what i don’t use it, and the issue of your private keys to getting stolen if your pc is hacked has long been solved with password protected keys.

All of these issues pretty much amount to nothing, the standard works and is more secure then passwords, same reason as to why enabling password login on SSH is not recommended.

I’m trying to understand how this is used, my current selfhosted setup is quite simple:

frontend - backend - vllm

Using the openai compatible api vllm returns with tool calls that need to be handeled by the backend, an results are then send to the frontend by the backend, the frontend never communicates with vllm directly.

Form what i can gather AG-UI is a way for the frontend to directly communicate with in my case vllm in a secure way? letting the frontend handle the tool calls?

Same with modern streaming services, you get awful resolutions on linux without them even telling you when you are a paying customer.

But the pirates get the full quality version no issue.

I’ve used waypipe and it worked in my testing.

I do think some of these limitations can be resolved. But it indeed poses a bit challenge. You can go to big lenghts with server occlusion checking to prevent wall hacks but under zero trust any game with directional sound already has build in wallhacks.

I mostly speak from experience with my developing my own game which is not an FPS. Previously the client would send “i build on this position”. Which could very easily be abused. Which I then changed to “i build with this angle and this distance from the previous node” the client would then already show the newly constructed “ghost” node while the server would check if that construction is valid and then send the real position to all clients. The only thing a player would notice is that with high ping the constructed node would move slightly as it got the definitive position from the server. While being significantly more cheater proof.

I suppose im biased towards this kind of thinking since im not working on a FPS game, what for me might be a simple change is a massive undertaking for other genres.

I do think there is quite an obvious solution that game developers dont yet realize.

The client is always compromised

Instead of relying on increasingly invasine client side anti cheat, with a zero trust mentality it doesn’t matter how many cheats the client has installed.

Ofcourse this is’t easy to do, but its the only thing that actually works, client side anti cheat will always be broken.

I’ve used a pinephone pro with arch and postmarket.

It works, but you really have to love linux to use it as a daily driver.

My banking app (bunq) worked using way droid.

I don’t use mint so this might be blatantly incorrect but after a bit of searching on mint’s release schedule I would assume gimp 3.0 will arrive with the 22.2 or 22.3 version. With 22.2 expected at middle 2025 and 22.3 at start 2026.