search

codyogden / killedbygoogle

Part guillotine, part graveyard for Google's doomed apps, services, and hardware.
https://killedbygoogle.com
MIT License
2.46k stars 385 forks source link

Android clipboard API #1417

Closed remcohaszing closed 5 months ago

remcohaszing commented 1 year ago

What's the Product's Name?

Android clipboard API

Describe the product in a single sentence.

Allow apps to access the clipboard

When was the product launched? Provide a specific date, if possible.

N/A

When was the product discontinued? Provide a specific date, if possible.

January 2022

What type of product was it? App, Service, or Hardware?

Android API

In 2018, Google release Android Pie (9). In this version, they removed the clipboard API, rendering many apps less useful or even useless. They say it’s a security feature, but their own apps (Google Chrome / Google Translate) still use it. (Do these apps classify as malware now?) Up to this day hundreds of users are begging Google to bring it back via https://issuetracker.google.com/issues/123461156.

Lenni-builder commented 10 months ago

I don't think this would fit into the list, since it's an API, not really a product.

mollthecoder commented 8 months ago

I don't think this would fit into the list, since it's an API, not really a product.

image image image image image image image And more.

github-actions[bot] commented 5 months ago

This issue is stale because it has been open 90 days with no activity.

Lenni-builder commented 5 months ago

This issue is stale because it has been open 90 days with no activity.

Please remove the stale bot. It just causes unnecessary messsages and like "+1" which unnecessarily fill up issue trackers.

Lenni-builder commented 5 months ago

How is this "completed"? Did the stale bot automatically close it? There should be proper discussion before closing an issue. Please reopen it.

mollthecoder commented 4 months ago

I do agree it's not really clear why the issue was closed. If an issue is being closed there should be a description from the person/bot closing it describing why the issue is closed, to avoid confusion. I also do agree that this issue should be closed after being discussed, not from lack of discussion. With code contributions stale bots can allow old bugs that are no longer valid to be removed from the issues list, however in this case it really doesn't make sense. A product that's been killed will (almost always) stay killed, no longer how long you wait.

Lenni-builder commented 4 months ago

I do agree it's not really clear why the issue was closed.

It is clear, the stale bot closed it since nobody spammed this issue with unnecessary "+1" comments. Instead of automatically closing them somebody should always manually check if the issue/feature request is still valid, no matter what kind of repository it is.

mollthecoder commented 4 months ago

I do agree it's not really clear why the issue was closed.

It is clear, the stale bot closed it since nobody spammed this issue with unnecessary "+1" comments. Instead of automatically closing them somebody should always manually check if the issue/feature request is still valid, no matter what kind of repository it is.

It could have been any Github Action as far as we know. It just says "github-actions", not the stale bot.

Lenni-builder commented 4 months ago

Most stale bots are just scripts for GH actions. So yes, it was GH actions, but a script (or whatever it's called) that makes it a stale bot.

Edit: It's called a workflow and you can find the stale workflow here: https://github.com/codyogden/killedbygoogle/blob/main/.github/workflows/stale.yml