TheDcoder

What the f**k bud, don't let it generate code for you, just let it explain stuff that you don't understand. At this point the code is completely screwed up, start over. Only make changes yourself and only if you understand them. It's a big mistake to replace the custom qhash function with _Crypt_HashData, the AI just hallucinated it.

No way bud, just asked ChatGPT's latest and greatest model to do the conversion for you. Do that bud, take help from GPT, one of the rare cases where it is useful Also maybe watch a simple explainer video on how bit operations work.

Those values are derived from the hash calculated by the qhash function which takes the Image ID as the input, I asked ChatGPT to convert it into AutoIt: Func qhash($inputstr) Local $instr = "" If IsString($inputstr) Then $instr = $inputstr Else Return -1 EndIf Local $h = 0x00000000 For $i = 1 To StringLen($instr) $h = BitShift($h, 4) + Asc(StringMid($instr, $i, 1)) $h = BitXor($h, BitShift(BitAND($h, 0xf0000000), -23)) $h = BitAND($h, 0x0fffffff) Next Return $h EndFunc Func BitShift($value, $shift) If $shift >= 0 Then Return BitShiftLeft($value, $shift) Else Return BitShiftRight($value, Abs($shift)) EndIf EndFunc Func BitShiftLeft($value, $shift) Return $value * 2 ^ $shift EndFunc Func BitShiftRight($value, $shift) Return Int($value / 2 ^ $shift) EndFunc I think you can figure out the rest of the logic to obtain the exact dir1 and dir2 values, it's just BitAND and BitOR operations. I think ChatGPT would be of great benefit to you here, you can use DDG's ChatGPT interface for free

Then every code execution vulnerability should get this rating... but they don't.

The 10/10 rating for this is highly inaccurate, that should only be reserved for fully remote arbitrary code execution. I agree with the points made in this video:

@jchd I'm afraid I don't really understand what you said, but it sounds about right... except for the part about copying, I don't see why that's necessary since it is already in the memory and not used by anything else, so just use that directly instead. All "updates" would be gone because the function would clean up all of the local variables.

Same as what gets passed if the parameter weren't a byref

There's no question of reading the value, the function totally disregards byref if the supplied expression is not a value that can be referenced

@jchd I don't think they are trying to actually manipulate the value though. Several years ago I encountered a similar problem with ByRef but it could be solved by simply treating the ByRef parameter like a normal non-ref one. So this is not a bug but could be a useful "feature" that can be added.

Have you considered supporting git repositories as packages directly? That way you don't need to deal with a central database at all (but you can still have one, of course). NPM supports this and even has a shorthand for adding git repos from GitHub directly I think.

I totally forgot about those functions, very handy indeed! But why doesn't TCPSend automatically handle that though? Is it just hardcoded to convert everything to ANSI?

Indeed I have, I couldn't send emoji with my scripts. I suspect that TCPSend is screwing with the encoding. You will have to manually find a way to convert your messages string to properly formatted UTF-8 binary and then send that directly with TCPSend. By the way, don't bother with BOM, it is fairly useless and even undesired, so it won't help you with anything but it can for sure screw up your text potentially if programs are not properly made to handle it. AutoIt's own IniRead function will fail if the file has a BOM.

C++ is just a bastardised version of C, I had to write some a few days ago

Or you can also use an older Beta version if needed.

It's not needed if you don't wish to authenticate, and the server will definitely disconnect you if you provide invalid credentials like "TestScript" So definitely remove the function calls to Auth functions. Not sure about other UDFs but the documentation on mine should be up to date according to the IRCv3.1 standard, which is fairly modern compared to the older RFCs. The IRC standards committee doesn't use version numbers anymore but everything should be backward compatible.

What's the exact error message? I looked at the script and the error messages are very detailed so we can pin-point the error

Oh, that's an interesting issue, never encountered it while I was working with IRC in AutoIt.

I am slightly curious, why did you start working on this with an older version of AutoIt?

@mr-es335 Anything is appropriate if you have the right use case, even some "inappropriate" things like GOTO are appropriate in the right circumstances. (It doesn't exist in AutoIt by the way.)

@Andreik My UDF also has a display functions for maps

Is there a way to do that? I tried several different approaches and none of them worked, the two most promising approaches I tried were: My own DIY double-buffer solution which listens for the `timeupdate` event on two audio elements and tries to start playback of the other one just a little while before the other ends, but the resolution is nowhere near high-enough for this to work. Gapless-5 - Even this fails and introduces small pauses in-between the files, even though it's supposed to work perfectly. I was actually streaming audio which arrives in little chunks of MP3s encoded as base64, so that might make the task a bit harder. I converted the strings to Blobs in my experiments.

@mLipok Looks like a very useful tool, thanks for sharing!

It's "AutoIt" by the way, as in "Automate it", not "Auto Information Technology" For some reason almost everyone (including me) gets it wrong initially.

I'm sure the AutoIt team would be happy to help you with consultation and custom terms in exchange for generous amounts of money

How are you so sure? Also turns out I missed the "LICENSE.txt" file in the same repository which clearly states that it can't be redistributed, it's under a proprietary license and not GPL. So it can't be the same as the version pointed out by Zedna. You may not: - Distribute the AutoIt source code and/or compiled versions of AutoIt created with the AutoIt source code. - Create derivative works based on the AutoIt source code for distribution or usage outside your organisation. - Modify and/or remove any copyright notices or labels included in the AutoIt source code. Full LICENSE.txt: Edit: I mixed things up, the version pointed out by Zedna also has missing stuff, so it could very well be the same thing. So sadly this is not the GPL version that I'm after.