Some questions for the Future
Hi, I would like to implement some other parts of the API (Room Topic, room image, ...) in the next days. Wondering if you would be interested in maintaining the SDK in the future (acc the PR ;-) ? @k-karuna I have forked from @SlimeQ repo so it would be nice if @SlimeQ could also send a PR for all his new stuff, because I would be rely on some of this .
Originally posted by @SlimeQ in https://github.com/baking-bad/matrix-dotnet-sdk/issues/11#issuecomment-1942395800
Would love to bring this SDK a bit further because we would like to use this in some parts of our Hackerspace in the future.
Cool, feel free to contribute! We are using this SDK as a transport layer for text messages in another SDK, so the key requirement for us - keep backward compability 😊
Hi, just a quick question: Is it a problem to switch to the api version v3 ? What I saw so long there are changes that will break. But newer matrix servers will no longer support the r0 version.
Hi, just a quick question: Is it a problem to switch to the api version v3 ? What I saw so long there are changes that will break. But newer matrix servers will no longer support the r0 version.
Primary feature is to be able to create textual channel of communication between clients, so it is ok if this will not be break backward compability for high-level SDK consumers.