12:34:53
binarybaron:matrix.org:
I dont want to be involved in war (especially not with you). Therefore I'll go with ExtraField::Nonce
12:42:46
binarybaron:matrix.org:
I'll take all of this into account. thanks!
16:59:05
boog900:monero.social:
meeting here in 1 hour
17:59:44
boog900:monero.social:
!meeting
17:59:45
moo:monero.social:
Starting meeting: https://github.com/monero-project/meta/issues/1317
17:59:49
boog900:monero.social:
1)greetings
18:02:23
hinto:monero.social:
hello hello
18:02:55
boog900:monero.social:
2) updates
18:05:04
plowsof:
👋
18:06:28
boog900:monero.social:
Me: Continuing my work on the tapes database, I am in the process of moving away from memory maps and chnaging the way we synchronize access.
18:06:28
boog900:monero.social:
The current method for synchronization wont allow cross process access, however last meeting I said it would.
18:06:46
boog900:monero.social:
Me: Continuing my work on the tapes database, I am in the process of moving away from memory maps and chnaging the way we synchronize access.
18:06:46
boog900:monero.social:
The new method for synchronization wont allow cross process access, however last meeting I said it would.
18:07:19
boog900:monero.social:
I have thought about it and I just don't think cross process access is necessary
18:07:45
boog900:monero.social:
and not having it makes it so much simpler.
18:09:22
hinto:monero.social:
me: continuing work on PoWER; another thing came up over the holidays I think is worth mentioning to this group although I'll announce it when the time is right (if it ever is)
18:10:36
boog900:monero.social:
secret hinto project 👀
18:10:54
hinto:monero.social:
IMO this is fine although in practice it means it will be one of us creating external programs that access the DB
18:11:15
hinto:monero.social:
either that or the API becomes polished for easy public use (unlikely, I think)
18:12:55
boog900:monero.social:
it means that you can't read the DB while Cuprate is running so any data you want you'll need to go through RPC or integrate directly into the node.
18:14:04
boog900:monero.social:
https://github.com/Cuprate/cuprate/issues/516
18:15:25
hinto:monero.social:
reminder that 516 is an opportunity to create "The API Spec v2" that starts from scratch without being held back by RPC and monerod-isms
18:15:47
hinto:monero.social:
(which a potential websocket interface could be built on-top of)
18:15:50
kayabanerve:matrix.org:
I would love support for batch JSON-RPC requests.
18:16:02
boog900:monero.social:
tbf we can just expose the DB handle directly
18:16:31
kayabanerve:matrix.org:
That could even be done on top of the current Monero RPC though.
18:17:47
boog900:monero.social:
3) Project: What is next for Cuprate?
18:18:20
boog900:monero.social:
I'll keep it in mind but just getting RPC working at all is the current target :)
18:19:08
boog900:monero.social:
I don't plan to spend much more time on the database then I'll split if from the RPC changes and PR it.
18:19:18
boog900:monero.social:
I don't plan to spend much more time on the database then I'll split it from the RPC changes and PR it.
18:20:17
boog900:monero.social:
I don't have anything else I want to discuss today.
18:20:40
boog900:monero.social:
hinto: do you have anything you would like to discuss?
18:22:36
hinto:monero.social:
nope, back to work
18:23:36
boog900:monero.social:
thanks everyone.
18:23:39
boog900:monero.social:
!meeting
18:23:42
moo:monero.social:
- Logs: https://github.com/monero-project/meta/issues/1317#issuecomment-3715806417
18:23:44
moo:monero.social:
- Next meeting: https://github.com/monero-project/meta/issues/1320