Create a user account for your bot. You’ll probably want to write down the password somewhere in case you want to log back in later. Discourse does not need it.
Use the interface to join any rooms that you want to be able to send notifications to
Open the user settings by clicking your avatar in the top left, then All Settings
Configure the bot’s display name and avatar
Switch to the “Help and About” tab, scroll down to “Advanced”, and copy the Homeserver address and your “Access Token” - you’ll need them later.
DO NOT CLICK LOG OUT. If you do, the Access Token will be invalidated, and it won’t work. Instead, just close the incognito window. If you forgot to open an incognito window, go back to step 1
Set up Discourse
In your Discourse site settings, enter your home server address in the chat_integration_matrix_homeserver setting. Make sure to include the protocol. (e.g. https://matrix.org). Do not include a trailing slash.
Paste the access token you copied earlier into the chat_integration_matrix_access_token site setting
Enable chat_integration_matrix_enabled
Go to the Plugins tab, then Chat Integration
Go to the Matrix tab, then Add Channel
Enter a name for the channel (this is only displayed in the admin interface, it can be anything)
Enter the “Room ID” for a room that you want to send notifications to. In the Element web client, you can find it by opening your room, clicking the name at the top, then scroll to the bottom. It will look something like
!cdGUowUAqlgLHVerqE:matrix.org
Save Channel
Use the Test button on the channel you just created to check that everything’s working. You should see something like this:
At the time of writing, there does not seem to be a way of obtaining an “access token” for a “bot” in a user-friendly way. The incognito window solution is the most user-friendly way I could find
The matrix spec does not currently define a way of providing “rich text” messages. There is a spec under development, but for now this plugin uses the “unofficial” method which has been adopted in the element.io client. Clients that do not support this will simply fall back to a plain text message
There is no provision in this implementation for ‘refreshing’ access tokens. This is based on the understanding that the majority of homeservers currently in use do not expire tokens. If this changes in the future, this will need to be revisited.
I just tried setting up a matrix integration using the instructions above, and it all worked ok. Can you confirm that you’re running the latest version of Discourse and this plugin?
Are you using the matrix.org homeserver, or your own homeserver? The 422 error is coming from that server.
I would suggest double checking your channel identifier, and also your matrix access token in your Discourse site settings.
I have absolutely the same issue as @almereyda has. @david, can you update obtaing “Access Token”, please? (Riot seems to be intensively developed )
+“Doctor log”
Acabei de executar a configuração e parece ter funcionado bem. Algumas teorias:
Seus salas estão criptografadas? Não tenho certeza se precisamos fazer um trabalho extra para suportar salas criptografadas.
Talvez os tokens de acesso expirem após algum tempo. Isso não acontecia quando eu construí a integração em 2017, mas isso foi há muito tempo . Tentarei minha configuração local novamente esta semana e verei se ainda funciona.
Para constar, @mattdm e eu conseguimos rastrear isso até uma barra final na URL do Homeserver nas configurações do Discourse.
Adicionei uma nota sobre isso às instruções no OP e também atualizei as instruções do token de acesso para funcionar com a interface mais recente do element.io.
Ao instalar a versão mais recente do plugin de chat (commit ba40ede510986f74a23345082ac578e126467b97) e configurar uma sala de teste do Matrix (sala pública, sem criptografia), recebo um erro HTTP 500 ao tentar um teste conforme descrito acima. O mesmo sintoma de spinner infinito que requer a atualização da página.
O token de acesso da conta do bot foi verificado independentemente enviando uma mensagem para a sala usando a API (_matrix/client/r0/rooms/{room_id}/send/m.room.message) para o nosso próprio servidor Matrix.
Os logs do Discourse mostram
Started POST "/admin/plugins/chat-integration/test" for 141.142.60.55 at 2022-11-16 18:16:47 +0000
Processing by DiscourseChatIntegration::ChatController#test as */*
Parameters: {"channel_id"=>"107", "topic_id"=>"466"}
Completed 500 Internal Server Error in 62ms (ActiveRecord: 0.0ms | Allocations: 10109)
NameError (uninitialized constant FinalDestination::HTTP)
app/controllers/application_controller.rb:387:in `block in with_resolved_locale'
app/controllers/application_controller.rb:387:in `with_resolved_locale'
lib/middleware/omniauth_bypass_middleware.rb:71:in `call'
lib/middleware/content_security_policy/middleware.rb:12:in `call'
lib/middleware/anonymous_cache.rb:361:in `call'
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/request_tracker.rb:198:in `call'
Não tentei, mas seria interessante. Você quer dizer colocar todas as postagens em um único thread para reduzir a desordem do canal, ou isso seria postar respostas de tópicos em um thread do matrix?
Tenho curiosidade se houve algum desenvolvimento na adição de suporte a respostas encadeadas para o Matrix. Alguns de nossos usuários apreciariam isso.
)
. Tentarei minha configuração local novamente esta semana e verei se ainda funciona.