2 ms·
Because then you're bound to the common protocol and it's development process, which is a waste if you have no intention of using federation.
by detaro 7y ago
Because then you're bound to the common protocol and it's development process, which is a waste if you have no intention of using federation.
- shmerl 7y agoI view it the opposite way. It's waste of time to reinvent the wheel and not concentrate resources. Federated protocol can be used without federation fine, but not the other way around. For FOSS projects, not doing it is strange, especially when lack of adoption for federated options is still a major global problem. So I'd question the intent behind this particular project. For those who don't care about openness (like Slack), I'd expect such behavior. But for open projects - not really.