Skip to Content
Foru.ms
Foru.ms logo

Changelog

Here you can find all the information you need to keep up with the latest updates to Foru.ms, including new features, bug fixes, and improvements.

Version 2.0

Release Date: January 8, 2026

Version 2.0 introduces a redesigned API with improved consistency, better resource naming, and standardized response formats. This is a major release with breaking changes.

Breaking Changes

Resource Path Changes

All singular resource paths have been consolidated to their plural form:

v1 Pathv2 Path
/api/v1/thread/*/api/v2/threads/*
/api/v1/post/*/api/v2/posts/*
/api/v1/user/*/api/v2/users/*
/api/v1/tag/*/api/v2/tags/*
/api/v1/notification/*/api/v2/notifications/*
/api/v1/private-message/*/api/v2/private-messages/*
/api/v1/report/*/api/v2/reports/*
/api/v1/role/*/api/v2/roles/*

Pagination Response Format

All list endpoints now use a standardized pagination envelope:

{ "data": { "items": [...], "nextCursor": "...", "count": 123 } }

Previously, responses used resource-specific keys like threads, posts, users. Now, all list endpoints return items under the items key.

Reactions System

The like, dislike, upvote, and downvote endpoints have been consolidated into a unified reactions subresource:

Reaction type is now specified in the request body.

Query Parameter Changes

Relationship endpoints have been flattened into query filters:

v1 Endpointv2 Equivalent
GET /api/v1/tag/:id/threadsGET /api/v2/threads?tagId=:id
GET /api/v1/user/:id/threadsGET /api/v2/threads?userId=:id
GET /api/v1/user/:id/postsGET /api/v2/posts?userId=:id

Error Response Format

All errors now follow a consistent format:

{ "error": { "code": "ERROR_CODE", "message": "Human-readable message", "details": {} } }

Subresource Patterns

New subresource patterns for related data:

New Features

Improvements

Version 1.3.3 - 1.9

Version 1.1.0

Version 1.0.0