Well I've run the text through three detectors and two of them give me a 0% AI generated result. Only Quillbot says it's 41% AI generated. I don't know if he found a way to bypass the detectors or if 41% is a false positive (halfway). But with this data, it's not nearly enough for an AI spammer tag.
Thanks!
I noticed 2 more Newbies:
Hridyansh Labs and
TokenTikas registered close together, both obviously hunting for Merit, and both rehashing what has been said already in this topic on the tech board within 10 minutes from each other. I don't know if it's some language model chatbot, but I have a very hard time believing they're genuine users:
So im syncing a full node of Bitcoin Knots (I don't know where to ask about this so im asking here and hopefully it's ok since it's just a fork) and unless im tripping, it closed itself with no error at all. Where can I find the log that would help trying to find out what happened there?
This kind of problem sometimes occurs when syncing a full node. If you ever see that both Bitcoin Knots or Bitcoin Core sometimes suddenly crash or close on their own, especially during syncing. If you want to find out exactly where the problem is, you need to look at the logs. Sometimes this happens because of problems with the logs. Usually, there are logs like this:
Linux/Mac: ~/.bitcoin/debug.log
Windows: C:\Users\<YourUsername>\AppData\Roaming\Bitcoin\debug.log
Since Knots is built on Core, it also keeps logs in the same place. By opening that file, you will understand at which stage it crashed or closed. And you can find the solution to the problem from there.
it closed itself with no error at all.
Did you start it from console? If not, try it: leave the console open to see if it outputs anything there when it closes.
When running from the console, sometimes when the program crashes or closes on its own, some error messages are displayed directly in the terminal. The terminal error board helps determine which location is causing the problem. So, once the console is open, launch Bitcoin Knots. If any (output/error) code appears, debugging will be much easier. Also, be sure to check the (debug.log file).