u/david_ph

This has been an issue for me for years, and now its fixed!

I'd add a list of sites I wanted to keep cookies for, so when I closed firefox, only those cookies would be kept. Except it would also keep other cross-site cookies, since by adding them to the exception list it also disabled total cookie protection for those sites.

So I'd spend time going through my cookies and manually deleting stuff that shouldn't be there.

Now finally, there are 2 lists, and you can have an exception list for clearing history on shutdown without bypassing total cookie protection.

"Add a way for cookie-clearing exceptions to not also affect cookie partitioning" https://bugzilla.mozilla.org/show_bug.cgi?id=1767271

I'm using an esp8266 (nodemcu v3) powered by a 12v SLA battery with a 12v to 5v step-down converter.

When I connect a rain gauge to a gpio + ground, I get constant spurious triggers.

If I power an esp8266 from a power bank or my computer's micro-usb port, it works fine.

The esp8266 also has an ina219 board and a solid state relay connected to read the voltage and control a battery charger. That all works fine.

Any ideas why the 12v to 5v power supply is causing spurious triggers on the gpio, and if there's any solution?

I just installed the latest update, lineage-23.2-20260716.

Now after I set a timer, and switch away from the time app or the screen turns off, it sends a notification beep.

The first time I used it after the update, it just kept beeping over and over every 5 or 10 seconds for a few minutes, though now it's just once. I'm not sure if it's a bug or it's supposed to be a "feature" -- but it's really annoying.

I just changed the settings to turn off notifications for the timer to "fix" it. The timer still goes off when triggered, without all the beeping.

I have a Canon lide 120 flatbed scanner that is about 9 years old. I went to use it, and at first it scanned without lighting up. Then, after unplugging/plugging the lamp eventually turned red (but still didn't produce a usable scan).

I tried a different cable; same problem (scan head lit up with a red light, instead of white). I figured it was just broken, so I ordered a new Canon lide 300.

After leaving it unplugged for several hours, and trying it again, now it seems to be working. The lamp lights up with white light, and produces acceptable scans.

My question is, do you think this was just a fluke, and the old scanner is fine, or is it a sign that the lamp is going bad and it will likely fail again eventually?