We're excited to share an update on #Fedify's development!
-
We’re excited to share an update on #Fedify’s development! While we’re actively working on Fedify 1.9 in the
mainbranch, we’ve also begun preparations for Fedify 2.0 in thenextbranch.Before you get too excited about revolutionary new features, we want to set clear expectations: Fedify 2.0 will primarily focus on cleaning up technical debt that we couldn’t address due to backward compatibility constraints. This means removing deprecated APIs and making breaking changes that will ultimately result in a cleaner, more maintainable codebase. Think of it as a major housekeeping release—necessary work that will make Fedify better in the long run.
Some of the planned improvements include adding
readonlymodifiers throughout our types and interfaces to better enforce our immutability-by-default principle, implementing our own RFC 6570 URI Template library for symmetric expansion and pattern matching, and various CLI tool migrations to our new Optique framework for better cross-runtime support. While the majority of changes will be about refinement rather than revolution, these updates will strengthen Fedify’s foundation and improve interoperability across the #fediverse. You can track all planned changes in detail by checking out the Fedify 2.0 milestone on our GitHub repository.#Fedify2 #fedidev #ActivityPub
-
We’re excited to share an update on #Fedify’s development! While we’re actively working on Fedify 1.9 in the
mainbranch, we’ve also begun preparations for Fedify 2.0 in thenextbranch.Before you get too excited about revolutionary new features, we want to set clear expectations: Fedify 2.0 will primarily focus on cleaning up technical debt that we couldn’t address due to backward compatibility constraints. This means removing deprecated APIs and making breaking changes that will ultimately result in a cleaner, more maintainable codebase. Think of it as a major housekeeping release—necessary work that will make Fedify better in the long run.
Some of the planned improvements include adding
readonlymodifiers throughout our types and interfaces to better enforce our immutability-by-default principle, implementing our own RFC 6570 URI Template library for symmetric expansion and pattern matching, and various CLI tool migrations to our new Optique framework for better cross-runtime support. While the majority of changes will be about refinement rather than revolution, these updates will strengthen Fedify’s foundation and improve interoperability across the #fediverse. You can track all planned changes in detail by checking out the Fedify 2.0 milestone on our GitHub repository.#Fedify2 #fedidev #ActivityPub
fedify@hollo.social congrats!
When we launched version 2 it was done similarly… much changed in the backend but the day to day UI remained exactly the same.
It was a major release because of how much work and refactoring went into it, and we said “if you don’t notice anything different it means we did our job right”
-
R ActivityRelay shared this topic
