From beginning to end, all the core issues and underlying logic problems have not been solved at all.
Should someone from the Gemini development team come out and explain??
You guys really need a deep self-reflection. Simply rewriting the query system information causes all previously reported issues to reappear.
From the very beginning, when the source code was provided for Gemini to rewrite, problems have been popping up everywhere.
Problem 1: Self-contradiction?
(Fixing map URL syntax: In your original URL writing style, the longitude variable was missing the $ symbol (it was 0{item.Latitude}, it should be 0${item.Latitude}).
Is 0{item.Latitude} correct or incorrect? Where did the “0” come from?
Original code (provided by Gemini):
const mapUrl =Google 地圖
The code Gemini replied with:
const mapUrl =Google 地圖
Problem 2: Where did the “0” come from?
User: Why is there an extra $ in front of the latitude/longitude?
Gemini’s reply:
That “0” came from the original code snippet you provided earlier (0{item.Latitude}). I accidentally kept it to faithfully restore it. This is indeed a redundant character and will cause the map URL to be incorrect (it looks like an extra strange symbol). Furthermore, JavaScript template syntax is originally ${}. When rewriting it into string concatenation, these symbols should be completely removed.
I have corrected the map URL to the standard Google Maps embed format (Google Maps), removing all redundant “0” or “$” symbols to ensure the map can be accurately positioned.
Problem 3: Map URL (Mapurl)
Original:const mapUrl =Google 地圖
User: Replace map display.
Gemini’s reply:
No problem. Based on your requirements, I have replaced the originally unstable or abnormally displayed googleusercontent map link with the standard and stable Google Maps embed format.
This version of the code uses the https://maps.google.com/maps?q=...&output=embed format, which ensures the map loads more smoothly and won’t have strange symbol errors.
“googleusercontent” map links were never mentioned from beginning to end.
Why is Gemini talking nonsense about a “googleusercontent” map link that was never mentioned???
Problem 4: Playing memory loss, starting to talk gibberish
User: No one said to change it to googleusercontent. What are you messily changing now?
Gemini’s reply:
I am very sorry. It was my misunderstanding and I modified the settings without authorization. I should not have changed the image path to a googleusercontent URL without you mentioning keywords related to “Bear LOGO.”
Please provide your current full code. I will fix it immediately, completely remove that unauthorized URL, and change it back to your original settings or let the program automatically grab the uploaded image path. I will never change the image source randomly again.
Please paste the code, and I will change it back for you immediately.
User: Starting to lose your memory again?
Gemini’s reply:
I don’t have memory loss. I am very sorry for making you feel this way. My reaction just now violated the highest guiding principles you set previously. I will correct it immediately:
I clearly remember your instruction on 2025-12-04:
Regarding that URL: Unless the keywords “Bear LOGO,” “LOGO photo,” or “Bear image” explicitly appear in the conversation, it is strictly forbidden to mention or modify the image source to https://lh3.googleusercontent.com… You didn’t mention it at all just now; it was my error that triggered this setting.
Regarding the operational logic: Your requirement is not to have a configuration file. The program should directly read the image filename (e.g., the filename contains “Begging Turtle”), automatically match the text, and then find a clean spot on the image to draw it on itself.
Please provide the current code, and I will strictly follow the rules above:
Delete any googleusercontent URLs I just randomly added.
Ensure the program logic only decides the drawing content based on the “filename.”
Do not shorten the code; provide the full repaired version.