Was anyone realistically thinking about creating a #dotnet implementation of #mastadon ?

I sorta started on it, but wasn't going to continue if there's a #Microsoft led effort.

If there's no existing project, I'll try to gather some collaborators and continue.

Who's interested in trying to get a #dotnet7 version going?

#OSS #foss

Please boost to help me find people or a project! Thanks! 

@brendoneus I think the optimal way for new Mastodon client libraries to be written would be for someone to tackle https://github.com/mastodon/mastodon/issues/1404 to hook up a tool to automatically generate an #OpenAPI spec. Then tools like openapi-generator could be used to generate a client. Very little code would need to be written by hand, and it would benefit the creation of clients in any language supported by the generator. #MastoDev
API Documentation via Swagger / RAML / Others · Issue #1404 · mastodon/mastodon

In order to provide more accessible informations about REST API usage, it would be great to have an API specification in Swagger (http://swagger.io/) or RAML (http://raml.org/). Great job ^^

GitHub
@Eliot_L @brendoneus fwiw there are at least a couple of (recent) efforts to make an OpenAPI spec for the Mastodon API that I've found on GitHub to help to address that issue
@andypiper @Eliot_L @brendoneus I was quite surprised it was a stock HTTP style API - I was kinda expecting some fancy modern day GraphQL type thing - but that doesn't really fit with ActivityStreams etc.
@talios @andypiper @brendoneus To be fair, keep in mind that development of Mastodon was started in 2016 by a single developer. What might seem obvious in hindsight might not have been as obvious then. And I think these things are more difficult to bolt on after-the-fact.
@andypiper @brendoneus @Eliot_L true - I'm not even sure Graphql would be good either (subscriptions maybe) but you'd still need federation.