• Grok does a much better job with this question than Gemini, ChatGPT and Claude

    From Rod Speed@rod.speed.aaa@gmail.com to aus.computers on Wed Apr 15 07:44:31 2026
    From Newsgroup: aus.computers

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From not@not@telling.you.invalid (Computer Nerd Kev) to aus.computers on Wed Apr 15 09:11:57 2026
    From Newsgroup: aus.computers

    Rod Speed <rod.speed.aaa@gmail.com> wrote:
    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question into search terms quite
    well, I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes. But then it's weird that it describes them as
    "The USSD codes (like *61...*XX#)". What's the "*61..." prefix
    about? You just use *XX#, eg. "*150#" to show your phone number.

    Again it wastes my time double checking that it's making up
    nonsense instead of me misremembering things myself. "*61" isn't
    at the beginning of all USSD codes as its statement suggests since
    it's stated in brackets like definition of the term "USSD codes",
    it's just the first selector of the codes it shows in example USSD
    commands later in its reply. The damn thing's trying to BS me at
    every opportunity. Wikipedia confirms the formatting:

    https://en.wikipedia.org/wiki/USSD#Format

    I waste more damn time checking where AI disputes my reality with
    its BS.
    --
    __ __
    #_ < |\| |< _#
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to aus.computers on Wed Apr 15 09:32:29 2026
    From Newsgroup: aus.computers

    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question

    Nothing garbled about the question

    into search terms quite well,

    And google doesnt do that

    I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes. But then it's weird that it describes them as
    "The USSD codes (like *61...*XX#)". What's the "*61..." prefix
    about?

    That's the bit of the string that tells it
    you are changing the delay till voicemail

    You just use *XX#, eg. "*150#" to show your phone number.

    It isnt about showing you the phone number

    Again it wastes my time double checking that it's makingup nonsense instead of me misremembering things myself.

    The obvious way to check if its made up nonsense is to try turning
    live voicemail off and see if that fixes the problem, fuckwit

    "*61" isn't at the beginning of all USSD codes as its statement
    suggests

    It says nothing of the sort. Its what is at the beginning of the
    USSD code to change the delay before going to voicemail

    since it's stated in brackets like definition of the term "USSD codes",

    More of your mindless bullshit

    it's just the first selector of the codes it shows in example USSD
    commands later in its reply.

    Its what specifys that you are changing the delay to voicemail

    The damn thing's trying to BS me at every opportunity.

    More of your mindless bullshit

    Wikipedia confirms the formatting:

    https://en.wikipedia.org/wiki/USSD#Format

    But says NOTHING about the fact that
    it has no effect if live voicemail is on

    I waste more damn time checking whereAI disputes my reality with its
    BS.

    There is no bullshit in that response
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From not@not@telling.you.invalid (Computer Nerd Kev) to aus.computers on Thu Apr 16 08:30:09 2026
    From Newsgroup: aus.computers

    Rod Speed <rod.speed.aaa@gmail.com> wrote:
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question

    Nothing garbled about the question

    into search terms quite well,

    And google doesnt do that

    I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes. But then it's weird that it describes them as
    "The USSD codes (like *61...*XX#)". What's the "*61..." prefix
    about?

    That's the bit of the string that tells it
    you are changing the delay till voicemail

    Then it should say "The USSD codes for changing voicemail settings
    (like *61...*XX#)", so it doesn't read as a general definition of
    "USSD codes".

    You just use *XX#, eg. "*150#" to show your phone number.

    It isnt about showing you the phone number

    Again it wastes my time double checking that it's makingup nonsense
    instead of me misremembering things myself.

    The obvious way to check if its made up nonsense is to try turning
    live voicemail off and see if that fixes the problem, fuckwit

    Then when it makes up nonsense you go and mess up settings that are
    irrelevent.
    --
    __ __
    #_ < |\| |< _#
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to aus.computers on Thu Apr 16 10:40:18 2026
    From Newsgroup: aus.computers

    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question

    Nothing garbled about the question

    into search terms quite well,

    And google doesnt do that

    I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes.

    Your problem

    But then it's weird that it describes themas "The USSD codes (like
    *61...*XX#)".

    What's the "*61..." prefix about?

    That's the bit of the string that tells it
    you are changing the delay till voicemail

    Then it should say "The USSD codes for changing voicemail settings
    (like *61...*XX#)", so it doesn't read as a general definition of
    "USSD codes".

    It doesnt read like a general definition of USSD codes

    You just use *XX#, eg. "*150#" to show your phone number.

    It isnt about showing you the phone number

    Again it wastes my time double checking that it's makingup nonsense
    instead of me misremembering things myself.

    The obvious way to check if its made up nonsense is to try turning
    live voicemail off and see if that fixes the problem, fuckwit

    Then when it makes up nonsense

    It didnt do that

    you go and mess up settings that are irrelevent.

    That setting is completely relevant and its trivial
    to reset it back to what it previously was if it
    doesn't do what the AI claimed it would do.

    Even you should be able to manage that

    And that's all you can do if you are stupid
    enough fart around using google instead
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From not@not@telling.you.invalid (Computer Nerd Kev) to aus.computers on Fri Apr 17 08:27:28 2026
    From Newsgroup: aus.computers

    Rod Speed <rod.speed.aaa@gmail.com> wrote:
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question

    Nothing garbled about the question

    into search terms quite well,

    And google doesnt do that

    I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes.

    Your problem

    Oh thank you for going back up the thread and making sure we didn't
    miss that important observation that escaped you the first time.

    But then it's weird that it describes themas "The USSD codes (like >>>> *61...*XX#)".

    What's the "*61..." prefix about?

    That's the bit of the string that tells it
    you are changing the delay till voicemail

    Then it should say "The USSD codes for changing voicemail settings
    (like *61...*XX#)", so it doesn't read as a general definition of
    "USSD codes".

    It doesnt read like a general definition of USSD codes

    Examples in brakets after a term define the term.

    You just use *XX#, eg. "*150#" to show your phone number.

    It isnt about showing you the phone number

    Again it wastes my time double checking that it's makingup nonsense
    instead of me misremembering things myself.

    The obvious way to check if its made up nonsense is to try turning
    live voicemail off and see if that fixes the problem, fuckwit

    Then when it makes up nonsense

    It didnt do that

    It does at least one time in ten according to the study, and a lot
    more often when you're asking questions that don't have answers all
    over the web that are easily found with a decent web search anyway.

    you go and mess up settings that are irrelevent.

    That setting is completely relevant and its trivial
    to reset it back to what it previously was if it
    doesn't do what the AI claimed it would do.

    Even you should be able to manage that

    And that's all you can do if you are stupid
    enough fart around using google instead

    There you can read actual accounts of what worked and judge whether
    your problem is similar, rather than being sucked into some AI
    fantasy land with misleading statements and advice taken and
    shuffled around from irrelevent webpages without context.
    --
    __ __
    #_ < |\| |< _#
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From Rod Speed@rod.speed.aaa@gmail.com to aus.computers on Fri Apr 17 09:34:38 2026
    From Newsgroup: aus.computers

    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote
    Computer Nerd Kev <not@telling.you.invalid> wrote
    Rod Speed <rod.speed.aaa@gmail.com> wrote

    https://grok.com/share/bGVnYWN5_b061e567-1729-4ed1-8de4-d92582667a7b

    Have fun answering that question with google etc

    That AI actually shows the search terms and results it's used when
    you click on "sources" at the bottom, so you can actually see how
    you could have got results like this with the info in a web search:

    https://discussions.apple.com/thread/255257954

    It did translate your garbled question

    Nothing garbled about the question

    into search terms quite well,

    And google doesnt do that

    I didn't guess your "Mobile carrier string that is dialled"
    meant the USSD codes.

    Your problem

    Oh thank you for going back up the thread and making sure we didn't
    miss that important observation that escaped you the first time.

    You never could bullshit your way out of a wet paper bag

    But then it's weird that it describes themas "The USSD codes (like >>>>> *61...*XX#)".

    What's the "*61..." prefix about?

    That's the bit of the string that tells it
    you are changing the delay till voicemail

    Then it should say "The USSD codes for changing voicemail settings
    (like *61...*XX#)", so it doesn't read as a general definition of
    "USSD codes".

    It doesnt read like a general definition of USSD codes

    Examples in brakets after a term define the term.

    More of your mindless bullshit

    You just use *XX#, eg. "*150#" to show your phone number.

    It isnt about showing you the phone number

    Again it wastes my time double checking that it's makingup nonsense >>>>> instead of me misremembering things myself.

    The obvious way to check if its made up nonsense is to try turning
    live voicemail off and see if that fixes the problem, fuckwit

    Then when it makes up nonsense

    It didn't do that

    It does at least one time in ten according to the study,

    Irrelevant to what it did with that particular question

    and a lot more often when you're asking questionsthat don't have
    answers all over the web that areeasily found with a decent web search anyway.

    That one doesn't have that

    you go and mess up settings that are irrelevent.

    That setting is completely relevant and its trivial
    to reset it back to what it previously was if it
    doesn't do what the AI claimed it would do.

    Even you should be able to manage that

    And that's all you can do if you are stupid
    enough fart around using google instead

    There you can read actual accounts of what workedand judge whether
    your problem is similar,

    That particular question doesn't

    rather than being sucked into some AI
    fantasy land with misleading statements and advice taken and
    shuffled around from irrelevent webpages without context.

    That answer doesn't do anything like that, you pathetic excuse for a
    bullshit artist
    --- Synchronet 3.21f-Linux NewsLink 1.2