댓글 (51)
It has genuine use-cases such as this DoNotNotify app, but could easily be misused - e.g. malware intercepting a wallet OTP notification and forwarding it to the attacker.
Access to the API is controlled by a specific permission which users have to explicitly enable in "Special app access".
https://developer.android.com/reference/android/service/noti...
DoNotNotify gives granularity and rules (which a specific app may have chosen not to implement).
For example:
"Allow <budget airline app X> to display notifications of gate changes"
"Block <budget airline app X> from displaying advertising notifications"Is this for real, like do you really not see the difference? Not tryingto be snarky or sth, just struggle to comprehend this.
You compare apples to oranges here. From a short look at the provided link, i guess it doesn'tcompare at all because it's something completely different?
Link you provided seems to be Samsung or OneUI only, integrated with Good Lock. This seems to collect and present notifications together with the ability to search. Does not seem to be open source.
DoNotNotify allows you to restrict apps to only sending you certain kinds of notifications.
They could supplement each other but you can't compare them as far as i'm concerned.
I created a free and open source set of filters to fix this. Soooo much better.
And, yes, some people will criticise code quality but (a) if those people aren’t actively contributing to the product then you should ignore them, and (b) I suspect the complainers will largely be drowned out by the many who will support your decision.
You certainly aren’t the only highly experienced engineer vibe-coding their way through a problem - I’m leaning very heavily on Claude, and somewhat on ChatGPT, at the startup I’m working on at the moment.
Thank you, Anuj!
Where was the instinct that held you back to reply is such a confrontational way?
Last week I was configuring Samsung for my mother and it constantly nags her with notification for setting up Samsung account (that's not the worst offender tho) and frankly that would really help here.
[0] https://developer.android.com/develop/ui/views/notifications...
FWIW, I suspect there isn't a single programmer you admire that hasn't looked back on moments in their career and cringed at some of their own code.
In some ways, I think it is the hurdle that Linus overcame as an undergraduate that I admire the most. Just putting it out there. This is code. Look at it. It might not amount to anything, but who dares wins.
Hope I find time to contribute :)
for notifications specifically, the risky bits would be: what happens if an app sends a notification payload that's malformed or huge, how do you handle permission checks if the notification system process restarts mid-filtering, and whether the filtering rules can be bypassed by crafting notifications with weird mime types or encoded text.
if you wrote tests for those edge cases (or even just thought through them), you're already ahead of 90% of shipped code, vibe-coded or not. the scrutiny you're worried about is actually healthy - peer review catches stuff automated tools miss.
Your concerns are valid but not unique to AI generated code, the same feeling has existed for as long as open source software has existed: is my code good enough, will I just look stupid when people suggest oversights and mistakes?
The fact of the matter is that if you have created software that solves an actual issue, especially if that issue was previously unsolved, you have created something valuable. Making it open source only means that the code is now open to contribution, forks, or other modifications by anyone using it.
The performative idea of open source software being a part of your resume and written only to increase your personal brand is a perversion of what the open source movement originally was about. It's about learning, and you learn by making mistakes, regardless of whether your bad code was written completely from your own brain or from the suggestion of an LLM.
Don't ever be afraid to open source your code, nobody has any right to expect anything from you, and if they do they are just too stupid to understand that free and open code is always a gift, regardless of how bad it is, if it solves a problem for real people.
FilterBox does seem to be superior with an inbuilt offline ML model to filter spam notifications, whilst also having a robust set of heuristic filtering options.
It's also amongst the snazziest apps to use with a design that delights. Best lifetime IAP I made 7+years ago.
FilterBox: https://filterbox.catchingnow.com/ Comparison post: https://www.reddit.com/r/androidapps/comments/hsq7ep/buzzkil...