makes sense. got it. ill add it to our todo list to fix the issue. 🫡 yes, it will be a great help if you report the invalid detection. also, im not sure if we are able to rebrand now since we recently gained some small amount of followers and only 2 users so hard, i think rebrand breaks it more... check it out:
JellyFish's avatar JellyFish
🚀 Introducing Our Service Monitoring We’re excited to announce the launch of our official service monitoring! 🎉 🔍 https://status.jellyfish.land provides real-time status updates and performance insights for Jellyfish Nostr services. Stay informed about uptime, incidents, and maintenance updates in one place. This is the best way to check for disruptions if you're using our services. 👉 Visit now: https://status.jellyfish.land 🛸 Gain access to our relay service at: https://jellyfish.land/relay #Nostr #Jellyfish #Monitoring 🚀
View quoted note →

Replies (3)

No problemo. While I have good faith in you, as I've seen you contributing to Khatru and other upstream Nostr stuff, my opinion as a user won’t matter much to the security companies. Generally, security providers have special channels for businesses to reach out, figure out what’s happening, press their case and provide any necessary evidence if required. Regarding rebranding, I agree. That would be a nuclear option if you can't fix the classification issue. Given the situation, I don’t see why security companies wouldn’t allow you to resolve it. Chances are that as soon as a human gets involved on their side (assuming it's a case of AI misclassification with no user reports or other issues) your domain will simply be reclassified as safe. As for the status page, it’s also inaccessible for me 🤣. I need to figure out a way to add an exception to my network security config. It’s been a while since I last had to do this.
thank you for your kind words. 🫡🪼⚡ yes, i agre with you. i hope they fix the isseu. meanwhile we will work on it actively to fix this bad experience.