corebird/nextbird not updating anymore

[drx69]

on latest 1.7.4.2, you can start it and it gets the feeds, however does not update anymore after that. You can kill it and restart and it gets new feeds, but same thing happens again.

[aia832003]

Same issue here running Pop OS based on Ubuntu 18.10

[Alexmitter]

I can confirm this issue too. Maybe a API change?

[lucaswerkmeister]

Same here as well, haven’t had the time to investigate yet. My current workaround:

while true; do flatpak run --devel de.lucaswerkmeister.nextbird || break; done

And then simply close the app whenever I want to reload the timeline, so it will restart itself automatically :/

[IBBoard]

See my responses to baedert/corebird#825. They changed the API so that there's no streaming. I've replaced streaming with polling (which is how mobile clients tend to do it, for battery life reasons) in https://github.com/IBBoard/corebird/tree/non-streaming

[Alexmitter]

@IBBoard would taking the patch files of your commits at this branch and applying them to this repo be a solution?

[IBBoard]

Give or take the fact that @lucaswerkmeister completely renamed EVERYTHING to Nextbird (and so all the file names are different, and references like "Cb.…" will change), then yeah, you should be able to pull my branch and get things working again 🙂 I've been running with polling-based "streaming" (and DMs, and lists, and search) since a short while after Twitter killed everything.

[lucaswerkmeister]

If you’re okay with it, then I can try to do the rebases (I didn’t change Cb prefixes yet, didn’t think of that), but probably not within the next week. Let’s see how bad the conflicts are :)

[lucaswerkmeister]

See my responses to baedert#825. They changed the API so that there's no streaming.

Well, that was earlier, and Corebird/Nextbird still used to work to some extent, it would just reload the entire timeline (presumably via polling) instead of adding new tweets at the top. But since more recently (three to four weeks ago, I’d estimate), those reloads don’t happen either, and the app just sits there with no activity at all.

[IBBoard]

Feel free to pull/merge - it's all open sourced! (just don't lose my authorship 😉)

As for the behaviour, IIRC Corebird did a single fetch at startup (using the same function as the "I've scrolled to the bottom" action) and initiated a streaming connection. Streaming got killed off, so Corebird wouldn't fetch updates. I'm guessing the full reload was a "network failure" behaviour, but I'm not sure.

Twitter did keep the old API in "flicker" mode for a while, though, so maybe the change from "occasional reload" to "no updates" is because they finally completely turned off the old API on the basis that people have had enough time to update?

[schmittlauch]

I can confirm that @IBBoard's corebird branch still works. I've been using that since the API change.

[lucaswerkmeister]

If you’re okay with it, then I can try to do the rebases (I didn’t change Cb prefixes yet, didn’t think of that), but probably not within the next week. Let’s see how bad the conflicts are :)

Yeah, so this didn’t happen.

The simple truth is that this workaround worked well enough for me that I wasn’t sufficiently motivated to do anything better, for over eight months. And then eventually @IBBoard pinged me about Cawbird, and I’ve been using that since then (end of August).

If anyone was still invested or interested in Nextbird – sorry I let you down. Go use Cawbird instead, it works. I’ll update the Nextbird README and then probably eventually archive this repository.