@sodiboo@autumn doesn't AOSP only update twice a year now? (At least thankfully it's twice a year and not never, yet.) So all the grapheneos updates are security updates (+ changes to grapheneos-specific things), while for new android features you'd have to wait for half a year.
@IngaLovinde@autumn Oh yeah. I guess so. That's probably why we haven't gotten it yet.
but updating fonts hardly needs to wait on Google to do it. i get that grapheneos has better things to do, but font support is kind of a user facing thing where GrapheneOS is Simply Outdated right now. it's not like Noto Color Emoji hasn't published a new version yet. update the damn fonts, lol
@sodiboo@autumn from what I understand, grapheneos = aosp + patches, and it's not just that grapheneos maintainers have better things to do than update fonts, but also that "updating fonts" means increasing the scope and the size of that "patches" part of the equation, and its scope might be too big already. (And also there needs to be a clear line between what belongs to "patches" and what doesn't; bringing updated fonts across this line blurs it and potentially expands the scope even more because there are many other features that are just as important as updated fonts.)
It sucks that AOSP is outdated, and the pressure here should probably be on Google which decides to make it progressively outdated (going from publishing the code frequently to once a quarter to twice a year).
And also there are other AOSP-based projects which have larger scope of their "patches" part, at the expense of certain other things, and I guess you're using grapheneos instead of these other projects for a reason.
@IngaLovinde@autumn Yeah. You're right. It's Google's fault. I also don't think we should be pressuring GrapheneOS to do anything about the emoji; but i will reiterate that it seems like it should be a fairly trivial task. like, i guess this mentality can't be applied to all the cosmetic papercuts because suddenly you have a Customization Overhaul Shaped Workload. but the one instance of it couldn't hurt that much. right?
I am indeed using GrapheneOS because it's stable and focuses on the stuff that really matters. crucially for me, it promises long term support for a particular device. I've had some bad experiences with other distros that just stopped supporting my device. and then i received no security updates whatsoever. :(
1❤️1
1