True, but google might have enough spite to stick it to meta, who knows.

I’ve reported it as spyware on google play. Let’s see if they ever get around to answering :-P

Yep, it’s going steadily downhill. New bugs introduced, old ones unfixed.

I’ve moved to Liftoff for now, which is nice. As soon as Sync is available, I’ll be there.

Well, if it crashes your phone repeatedly, it’s already worth reporting even if it’s not affecting anyone else for now. Better to fix it early than to leave a critical bug in the code that might affect other functions further down the line, you never know how and where they eventually interlink.

Make sure you report the issues on github as well, so the devs can actively work on them.

https://github.com/dessalines/jerboa/issues/ (just check if a duplicate already exists). Is the instance where your account is registered already migrated to 0.18.0? Apparently using Jerboa 0.0.35 with 0.17.4 (and older) causes problems due to a change in API handling. At least that was the reply I got to some of my reported issues, since my home instance is not yet upgraded.

I’m using Fennec, comes with full add-on support as well. But I’d rather use Jerboa (or in the future, Sync) instead of the mobile browser.

Not yet, but I’m hoping it will come in the future.

On the desktop version it’s possible via a greasmonkey script: https://greasyfork.org/en/scripts/469297-block-lemmy-instances

If you add a second account, you can tap on the arrow next to your profile and add it there, then when you open the profile view again it will show your other account with the full instance name, so… You’re currently using the other one.

But I agree that it’s a bit of a clumsy workaround, and they should show it somewhere (ideally even display the full username instead of just the local one).

That’s good for you, I suppose, and the reason why bug trackers exist. They are not universally applicable.

Comment reply works, and upvoting comments as well.

It’s replying to DMs that’s bugged, and voting on posts that causes the crash.

I’ve reported them both with screenshots and video evidence, you can check it here:

https://github.com/Coffee-Viking (scroll down to the bottom to ‘reported issues’).

https://github.com/dessalines/jerboa/releases

With an alpha version that’s releasing updates every 3-8 days, it’s generally better to get it directly from the source. Google play takes one week to verify new releases, which doesn’t matter for established apps, but with rapid release cycles in active development, it can be annoying.

They are also pushing updates to F-Droid though if you want to have some app store behind it, they publish updates within hours of releasing.

Never crashed for me on login, but there are some showstopper bugs:

You can’t up/downvote a post when you enter the comment view.

Replying to a PM from the inbox will instead send the reply to yourself.

Would be nice, agree.

Yes, Nova is the best! Glad you like it 😁

I haven’t used the redesign for a single minute. Had a look, hated it, went back. But yeah I wouldn’t be surprised if that’s the exact intention.

That’s not quite how ads work.

You get fractions of a cent for displaying them, but the majority of the money comes from clicking, and the CTR (click-through-ratio) is how advertisers measure success.

If you’ve got the full solution on one page, users are more likely to engage in ads. If they follow a link off-site first and continue there, they are unlikely to engage.

Who?

Amen.

Yep, we opened up, polled the users, got told to keep it closed, and down went the shutters.

Yes, on some older comments I received, and it works completely fine for me.