Summarizer

LLM Input

llm/8d7ff4a1-085d-4b84-a357-52acc95c6355/batch-2-b71a2b35-95b9-43ee-aa1a-7bd7352e01db-input.json

prompt

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": "46499982",
  "text": "Can you share a screenshot of the notification, and the rule that you created for it at [email protected] please?\n\nAlso, do note that if it is a persistent notification[1] then the Android OS does not allow it to be dismissed. In such a case, you will see the notification in the blocked history with a warning icon next to it.\n\n[1] https://developer.android.com/develop/ui/views/notifications..."
}
,
  
{
  "id": "46500557",
  "text": "AutoNotification app can block persistent notifications if I understand correctly what it is. Hides things like \"Wifi Calling\" that you can't normally disable, swipe. Doesn't require root. So there might be the way. It became less reliable on latest samsung phones, but works on pixels afaik."
}
,
  
{
  "id": "46500948",
  "text": "Thanks for the heads up! Will take a look at it."
}
,
  
{
  "id": "46501134",
  "text": "Is there anything like this for iOS? Or is something like this impossible for a 3rd party to do on iOS?"
}
,
  
{
  "id": "46501458",
  "text": "iOS doesn't give developers access to other apps' notifications, AFAIK. I'm not an iOS developer though - maybe someone with more knowledge can chime in."
}
,
  
{
  "id": "46500259",
  "text": "For samsung users I think good lock can do something similar."
}
,
  
{
  "id": "46504007",
  "text": "ad block for android notifications (maybe for ios notifications too?)"
}
,
  
{
  "id": "46505811",
  "text": "This problem was supposed to be solved by app stores filtering these apps out. Sadly this does not work 100%. Some apps do this but are too-big-to-ban-from-the-appstore and others point to the first group and scream about selective enforcement. Thank you for providing this extra layer of protection!"
}
,
  
{
  "id": "46503278",
  "text": "I am surprised that nobody seems to have the opposite problem: Modern Android just no longer delivers notifications in realtime but bunches them and delays them to a degree that you can't rely on them anymore for synchronous communication. Whatsapp and Gmail messages often trigger notifications up to 15 minutes after being received for me. Infuriating."
}
,
  
{
  "id": "46504811",
  "text": "With apps like Signal, installed via apk, without going through Google on a de-Googled phone, I receive notifications in real time. What's the point of having all notifications go through Google, except to save some battery life and data?\n\nAlso, can Google read push notifications going through FCM?"
}
,
  
{
  "id": "46500738",
  "text": "Imho there are 3 separate classes of notifications\n\n1) Ads - these should not exist, really, or at worst should be flagged in the app store as an anti-feature isolateable from other notifications.\n\n2) \"Recommendations\" - that is, stuff you didn't subscribe to but are things the app offers that they \"think you would like\". These are defensible but should never ever be mixed with...\n\n3) Stuff I actually explicitly subscribed to.\n\nBreaking these rules should be rejection from the app store. Especially now that Google is legally required to allow 3rd-party app stores, they have much greater grounds to properly curate the Play Store. Let the filth live on 3rd-party stores."
}
,
  
{
  "id": "46503759",
  "text": "Having never had a google account or used the \"play\" store, but having only used android phones(so far) I would try this from fdroid, etc.\nI have a workarounds that dissables all notifications except for pm's, the trickiest ones bieng for the varios google (dis)services.\nThe other main workaround is to use webpage sign ins rather than apps through an oddball browser that breaks anything........hmmmm, too agressive, which luckily comes in another flavor that I have set up for banking, and certain other sign ins.\nBut what I would realy realy like a cache cleaner that would wipe EVERYTHING , or better yet a detailed list of all running services and cached data AND bieng able to see the network. could be called WTFIGO, or FIGO for short"
}
,
  
{
  "id": "46501357",
  "text": "when will it be available through fdroid?"
}
,
  
{
  "id": "46500228",
  "text": "This is really great. I chuckled seeing MyGate. I hate that app. My society uses it and I'd need this exactly for it. I hate that Android doesn't force devs to use the right notification category. Apps need to be penalized for not adhering to that."
}
,
  
{
  "id": "46500361",
  "text": "If you really need an app, e.g. for work, put in a separate user profile (sorry iOS users, your phone is gimped)."
}
,
  
{
  "id": "46500718",
  "text": "I agree, this is an excellent idea and I am excited to try it."
}
,
  
{
  "id": "46500279",
  "text": "You're welcome, friend!"
}
,
  
{
  "id": "46501595",
  "text": "this isn't a native feature?"
}
,
  
{
  "id": "46500210",
  "text": "It would be neat to be able to do LLM filtered notifications. Perhaps with a local LLM for users that prefer.\n\nI hope that Apple does a better job of this too! I don't want Uber's ad notifications, but I do want their notifications about my vehicle status."
}

]
</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.

commentCount

19

← Back to job