samcrawford

I switched from Spotify to Amazon Music about 9 months ago, and cancelled Spotify Premium as a result (due to price, not bugs). Amazon Music is so much worse.

1. If you have no connectivity, the app will frequently get stuck in the offline state, playing the spinner indefinitely, even after connectivity has returned. I had similar issues on Spotify, but Amazon Music is so much worse. 2. I had Amazon Music eat my entire cellular plan's data monthly allowance in a day, after it seemingly got stuck in a loop trying to download the same podcast again and again. The podcast is unplayable when it gets in this state, even on perfect Wi-Fi, it just never starts playback. This has happened twice now (incidentally on the same podcast, but different episodes), even after deleting and reinstalling the app entirely.

The second bug is a deal breaker, so I've gone back to Spotify.

This is indeed sad. We are/were a customer, and one of the earliest edge computing customers. For a long time they've been the only provider truly offering the ability to run native code at the edge. But they've not really taken advantage of their early lead, so others have caught up. Also, reliability and capacity problems have become very commonplace in the past year or so. Hope the team has a safe landing elsewhere.

Not included with Prime in the UK

Great write-up! One question I had was around the use of keepalives. There's no mention in the article of whether keepalives were used between the client and reverse proxy, and no mention of whether it was used between the reverse proxy and backend.

I know Nginx doesn't use keepalives to backends by default (and I see it wasn't setup in the optimised Nginx proxy config), but it looks like Caddy does have keepalives enabled by default.

Perhaps that could explain the delta in failure rates, at least for one case?

The same author has been reporting diligently on Pollen, and has said he will do a write-up on the collapse there. I will be very interested to read that.

I'm not so sure. If I load a saved map in Google Maps (e.g. someone has saved a route with markers and shared it with me), and then I go offline whilst viewing it, Google Maps on Android will show an error after a while and I'll lose the route and markers entirely. This occurs even if I've marked the area as an offline map. I guess it's just a case that they treat the saved routes in a different way. But it's really annoying for my use case (which is finding crewing points for long distance running events in the middle of nowhere with no mobile coverage).

My experience with Paypal is the opposite. On multiple occasions I've had someone send me money on Paypal, but then it gets held up in checks and verification for 2-4 weeks, during which time I cannot access it. Sometimes it is instant though. There seems to be no pattern to it. This lack of certainty discourages me from using Paypal to receive payments in the future as I now consider it as a risky, slow, last-resort option.

I'd second Mosyle Business. We pay for about 40 licences. It costs us very little and they provide quick support.

I've been using Gen1 eeros since they were first released in around 2016. They're still getting software updates and they're still rock solid.

I'll be first in line to purchase a new set if they offer a model that supports PoE here in Europe.

Disclaimer: I've done a bunch of work with the Eero team from 2015/2016 til present day. Their team has an extremely high concentration of very smart and talented people, they are great to work with.

For what it's worth, we run "edge compute" with two separate mid-sized CDNs and pay about $0.005 per GB. This required a bit of negotiation, but has no minimum commitment and is on a monthly term. Yes, even lower fees can be had if you build your own infrastructure and pay for bandwidth on a CDR, but this is a fairly apples-for-apples case where we are not doing that.

So yes, AWS, GCP, Azure bandwidth pricing is very high. Oracle is, amazingly, the outlier with lower bandwidth pricing.

Filtering out the spam results is only half the problem. In my experience, a legitimate site's content is cloned by a spam site, and that one appears in a Google search and the legitimate one does not. The example that keeps hitting me is GitHub Issues.

Filtering out the spam only removes the clones; it doesn't get the good results back in.