Avatar
fmar
30782a8323b7c98b172c5a2af7206bb8283c655be6ddce11133611a03d5f1177
I like freedom and to build stuff Building dart NDK Devops at nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm #bitcoin #nostr #hanggliding #sailing #batucada #diy #powerwall

Better would be to have both options. Nostr is stronger the more clients are developed. And I still use amethyst for sone things.

I did try to comment most of the feed components on amethyst's code and leave just a simple list and it still was not fluid enough. That's why I suspect something related with how data listener/consumer model is handled.

U using 0.11 version? If so and it is off then it's only until android system doesn't kill it. Next version has a complete rewrite of relay socket connectivity and will stop any data fetching on background with pull setting off.

Yeah I'm bit in denial about it being an old phone.

But the fact is that flutter code can make it quite usable.

Can you confirm if primal native android code is not using also jet pack composer? Because they're also quite fast UI on my phone. Maybe it's not a jet pack compose issue but something related to how amethyst uses live data or similar, I don't remember exactly what was the problem. It's on some github task comments...

Absolutely.

Next release in few days.

Main new features:

- gossip (outbox/inbox) model

- nip51 relay sets for blocked/search

- local DB cache for feed/profile/notifications

- login as....

It will check for notifications every 60s if you have the setting pull background service turned on.

This is to avoid needing google fcm push dependency and still get notifications.

Turn it off if you prefer.

I will add a setting for choosing how often.

Po co chłop? Sam ptak nie wystarcze? :)

That's probably because the client doesn't connect to relays but to primal's caching service.