search

kensanata / bitlbee-mastodon

A Mastodon plugin for Bitlbee
https://alexschroeder.ch/software/Bitlbee_Mastodon
GNU General Public License v2.0
30 stars 7 forks source link

Subscribe to local and federated timelines #2

Closed rodneyrod closed 6 years ago

rodneyrod commented 6 years ago

Or if these options already exist, reference them in documentation.

kensanata commented 6 years ago

Yeah, this is missing at the moment. I think all we have is the TIMELINE command which we could adapt, but all it does is show some toots, not open a new stream. A new stream would be opened like the hashtag subscriptions, except for the two special keywords LOCAL and FEDERATED, I guess.

rodneyrod commented 6 years ago

Yep that's pretty much what I had in mind too. Maybe if you were also concerned about getting that mixed up with #local and #federated hashtags, maybe they could be labelled local_timeline and federated_timeline in Bitlbee.

kensanata commented 6 years ago

The current commit 9423fb6 has support for the local and federated keywords when using the timeline command. But that's just a display of the last batch. I also implemented joining the channel and all that (see help mpublic for more). Surprisingly, it seems that the streaming API does not support just local toots. Thus, right now you're getting all the public toots when joining a local channel, i.e. the federated and the local timeline are not distinguished.

kensanata commented 6 years ago

I created an issue for this.

kensanata commented 6 years ago

The new URL seems to work, even if it seems a bit slow right now.

kensanata commented 6 years ago

Fixed in 180569f.

kensanata commented 6 years ago

Hm. I think there's still a bug lurking in there somewhere. When leaving the federated or local channel, the HTTP request isn't killed, the statuses still keep coming, and now they just end up in your default timeline.

kensanata commented 6 years ago

I think this is fixed by b3828c2. I'm still not sure everything works as it should. For example, when I joined both the local and the federated timeline of my instance, I had the impression that statuses on the local timeline got doubled. If that is indeed an issue, we should create a new one for that.

rodneyrod commented 6 years ago

Thanks so much for this, and for the extra work that went upstream too.

kensanata commented 6 years ago

I think 0452610 fixes the toot duplication in the home stream.