Like it or not, #Mastodon successfully did an #EEE of the #Fediverse as far as API is concerned.
Like it or not, #Mastodon successfully did an #EEE of the #Fediverse as far as API is concerned.
Like it or not, #Mastodon successfully did an #EEE of the #Fediverse as far as API is concerned.
Non-Mastodon software with Mastodon API implemented can be connected to third-party services like brid.gy and fedica.com, to mention a few.
It is rare to see third-party services implement any support for non-Mastodon software using their respective API. #Fedica recently added #Pixelfed support; and a few other alt #frontends support either #Misskey or #Pleroma.
So… yeah, there's no doubt the “competition” is over as far as this particular usage is concerned. Mastodon won, got what it wants. Either implement it and allow your users to use other third-party software… or don't and wait for other developers to support your platform.
Not good, but we have to face the reality sooner rather than later, so we can move forward. Maybe make it part of #ActivityPub 2.0 and finally have a universal fediverse API that all can agree with and use.
This rant/reaction stemmed from this thread: https://makai.chaotic.ninja/notes/9xs35rslyb || https://c.im/@youronlyone/113082194085637021
This is EE, we've yet to see Extinguish yet. This is kinda how APIs grow, see also: browser APIs.
Someone implements a new api, makes it usable. Other users can also implement or tweak, and later down the line it is standardised by a committee (or by defacto).
Extinguish is only really possible if you can add an API that your competitors cannot implement, either due to technical reasons or licencing. ActiveX was what did it for Browsers.
The fact that this API has been implemented means that Extinguish has not happened.
Isn't the point of EEE that it's evil? (so it's more like EEEE)