Embed Notice
HTML Code
Corresponding Notice
- Embed this notice@darkphoenix :blobcatshrug2: i dont think so... how can you as a sharkkey user just say that you would prefer the Masto Client API as a standard...
The reason why nobody implements ActivityPub C2S is basically the individuality of the servers itself, Threading wouldnt be possible in the same way for *key and *oma, it is nearly insane to use the Masto client API as standard...
Tbh, how about properly fixing the S2S standard first and let every server have their own individuality by implementing additional/different Client API's which they need to fulfill their own special features?
It makes sense to unify S2S and C2S when you want to have every server exact with the same features but the main reason that the reality isnt like this is that devs dont want certain features and do want push their own stuff (and that isnt even a critic against gargron)