You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[FediDB software](https://fedidb.org/software): periodically polled software census, with statistics per implementation
77
-
78
-
### Non-backwards-compatible changes
79
-
80
-
Non-backwards-compatible changes to the specification require chartering a new working group at the W3C. It also requires making changes in dozens of ActivityPub implementations and tens of thousands of running servers. This is a lot of work and is not done lightly.
72
+
Breaking changes to the specification require chartering a new working group at the W3C. It also requires making changes in dozens of ActivityPub implementations and tens of thousands of running servers. Breaking changes also cause disruption on the working network, since implementations and servers will upgrade gradually, on their own pace, not all at once. This is a lot of work, inhibits the point of the protocol (connecting people and communities), and is not done lightly.
81
73
82
74
Examples of such changes:
83
75
84
76
- Making optional features mandatory
85
77
- Forbidding optional features
86
-
- Deprecating features
87
-
- Making
78
+
- Forbidding required features
88
79
89
80
To propose a breaking change to ActivityPub, add a new issue. It will be discussed and flagged for the next version of ActivityPub.
81
+
82
+
## Lists of implementations
83
+
84
+
These lists are externally maintained and initiated.
0 commit comments