• 0 Posts
  • 44 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle

  • No, it’s completely different.
    In most eastern bloc countries, communism is often associated with external oppression.
    In Spain, fascism was a local phenomenon and the current democracy comes from a voluntary transition from fascism, so there has never been a purge of fascism in Spain.
    Even today there are lots of pro-fascists in major political parties, and there is a not small amount of nostalgia.
    I would say, generally, the feeling in Spain about fascism is comparable to the feeling in Russia about the USSR.
    Obviously there is also a strong anti fascist movement, but in lots of big cities it’s not strange to see fascist flags on some people’s balconies.



  • They’re not wrong.
    Of course you can fork and have full control over your fork, but Graphene and company want to be able to keep merging AOSP’s code to keep up with features and improvements.
    Merging code from a divergent codebase is harder the more divergence there is, and with big codebases it can easily overwhelm small and medium-sized teams.
    It’s the same reason there aren’t lots of chromium forks with manifest v2 support, while it is technically feasible, it requires a bigger effort than most projects can afford.
    Keeping an open AOSP fork is not a bad idea, but it’s not clear whether GrapheneOS or any other project will be able to keep up with that workload.
    Of course Linux phones require a lot of work too, but it’s work oriented towards making it work instead of towards undoing whatever sabotage google ads to AOSP, so it might motivate more people or be easier to do.
    Also, both approaches are compatible.
    Linux phones can use waydroid, which depends on AOSP, to run Android apps.















  • That’s obviously not what enabled means, at all.

    If there is a button visible that executes a function when receiving a click, that feature is enabled.
    That does not mean that the feature is actively in use, of course. Enabled and active are different states for a program’s functionality to be.

    I believe it’s pretty easy to understand, there are people like me who don’t want to have AI functions popping up in our browsers without explicit enabling on our part.
    I understand that you disagree, but it is not a difficult position to understand.

    You don’t need to re-define opt-in and opt-out just because you support Mozilla in adding AI features to Firefox.