spirobel

fn main() {
    println!("I Am No Longer Speaking at RustConf 2023");
    println!("Author's talk about Compile-Time Programming got downgraded from a keynote to a regular talk.");
    println!("The author feels that the decision was strange and not justified.");
    println!("The author clarifies that their talk was based on their own ideas and not endorsed by the Rust Project.");
    println!("The author is disappointed by the lack of communication and transparency from the Rust Project.");
    println!("They feel insulted and decide not to participate in RustConf anymore.");
    println!("They express their frustration with the situation and express their disapproval.");
    println!("The author concludes that they will not participate in the game and will not accept the decision.");
}

spirobel

  zig.news
  https://ziglearn.org/
https://ziglang.org/documentation/0.9.1/
https://github.com/ratfactor/ziglings

and reading the stdlib as documentation is still not a priority for it.
https://github.com/ziglang/zig/tree/0.9.x/lib/std
https://forum.ziggit.dev/ is also a good resource and there's the
A forum for programmers of the Zig Programming Language
whenever you see syntax you're unsure of, check the language reference

spirobel

1/26/2022, 11:09:24 AM - spirobel: I just wanted to mention that it might be a good idea to watch this talk when diving into the monero codebase: https://www.youtube.com/watch?v=DY0iE0cBXbc wallet2 is the most important spot to look at it. 
1/26/2022, 8:28:23 PM - afungible: I saw the presentation in full. I have some questions about architecture/ codebase. Must I take it to #Monero dev IRC?
1/26/2022, 10:12:07 PM - Rucknium: I and a few others have been sounding the alarm on this for a while. It is too easy to pitch into a downward spiral at this point in terms of dev resources. We don't have enough devs who want to help onboard new devs, leading to few new devs. Then some existing devs become less active, making it even harder to onboard new devs...and repeat.
1/26/2022, 10:15:49 PM - Rucknium: The number of researchers is even further into the "red line", but in a sense there is ready-made documentation in the form of research papers, so the onboarding issue arguably isn't as severe.
1/26/2022, 10:21:04 PM

spirobel

#!/bin/sh
IP=127.0.0.1
PORT=18082
METHOD="create_wallet"
PARAMS="{\"filename\":\"emptywallet\",\"language\":\"English\"}"
curl \
    -u username:password --digest \
    http://$IP:$PORT/json_rpc \
    -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
    -H 'Content-Type: application/json'

spirobel

start the wallet rpc like this without setting a daemon
./monero-wallet-rpc --rpc-bind-port 18082 --wallet-dir . --disable-rpc-login --log-level 4 --non-interactive 

so it will  respond instantly to requests.
afterwards you can set the daemon connection like so:
#!/bin/sh
IP=127.0.0.1
PORT=18082
METHOD="set_daemon"
PARAMS="{\"address\":\"node.sethforprivacy.com:18089\"}"

spirobel

spirobel: @woodser I was reading this issue: woodser/monero-ts#58 does this also apply to createWalletFull? Can I only open one wallet at a time? Or did I read this part of the test right: https://github.com/monero-ecosystem/monero-javascript/blob/ff92010b0d2df89025166f54ec1d00ce88357b60/src/test/TestMoneroWalletFull.js#L170 seems like many wallets are opened and synced in a for loop and then they run in parallel until close is called. What happens when close doesnt happen and the program crashes? https://github.com/monero-ecosystem/monero-javascript/blob/778473a4e081f03c74697e6ace3a0d416fe03888/src/main/cpp/monero_wasm_bridge.cpp#L1221 it is just a clean up to prevent memory leaks, right? so it should be no big deal.

woodser: @spirobel you can open more than one full wallet at a time if it's not saved before closing, any data since the last save would be lost

spirobel: thanks! this makes a lot of sense! I saw the wallet.getData() call in the wallet save method. ht