-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APK files #156
Comments
Any chance, @jasoncheng? Are you still maintaining the app (not much activity here lately)? |
@jasoncheng ^^ ping – are you still there (and hopefully doing fine)? |
Hi, long time no see, sorry for the late to reply; |
Yeah, has been some time… I'm not on Friendica and not a dev, so I cannot tell about the API. But I'm glad for everything that makes the Fediverse grow 😄 In a case of emergency, even when it's written in Flutter or RN (where a simple "Hello world" results in a 5 MB Best wishes for your carrier and a stable job then (first things first, if not necessarily in that order 🤣) – and look forward to the rewrite! |
Hi @jasoncheng just a friendly ping: any news? Or shall I rather mark the app "currently unmaintained" and wait until you possibly find time for it? No bad feelings, just wanting to keep things transparent for the users. And it makes no sense to permanently annoy you with my pings if you cannot work on it anyway. |
Another half year, another friendly ping: Will you pick up again, or did you give up, @jasoncheng ? |
Yikes, more than a year again. I don't even know if that last release is still working, and no life signs from you, @jasoncheng 😭 Guess I'll have to remove your app from my repo for now and wait for your ping should you pick up again? Or does it really make sense to keep the old version up and wait? |
May I suggest you attach the APK files to your releases instead of storing them in a separate branch? Keeps the repo more compact and makes it easier to find them (plus my updater has it easier to fetch them (see #98); Github API has its limitations, unfortunately).
In case you are unsure about how to do that, please see Creating releases in the Github documentation.
The text was updated successfully, but these errors were encountered: