Lysand 0.4

0.4 • The Federation Update

After a month of work, Lysand 0.4 is finally out now!

This release adds:

• Support for inbound and outbound federation with other Lysand instances: This is limited to follow requests and sending notes for now
• Full Docker support: Docker is now the default way to run a production Lysand instance
• Automatic database migrations: Database is now automatically migrated without needing to run prisma commands (Prisma has been removed)
• Better stability: Lysand 0.4 brings refactoring into API routes that strictly validates all data sent to it, preventing accidental 500 errors
• Better logging: All server errors are now logged properly instead of displaying an ugly stack trace in the logs. Additionally, console logs are now colored and have dates formatted
• Non-monolithic architecture: Hosting the database, API layer and frontend separately on entirely different servers (and even having multiple of those at once) is now possible!
• Many bugfixes: Many bugs to existing routes and client incompabilities have been eradicated.
• Official production instance: An official instance, https://social.lysand.org is now up for testing purposes! (do not expect this instance to be stable, as it follows the main branch). It also has a sister at https://social2.lysand.org for federation testing.

In progress:

• ActivityPub compatibility: @CutestNekoAqua is now working on an ActivityPub bridge for Lysand, allowing you to federate with fediverse instances (this is a work in progress)
• Lysand-FE: A custom frontend for Lysand instances is being developed as an official client

As always, please report any bugs or feature requests at the issue tracker!