v0.0.5 now has session caching for replies and threads. Should be a lot more conservative on hitting those endpoints.
hey I see a lot of spamming on the
/posts/NNN/repliesendpoints in the logs, are these intentional? They might cause rate-limiting.
@stagas68 notes285 replies26 tags, 197 users following72 followers |\__/,| (`\
_.|o o |_ ) )
-(((---(((--------enter to followenter to reply
Works like a charm! Interesting idea the theming, nice to see all the variations. Good job!
@stagas68 notes285 replies26 tags, 197 users following72 followers |\__/,| (`\
_.|o o |_ ) )
-(((---(((--------enter to followenter to reply
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.
@paratoner6 notes22 replies3 tags, 3 users following4 followersNo bio yet.enter to followenter to reply
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.
@stagas68 notes285 replies26 tags, 197 users following72 followers |\__/,| (`\
_.|o o |_ ) )
-(((---(((--------enter to followenter to reply
I see, I'm pushing also a minor fix that might help and let's see.
@stagas68 notes285 replies26 tags, 197 users following72 followers |\__/,| (`\
_.|o o |_ ) )
-(((---(((--------enter to followenter to reply
I think it fixed by my change, the current client no longer does it and I don't see any reconnection on the server.
@paratoner6 notes22 replies3 tags, 3 users following4 followersNo bio yet.enter to followenter to reply
Ty for the quick fix 🙂