Alex Schroeder
Alex Schroeder
The API doesn't support that, so the Bitlbee Server would have to remember the last message id seen or something like that. Currently, nothing like that is supported.
Check out [websockets](https://github.com/kensanata/bitlbee-mastodon/blob/websockets/src/websockets.md) for some documentation of what I'm trying to do.
Looks like this part is done! I'm using the websocket branch right now. More testing, more daily use required, of course. All the testing needs to happen with Mastodon, however!...
Still unhappy. For the moment, I am back on the master branch, without websockets. If somebody knows how to do it, let me know.
Anybody interested in helping out, the beginning of some code is in the websockets branch: #43.
I currently able to sign in to a Pleroma instance, but I keep getting disconnected: ```text pleroma - Logging in: Verifying credentials pleroma - Logging in: Getting home timeline pleroma...
That issue was solved by also appending the access token as a parameter to the URL. This goes against what I believe is correct. It should be passed along as...
Next problem: I'm getting empty websocket messages that cannot be parsed, I'm not seeing any statuses in my timeline and I'm being disconnected after 2min. ```text 23:12 pleroma - Logging...
I’m not sure but I think this is caused by #21. This ought to work but it doesn’t.
Hm. Always a possibility, unfortunately. It works for me so I wonder whether you're doing anything suspicious? Filters? Hashtags?