Hacker News new | ask | show | jobs
by zepto 2023 days ago
Is it already usable?

The repo says it is unfinished, and commits seem to have stopped a year ago. It looks like it has been abandoned.

Has it been used in production somewhere?

1 comments

Here's yet another option that does essentially the same thing but doesn't provide a reference implementation for self-hosted push server. https://github.com/onepf/OPFPush/tree/master/samples/pushcha...

I wouldn't be surprised if Amazon has their own internal implementation of the same thing to use in their Android apps.

So, no. It’s not already usable and there are no complete alternatives you can point to.

You speculate that Amazon may have an internal framework for this, but so what? Even if your guess was correct, that’s not AOSP, and it’s not open.

Your statement that AOSP ‘already does’ this simply isn’t true.

It seems like you don’t distinguish between things that are possible in principle, and things that are actually true.

You're essentially suggesting that Android should have Tor built in. The point is that it's possible to use other push services on Android and has been done, just like it is possible to use Tor on Android. There is no reason that AOSP itself needs to implement Tor any more than Windows or AOSP needs to provide a push API. Both are possible to implement on top of the platform and have been implemented on top of the platform.

This is unlike iOS, which is the real broken platform.

Why are you talking about iOS?

Also who said anything about Tor? What relevance does it have?

Of course any open source project can have features added in private. Those are not part of the platform.

It’s certainly not true to say those features already exist in the platform, as you falsely tried to claim upthread.

It also doesn’t mean you can add them to the platform if the maintainers don’t accept them.

As I say, you are confusing what is possible in some other reality with what is actually true.

Push messaging is a service, just like anonymous proxies are a service. It doesn't make sense to put them into a platform if they can be built on top of the platform. It would make sense to put something like this into iOS because it can't be built on iOS. It doesn't make sense to put it into AOSP.
Earlier you said AOSP had a framework for push notifications, a statement found to be false when checking the links you provided.

Now you say it doesn’t make even sense to put this feature in the platform, confirming that you were lying when you said it already was part of the platform.

Why are you talking about iOS?