The ugly news: the error message when .NET Standard versions mismatch isn't very helpful, you have to look up the matrix (https://docs.microsoft.com/en-us/dotnet/articles/standard/library)
to figure out what you should retarget.
The good news: I know a little more about NuGet now.
The bad news: I still don't have a way to unit test a .NET Standard library in Visual Studio 2017.
Of course, now I see there's already a .NET Standard library for Mastodon... I kinda still want to roll my own, though...
This is apparently a SSL versioning thing: https://github.com/glacasa/Mastonet#connection-issues-with-net-framework
Maybe I'm betraying my lack of experience, but to /api/v1/apps you POST "key=value&otherkey=othervalue" but the response is JSON? Why not make both JSON?
To be clear, in order to make a client-side app that can connect to an arbitrary Mastodon instance, the app itself would have to register as a client w.r.t. #OAuth2 ? So each user of my app would be registered as a separate client as far as OAuth is concerned?
I'm not saying that's bad, I'm just making sure that's the way people are doing it.
Everyone is welcome as long as you follow our code of conduct! Thank you. Mastodon.cloud is maintained by Sujitech, LLC.