264 karma · joined October 17, 2024
It looks like the situation is actually more complex and interesting than "The registry rug-pulled me". My .sexy domain price was increased by the owners of .sexy (to $3000) since I bought it 6 years ago BUT in Hover's system it was supposed to retain the legacy price of $38 as it had for the past few years. Something went wrong between Hover and the registry where the legacy price wasn't honoured and as such, it bumped to $3000 on renewal. Apparently support really flubbed this one and we both agreed that going the "post on HN" route for customer service isn't exactly a win on their part.
The money has been refunded and I've been assured they're looking into the bug. Will probably do a follow up blog post!
...But I'm also not a Uniregistry customer, I'm a Hover customer. Do I have any recourse with the TLD owner?
Nice work!
CoMaps also has a better system for distributing map data now which isn't bound to app updates. Not sure if this has made its way back to the other app, but it's quite nice.
Sure, "it's just frontend", but that's actual use enough for me to take it seriously.
It can't render all your math in exactly the same way. If you need it to do that, it may not be for you.
The graph being all nice before the Microsoft acquisition is a fun narrative, until you realize that some products (like actions, announced on October 16th, 2018) didn't exist and therefore had no outages. Easy to correct for by setting up start dates, but not done here. For the rest that did exist (API requests, Git ops, pages, etc) I figured they could just as easily be explained with GitHub improving their observability.