jarm0

6 ms·

1.
by jarm0 3mo ago
According to https://metastatus.com/ only "Facebook Ads Manager" is having problems.
2.
by jarm0 3mo ago
"I'll just do this small release on a Friday before heading out" - thought a software engineer before AI-slopification period. Today it was probably some AI agent which fixed all of the performance issues by deleting everythi
3.
by jarm0 3mo ago
downdetector seems to be working now again, spikes clearly visible.
4.
by jarm0 3mo ago
In what situations does it even go for 404? Same for Messenger and Instagram. Never seen that before.
5.
by jarm0 3mo ago
Nope, all dead for me.
6.
Show HN: Candalf – a simple tool to manage Linux/Unix-like systems via shell+SSH
2 points by jarm0 5mo ago|0 comments
7.
OpenAI's O1 just hacked the system [video](youtube.com)
2 points by jarm0 2y ago|0 comments
8.
by jarm0 2y ago
I've also used Netdata for years on many servers now. One of the problems with it is its way to fail silently when some healtcheck or alarm is configured badly instead of erroring out on the process start. I understand the reasoning be
9.
by jarm0 3y ago
Creating complex software is not at all complicated, and sometimes it is done right at the beginning of a project, even before solving a single business problem.
10.
by jarm0 3y ago
Double-checked - no e-mails prior 18th of August from "Google Play Console". Also, double-checked "Google Play Console" (even under "Archived messages") - first message about deprecation I see is from 17th of A
11.
by jarm0 3y ago
But this is also kind of a problem created by Google - why force from 30 to 33 and not force from 30 to 31, then 31 to 32 etc? Gradual API level upgrades would make more sense in my world and probably would be less risky for every party.
12.
by jarm0 3y ago
Not sure this can be used to "save to home screen" e.g. trigger PWA installation flow like on Android.
13.
by jarm0 3y ago
What do you mean by that? Are you effectively trying to say that allowing upgrades does not have any risk of attack surface? I'm pretty sure that updating things have also a pretty high risk on introducing new previously non-existing s
14.
by jarm0 3y ago
I'm the OP and thank you for thinking along with me here. As stated in numerous replies already then I totally agree that I could have done better in terms of testing things out - of course, there's always room for improvement in
15.
by jarm0 3y ago
I'm the OP and wanted to clarify in case you missed some points - it is a legacy application which does not have any active dev teams on it and needs only developers attention when Google says so and as mentioned by multiple other comm
16.
by jarm0 3y ago
Actually nowadays it's not that bad anymore. Android browser itself offers installable PWA and there is an event called beforeinstallprompt event ( https://developer.mozilla.org/en-US/docs/Web/API/Win
17.
by jarm0 3y ago
Typical "legacy application situation where no team is assigned to" here. At least I've never seen in my 15+ year career a legacy application, which has a very good maintenance/testing model in place. It will just not wo
18.
by jarm0 3y ago
It's true that in the future I would do some more thorough testing, but never-ever for this legacy application can I build a bullet-proof automated testing solution - there will not be a budget for that for sure. However, even with a f
19.
by jarm0 3y ago
Totally understand that a roll-back is more complex, but it doesn't explain why pulling back/pausing/deleting/yanking a release is not possible either - customers who got the newest faulty release can uninstall & ins
20.
by jarm0 3y ago
A-ha - good tip about roll-out, uninstall & install. Was not aware of that possibility. But yeah, it's still a hack and there should be a better way - just let me delete/cancel latest release even if roll-out is 100% for whate
21.
by jarm0 3y ago
I agree that things could have been done better in many ways. However, as explained, it is a legacy application, which does not see any active development nowadays and it would just not make sense to build such a robust QA. This particular
22.
by jarm0 3y ago
Agreed about conflicting message. And even better - e-mail was pretty vague and had to Google a separate link ( https://support.google.com/googleplay/android-developer/answ... ) for more info. If I could go back in
23.
by jarm0 3y ago
Yes, that's definitely one side of the problem and I'm not chasing too much backwards-compatibility. My biggest concern in this particular situation is that there is no way (with Android, at least) to pull-back/cancel/ro
24.
by jarm0 3y ago
Agree that not everything can be web-based and your list of apps seem to be non-typical if there exists a list of typical apps of course.
25.
by jarm0 3y ago
But how does that help end-users? They would still need to know that they need to use different store etc. It's a pain. At least Android allows (relatively) easy side-loading APK's for the most critical situations, but for iOS tha
26.
by jarm0 3y ago
It was working with Android 12+ before without problems. Upgrading API target level made some flags mandatory (for PendingIntent to be specific), which throw RuntimeException. But as I also wrote in the article itself then this is a legacy
27.
by jarm0 3y ago
Good point, but as I also wrote in the article then one and only reason for doing anything was an API level deprecation e-mail from Google less than 3 weeks from its deadline and it states that review could take a week (never happened befor
28.
by jarm0 3y ago
Yeah, that's also true, but at least this kind of problems can be handled by a roll-back or whatnot. Situation we're currently are in does not allow to do anything while we know that bad build is in production and phones are updat
29.
by jarm0 3y ago
Thanks for the tip!
30.
Prisoners of Google Android development(solutional.ee)
427 points by jarm0 3y ago|310 comments

More ›