I'm on your side in this argument (approximately; asking what ethics even is and where it comes from can be productive but shouldn't conclude "and therefore AI agents working with humans don't need to integrate a human moral sense" -- at least that'd be a really bad conclusion to humanity as AI scales up).
Can't recommend letting an LLM write for you directly, though. I found myself skipping your third paragraph in the reply above.
Yeah but nobody is gonna read it if they waded through five paragraphs of insubstantial LLM slop from you before. You betrayed the trust of everyone reading that post, wasting their time, energy and quite frankly making us feel a little dirty for reading in good faith what turned out to be something you put zero effort into generating and took us a lot of effort to read. Fool me once, shame on you; Fool me twice, shame on me and all that.
This is exactly, genuinely, 100% what I was talking about when I said you were being direspectful of good discussion culture. You're turning it from high-trust into low-trust and soon nobody will be reading any comment longer than two sentences by default.
Thing is, when you open a webpage it's clear that it may automatically execute code (Javascript, WebAssembly). What needs to be clear (and by default limited) is the authority of that code.
Bookies determine the odds and typically refuse to take bets from skilled bettors.
A market is open to all, with the odds influenced by all participants. In established betting markets such as for stocks, pros dedicate their careers and their organizations to improving the public estimates emerging from the market (though not for the sake of that improvement).
General prediction markets might turn out bad, but the above isn't an argument why, it's namecalling.
A suggestion born of experience: besides printing the seed for an image, add it to the image file as metadata. Otherwise, if you're me, you'll lose it.
Huh, surprising -- it's very different from most people using most software. (Of course HN is not most people.)
I tried to fill myself in by asking Claude Opus neutrally "do most users of Monero run their own node?" and was told it couldn't find good data, it's community-promoted behavior, but there were multiple reasons for skepticism.
Anyone curious about how Monero is implemented would immediately understand why it's a bad idea to use remote nodes.
>What is the difference between a lightweight and a normal wallet?
>For a lightweight wallet, you give your view key to a node, who scans the blockchain and looks for incoming transactions to your account on your behalf. This node will know when you receive money, but it will not know how much you receive, who you received it from, or who you are sending money to. Depending on your wallet software, you may be able to use a node you control to avoid privacy leaks. For more privacy, use a normal wallet, which can be used with your own node.
Most monero users are on the desktop where the common practice is to download and run their own nodes and/or use monero from Android on apps like CakeWallet, where their node is used and assumed as trustworthy.
To give background info: most users are on desktops because monero mining happens using CPU and instead of GPU, so they install the wallet which comes with a miner included and installs the node as well. They basically make some little income every single day and accumulate that profit.
The other miners like GuPax also install a node on the local computer as well, so a large majority of users simply runs nodes locally because they don't want to send their hashes to remote nodes which might fool them.
Thanks for explaining. I'm still confused: CakeWallet (and similar) were a reason to doubt the original claim. Are these "popular" wallets rarely used, or are you considering the nodes that they trust as equivalent to your own node?
People using monero tend to be well informed, or at least better informed than average crypto users. What I see happening is that most users have at minimum three different wallets: One for mining on the desktop, one "cold" wallet for storing the bulk of their money and then one wallet on cakewallet with pocket money for the convenience of small and fast transactions (e.g. donations, small payments).
From that sense in regards to CakeWallet: Android isn't anywhere secure and there is a real danger that key credentials are stolen by rogue apps. In the end doesn't really matter much about whichever nodes are trusted by cakewallet because the monetary values hosted on those Android wallets don't tend to have much value much to begin with.
I've been a long time user and never saw reports of cake wallet being insecure or people losing their wallet money from there. In either case most people using monero tend to be extra cautious from the start.
Well reading comprehension tells us they were surprised that most monero folks run their own nodes and that they were unable to find supporting information.
No, reading comprehension tells us that Claude Opus output the "unable to find supporting information" claim, which abecedarius faithfully relayed to us. There's no evidence in the text that suggests abecedarius attempted to find supporting information.
It was a form of "huh, interesting. I tried to quickly find some more evidence for this but failed."
If Claude as search engine were able to link to some backing (maybe like "we estimate around n nodes regularly joining the network, which roughly matches the order of magnitude of estimated users" ) -- that'd be great! I'd have said I was surprised but look what I found.
Instead:
- it couldn't dig up anything supporting, except that Monero sites encourage users to run their own node;
- one point it raised against was confirmed by another reply to my comment ("apps like CakeWallet, where their node is used and assumed as trustworthy"). (Claude listed the same and a couple more wallets it called "popular" with similar trust dependence.)
I agree with GP that just relaying a chatbot is rude. That's why I didn't do that.
Okay and if they had said Google we wouldn't be doing this dance, people just hate AI and its obnoxious to see comments about it on HN all the time. On a crypto post no less.
We get it you guys don't like AI, next!
It is equally obnoxious to people who talk about AI for everything as if it is a savior, it's a tool use it or don't.
The UCSD system was indeed astonishingly, unusably slow. When I got to try it in high school computer lab, in the 80s, I was like "Did whoever ported it to this particular computer just totally fuck it up? WTF?!"
An Infocom adventure on a machine with 16k RAM also had frequent pauses to fetch from floppy, but it was much more tolerable.
Re verb lookups in Basic: you could use DATA statements and READ in a FOR loop for lookup. I don't know what was typical but that's what I recall from some examples.
Maybe it's better now, but what I ran into in trying twice is that if you're not into installing by "curl | sh", then trying to build from source was an awful experience. It had out of date instructions for installing a whole lot of dependencies. I'd figure out one problem only to run into another, and another. Gave up both times, a few years in between.
There are a few really good ways to install Nix, including ones that people often invoke via `curl | sh`. If you prefer, you can download the exact same installers, and verify the checksums, read their code, etc. You don't have to actually use a different installer just to avoid `curl | sh`.
There are distro packages out there, but those can also come with gotchas; e.g. IIRC Ubuntu's package was configured not to allow `/bin/sh` in sandboxes, which caused some things to break in obscure ways :-(
Can't recommend letting an LLM write for you directly, though. I found myself skipping your third paragraph in the reply above.
reply