f7f2146fa5
miscellaneous cleanup and notes
4 years ago
76b90d3c8a
correct a few more places where the client expected hashes in pin responses
...
or where the server incorrectly provided them
4 years ago
8e725f3d7c
stop returning the hash of all user pins after pinning
...
the client doesn't use it and it's CPU-intensive
4 years ago
caece0123e
archive pin logs instead of removing them outright
4 years ago
f7bd3bdc23
don't pin falsey document ids
4 years ago
471a9a33ac
take note of a minor error with pin RPCs
4 years ago
bd3e18d1a8
only cache a user's pinned channels if there are no errors when loading them
5 years ago
bef18a9320
hotfix
5 years ago
cb53bd1c15
lint compliance
5 years ago
14feef1757
calculate pin list checksums in a worker
5 years ago
70a0d4efb4
move more database reads into the database worker
5 years ago
4ba36a9173
load user pins in the database worker
5 years ago
90899aa2f4
start reviewing and removing XXX notes
5 years ago
2a9780abcf
lint compliance
5 years ago
81c7416095
lint compliance
5 years ago
1230057970
disable IS_PAD_PINNED
5 years ago
32d769447a
begin standardizing our method of streaming lines from files
5 years ago
021a6b361f
remove a bogus XXX note
5 years ago
38c1700173
Respond to pinning RPCs as soon as possible
...
(instead of waiting until you've read an unbounded number
of pin logs while queries back up in memory)
Also replace instances of 'publicKey' with 'safeKey' or 'unsafeKey'
to clearly and correctly indicate their format.
5 years ago
3dc789cbca
replace pinned.js with low-profile streaming implementation
5 years ago
1231cacef1
remove XXX
5 years ago
802034616c
centralize historykeeper-rpc interaction in rpc methods
5 years ago
bde17a62a1
continue refactoring rpc
5 years ago
fa525817ba
fix broken removePins RPC
5 years ago
c765362744
move more rpc functionality into modules
5 years ago
c93b39c094
separate more rpc functionality into pinning and core submodules
5 years ago
ansuz