Getting closer to kibo.money v0.5 feature parity but there will be changes (for example changing min/max markers which caused jumps on more limited hardware by a magnetic crosshair)
#Bitcoin
Open vibe’s image quality is terrible lol
Major work being done on kibo.money for BRK
On the menu we have:
- Support for the new datasets format (from the new API)
- Support for multiple intervals (from the new API)
- Migrating to the Lightweight Charts v5 from v4
Which means many breaking changes and a lot of code to rewrite
That before the 5 year, everyone was constantly talking about the 4 year (below) until it went to shit and didn't fit the narrative
Let Bitcoin do it's thing and "stay humble, stack sats"
Actually yeah but it was a disaster
Tried crossposting (via https://connect.nos.social) to a new x account (which I created to hopefully reach more people)
It got insta-banned
test
Just like on the screenshot (which is option 1)
res = fetch(URL).json()
arr 1 = res[0]
wantedValue = arr1[index]
Hope that's clear enough
When fetching multiple datasets at once, do y'all prefer
[arr1, arr2]
OR
[
[arr1[0], arr2[0]],
[arr1[1], arr2[1]],
...
]
?
Currently supporting the first option in BRK
Was hoping for a bit more too
Bitcoin Research Kit
An exact description of Mullvad browser
Rust FTW
But it’s quite interesting, for one it must’ve been the biggest TS project out there but secondly the funny part is that it’s the literal opposite of what languages usually do (going from a non native compiler to a different one)
Wonder what will be the repercussions of this move, if any
Anyway TS was fun but personally I moved to JsDoc and didn’t look back
