We will also be publishing FEPs to ensure that this becomes a standard that can be supported by every ActivityPub implementation.
The #mastodon team just can’t help reinventing features. It’s already a standard any #ActivityPub implementation can support. They could even jump in the discussion forum and work on modifying the existing #FEP If its missing something they need.
Yes, it takes time, but we are a very small team, with only one full-time developer for the backend
It’s wild hearing the largest project on the #fediverse complain about bandwidth/resources. They are, by far, the most well funded organization in the space. Maybe if they stopped ignoring every other implementation and collaborated, it would be a better utilization of their “limited” resources?
