Their game is clearly to squeeze very hard for a few years, and then deprecate the product. I can't imagine that there are companies that are fine with such price hikes.
Their game is clearly to squeeze very hard for a few years, and then deprecate the product. I can't imagine that there are companies that are fine with such price hikes.
If that feels hard to you (to set up your app pointing to another DB, run a single E2E-testable part of your app with it's own DB connection, etc), fix that.
Fortunately I was able to get accepted into the StarLink early access around that time and managed to cancel the DSL. Even though ATT clearly did not want my business anymore, they still made sure I had to jump through countless hoops to finally disconnect and terminate billing. I had to sit on the phone for a couple of hours, being transferred between phone reps and managers until I finally got one person with the authority to shut my account down.
My personal longest issue with ISP's was when the software config once went wrong in their side, took me a month and allmost daily phone calls until I got to 4th line support that was an actual techie who fixed it in 10 minutes.
I might give this idea another go myself with this nice rust library. With some heuristics one could partition the recursive closure of dependencies in a way optimizes for reuse (e.g. try to compute shared subtrees). Probably more efficient than a random tar of e.g. the entire root file system of a buildroot android system.
I found about this [1] amazing live coding session by lftkyro on YouTube showing how to build a live music pattern editor on the C64.
The USPS knows about deliverable addresses but won't give that information to the federal government because then it'd be public domain and they would lose several of their primary data moats (Zipcodes, addresses, delivery routes, for example). The Census has very complete knowledge of every address, but won't give it up because it's illegal (see Title 13 of the US Code). There is an ongoing attempt by the DOT to collect a National Address Database (https://www.transportation.gov/gis/national-address-database) by collecting information from the address assigning authorities (usually county governments), but it's incomplete and unlikely to ever be complete because of holdout/underfunded local governments.
There are several address datasets that are private (Google has a fairly complete one, FedEx/UPS probably have the most complete, TomTom, CostQuest, etc.). I started https://openaddresses.io/ to try and collect them (NAD is based off this idea) into an open-licensed dataset.
The broadband companies have records that say "this address is connected to this network, which could theoretically have this service level", but (a) they won't/can't tell you where they think the address is and (b) won't spend the time to match their address string format with the government's address because both are private data.
Finally, without the address -> location data, even if we could get broadband providers to tell us what service is available at each address, we couldn't put that service level on a map because we don't know where the address is.
----
The Markup published some work in 2022 where they used OpenAddresses to use ISP's own tools to gather per-address service offerings and put them on a map. This is what the FCC's broadband map should be doing, but can't for the above (and political) reasons: https://themarkup.org/show-your-work/2022/10/19/how-we-uncov...
Muniplicities are the data owners, but data is also collated nationally.
See [0] for a viewer of this public data.
Also, all our surveying/road data is managed in a similar fashion, and this is regularly imported in e.g. openstreetmap.
[0] https://bagviewer.kadaster.nl/lvbag/bag-viewer/?zoomlevel=1
I bought a 12GB Nvidia card a year ago. In general I'm having a hard time to find the actual required hardware specs for any self hosted AI model. Any tips/suggestions/recommended resources for that?