I play the game with SiriusXM to only pay the intro price and listen to that 90% of the time I am in the car. XM has a weird collection of DJs, some are obnoxious or grating, but also after many years of listening to them they feel like people I know.
The local NPR backed station the Current is good but their audio quality is terrible, even their HD stream is muffled and wonky. They also eliminated many of the DJs I had grown to like and I never got that same connection with their replacement, which definitely impacted how I listen.
Once my visiting family departs I am going to finish building the Little Free Library I started last month. We have lived in our current home for 5 years and it is about time I share my love of reading with my neighbors.
https://littlefreelibrary.org/
We watched the Australian Episode of Everybody Feed Phil, and Mel Brooks made an appearance. He seemed a bit old but when I looked him up on Wikipedia I was shocked to learn he was 99. Still working, still funny, what a life.
Haven't encountered that yet, but probably something I will need to solve. I started with just a few newsletters I already subscribed to with Kill the Newsletter that never had that problem, I need to research what the various sending frameworks do to track opens these days.
This looks nice. Ran through a 5 question Go scenario and got 4/5 right. Which feels about right with my current depth of knowledge.
One of the very first pieces of code I wrote when I was figuring out if I liked development was a flashcard program to help me study in college. I really wish I still had that code.
I built my own version of Kill the Newsletter. Been testing it with various newsletters. Learning that a lot of the popular email newsletters are horrific, but if you have any, popular or ones only two people read that you like, I want to know!
I also bought some steel table legs and rebuilt our kitchen table and bench yesterday. The table came with wooden legs that always seemed unstable, I would confidently stand on my table now.
It seems fairly obvious that the "identity" portion of this is more important than the actual cost of providing the storage. Though maybe more folks than I imagine can hit the 5GB limit quickly. I have emails dating back to 2008 and just calculated I am only using 8.5GB. I keep everything so getting down to 5GB would be a hassle more than a challenge.
I would argue that Google really wants to earn your storage dollars. Their constant notifications on my device warning me I was low on space is what drove me to Immich.
The fact that this also shuts off access to many public library Ebooks on these devices should be getting more press. My wife exclusively uses her Kindle for library books and it looks like it will be impossible to get legally acquired library books onto her device from our library system, which is using libby/overrdrive.
Track it! Any Spreadsheet. Columns: date, where you filled up, how many gallons, dollar total, odometer reading, mpg function ((currentodo - prevodo) /gallons), ppg function (total / gallons).
You could also install something like https://lubelogger.com/ (naming decision aside), if you happen to do any self-hosting. It is a lightweight vehicle tracker. It has a fuel tracking screen. I personally only use it to track maintenance, but have been thinking about starting to track fuel consumption given the current disruption.
I have been using HA to water my garden for 4 summers. I setup a Tempest weather station this fall, and will have some fun experimenting with using rain and temperature data collected in my back yard to make watering decisions.
The honest answer is you probably won't find it. Historical documentation is hard, it is the first "features" cut when teams are scrambling to meet a deadline. There is no malice in this, it's just something that the end user doesn't need or see so when shit hits the fan, it get skipped.
Commit logs, slack/email/etc, documentation silos, or issue trackers are your best bet, other than actually being able to talk to the author(s) of the code.
But in general, the decision was made because in the time the developer had to implement the feature or fix, this was the best solution they could come up with. Hopefully if there were clear tradeoffs, there is some comment as to what they might have done with more time. Likely though they were rushed, told their team they wanted to go back and fix this, and then were ushered into a new project the second this one stabilized.
I think gghhjnuhbb has the best alternative to finding actual documentation and that is sitting and putting yourself in their headspace. That can sometimes lead to insights you might have missed.
Funny, I am taking an American Sign Language course, and one of the components is talking about dates/days/weeks. Next Week, Next Monday, Last Tuesday, etc. I was talking to some of my classmates who were all struggling to fully understand when to use what sign(as was I), and I pointed out that talking about next Friday in English can get confusing depending on how each participant thinks about things.
Not surprised an LLM gets this wrong, lots of content consumed with various ideas on how these things should should work.
Not really any places where things get sold, but opt-in in the background for newsletters is bad in certain sectors. Ticket platforms are terrible. I like to use a new email for every event and boy does that lead to new round of clicking opt-out until I can deactivate the email after the event has concluded.
I switched to using masked emails with Fastmail primarily so I could see who sold my data. The potential security benefit was not really a driver. Having 1Password be able to generate a unique email makes it a no-brainer these days. For those services that require a username that is not your email, they can usually be used without the domain part. Works really well.
I even wrote a tiny little local only web app that I can use to generate a masked email on my phone, so when I need an email for an in person thing I can just show them my brand new weird email directly on my phone.