MollyRealized

"Messages" appears to have disappeared from Google Takeout. Does anyone know why Google removed it, or if there is an official notice or explanation?

I recently read a blog post where someone calendered a reminder for five years into the future, then actually followed up on it.

I'm wondering how you guys do it - what your reminder 'systems' are. I have not really been able to find something that's been very ubiquitious and able to capture my thoughts -- I have ADHD and really need kind of a "braindump -> successfully reminds me later" system.

Thank you in advance for the time you take in describing your systems - it would be deeply appreciated.

Does anyone has a copy of the "Hacker News Fixed Width for Widescreen Monitors" userstyle?

I've checked several of the Userstyles.org mirrors, as well as more modern websites, but cannot find this particular userstyle I used all the time.

I am wondering if people have already done the work on what I'm about to describe. I'm going to try to define what's in my mind by explaining the working circumstance. The humidity part of the below, however, is solved - I'm just trying to explain the kind of substitution I'd like.

For me, temperature doesn't mean as much as stickiness. So I worked out a script that takes the dew point and maps it against a humidity comfort index. I have both the next 24 hours, and the next six days.

Right now, my script reads out the next 24 hours like this:

"From 5-10 AM, it will be pleasant (0). At 11:57 AM, it will be sticky (1). At 12:57 PM, it will be pleasant (0). From 1-10 PM, it will be refreshing (-1). At 11:57 PM, it will be pleasant (0). From 12-4 AM, it will be sticky (1)."

What I'm wondering - before I try to reinvent the wheel - is if there is basically a generalized library or reference that lets you define things using more ambiguous, human terms. I imagine it would have to define not only morning, afternoon, and evening, but also have "early", "mid", and "late" adjectives, as well as overnight.

For example, if this library existed, I could implement it into the script and then it might say:

"This morning, it will be pleasant (0). At noon, it will be sticky (1). The afternoon and night, it will be refreshing (-1). Overnight, it will be sticky (1)."

Is there an agreed-by-popularity successor to 'nativefier'? I see that the author discontinued development, but I imagine the need didn't go away. How do people accomplish its purpose?

Original announcement: https://news.ycombinator.com/item?id=10930718

Are there places on the Internet that collect configuration files for popular software that lets you "import settings"?

For example, I'm interested in seeing what people have done for their Open Shell setups. I found one person's XML file. But there's got to be more of these things, I hope.

I am wondering if Chocolate or other package managers or public domain software hosts have 'most downloaded' or 'most installed' lists at URLs - for the purpose of software discovery.

I just had a frustrating experience with Android's bug tracker. I reported a regression in the App Battery Usage UI where battery optimization settings are now hidden behind non-obvious text interactions. Instead of evaluating the technical merits, a Google employee marked it "Obsolete" because I'm "an Android user, rather than an Android Open Source Developer."

This seems wrong. The bug is legitimate and impacts usability. Being redirected to general user support forums feels like a dead end for technical UI regressions that need developer attention.

Questions for the HN community: - Is there an actual policy against end users filing Android bug reports? - Where should technically-minded users report UI regressions that affect core Android functionality? - Would any AOSP developers be willing to "sponsor" this bug report if there's truly a developers-only policy? - Has anyone successfully gotten UI/UX issues addressed through the standard user support channels?

Context: https://issuetracker.google.com/issues/390590782 if any Googlers are reading.

For reference, I'm not talking about basic usage questions - this is about a specific UI regression that makes battery optimization settings less discoverable than in previous Android versions.