The e/OS/ CEO said during an interview [1] that GrapheneOS, being a security hardened product, was especially useful for p*ophiles to evade justice. This is totally unacceptable. People defending e/OS/ (and Murena, same people, just branding for devices) are either dishonest or useful idiots.
If you can, try again (don't forget to start with `./mach bootstrap` to install dependencies) and open an issue if the build fails. SpiderMonkey is shipped pre-compiled for most architectures, so it's not a big hurdle in terms of build time.
A pure AOSP distribution is now lacking a lot of basic apps. Distributions like LineageOS or GrapheneOS fill the gap with their own, but pure AOSP is totally unusable.
Googles been quietly chipping away at AOSP for years. There was a point where AOSP was actually decent, google made sure that wasn't the case for long.
Technical problems give way to philosophical differences but the over-arching problem is that the people behind ATProto really want to make a social media ecosystem that attracts lots of average people who will refuse to understand that the solution you're giving them can't do things Twitter could do back before Musk bought it. People get angry enough at Bluesky not having an edit button, and it's at least possible to talk about how editing can be abused.
An "AppView" is the API server that most clients connect to that aggregates data from the network and serves it in a more useful way. mu.social still uses bluesky's AppView (api.bsky.app).
The name is confusing. I thought clients were appviews myself for a while.
I kind of started calling them all “apps” with true appviews being “independent apps”. I think sometimes it makes sense of think of this as an implementation detail. For example, Mu could actually switch to its own database if they do a bunch of technical work in the future. From the users’ perspective, it wouldn’t be noticeable.
I don't believe this is a good solution: users will obviously click on that add-on install dialog box without being better informed and protected against malicious / buggy / attacker controlled web sites.
Hopefully they will move to a better solution that offers some integrity guarantees instead, like https://rwc26.waict.dev/ that they have an early implementation of in nightly builds.
It has build.rs that will run as soon as you compile the dependency. That's not the same thing but pretty close to a post install script: it's very likely to run.
It's very naive to believe the "no influence" part. I will never give to Ladybird given their closeness with fascists. Is that the kind of influence they expect?
[1] https://grapheneos.social/@GrapheneOS/116353973732143171 (full interview at https://www.youtube.com/watch?v=jQV7498NRQw)