the original demo code in README is:

The Date#format Method
class Date
  def format( spec ) self.strftime( spec.to_strftime ); end
end
The new Date#format method formats the date like the passed in example:

date = Date.today   ## test run on 2020-02-09

p date.format( 'January 02, 2006' )         #=> "February 09, 2020"

but the 'format' method is a built in stdlib privat

The listed versions required for Django, Celery, and django-celery are all (slightly) different between the two files. Presumably setup.py is authoritative? How about fixing requirements.txt and reading it into setup.py to guarantee consistency? I'm happy to submit a PR for that if you're interested.

Notes raw data is currently unsaved in the JSON export. Suggest to encode it as x64 string so it can save special characters into the JSON file without causing errors. Things like brackets and quotation fields will probably mess with the data. (){}[]""
Entity description text, which is separate from notes, should probably also be saved this way. Mostly because both fields support markdown text.

There could be new starting positions for realms. Ancient could start in middle of the galaxy and rest of the realms from outside of the galaxy.

We have private and general public documents used in different places such as Team, Enterprise, etc. As it is not clear which of them are private and which are public, if person removes private document then he/she will not be able to add it to team again unless it is re-uploaded. Being able to identify if document is private or public might be helpful. Small icon like Shield or lock for private c

• New: Balancing speed and detection efficiency
• New: TESS
• New: Command-line interface
• New: Uncertainties

This button is supposed to be used for uploading data so maybe it's better to use something that suggests more uploading than syncing?