o7moonive deleted the previous server since editing the description doesn't seem possible at the moment. it seems to not have been removed from the server list though, sorry for making such a mess lol 20:26o7moontest message 1 20:27o7moontest message 2 20:30o7moontest message 3 20:33o7moon5 !! 20:39o7moon6 20:42o7moonif i had to guess, the /post_msg endpoint actually adds a message to channel history but the websocket message is what relays messages to those currently in the channel. ive been trying to manually POST to /send_msg but i think im doing it wrong lol 20:50spythemanhello 21:30o7moono/ 21:31o7moonoh odd it sent twice 21:31o7moonor not 21:31o7moonvisual bug that went away on refresh 21:31spythemanswitching channels makes it show it 2 times 21:43spythemana refresh fixes it, yes 21:43
Mar 1
alex@o7moon /post_msg via HTTP will work, just don't forget to add the "token" cookie 02:14o7moon@alex yep, the issue was that I was copying the form data from the Firefox inspector which had stripped out important spaces 13:38o7moonAs far as I can tell though, I also have to send a websocket message to get it to show up in real time? 13:45alexyes, that is correct 13:54alexit should be fixable on the backend, but for now thats how it works 13:55o7moongot it 13:57
Mar 2
qp908:15
Mar 3
vcvhi? 19:44
Mar 4
alex@o7moon done, /post_msg messages are now sent to websocket clients right away 18:56o7moonnice, i might try writing a terminal client 23:01
other than from the webpage? that seems like the only thing I'm missing to send a message 00:19alexyeah, true will publish /api/me tomorrow 00:34alexdone: 19:20alexhttps://volt.im/api/me19:20alexI've added api documentation to the home page :) 19:26
Mar 8
o7moonthis message sent from my api wrapper 20:18o7moonall it's missing is receiving websocket messages 20:20alexnice :) 20:44
Mar 29
doesnmdoes anyone implement/start implementing mobile client? 11:20alex@doesnm not yet. The volt client will run on mobile later this year. 12:13alexBut it's not open source. 12:14doesnm15:21