Greasy Fork is available in English.
ChatGPT ChatTree 🌳, 🚀állandó és korlátlan interakciók kezelése a ChatGPT-vel🚀 🔄ChatGPT beszélgetési fa valós idejű frissítései és vizualizációja🔄 💡beszélgetési tippek a ChatGPT-tel, egyéni megjegyzések, könyvjelzők💡🔍Intelligens keresés a ChatGPT-ben: gyorsan megtalálja a kijelölt beszélgetéseket🔍 📋ChatGPT Interakció Kezelési Panel, felhasználóbarát felület, átfogó interakciókezelési lehetőségek, kategorizálás, címkék és több📋
< Feedback on ChatGPT ChatTree 🌳
Please check if you are using tampermonkey to install the script. This script works well on edge and chrome. I'll check for brave later.
Current version (2024.09.27.02) is throwing a 'URIError: URI malformed' when trying to install on Brave (v1.70.123). It installs just fine on Firefox DevEd (132.0b3 64-bit Win10), so the problem maybe chromium-related (and could also affect Chrome, Bing, etc.).
Are you using TamperMonkey? I only ask because I chose to ignore the directions and tried it (in Firefox Dev Edition) using ViolentMonkey** instead and received that same error upon installation. I assumed it was because of some edge case bug caused by not using TamperMonkey, but assuming you used the proper one, it could be a problem with the latest version of the script itself?
**(Because it honestly wasn't worth it for me to grab a whole different userscript manager for it. Maybe one day I'll try it temporarily in a sandbox, then if it's worthwhile make it work in ViolentMonkey.)
It's true that the script has some problem when using violentonkey. Honestly, tampermonkey provides better help for developers and I was trying to figure out how can I write the same functions in violentmmonkey. Maybe some time later there will be one adapted for it. But for now I only write and update the script for tampermonkey.
If you don't mind, you can try tampermonkey for a while, haha.
Current version (2024.09.27.02) is throwing a 'URIError: URI malformed' when trying to install on Brave (v1.70.123). It installs just fine on Firefox DevEd (132.0b3 64-bit Win10), so the problem maybe chromium-related (and could also affect Chrome, Bing, etc.).