I understand this, the array is reversed, what is not clear is there is no other way to get to the newest item.. there is no way to have it ordered newest first..
It is only reverse in returned data, not whole history. So, it contains newest, it isn't the first, it is the last element. So, imagine getting limit = 1000, index = -1. The newest is result[result.length - 1]
I have just stepped away from linux
Haha, I don't like linux either. I don't use it unless I have to.
can we help make such improvements? are there ways to get in touch that you are aware of ?
You can open an issue if you think you found a bug:
https://gitlab.syncad.com/hive
As for discord, there are two community discords you can hang around!
HiveDevs discord server:
https://discord.gg/JAEDPH3HVs
Hive (more general) discord server:
https://discord.gg/GUB7BCrE3x
I do know there are other chatting applications people use but I don't use them so I don't know specific details.
thanks for the links to the devs. i think i will log in and see the conversations.
i use netBSD and freeBSD. what is your os of choice?
i get it, but i don't get why . just seems backwards somehow. not something i really want to pursue.
thanks for the links to the HiveDevs chat. I will enjoy listening in. and you said you found answers in the chat logs.
Haha, Wind👀ws, nothing special there
Well I don't really know. Probably due to how it is filtered (it is rocksdb as far as I know). So, reversing it is twice the cost, so they don't I assume.