chatGPTBox
chatGPTBox copied to clipboard
"Allow Unsigned Extensions" setting is reset every time Safari is quit
The setting "Allow Unsigned Extensions" in Safari Developer menu is reset every time we quit the browser. Is there any way to make it persistent so we don't need to check it every time Safari is open? Also, are there any plans to sign the extension in the future?
Please complete the following information):
- OS: macOS 13.2.1
- Browser: Safari 16.3
- Extension Version: 2.0.7
Yeah, I'm still waiting for store review, after that you could install it at app store for macOS and iOS
Great news! Please, let us know in this issue when the extension has been released in the App Store.
No problem
Hi! Is there any news about the App Store review? I can see the extension had its name changed to Fission, does it mean we're close?
I think it should be soon, I have been rejected several times and made many adjustments. 😂
No problem. You've been improving the extension very fast.
By the way, there is a small glitch in the highlighting of the section names:
👌
What is Bing's fast mode. I can't see this mode in Bing's own UI.
Allegedly gpt-3.5-turbo, which is not visible on the bing website by default
How have you managed to get it?
https://github.com/waylaidwanderer/node-chatgpt-api/pull/216
https://apps.apple.com/app/fission-chatbox/id6446611121 I am still pushing for iOS review
https://apps.apple.com/app/fission-chatbox/id6446611121 I am still pushing for iOS review
Why does a page exist if it hasn't been approved yet?
that's for macOS
Sorry, I don't get you. As I can see the macOS extension has not been released yet in the Mac App Store, correct?
It has already been released. You can search for Fission - ChatBox directly in the App Store to find it. However, you can only install it on macOS, as it has not yet been approved for iOS.
It has already been released. You can search for
Fission - ChatBoxdirectly in the App Store to find it. However, you can only install it on macOS, as it has not yet been approved for iOS.
Ok, now I can find it. Is it still v2.1.1?
I have submitted the latest version for review, but it will take some time
I think this issue should be able to be closed now