13:57:18 <m-relay> <i​nhumaite:matrix.org> Hey there, I'm currently working on a kind of guide to easily chose CPU for Monero (and also Arweave). Do you know if a dataset/database/api exists that could contain an historical view of the CPU/TDP/Price over time?
14:03:34 <m-relay> <j​effro256:monero.social> #xmrmine:matrix.org is probably a better channel for this
15:34:38 <m-relay> <r​brunner7:monero.social> IMHO if you have made a good experience with Neovim for C++ development, and you want to popularize it, some quality links to install instructions and tutorials would be good. And don't forget graphical debugging, Monero code can be so complex that after reading you still don't have a clue what that damn thing does, you have to watch it in the debugger.
16:53:45 <m-relay> <j​babb:cypherstack.com> yes, please feed me your plugins for your favorite IDE as well :D
17:11:01 <m-relay> <p​reland:monero.social> What is your IDE of choice?
17:22:19 <m-relay> <p​reland:monero.social> Also, I saw this on the release announcement for pruning from back in 2019:
17:22:19 <m-relay> <p​reland:monero.social> “While the Monero blockchain can theoretically be pruned far further than this release enables, more testing is needed to push these limits.”
17:22:21 <m-relay> <p​reland:monero.social> What is this referring to?
17:34:08 <m-relay> <r​brunner7:monero.social> Me? I mentioned a bit earlier: I use VS Code.
18:15:06 <moneromooo> I *think* it means that a node could dump more data if it really wanted to, and could still verify future incoming blocks, but it would become useless to other nodes, so it'd be a pure leech. I did not do that.
18:16:22 <moneromooo> Not sure what the testing part is about though, since it'd require the code for further pruning to exist, and AFAIK I'm the only one to have worked on any kind of pruning.
18:17:26 <moneromooo> While I'm on about this... there's a tool to prune extra data that pretty much nobody uses I think, it saved about 200 MB IIRC at the time, called monero-prune-unspent-outputs-data or similar.
18:17:52 <moneromooo> You're still useful to other nodes, and it's orthogonal to the main pruning system. Free 200 MB.
18:18:12 <moneromooo> er, prune-spent, not unspent.
18:19:17 <moneromooo> I guess 200 MB isn't very much now that the chain is huge...
18:19:38 <moneromooo> It's a (close to) constant since it prunes data from pre-rct times.
20:18:42 <m-relay> <p​reland:monero.social> Lol prune unspent outputs
20:18:53 <m-relay> <p​reland:monero.social> Yeah I figured it was from pre-rct
20:19:59 <m-relay> <p​reland:monero.social> I’m assuming that there isn’t a way to prune outputs post-rct
20:20:01 <m-relay> <p​reland:monero.social> Cuz, ya know, that would ruin the whole point
20:20:52 <m-relay> <p​reland:monero.social> Which is a shame, because it does mean that the blockchain is in a never-ending race against consumer storage size
20:21:23 <m-relay> <p​reland:monero.social> And the more Monero gets adopted, the quicker that we reach the point that the blockchain is simply infeasible to store for most people
20:28:43 <m-relay> <m​eatmonster:monero.social> true, probably some good ones exist on youtube already. thing is it's the same language server protocol and debug adapter protocol as used by vscode. clangd, nvim-dap, nvim-dap-ui and codelldb or vscode-cpptools