Article suggestions: Difference between revisions
→List of incidents not yet covered: Add Atlassian forced cloud transition |
→List of incidents not yet covered: Add reports of Google delaying Android security patch sources to harm custom roms |
||
| Line 278: | Line 278: | ||
|Users forced from on-premise to cloud only subscriptions | |Users forced from on-premise to cloud only subscriptions | ||
|<ref>{{Cite web |title=Ascend to the cloud: The next chapter for Atlassian and our customers |url=https://www.atlassian.com/blog/announcements/atlassian-ascend}}</ref> | |<ref>{{Cite web |title=Ascend to the cloud: The next chapter for Atlassian and our customers |url=https://www.atlassian.com/blog/announcements/atlassian-ascend}}</ref> | ||
|- | |||
|Google | |||
|Google apparently plans to reduce the interval of publishing source code of security patches they consider non-critical. This is another blow to the custom ROM community. | |||
Right now we don't have these incidents organised chronologically, maybe we should have a table with a timeline of measures Google takes to enshittify and close down Android (more APIs moved to Play Services, Developer verification, withholding AOSP device trees for Pixel devices to mess with Graphene OS, now delayed source code disclosure). What's worst, they always cite safety as a reason. | |||
|<ref>{{Cite web |title=Exclusive: Google wants to make Android phones safer by switching to ‘risk-based’ security updates |url=https://www.androidauthority.com/android-risk-based-security-updates-3597466/}}</ref> | |||
|} | |} | ||