Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DR
Posts
0
Comments
465
Joined
2 yr. ago

  • Keep in mind that other reputable repos like izzyondroid still work, fdroid is more then one thing. We wont loose the apps, nor the 3rd party repos, the only thing really "at risk" here is the official fdroid repos.

    this isn't like some closed source stuff, the entire fdroid ecosystem is fully foss so anyone can sweep in at any time and do their own thing while still being mostly or completely compatible

  • well, I'm not sure traditional is the right word, multiseat has been used for a very long time. It used to be a bit better supported. The issue is that since the migration to wayland, it has become... a lot less supported. It is still possible, but most of the guides are x11 guides for a reason.

    EDIT: I should say I hope seatd at some point could support multiseat but at the current time I don't think it has any facilities to, systemd-logind / elogind do support multiseat, but I dont currently use them

  • I generally don't really think this is the case, there are still plenty of apps from other languages in QT. in fact, for cross platform apps, QT is immensely more popular then GTK is. Rust itself had disproportionately less apps developed in QT then other stuff, (Python for instance). especially when you consider cross platform. and at least for open source anyways. closed source I cant comment on

  • a few reasons I think, the QT bindings are split between cxx-qt and qmetaobject-rs . Neither of which are super great IMO, but even if they were, we have UI frame works like slint and egui which are already becoming quite good, slint has a good native look that resembles QT so people wanting that design can use that instead.

  • I never said they worked perfect. The fact that they work at all is a goddamn miracle. Have you ever read some of the specs for all the things they have to support? It's absolutely absurd.

    Them working good is relative to literally anything else. I could go on for list for days about issues on almost anything. Linux, Windows, OSX, Gnome, KDE. It doesn't matter whether something has problems or not. What matters if they're the best that you can get.

    Literally, no other browser is remotely close to Firefox and Chrome in terms of how well they actually work. Not a single one. Full stop. End of story. Forks excluded for obvious reasons.

  • nah, there are legitimate concerns around chrome's privacy stuff, a lot of people would be fine if they could run cromite or one of the privacy centric forks. the main issue is that vendors for some reason lock down webview to the google play store provider. I presume this is due to some false security notion around a bad webview being installed. but that would be a lot of steps so...

  • what do you mean by secure, as far as "is it safe to use this browser" then yes, webview is reasonably secure, it's still running chrome. you have all of the security benefits and everything else, wont have to worry too much about malware or anything else. however if you mean by private then well, it's chrome. everything that sketches people out about chrome is all there too

  • it's not unheard of, multimedia is actually a pretty decent target, however this is due to a lot of media libraries being ancient even in deployment (see the libwebp stuff recently in chrome). However with stuff like mkv which is something that gets updated often, the risk is significantly lower so long as one is up to date. There are lots of people running outdated software which could be susceptible to these attacks.

  • is there a way to be certain? not absolutely however simply being up to date will make the risk pretty much negligible. you probably have a higher risk of catching an STD from eating food after a day of wearing gloves and other protective gear