• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle


  • There are good reasons not to federate, Legality is kinda murkey when it comes to stuff like this. Federation could (not saying it would) be used as a weapon against them. I mean, there are all sorts of instances on the federated networks, many of which do not comply with US law. Not just the real shitty stuff, But even instances that just don’t care about DMCA for instance. It could simply be that Federation is just way too much of a hassle, which I really couldn’t blame them. I did try to host my own federated service instance and it was just kinda too much.


  • Working with android can be a bit of a pain for sure. I’m only talking about android here since that’s all I’ve tested, so don’t apply what I am saying to chromium, Android and Chromium are two seperate projects, by two separate teams. but in the end it’s important to realize that google has actually needs for these devices. As long as you work within the bounds of needs it’s actually not that hard to actually work with. Android has a LOT of stuff for sure.

    Android actually allows you to configure most things (granted the documentation is absolutely horrid, Grep my beloved). It is true that most android phones are running proprietary stuff, but this isn’t really any fault of google. Google has gone to fairly great lengths to make AOSP a fairly open ecosystem. Nearly every rom is heavily customized as per customers requirements. AOSP can actually run on most hardware fairly easily. Hell it even works just fine on the vanilla kernel (Waydroid for instance). The Issue is that it’s nearly impossible to market consumer devices with only FOSS/AOSP stuff, the margins on phones are actually terrible. The biggest issue is finding a phone that can accommodate the more open stuff, not the issue with google pushing crap. In the end Google is making devices for people who will fight tooth and nail to grab the gun to shoot themselves in the foot. A lot of their motivations are based on that. But doing your own AOSP is still easy enough. Just need hardware for it.


  • Chromium and AOSP are not good examples for what you’re saying. Both Chromium and Android have thriving ecosystems of forks and alternatives based on them. Built on the work that Google is doing with them. So I really don’t think those are good examples of applications that aren’t healthy because you can just use a fork.

    Yes, Google controls upstream, but there’s no reason why you can’t use downstream.As you said, it puts maintenance burden on the forks, but people are willing to do that. That’s the thing.

    EDIT: This is my off account, So, unfortunately, you’ll have to take my word for it, but I did used to be part of an Android ROM team in the past and still do Android work private sector today.