To avoid curl timeouts in migrations:

$settings['http_client_config']['timeout'] = 500;

gunzip < db/backupfile.sql.gz | drush sqlc

https://understanddrupal.com/lessons/how-debug-drupal-migrations-part-2/
also install migrate_sandbox module

This method actually worked very nicely today:

Host github.com
  AddKeysToAgent yes
  IgnoreUnknown UseKeychain,UseKeychain
  IdentityFile ~/.ssh/id_ed25519

The high watermark can be set via Drush before running the migration in order to get a different timespan of updates.

For example, to get all updates since 9/1/2023:

drush mshw publication 20230901
drush mim publication --update
Clearing the high watermark will pull all records:

drush mshw publication
drush mim publication --update

This blog post also helped me get my xdebug working with a mac, lando, and vscode https://thehigglers.com/blogs/how-to-configure-xdebug-with-lando-for-dr…
I think the main thing was to install the official php debug extension in vscode. My settings that are currently working 1/2/2024 are below. FYI also in the debugger pane in vscode, you have to click the green arrow to start listening for connections.

Source grabs it from the JSON feed, process does the mapping to the Drupal fields in the publication2 content type, and destination defines the content type it will map into:

Just got to http://base_url/jwt/token

Embeddings versus Fine Tuning: https://youtu.be/_wtfszFzqt0
Forcing it to answer from the data given through embeddings, versus augmenting the sum of chatGPT data. From the spreadsheet example listing a bunch of animal names, which one is likely to speak English was asked, and it's forced to answer and choose from the list of animals, so it picked "Turtle" probably because of the Teenage Mutant Ninja turtles roflol!