one of the best

(link in alt text)

And then for no good reason a “FOSS” app’s binary grows by a couple MB…

>no GUIX, Parabola or Gentoo on a DRMed SaaSS platform
fitting

simple is often the opposite of easy

Good that you’ve enjoyed it. But a fundamentally wrong thing about systemd is that it is actively harming the best thing about Linux – freedom. Some programs won’t work on a non-systemd distro because how tightly coupled and vendor non-agnostic anything that becomes dependent on might become at times. Of course it’s not as bad as glib(loat)c, but still if something can be done without any degradation of functionality via standard POSIX facilities, WHY either incur additional maintenance overhead for non-systemd implementations or punish people for their computing choices if there’s no one to maintain it?

systemd is more like, uhh, ignition that takes care of way too many things beyond starting the engine

*devuan, artix or alpine

*keys and *omas are more fun though. mastodon’s way too businesslike to encourage a fair share of people to pick it over shitter (it works other way around as well tho)

will this affect invidious/piped?

imagine using an sms app that requires network access

Apparently there are multiple crates but no official toolchain so unsure how that works in practice. You’re still limited to either waiting for hours or cross-compiling though since currently the best available RISC-V CPU is quad-core 2.5 GHz (which still looks hella promising, 2 years ago best we had was 1.5 GHz dual-core). This blog post by Drew DeVault goes into detail of how daily driving RISC-V looked like 2 years ago. I suppose these days it looks noticeably better, especially since Samsung and Apple have been eyeing RISC-V adoption due to ARM consortium doing some monopolistic shit with their licensing. But eventually, so far, not enough critical mass was attained and afaik the whole drama mellowed out a bit.

Regarding the energy efficiency, some experimental units managed to even be manifold better at this:

https://arstechnica.com/gadgets/2020/12/new-risc-v-cpu-claims-recordbreaking-performance-per-watt/

But on the other hand, studies involving some RISC-V models show quite the contrary when it comes to energy efficiency, although the thermal performance is much better:

https://link.springer.com/article/10.1007/s11227-024-05946-9

And below is a screenshot from a comparison by Gary Explains using more microcontroller models. So it really depends on the specific model, but it seems like the design of RISC-V has some solid potential to beat ARM in terms of energy and thermal efficiency.

I agree with you that every proprietary software must be presumed to be a trojan with a backdoor but still some critical, low level free software being decades old C codebases with oftentimes millions of LoC has proven to be a double-edged sword where on one hand most of it is super optimized (just compare launch times of lightdm or GDM to e.g. regreet) but on the other hand by pure probabilistics it’s more likely to contain some vulnerabilities accumulated over the years of imperfect code reviews.

Sure I believe it’s worth hoping and supporting initiatives that might one day bring us to something like RISC-V smartphone with high level of hardware security that’d run something like Alpine (a minimalist distro) but based on Redox OS. Maybe that’ll come true in a couple of years.

But right now GrapheneOS even despite proprietary hardware is the best option security-wise, unless you’re willing to tinker with hacking together some RISC-V SBC-based device (which might even have better battery life than most smartphones by up to 60%!), but the optimization of basically any software is going to suck so badly. And forget compiling any Rust code on the currently available RISC-V CPUs. want memory safety? pick something with a VM/GC instead.

AOSP is not proprietary. Also security is not achieved merely by the merit of being libre, see CVEs for sudo, glibc or Apache HTTP server or even the Linux kernel itself.

And when it comes to proprietary firmware updates, in case of x86 one such notable example is the microcode which is pretty important to keep updated for security.

on Firefox if a desktop addon has no mobile version you can look up how to add custom add-ons collections when it comes to cookie prompt blockers, but ublock origin and adding filters to it work out of the box. Recently also some apps started showing cookie prompts with no option to decline unless you pay, if they can work offline, make them so

bring them in to !WallStreetBets@lemmy.world

This is a centralization problem. Come and force federation upon my SimpleX server in Iceland!

just get an extension and adblocker filters to automatically dismiss/block cookie dialogs and use an allowlist for sites from which you actually need to persist cookies in your browser’s settings and set your browser to delete everything else on exit. With Firefox and browsers based on it you can, in addition to that, use container tabs (try sticky containers extension) for even better context isolation.

Pinephone doesn’t have features like IOMMU isolation or even verified boot. Also as a matter of fact, permission control, unless you’re using flatpak/bwrap/firejail is actually better on Android than Linux. Plus long before the first usable part of Linux written in Rust was released, large parts of low level AOSP code were already rewritten in it.

https://madaidans-insecurities.github.io/linux-phones.html

oh sorry then, thought it works like some radar, don’t know what the proper name is for what I’m thinking about then. I’m not a mobile dev so I could be wrong.

to find restaurants close to a courier

https://grapheneos.social/@GrapheneOS/111957964224325239

https://grapheneos.org/faq#future-devices

https://grapheneos.social/@GrapheneOS/111738765361100063

https://grapheneos.social/@GrapheneOS/111676448278523353

https://grapheneos.social/@GrapheneOS/111676423446810227

https://social.linux.pizza/@piracyy/111712189066209594

https://grapheneos.social/@GrapheneOS/111975424959573607