Tusky @Tusky

@xurizaemon There isn't a way. Well, technically F-droid's current release uses pull notifications instead of push, but you can't switch between them.

I'm redoing the notifications currently because the old push system was always rather broken. Hopefully pull notifications won't be necessary when I'm done.

@silbaer If you go to the google play store page for tusky it should show a "Become a beta tester" section that has an "I'm in" button. If it doesn't show up, this link should also let you join: https://play.google.com/apps/testing/com.keylesspalace.tusky

@lattera I'm (@Vavassor) accepting donations sort of recently through patreon.com/Vavassor or paypal.me/Vavassor.

I've been avoiding advertising here just because I don't want any confusion that those funds aren't compensating any other contributors.

@maloki There should be a "Become a beta tester" section on the store page now near the bottom with an "I'm in" button.

If there isn't, I think you can also join on this page https://play.google.com/apps/testing/com.keylesspalace.tusky although the wording there makes it sound like a closed beta.

Starting an open beta on Google Play beginning now with version 1.1.4-beta.1.

Beta versions will also be available in .apk form at https://tusky.keylesspalace.com/

Testing a new possible push notifications system is the particular goal at the moment. But I'll be keeping the beta program open from now on. So feel free to join/leave if ever you want to check out in-progress versions.

@roach Oh, that's probably the same issue that some users ran into the update before last? Clearing app data or reinstalling should fix it.

Starting a Roadmap at this page: https://github.com/Vavassor/Tusky/projects/1

Not much there yet, but going forward it'll show generally the progress of features and changes planned for release.

That notifications in general are not working well is the next major thing I'm (@Vavassor) focusing on, by the way.

I'd like to find a system that's consistent and also FOSS, so F-Droid can use the same notification system. I have some promising leads, but things are a bit up in the air still.

Note: this version uses a separate notification system from the version on google play and amazon. It checks for notifications on a set interval, which unfortunately is not so immediate and can diminish battery life.

The reason it was taken off F-Droid in the first place was because of the closed-source tech that was used for push notifications. So this is also why there's this difference in the replacement system.

Other than that, the versions are identical.

Tusky is finally back in the main F-Droid repository! https://f-droid.org/repository/browse/?fdid=com.keylesspalace.tusky

You can just as well search for "Tusky" in the F-Droid app to find it.

@jgbresson It was first reported on blackberry and a few tablet devices, but I haven't heard it being mentioned as a new problem. Were you able to see images on a previous update and not this one?

Also, here's the current issue page for it if you have anything you'd like to add: https://github.com/Vavassor/Tusky/issues/198

@kelbot I can put the fdroid apk on the website if you want. I mostly just didn't because fdroid builds theirs separately so I don't touch it. And it was easier to just copy the google one I already had on hand.

But it wouldn't be hard to do a quick build and put that version up there, too.

@cocorax Unfortunately it's the longest-standing unfixed bug in the app. Usually forcing a refresh like leaving the page and re-opening it gets rid of it, but it's very annoying.

Mostly the trouble is it's not just one single bug and can be caused a few ways and it's not always easy to track down what combination of situations led to it happening.

@vruz I'm thinking it's still broken on some devices, then. What's the brand and model of your tablet?

@vruz Ah someone had just submitted code to fix this issue, I suppose it's not yet fixed for everyone. Did this just start happening or does it always fail to load images for you?

(The bug page for this is here, by the way: https://github.com/Vavassor/Tusky/issues/198 )

Currently (at the very present) I'm adding the build data for Tusky to F-Droid and submitting that as soon as I can. I've received a lot of requests to resubmit the app to their store and inquiries about it.

It could take a while to be approved and hit their next build & release cycle. So it will likely be a couple of days before it can appear on F-Droid.

Tusky 1.1.3 is currently rolling out on Google Play and will be available on the Amazon app store tomorrow! It includes direct messages, profile editing, and viewing your mute list and follow requests.

Also, *many* new translations contributed by generous people: Japanese, Polish, Dutch, Turkish, and Arabic.

There's a Tusky update coming hopefully soon, mostly to address missing features including direct messages, profile editing, a mute list, and follow requests. Also, a BUNCH of new translations.

Right now I'm talking with F-Droid to see if I can get the app back in their store, and working on the follow requests, but everything else is checked off.