Fedify 1.0.9

Released on November 14, 2024.

• Suppressed a TypeError with a message unusable due to Node.js's mysterious behavior. [#159]

  • The verifyRequest() function no longer throws a TypeError when a given Request object's body is already consumed or locked. Instead, it logs an error message to the ["fedify", "sig", "http"] logger category and returns null.
  • The Federation.fetch() method no longer throws a TypeError when a given Request object's body is already consumed or locked. Instead, it logs an error message to the ["fedify", "federation", "inbox"] logger category and responds with a 500 Internal Server Error.

Fedify 0.15.7

Released on November 14, 2024.

• Suppressed a TypeError with a message unusable due to Node.js's mysterious behavior. [#159]

  • The verifyRequest() function no longer throws a TypeError when a given Request object's body is already consumed or locked. Instead, it logs an error message to the ["fedify", "sig", "http"] logger category and returns null.
  • The Federation.fetch() method no longer throws a TypeError when a given Request object's body is already consumed or locked. Instead, it logs an error message to the ["fedify", "federation", "inbox"] logger category and responds with a 500 Internal Server Error.

Fedify 1.2.4

Released on November 12, 2024.

• Fixed a bug where default document loaders had thrown a TypeError with a message Body is unusable: Body has already been read or Body already consumed when the content type of the response was an HTML document and there's no link to a JSON-LD document.

• Fixed a bug where verifySignature() and verifyJsonLd() functions sometimes had thrown a jsonld.ValidationError error. Now such errors are caught and logged as warnings, and the signature to verify is considered as invalid.

Fedify 1.1.4

Released on November 12, 2024.

• Fixed a bug where default document loaders had thrown a TypeError with a message Body is unusable: Body has already been read or Body already consumed when the content type of the response was an HTML document and there's no link to a JSON-LD document.

• Fixed a bug where verifySignature() and verifyJsonLd() functions sometimes had thrown a jsonld.ValidationError error. Now such errors are caught and logged as warnings, and the signature to verify is considered as invalid.

Fedify 1.0.8

Released on November 12, 2024.

• Fixed a bug where default document loaders had thrown a TypeError with a message Body is unusable: Body has already been read or Body already consumed when the content type of the response was an HTML document and there's no link to a JSON-LD document.

• Fixed a bug where verifySignature() and verifyJsonLd() functions sometimes had thrown a jsonld.ValidationError error. Now such errors are caught and logged as warnings, and the signature to verify is considered as invalid.

Fedify 0.15.6

Released on November 12, 2024.

• Fixed a bug where default document loaders had thrown a TypeError with a message Body is unusable: Body has already been read or Body already consumed when the content type of the response was an HTML document and there's no link to a JSON-LD document.

Fedify 1.2.3

Released on November 6, 2024.

• The fedify node subcommand now can recognize multiple values of the rel attribute in the <link> HTML elements.

Fedify 1.2.2

Released on November 1, 2024.

• Handle connection errors (rather than HTTP errors) in the Context.sendActivity() method.

• Support the fedify command on Windows on ARM64 via x64 emulation. [#160]

Fedify 1.2.1

Released on October 31, 2024.

• Now fedify node command can render the node's favicon with image/vnd.microsoft.icon or image/x-icon format.

Fedify 1.2.0

Released on October 31, 2024.

• Added InboxContext.recipient property.

• Added NodeInfo client functions.

  • Added getNodeInfo() function.
  • Added GetNodeInfoOptions interface.
  • Added parseNodeInfo() function.
  • Added ParseNodeInfoOptions interface.

• Re-exported Semantic Versioning-related types and functions:

  • Added SemVer type.
  • Added formatSemVer() function.
  • Added parseSemVer() function.

• Added followedMessage property to Actor type in Activity Vocabulary API.

  • Added Application.followedMessage property.
  • new Application() constructor now accepts followedMessage option.
  • Application.clone() method now accepts followedMessage option.
  • Added Group.followedMessage property.
  • new Group() constructor now accepts followedMessage option.
  • Group.clone() method now accepts followedMessage option.
  • Added Organization.followedMessage property.
  • new Organization() constructor now accepts followedMessage option.
  • Organization.clone() method now accepts followedMessage option.
  • Added Person.followedMessage property.
  • new Person() constructor now accepts followedMessage option.
  • Person.clone() method now accepts followedMessage option.
  • Added Service.followedMessage property.
  • new Service() constructor now accepts followedMessage option.
  • Service.clone() method now accepts followedMessage option.

• Log messages now can be traced using LogTape's implicit contexts. [#118]

• Added options for an AMQP driver to fedify init command.

  • Added amqp value to the -q/--message-queue option of the fedify init command.

• Added fedify node subcommand.

• Added more log messages using the LogTape library. Currently the below logger categories are used:

  • ["fedify", "nodeinfo", "client"]