Fedify 1.0.16

Released on February 19, 2025.

• Fixed a bug where the fedify init command had failed to locate package managers on Windows. [#210]

• The fedify command became aware of FEDIFY_LOG_FILE environment variable to log messages to a file. If the variable is set, the command logs messages to the file specified by the variable.

Fedify 1.4.1

Released on February 10, 2025.

• Fixed a bug with nested object hydration in Activity Vocabulary API where deeply nested properties (like Object.getAttribution() on Activity.getObject()) were't being properly hydrated during toJsonLd() calls. Previously, subsequent calls to toJsonLd() on nested objects could result in inconsistent JSON-LD output where nested objects remained as URLs instead of being fully expanded.

Fedify 1.3.8

Released on February 10, 2025.

• Fixed a bug with nested object hydration in Activity Vocabulary API where deeply nested properties (like Object.getAttribution() on Activity.getObject()) were't being properly hydrated during toJsonLd() calls. Previously, subsequent calls to toJsonLd() on nested objects could result in inconsistent JSON-LD output where nested objects remained as URLs instead of being fully expanded.

Fedify 1.2.12

Released on February 10, 2025.

• Fixed a bug with nested object hydration in Activity Vocabulary API where deeply nested properties (like Object.getAttribution() on Activity.getObject()) were't being properly hydrated during toJsonLd() calls. Previously, subsequent calls to toJsonLd() on nested objects could result in inconsistent JSON-LD output where nested objects remained as URLs instead of being fully expanded.

Fedify 1.1.12

Released on February 10, 2025.

• Fixed a bug with nested object hydration in Activity Vocabulary API where deeply nested properties (like Object.getAttribution() on Activity.getObject()) were't being properly hydrated during toJsonLd() calls. Previously, subsequent calls to toJsonLd() on nested objects could result in inconsistent JSON-LD output where nested objects remained as URLs instead of being fully expanded.

Fedify 1.0.15

Released on February 10, 2025.

• Fixed a bug with nested object hydration in Activity Vocabulary API where deeply nested properties (like Object.getAttribution() on Activity.getObject()) were't being properly hydrated during toJsonLd() calls. Previously, subsequent calls to toJsonLd() on nested objects could result in inconsistent JSON-LD output where nested objects remained as URLs instead of being fully expanded.

Fedify 1.4.0

Released on February 5, 2025.

• Document loader and context loader are now configurable with a factory function for more flexibility.

  • Deprecated CreateFederationOptions.documentLoader option. Use CreateFederationOptions.documentLoaderFactory option instead.
  • Deprecated CreateFederationOptions.contextLoader option. Use CreateFederationOptions.contextLoaderFactory option instead.
  • Added DocumentLoaderFactory type.
  • Added DocumentLoaderFactoryOptions interface.
  • Added the second parameter with DocumentLoaderFactoryOptions type to AuthenticatedDocumentLoaderFactory type.
  • GetAuthenticatedDocumentLoaderOptions interface became to extend DocumentLoaderFactoryOptions interface.
  • Added a type parameter TContextData to CreateFederationOptions interface.
  • Fedify now assigns a random-generated http:/https: URI to activities if these do not have explicit id properties. This behavior can be disabled by excluding autoIdAssigner() from the CreateFederationOptions.activityTransformers option.

• Introduced ActivityTransformers for adjusting outgoing activities before sending them so that some ActivityPub implementations with quirks are satisfied.

  • Added @fedify/fedify/compat module.
  • Added ActivityTransformer type.
  • Added autoIdAssigner() function.
  • Added actorDehydrator() function.
  • Added defaultActivityTransformers constant.
  • Added CreateFederationOptions.activityTransformers option.

• The suppressError option of Activity Vocabulary APIs, traverseCollection() function, and Context.traverseCollection() method now suppresses errors occurred JSON-LD processing.

• WebFinger responses are now customizable. [#3]

  • Added ActorCallbackSetters.mapAlias() method.
  • Added ActorAliasMapper type.

• Added Context.getNodeInfo() method. [#203]

• Added shares property to Object class in Activity Vocabulary API.

  • Added Object.sharesId property.
  • Added Object.getShares() method.
  • new Object() constructor now accepts shares option.
  • Object.clone() method now accepts shares option.

• Added likes property to Object class in Activity Vocabulary API.

  • Added Object.likesId property.
  • Added Object.getLikes() method.
  • new Object() constructor now accepts likes option.
  • Object.clone() method now accepts likes option.

• Added emojiReactions property to Object class in Activity Vocabulary API.

  • Added Object.emojiReactionsId property
  • Added Object.getEmojiReactions() method.
  • new Object() constructor now accepts emojiReactions option.
  • Object.clone() method now accepts emojiReactions option.

• Added allowPrivateAddress option to LookupWebFingerOptions interface.

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

  • ["fedify", "compat", "transformers"]

• Added -t/--traverse option to the fedify lookup subcommand. [#195]

• Added -S/--suppress-errors option to the fedify lookup subcommand. [#195]

Fedify 1.3.7

Released on February 1, 2025.

• Updated LogTape to version 0.8.1, which fixes a bug where lowestLevel option had incorrectly behaved.

Fedify 1.3.6

Released on January 31, 2025.

• Fixed a bug where getUserAgent() function had returned a User-Agent string with a wrong JavaScript runtime name on Node.js. [#203]

Fedify 1.3.5

Released on January 21, 2025.

• Fixed a bug where CreateFederationOptions.allowPrivateAddress option had been ignored by the Context.lookupObject() method when it had taken a fediverse handle.

• The lookupWebFinger() function became to silently return null when it fails to fetch the WebFinger document due to accessing a private network address, instead of throwing a UrlError.