5 ms·

curl? O:-) Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. which java sdk did you try?

rb808 9y ago
thanks, I thought it was a bit more complicated with session ids etc, will look at keeping it simple again. I used the Java SDK from Kamax that was on https://matrix.org/docs/projects/try-matrix-now.html https://matrix.org/docs/projects/try-matrix-now.html. would be nice if there are others. I'm excited about it though - is just what I've been looking for.
- maxidorius 9y ago
  I am the author of the SDK - feel free to open an issue on the github repo or come in the dedicated Matrix room #matrix-java-sdk:kamax.io and we'll get you started.
  - rb808 9y ago
    Wow thanks, will check. I had trouble with gradle build, I think because was latest version with intellij.
  - Sammi 9y ago
    All my upvotes to the both of you for your responsiveness. Keep up the good work!
sli 9y ago
> Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. Huh. So Haskell + Servant might be really nice for writing a client, then, yeah?
- Qwertie 9y ago
  Anything you can make HTTP requests in really. I have messed around with sending messages from Ruby and Bash and it's quite easy. And a lot more easy if there is an SDK for your language which will handle a few things for you.
  - syntaxfree 9y ago
    So what's irssi for Matrix?
    - kqr 9y ago
      weechat-matrix. You should be using weechat over irssi anyway!
      - unicornwizard 9y ago
        Why? Longtime irssi user here.
        kqr 9y ago
        I usually view it as a cost–benefit sort of thing. When a choice has nearly zero cost, only very little benefit is needed to make it the rational choice as far as I'm concerned. What does WeeChat offer over irssi? Very active development, scripting in many languages, dynamic filtering, raw buffer views, sane defaults, helpful configuration interface, good documentation, live/hotswapping upgrades, architectural soundness, many options for interaction (FIFO pipes, client-server protocol) and so on and so forth. I'm always surprised at how little WeeChat gets in my way when I want to do something out of the ordinary. And unless you are heavily invested in the irssi ecosystem, the switch is basically effortless. That's the cost–benefit of it. Another way to view it is this: People who switch from Irssi to WeeChat keep using WeeChat; while people who switch from WeeChat to Irssi go back to WeeChat.
        andrewshadura 9y ago
        What I don't like about WeeChat is the UI. It's subtly different from irssi’s, which makes it difficult for me to switch.

rb808 9y ago

thanks, I thought it was a bit more complicated with session ids etc, will look at keeping it simple again. I used the Java SDK from Kamax that was on https://matrix.org/docs/projects/try-matrix-now.html https://matrix.org/docs/projects/try-matrix-now.html. would be nice if there are others. I'm excited about it though - is just what I've been looking for.

maxidorius 9y ago
I am the author of the SDK - feel free to open an issue on the github repo or come in the dedicated Matrix room #matrix-java-sdk:kamax.io and we'll get you started.
- rb808 9y ago
  Wow thanks, will check. I had trouble with gradle build, I think because was latest version with intellij.
- Sammi 9y ago
  All my upvotes to the both of you for your responsiveness. Keep up the good work!

sli 9y ago

> Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. Huh. So Haskell + Servant might be really nice for writing a client, then, yeah?

Qwertie 9y ago
Anything you can make HTTP requests in really. I have messed around with sending messages from Ruby and Bash and it's quite easy. And a lot more easy if there is an SDK for your language which will handle a few things for you.
- syntaxfree 9y ago
  So what's irssi for Matrix?
  - kqr 9y ago
    weechat-matrix. You should be using weechat over irssi anyway!
    - unicornwizard 9y ago
      Why? Longtime irssi user here.
      - kqr 9y ago
        I usually view it as a cost–benefit sort of thing. When a choice has nearly zero cost, only very little benefit is needed to make it the rational choice as far as I'm concerned. What does WeeChat offer over irssi? Very active development, scripting in many languages, dynamic filtering, raw buffer views, sane defaults, helpful configuration interface, good documentation, live/hotswapping upgrades, architectural soundness, many options for interaction (FIFO pipes, client-server protocol) and so on and so forth. I'm always surprised at how little WeeChat gets in my way when I want to do something out of the ordinary. And unless you are heavily invested in the irssi ecosystem, the switch is basically effortless. That's the cost–benefit of it. Another way to view it is this: People who switch from Irssi to WeeChat keep using WeeChat; while people who switch from WeeChat to Irssi go back to WeeChat.
        andrewshadura 9y ago
        What I don't like about WeeChat is the UI. It's subtly different from irssi’s, which makes it difficult for me to switch.