AProfessional @ AProfessional @lemmy.world

Posts

0

Comments

651

Joined

2 yr. ago

Many toolkits make dbus usage simple. It’s also introspectable so very easy to explore or generate bindings for dynamically.

It’s pretty nice to use IME.

EAC does support Linux and can be enabled. It just isn’t as secure.

Yes they use kernel level anticheat and they are correct it would be easier to cheat on Linux.

The Nvidia drivers perform fine generally but it would be nice to verify it.

Phones are very dynamic devices constantly migrating between unknown networks, they suck as a server.

Plus the whole point is to control device wakeups. The opposite is true for a server.

Verizon has prioritized traffic so other carriers get faster speeds than Fi over the same network.

Fi hasn’t been competitive in many years anyway. You can get more and faster data for cheaper.

It is usually easy to detect a specific client. Like even if you ignore the keys there are dozens of little details like the TLS fingerprint of whatever library they use not matching iOS. Things that are easy to miss and sometimes hard to bypass. Then there are heuristics on how it is used is likely unique.

I’m not saying it’s necessary but “some raytracing“ is very little, the next hardware refresh will be a lot more raytracing.

Safari has supported mv2 extensions for years and recently added mv3 support.

However it never supported WebRequest blocking.

Brave claims they will maintain it in their fork but that won’t last long.

Developers don’t need to keep mv2 support, Firefox supports mv3 plus extra APIs on top.

Tables like this suck. They are made by one of the projects in the comparison and they include no data.

The bug is that they parse a glib keyfile with configparser which is a different format. So what is valid in one isn’t in the other.

More annoying because Mozilla does publish the stable flatpak, just not betas.

Flashback is based on old GNOME 2 code but unlike MATE it’s not maintained or improved.