llm/8d7ff4a1-085d-4b84-a357-52acc95c6355/batch-0-cfe6e6bd-f01a-4f2a-bc59-77e137fd60fb-input.json
The following is content for you to classify. Do not respond to the comments—classify them.
<topics>
1. Open Source Necessity
Related: Strong demand for open-sourcing due to security concerns around notification access, requests for F-Droid availability, mentions of trust issues with closed-source apps accessing sensitive data like OTPs and 2FA codes
2. Internet Permission Security
Related: Discussion about whether lacking INTERNET permission provides sufficient security, concerns about permissions being added silently in updates, debate over slippery slope of future permission additions
3. Network Access Control
Related: Android's ability or inability to block app internet access, GrapheneOS and custom ROM features, differences between Pixel, OnePlus, Samsung, and Xiaomi implementations of network toggles
4. Alternative Solutions
Related: Mentions of BuzzKill, Alertly, FilterBox, NetGuard, AutoNotification, Tasker plugins, and Before Launcher as existing alternatives for notification management
5. Promotional Notification Abuse
Related: Frustration with apps like Uber, DoorDash, MyGate, Facebook pushing ads through notifications, apps using single notification channels for both important alerts and marketing
6. App Store Enforcement
Related: Suggestions that Play Store and App Store should enforce guidelines against notification spam, complaints about lack of enforcement against big players, too-big-to-ban problem
7. Notification Channels Problem
Related: Apps misusing notification categories, mixing promotional with transactional notifications, creating excessive channels, lack of proper categorization enforcement
8. iOS Limitations
Related: iOS lacking equivalent notification filtering capabilities, Apple not allowing third-party access to notifications, iOS users unable to control notification spam effectively
9. Battery and Performance
Related: Questions about battery impact of notification processing, discussion of push-based notification handling, app showing minimal battery usage
10. On-Device ML Classification
Related: Suggestions for lightweight on-device machine learning to classify promotional vs transactional notifications, requests for smarter filtering beyond regex patterns
11. Notification Digest Feature
Related: Requests for grouping notifications, scheduled delivery of batched notifications, cooldown periods between buzzes, Android 15 notification cooldown feature
12. Gated Community Apps
Related: MyGate as primary use case, vendor lock-in forcing notification tolerance, apartment apps with mandatory usage that spam notifications and ads
13. Privacy-First Design
Related: Appreciation for offline processing, no servers or tracking, discussion of data collection by typical utility apps, trust implications
14. Permanent Silent Mode
Related: Users describing keeping phones permanently on Do Not Disturb, only allowing specific contacts, philosophy of asynchronous communication
15. One Strike Policy
Related: User behavior of immediately disabling all notifications from apps that send spam once, complete notification blacklisting as solution
16. Rule Sharing Challenges
Related: Desire for country-wise template rules, difficulty of writing many rules manually, limitation that sharing would require internet access
17. Persistent Notification Limits
Related: Android OS restrictions on dismissing persistent notifications, VPN and system notification handling limitations
18. WhatsApp Communication Dependency
Related: Third world reliance on WhatsApp calls, data-off strategies failing when calls are WhatsApp-based, messaging app notification management
19. Elderly Notification Overload
Related: Comment about elderly users suffering worse from spam notifications and text messages, scale of garbage notifications targeting older users
20. Web Alternatives to Apps
Related: Using websites instead of apps to avoid notification spam, Facebook mobile web as workaround, reducing app dependency
0. Does not fit well in any category
</topics>
<comments_to_classify>
[
{
"id": "46501146",
"text": "I would love to use this, but I don't want to allow a third party app with closed source to read all my notifications. This can read OTP passwords, full messages, etc. so it must be open source for me to consider it.\n\nI would donate/pay for this if it was open source on F-Droid.\n\nKudos to you for building it. I put off building this exact same application so many times it's not even funny. Too bad I'm too lazy to maintain something like this."
}
,
{
"id": "46501301",
"text": ">I would love to use this, but I don't want to allow a third party app with closed source to read all my notifications. This can read OTP passwords, full messages, etc. so it must be open source for me to consider it.\n\nThe app lacks the INTERNET permission so it can't really exfiltrate data even if it wanted to."
}
,
{
"id": "46501367",
"text": "This is correct, but it is still a slippery slope. At some point the dev ends up adding internet permission (might be for legit reasons too), and lo and behold you are sharing your data. For something as sensitive as notifications, I really can't trust anything but open-source app which is vetted by a few seasoned people and hosted on F-droid."
}
,
{
"id": "46501534",
"text": "Related, GrapheneOS has a handy feature to disable network access for individual apps."
}
,
{
"id": "46504076",
"text": "Also non-GrapheneOS Android. I'm on CrDroid (Android 16), ans if I go into \"Settings -> Apps -> Some App -> Mobile data usage\", there's a toggle for \"Allow internet access\", and a few more to control network access on Wi-Fi, cellular, background, and VPN."
}
,
{
"id": "46504766",
"text": "If the permission is added in retrospect wouldn’t you still need to opt in?\n\nfwiw i completely agree that oss is the way to go here"
}
,
{
"id": "46506972",
"text": "I’m interested in what you’re suggesting. Who are those auditors you trust? Does f-droid imply things have been audited?"
}
,
{
"id": "46502010",
"text": "That's another pet peeve of mine: Why the hell can't we block internet access for apps in (native) Android? Everything else is a permission, but this is not, somehow."
}
,
{
"id": "46502649",
"text": "Maybe Google doesn't want users blocking ads from getting loaded."
}
,
{
"id": "46502806",
"text": "Wait, we can in Android. In my OnePlus 12 in the app settings under \"data usage\" there are two toggles for \"disable mobile data\" / \"disable wifi\""
}
,
{
"id": "46506435",
"text": "Not present with a Pixel with Android 16, my effective choices are:\n\n1. App can't use mobile data in background\n\n2. App can use mobile data in background except in Data Saver mode\n\n3. App can use mobile data in background regardless of Data Saver mode\n\n____\n\nFor anyone doing comparisons, the literal settings appear under \"Mobile Data Usage\" as:\n\n* [X] Background Data (\"Enable usage of mobile data in the background\")\n\n* [ ] Unrestricted mobile data usage (\"Allow unrestricted mobile data access when Data Saver is on\")"
}
,
{
"id": "46504382",
"text": "I have an S25 Ultra with the latest version of Android, and these options don't seem to be there at all. I don't have a \"data usage\" under Permissions for any apps. I do have a Mobile Data section under App Info for any given app, but there's no way to toggle the options you mentioned."
}
,
{
"id": "46503428",
"text": "Wow, thought it was GrapheneOS only, but no.\n\nConfirmed these settings on One+15 on OOS16 (based on Android 16).\n\nIs it also the case for other Android brands?\n\nP.S. I did use it before to turn off ads."
}
,
{
"id": "46505287",
"text": "Google's Pixel phones (near stock Android) famously do NOT have the option."
}
,
{
"id": "46505902",
"text": "Xiaomi phones also have it but you can block Wi-Fi only for user (non system) apps. However you can block mobile data access to all apps.\n\nNone of the Samsungs I have owned so far had this feature and neither did my last Pixel."
}
,
{
"id": "46502303",
"text": "It's hard to rule out intentional side channels without access to source."
}
,
{
"id": "46501376",
"text": "Is that actually required? I thought that was implicit"
}
,
{
"id": "46501553",
"text": "It's automatically granted but the app needs to declare it in order to access internet. Because of that it's not enough that the app _currently_ doesn't request internet permissions, because if it ever starts, it would be mostly transparent to a user"
}
,
{
"id": "46501528",
"text": "Yes. Without the permission all network requests will just fail."
}
,
{
"id": "46501785",
"text": "You can silently add the permission in an update though. It's safe if you don't auto-update it I guess."
}
,
{
"id": "46501353",
"text": "Fair enough, you only have my word on it (that it doesn't send any data to the Internet). But you do have my word :)\n\nAnother person requested that the app be open-sourced as well. I will look into that."
}
,
{
"id": "46501732",
"text": "I'm going to join the list of voices requesting open source here. If you're not planning to charge money for this, there are several benefits starting with increased trust.\n\nMobile apps are a cesspool of user-hostile behavior, and I have a strong preference for not giving closed source apps access to sensitive data."
}
,
{
"id": "46501988",
"text": "I would greatly appreciate it, if this was open source :)\nEspecially since this will be able to read 2FA codes sent by SMS.\n(I get that SMS 2FA codes are not perfectly safe to begin with, I personally don't love them either, but they are still used on a bunch of services)\n\nJust makes me sleep a little better."
}
,
{
"id": "46502262",
"text": "It took me a moment to find, but Alertly claims to do something similar while being open-source. Last commit was made two years ago though.\n\nhttps://f-droid.org/packages/com.example.notificationalerter\n\nhttps://github.com/lightningcpu/Alertly"
}
,
{
"id": "46502510",
"text": "What about this?\nhttps://f-droid.org/packages/co.adityarajput.notifilter"
}
,
{
"id": "46501583",
"text": "It's something i've also vaguely thought about building myself, because god damn uber, how many times do you need to send me an advert for uber one? just tell me when my car is here.\n\nso congrats to the author of this. I do agree that I'd prefer it open sourced too, it feels a bit risky it having access to all your notifications."
}
,
{
"id": "46501831",
"text": "If you're feeling skeptical and just want to be sure,\nyou can use this NetGuard https://github.com/M66B/NetGuard\nto block internet access for any app."
}
,
{
"id": "46502047",
"text": "Great tool. Additionally, some Android forks (ColorOS) allow you to do this without apps, directly in the system settings of the app"
}
,
{
"id": "46501945",
"text": "TIL! What a find. Thanks mate!\n\nI might actually try this now."
}
,
{
"id": "46502031",
"text": "You're welcome"
}
,
{
"id": "46500001",
"text": "I’m now an iOS user but the problem is actually the same here : apps not respecting communication channels to push ads (mostly to their own app or service). I usually fully block notifications from most apps but for some apps the notifications are really convenient (carpooling, transport or delivery app).\nYes I want to know if the train I booked is delayed. No I don’t want to be notified that you are now partnering with another transport company and that you are sharing 5% off coupons to try it…\nI systematically give a 1 star review explaining the issue and mail the devs if possible. I even think that Apple Store and Play Store ToSs are against this practice but they are not enforcing it sadly…"
}
,
{
"id": "46500942",
"text": "Worse even because iOS doesn't offer notification groups/channels like Android does (ignoring the fact that market leaders like Uber, DoorDash, etc. eschew them in favor of \"General\" channels they can pump both delivery/ride info and ads through.)\n\nIMO this needs to be an app guideline enforced by the iOS App Store and Play Store. I remember back in the day, iOS used to be known for having less spammy notifications."
}
,
{
"id": "46501292",
"text": "I remember when I first started seeing obvious ads in notifications and assumed Apple would come down hard. I wish I had been right.\n\nIf any app abuses the notifications at all I turn them all off, that's the only way to stop it. If the notifications are required for the app's operation, well, then I have to delete the app.\n\nSociety has fucked itself over allowing these to exist."
}
,
{
"id": "46507170",
"text": "Society has fucked itself over allowing everyone to be dependant on software entirely from two american companies.\n\n20 years ago the idea that I'd have to have an account with an american company so as to be able to interact with so much of my on-another-continent society would be ridiculous!\n\nNow it is the default. It is sad."
}
,
{
"id": "46502172",
"text": "> IMO this needs to be an app guideline enforced by the iOS App Store and Play Store.\n\nYeah, but... money."
}
,
{
"id": "46502254",
"text": "Maybe this matters at the bottom end of the market, but it's mainly the top players I see take this approach to notifications. DoorDash, Uber, and the social media platforms all have incentive to stay on the official app stores.\n\nI expect the bottom end of the market is also dependent on the official app stores to make money. What real alternatives do users have, especially with sideloading on Android now requiring Google bless your APK anyway? (edit: Looks like Google has started to walk this back slightly. Even still. https://android-developers.googleblog.com/2025/11/android-de... )"
}
,
{
"id": "46502518",
"text": "I chose the hard way and disabled them anyway. If I want to know if a train is delayed, I check. If I wait for a driver, I check. Actually the latter is better as I'm not surprised by the guy arriving but can synchronize well. And frankly, I don't complain.\n\nAnd every evening or so I sit down on my computer and check WhatsApp notifications on web.whatsapp.com to catch up with what's going on in groups people added me to. I find this quite good for my well-being."
}
,
{
"id": "46500381",
"text": "Here is a fun story. Just like you, I too live in a “gated community”, and we also default to MyGate. We have a founders group in there, and the things with MyGate and its irritations would sometimes come up. We all would wink and go about our days. The founder of MyGate is in the group and is one of the neighbors. We sometimes teased that we would just camp out outside his home, asking him to fix these excessive notification issues and bugs, and to add/edit features. ;-)\n\nAnother founder friend lives in a different mid-sized community and was using MyGate. He got pissed not just at the ads but at the massive data gathering—contacts, camera, flashlight, and everything. He ended up creating https://dobermanapp.com"
}
,
{
"id": "46507417",
"text": "Ah we live in the same ‘gated’ community and probably are neighbours then ?"
}
,
{
"id": "46500006",
"text": "My solution to this problem was to have my phone permanently on silent. The logic being - there was nothing so urgent 25 years ago that couldn't be solved by an asynchronous answering machine message checked once a day; why do I need moment to moment updates now.\n\nNowadays I'd probably use a tool like yours. My partner is going through legitimate withdrawal symptoms after two years of short-form content addiction. Turning off all notifications was one of the first things I did for them."
}
,
{
"id": "46500050",
"text": "I'm occasionally keeping my data turned off and am telling everyone \"if urgent call me\"."
}
,
{
"id": "46500641",
"text": "(3rd world) problem: most people think calling is pressing the phone button inside Whatsapp."
}
,
{
"id": "46501274",
"text": "At least on iOS, internet call is treated basically the same as cellular, showing a splash caller screen and ringing if not on silent. This means that it's trivial to setup phone in such a way that no notification gets through but calls do, even with sound."
}
,
{
"id": "46501773",
"text": "The point being made above is that if data is turned off, you can no longer receive calls made over WhatsApp."
}
,
{
"id": "46501609",
"text": "This is also true on Android."
}
,
{
"id": "46506953",
"text": "The same in Switzerland and it's not 3rd world"
}
,
{
"id": "46502073",
"text": "Even when checking once a day, it's still worse with spam notifications. It's like getting 20 spam phone calls on your answering machine between the real ones."
}
,
{
"id": "46502331",
"text": "Another option is to avoid those kinds of apps. I get 0 notifications I would consider spam."
}
,
{
"id": "46505257",
"text": "There are e.g. banking apps doing that."
}
,
{
"id": "46506368",
"text": "Consider using another bank. Maybe there's a higher tolerance for that kind of bullshit in the US but I've never seen a single notification from my bank. If it sent me spam I would assume they got hacked."
}
]
</comments_to_classify>
Based on the comments above, assign each to up to 3 relevant topics.
Return ONLY a JSON array with this exact structure (no other text):
[
{
"id": "comment_id_1",
"topics": [
1,
3,
5
]
}
,
{
"id": "comment_id_2",
"topics": [
2
]
}
,
{
"id": "comment_id_3",
"topics": [
0
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices for matches
- Use index 0 if the comment does not fit well in any category
- Only assign topics that are genuinely relevant to the comment
Remember: Output ONLY the JSON array, no other text.
50