hey @paratoner6 notes22 replies3 tags, 3 users following4 followersNo bio yet.enter to follow I see a lot of spamming on the /posts/NNN/replies endpoints in the logs, are these intentional? They might cause rate-limiting.
@paratoner6 notes22 replies3 tags, 3 users following4 followersNo bio yet.enter to follow · 10 repliesenter to reply#tlog61 notes18 followersenter to follow #mobile8 notes4 followersenter to follow client new version released ! Optional core Markdown support, simple themes, read-only profile display support. Next I would like to try and get the app on the Play Store for convenience.
Ah, woops! I will take a look at agressive caching for nested threads. I think I overlooked that part while implementing replies. Good catch!
v0.0.5 now has session caching for replies and threads. Should be a lot more conservative on hitting those endpoints. #open_source11 notes29 followersenter to follow #mobile8 notes4 followersenter to follow #tlog61 notes18 followersenter to follow
Works like a charm! Interesting idea the theming, nice to see all the variations. Good job!
Another thing I'm noticing is the firehose endpoint is reconnecting every few seconds instead of being kept alive. Is this a limitation of some sort of the EventSource client you're using? Because it might omit some messages, the reconnection doesn't do any replay.
Ty for the informal beta testing hahaha I've found that the connection drops from the server's heartbeat are treated as errors by my client. Pushing a fix in 0.0.6 to reconnect quick and reconcile missed msgs.
I see, I'm pushing also a minor fix that might help and let's see.
I think it fixed by my change, the current client no longer does it and I don't see any reconnection on the server.
Ty for the quick fix 🙂