Resinator's error messages look amazing! I also feel like I’ve gained a lot of cursed but useless (to me) knowledge, so thanks for that. :-)
I don't have a horse in this race, but regarding FONT resources, I would like to humbly suggest not supporting them at all. Radical, but from what you wrote, they do seem pretty weird and ripe for accidental misuse. Plus, they are obsolete and it seems like Resinator already intentionally diverges from rc.exe in a few cases anyway.
I'm actually pretty okay with where I've landed with FONT resources. The legwork has already been done in figuring things out, and with the strategy I've chosen, resinator doesn't even need to parse .fnt files at all, so the implementation is pretty simple (I wrote a .fnt parser, but it's now unused[1]).
One thing I’ve always felt is that the relative difficulty of each task seems to have flipped? I could write a bird classifier in my sleep using fastai, but I have no idea how to do a GIS lookup.
An LLM will tell you how to do the GIS lookup, but ironically as privacy laws become better it will genuinely become a harder and harder task unless the user explicitly wants you to do it.
I don't think that makes the task harder. You should just not do the task at all if the user doesn't want it.
Flashback to when apple rolled out their enhanced privacy tools and when I said "that data is blocked unless the user gives us permissions" the project manager un-ironically anguished "But how will we track them?!"
Won't someone please think of the commercial interests?! /s
Is there a mapping from, say, a geo location to a list of Umbra files which cover that location? I'd hate to download 42TB of data and then have to grep through it :-D
The JSON files in the S3 bucket can be downloaded in isolation from any other format and they're pretty small. I did some geo-enrichment of them in a previous blog post where I found the country and waters of Umbra's ship imagery. https://tech.marksblogg.com/yolo-umbra-sar-satellites-ship-d...
The above relies on network calls to OSM but with Capella, I found a way to get the smallest GeoFabrik partition for each image using a single GeoJSON file. The code could probably be modified to work on Umbra's feed with a bit of work. https://tech.marksblogg.com/capella-open-data-free-satellite...
Lastly, Umbra have ~24 locations they image frequently but there is an 'ad hoc' folder with a lot of subject names in English that give away the location and subject matter. This might be easier to look through for interesting imagery.
aws s3 --no-sign-request ls 's3://umbra-open-data-catalog/sar-data/tasks/ad hoc/' | grep -i 'tesla\|nvidia\|saudi'
Hi! Our Archive Catalog STAC API indicates which items are in our Open Data Catalog on AWS. You can use the STAC Search endpoints to filter by this property alongside location. Instructions in our docs:
Unfortunately we don't directly link to the s3 assets for those items at this time :( So you'll still have to pull the list of files and grep by task ID.
> We will abstain from using [parser generators] here. I want to ensure there are no dark corners where magic and confusion can hide, so we’ll write everything by hand. As you’ll see, it’s not as bad as it sounds, and it means you really will understand each line of code and how both interpreters work.
It has to be satire because of Tom's complete overreaction and the fact that comments are actually one of the easiest things to handle when building a lexer (usually, you just discard them). Eval'ing them makes no sense.
That said, I suppose stranger things have happened.
It's possible that OpenAI have implemented both soft and hard limits, and repeating it in the prompt just prevents it from hitting the user with a scary error.
I don't have a horse in this race, but regarding FONT resources, I would like to humbly suggest not supporting them at all. Radical, but from what you wrote, they do seem pretty weird and ripe for accidental misuse. Plus, they are obsolete and it seems like Resinator already intentionally diverges from rc.exe in a few cases anyway.
reply