Technology

2414 readers

376 users here now

Which posts fit here?

Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.

Rules

1. English only

Title and associated content has to be in English.

2. Use original link

Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.

3. Respectful communication

All communication has to be respectful of differing opinions, viewpoints, and experiences.

4. Inclusivity

Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

5. Ad hominem attacks

Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.

6. Off-topic tangents

Stay on topic. Keep it relevant.

7. Instance rules may apply

If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.

Companion communities

[email protected]
[email protected]

Icon attribution | Banner attribution

If someone is interested in moderating this community, message @[email protected].

founded 1 year ago

MODERATORS

[email protected]

Google makes Android development private, will continue open source releases (arstechnica.com)

submitted 2 weeks ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

Google says this change will simplify things for developers and OEMs.

all 6 comments

sorted by: hot top controversial new old

[–] [email protected] 26 points 2 weeks ago* (last edited 2 weeks ago)

Google continues to do everything they can to close android down and force everyone to use their os directly. Imo this is a direct attack on graphene OS and anyone based on aosp. Now for every release developers will have to manually merge basically an unusable mess of changes.

Edit: https://discuss.grapheneos.org/d/21231-google-will-develop-the-android-os-fully-in-private Might not change anything actually.

Seems like graphene is already merging based on tags vs individual commits. It's also not like google is letting anyone (graphene) merge commits into android.

Iirc the graphene developers have basically given up on up streaming some changes because google doesn't actually want many of the security fixes/ changes graphene devs make. Their faq still says they'll try to upstream stuff, I wonder if this will impact that. https://grapheneos.org/faq#upstream

[–] [email protected] 17 points 2 weeks ago

There's little need for them to hide their development work like this. They just don't want to take the time to adopt a FOSS-friendly process that keeps the community in the loop early.

[–] [email protected] 5 points 2 weeks ago (1 children)

So, when will we have a proper open os for phones and what is the biggest problem here? Should we wait for EU to force google to dismantle the Play Store?

[–] [email protected] 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

The main challenges I can think of is lack of native app support, phone hardware being pretty proprietary, and lack of carrier compatibility. Any truly open phone OS would have to emulate Android or iOS apps which would be very demanding on resources. Or just exclusively have web apps and fully open source apps of which there are very few for phones. Then you’d have to reverse engineer the chips that talk to the towers and/or get cell carriers to release firmware. Just overall a mess that has basically translated into the smartphone market being dominated by megacorps.

[–] [email protected] 2 points 2 weeks ago

sigh