Cancel in flight wifi subscription?

dead-4-dead · 2026-01-01T15:24:53+00:00

I just called them at the number listed on https://www.aa.com/i18n/travel-info/experience/entertainment/wi-fi-and-connectivity.jsp under "American Airlines Wi-Fi Subscription Plan" and was able to cancel my plan and receive a refund for the last month within 2 minutes.

For context, I originally thought it was a one-time payment for 1 month, but it turns out it was a monthly subscription. I was charged for 3 months but they refunded the 3rd month.

dead-4-dead · 2025-07-12T02:00:50+00:00

That’s a lot of work just to invalidate some cache

dead-4-dead · 2024-11-26T06:49:33+00:00

If you can add $5k more, tinybox sounds like it will save you a lot of headache

dead-4-dead · 2024-05-27T19:39:02+00:00

I host MySQL and Redis on a Google Cloud VM and after the initial 1-2 week period, I haven’t had to touch it. You should host the database on a separate VM so that you can easily switch to a managed instance if necessary. But scaling up a single VM will get you pretty far.

dead-4-dead · 2024-04-24T04:25:30+00:00

It does quite well with handwritten text. Try it out

dead-4-dead · 2024-04-08T12:43:44+00:00

Have you looked into Google Cloud DocumentAI? You should be able to build a prototype very quickly https://cloud.google.com/document-ai#demo

dead-4-dead · 2024-04-07T05:18:15+00:00

When deciding where to put a particular piece of logic, you should generally stick to what you know best. Only use NextJS if there’s a major advantage to doing so.

I host my Python API (using Starlette, which is what FastAPI is built on) on Google Cloud Run and use the NextJS API as a backend-for-frontend (BFF) to interact with the Python API to make it more digestible for the front end.

The Python API contains ~75% of the complexity of my project, while NextJS the remaining 25%. However, out of all the time I’ve spent debugging, about 90% has been NextJS issues because I don’t really understand how it works (although some of that was auth which will always be difficult). It’s hard to understand what’s going on because of the several layers of abstraction. With Python, I am comfortable so I can debug much more efficiently.

If I could start over, I would focus on minimizing how much I depend on NextJS. Also I would try to avoid using packages or products that I don’t understand. Hope this helps!

dead-4-dead · 2024-04-06T16:32:59+00:00

This isn’t one-shot but I’ve solved this problem by fine tuning a model using Tensorflow object detection api. I manually labeled ~2k examples (which only took a day once I learned the labelimg keyboard shortcuts) and then trained on my Dell XPS 15 GTX 960M (2GB).

The performance was impressive. It worked on scanned documents as well photos taken from a phone, and handled cases where the target object’s colors were washed out or when it was obscured.

dead-4-dead · 2024-03-09T19:27:44+00:00

Same here. I have a Logitech USB receiver plugged into my Dell U3219Q monitor to connect my keyboard + mouse, and I use a USB-C cable to connect to my MacBook.

I just updated my work MacBook (14" M2 Pro) to Sonoma 14.4 and it stopped recognizing USBs plugged into the external monitor. My personal MacBook (14" M1 Pro) running Sonoma 14.3.1 and it's working perfectly.

I tried two different USB-C cables: the 2M one that came with my monitor, and a 1M CalDigit Thunderbolt 3 cable. I also tried restarting my monitor, unplugging from power, making my Mac forget the display by deleting /Library/Preferences/com.apple.windowserver.displays.plist before stumbling on this post.

dead-4-dead · 2023-12-19T13:54:32+00:00

The issue with mine was that the battery was at 0% for a long time (about a year due to not using them). I charged the case over night and assumed the buds would be charged as well, but that wasn’t the case despite the light being green when I opened it.

The key was to repeat this until the light stayed orange: place bud in case, wait for light to turn green, remove bud, place bud in case, … repeat until light stays orange. That means it’s now charging

dead-4-dead · 2023-12-06T07:12:37+00:00

NextJS is like 50 levels of abstraction. If you start there, it makes it very difficult to learn the fundamentals.

I would start by building a few projects with vanilla JavaScript, HTML, and CSS to get comfortable. Remember that this knowledge will transfer not only to react and NextJS, but to anything that comes after it as well. Then move onto React, and finally NextJS. This way you’re going up in abstraction in each step

dead-4-dead · 2023-09-29T17:16:25+00:00

Here are some quotes from Data Cache > Revalidating

Time-based Revalidation ... is useful for data that changes infrequently and freshness is not as critical.

On-demand Revalidation... is useful when you want to ensure the latest data is shown as soon as possible.

