@kaniini Hey, how's #litepub going? Trying to reverse engineer a list of API endpoints to implement for Mastodon federation compatibility, and existing docs are ... sub-optimal, to say the least. #ActivityPub
A more basal reason why I get mad when I see 'node install' (or 'pip install' to be fair) under "Installation" in a program's docs, is that it speaks to the existence of a fast-growing class of software which makes BIG assumptions about potential users, chief among them that they want an entire development toolchain on their system to run what should be distributed as a single fucking executable! All the bloat of Electron, none of the ease. #UXfail
A more basal reason why I get mad when I see 'node install' (or 'pip install' to be fair) under "Installation" in a program's docs, is that it speaks to the existence of a fast-growing class of software which makes BIG assumptions about potential users, chief among them that they want an entire development toolchain on their system to run what should be distributed as a single fucking executable! All the bloat of Electron, none of the ease. #UXfail
...and NONE of the people who've written an #OpenAPI documentation rendering tool can be bothered to ship a package for it.
(Except a node package. Some of them can ship those. By god, I've made it to late 2018 without installing an ENTIRE DEVELOPMENT ECOSYSTEM to run somebody's stupid tool, I'm not about to start now.)
((I'm just going to pretty-print the JSON and dump it in my issue tracker and call it good, no thanks to any of these helpful tools.))
I'm trying to find docs on the federation API for Masto et al. Mistake #1, I know. Anyway I found a GNUsocial plugin somebody is writing; the API is specified in JSON using a standard called #OpenAPI 3.
Great, I think, surely there's a web tool to generate docs from this definition. Lo, there are several! All written with hip JS frameworks du jour.
Not a single fucking ONE of them can produce an intelligible printout, nor save intelligible HTML. Not one.
@RussSharek Good to know. Not sure what's going on, I've got a user whose join doesn't seem to be syncing. Ah well, I suppose we'll either figure it out or maybe just use Jabber.
So I tried a #Riot / #Matrix room (on a different server than riot.im, in an attempt to be a good federated citizen) with encryption, and that was pretty terrible, so I tried one without, and it doesn't seem able to present a fully consistent view to people who've joined or are trying to join. Is this the current state of the platform (with encryption turned off), or am I experiencing weird rare problems that are unlikely to keep happening a lot?
@rick_777 Thanks, definitely have stared at those docs a while but they're pretty hard to understand from an app-building perspective. I think what I'm looking for is "given ActivityPub, here is an example of actually implementing $trivial_social_app."
Is there any overview out there about how to talk to e.g. the Mastodon backend, Pleroma, etc, that is higher level than raw API docs? Trying to find a good place to start, and digging through code and the blog posts I've seen so far isn't getting in my brain. #mastodev#fedidev#pleromadev
A functional test suite for the #Pleroma back end would also be a functional test suite for any drop-in replacement, including those not yet written... #fediverse#mastodev#TDD
A functional test suite for #Pleroma would also be a functional test suite for any compatible API, including those not yet written... #fediverse#mastodev#TDD
it’s not enough to produce free alternatives to scabware if we can’t support the labor and materials to steward the ‘ware through every cycle of its development and usage. linux is a spectacular failure in this regard: a vital technology and thriving community eclipsed by corpers who can just buy lifetimes, who can turn our works into rent-generators with impunity. to make better software, we must enmesh our obligations to the craft with our communal survival and wellbeing.