It NEVER fails
-
d@nny "disc@" mc²replied to Charles U. Farley on last edited by
@freakazoid @jdp23 @moira @inquiline @cmdr_nova @julian governance is hard when people want to influence it via out-of-band methods to achieve their own goals at the expense of other stakeholders. governance requires mutual respect and the will to invest in improving processes instead of working around them. governance requires the abolishment of implicit hierarchy. the group that continually succeeds at this over time will hold the mandate of heaven and will succeed mastodon's unjust rule. cc @ireneista
-
Robert Kingett backupreplied to Jon on last edited by
@jdp23 @freakazoid @moira @inquiline @cmdr_nova @julian Do you have a link for LetterBook?
-
Jonreplied to Robert Kingett backup on last edited by
-
[email protected]replied to d@nny "disc@" mc² on last edited by [email protected]@hipsterelectron @jdp23 @moira @freakazoid @inquiline @cmdr_nova @julian
>i believe there are already mastodon-compatible codebases not written in ruby on rails
What do you mean by "mastodon-compatible"? If it's "talks AP and presents (a superset of) masto client api" then you're replying to one (sharkey) and I'm too writing from one (akkoma), and about every other microblogging software from here (pleroma, forks of misskey other than the mainline, gotosocial, even snac2) count.
And as for development of AP outside of Mastodon, there are Fediverse Enhancement Proposals: https://codeberg.org/fediverse/fep but they seem to be largely ignored, unfortunately. -
@[email protected] said in It NEVER fails:
And as for development of AP outside of Mastodon, there are Fediverse Enhancement Proposals: https://codeberg.org/fediverse/fep but they seem to be largely ignored, unfortunately.
Sure, but that's because the FEP list isn't meant to be enforced in that manner. It's purely democratic, and individual implementors (Mastodon and its derivatives included) decide whether or not to follow them.
-
Oops. sorry I missed this over the weekend. I talked about this some in the "It's not an either-or situation" section of https://privacy.thenexus.today/mastodon-hard-fork/#either-or
"There are hundreds of thriving communities running on Mastodon and its forks today, some of which have been around for years, and there isn't any way yet to move a community to a new platform. A new fork can make a lot of valuable incremental improvements before (or in parallel with) rewriting. And GoToSocial's niche is small or single-user instances; kudos to them for taking that focus, but that also means it's not clear how well-suited it'll be for medium-sized community-oriented instances with several hundred or more users"
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] -
David Gerardreplied to d@nny "disc@" mc² on last edited by
@hipsterelectron @[email protected] @moira @freakazoid @inquiline @cmdr_nova @julian
what do you mean that isn't provided by pleroma, misskey and their forks?
completely unrelated codebases. but the API is incrementally becoming compatible between these and Mastodon just so everyone can talk to each other.
hell, even Lemmy is motivated to interoperate with Mastodon sufficiently that awful.systems has active users on Mastodon instances who participate (mostly) just fine.
-
d@nny "disc@" mc²replied to David Gerard on last edited by
@davidgerard @moira @freakazoid @inquiline @cmdr_nova @julian an explicit specification for the API, ideally a w3c spec is what i'm thinking of. agree that most forks are working their way towards this but if we have a formal protocol we can bash eugen over the head with it is all
-
@[email protected] @[email protected] there is one, the C2S API for ActivityPub.
-
@julian @hipsterelectron oh yeah anything that will get website boy to come to the party will save a lot of annoyance