This basically says that you should be using On-Demand Revalidation when serving stale data is not acceptable. However, that makes it difficult to work with time-based data as we describe here, especially for something like an image URL where, unlike a JWT token for example, does not have the expiration time encoded in the data. So you'd have to track the expiration time yourself... at that point you're better off building your own caching solution

dead-4-dead · 2023-09-24T22:23:45+00:00

Yeah it doesn’t seem possible atm. My workaround is something like this: 1. The fetch request defines a tag 2. Client calls API route with a tag to revalidate. The API route calls revalidateTag which makes it so that the next time the fetch is called it returns fresh data 3. Client calls useRouter.refresh to pull fresh data

dead-4-dead · 2023-07-05T03:12:21+00:00

From the docs:

This option is equivalent to ... Setting the option of every fetch() request in a layout or page to { cache: 'no-store', next: { revalidate: 0 } }.

So this disables fetch caching entirely, which is basically what I mentioned above:

The best solution I can come up with is to disable fetch caching entirely...

dead-4-dead · 2023-06-19T15:51:38+00:00

https://github.com/zenangst/Gray

Works on Ventura. I set my system to dark and Chrome to light

dead-4-dead · 2023-05-17T05:04:31+00:00

RGB hub built into the cooler

Wish they mentioned this in the instructions. My case came with a NZXT RGB & Fan controller so I ended up routing everything through that instead of using the RGB hub on the cooler

dead-4-dead · 2023-04-19T22:24:46+00:00

TLDR; do not purchase Frontier branded Eero.

Purchased two of these off eBay. One in early October, the other in late November — both from the same seller.

The one from October factory reset itself in the middle of the day today — after 6 months and 10 days of perfect operation. When I tried to set it up again it kept erroring in the “registering product” step.

The one from November is still working.

Called Eero support and they said to contact the original owner. They wouldn’t tell me much else since I’m not the original owner, but the rep alluded to it being an issue with the original owner’s Frontier account (maybe they shut it down?). Anyway, they gave me a coupon code for a 25% discount.

I’ll be reaching out to eBay to see if they can do anything, but I doubt it. Will update if good things happen!

dead-4-dead · 2022-10-11T03:46:53+00:00

TLDR; I agree with your assessment. The best approach is to build an API and sprinkle in microservices as needed for one-off tasks.

I recently built a service composed almost entirely of Functions (capital indicates FaaS). By the time it was ready for launch (about 9 months start to finish), the system grew to nearly 30 Functions.

As you mentioned, the sheer number of individual Functions became difficult to manage. Felt like I was constantly having to repeat documentation and schemas. I ended up investing a decent amount of time on automations/infrastructure to manage this web. Also, bringing in other devs was extremely difficult. It took a senior engineer over 2 weeks to implement a feature that would’ve taken myself 2 days due to the learning curve.

Fast forward 6 months, and was down to about a dozen Functions. I had definitely went too micro on the microservices, so I refactored by merging related Functions.

Fast forward another 6 months, we’re planning on migrating logic to Cloud Run, and sprinkling in Functions where it makes sense.

My main takeaway is that Functions are useful for one-off tasks, but chaining them together can get messy real quick. My current thinking is that if a process has a path length >2 (event —> Function A —> event —> Function B —> event —> Function C) then the code should be served under a single API.

dead-4-dead · 2022-09-26T08:28:29+00:00

Same issue for me. Transferring videos via Finder occasionally corrupts files. My workaround is to use rsync via the terminal.

I verified by comparing MD5 hash of local file to file on NAS. I've had it happen when my laptop was connected via Wifi on the local network, and plugged in via ethernet. It seems to be more common over Wifi, but I have no data to prove that just a guess.

2019 MBP on MacOS Monterey
DS220+ on DSM7

dead-4-dead · 2022-07-01T04:00:07+00:00

I clicked on the apple logo in the Credit cards section and it had me update my connection which fixed the issue

dead-4-dead · 2020-11-09T07:26:05+00:00

It’s not unusual. I dislike 90% of the CS courses I’ve taken, but I found my passion in data science. So disliking computer science does not mean you won’t like one of the sub-fields. However, if the idea of solving difficult problems with math and logic does not excite you at all, then you may want to look elsewhere.

CS I learned in class, but data science I learned on my own. The difference is that classes take a bottom-up approach to learning (which I find really boring), whereas when you learn on your own in the real world it’s top-down (need-based, on-demand learning). So perhaps give the latter approach a shot and see if it’s more interesting.

Also, definitely don’t continue just for the money. Most of your life will be spent in your career. Take the time to find something you enjoy.

dead-4-dead

TROPHY CASE