You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a little off-topic, but I just wanted to say that the icon you made for this is really pretty!
Now, to what I am actually opening this ticket for: I have tried to send posts from Primal several times while having the Flamingo extension installed. However, I have noticed two things:
Nothing shows up in the console that would explain the error - just that a promise failed, together with a tracelog full of squashed names and identifiers; naturally, because the code is likely minified.
I can click however many times I want on the "Post" button, nothing happens.
Now, one potential contributing factor is that I use Opera GX; Chromium based. Adding Chrome extensions is a supported feature and when I inspect the global namespace, I can see the window.nostr object. In fact, on AstralNinja and iris.to, this works totally fine. Just not on Primal.
Do you have any idea how I could debug this, or instructions on how to build a debug version of the extension so I could attempt debugging by installing that instead to maybe get a bit more output?
Thank you and kind regards,
Ingwie :)
The text was updated successfully, but these errors were encountered:
Hello there!
This is a little off-topic, but I just wanted to say that the icon you made for this is really pretty!
Now, to what I am actually opening this ticket for: I have tried to send posts from Primal several times while having the Flamingo extension installed. However, I have noticed two things:
Now, one potential contributing factor is that I use Opera GX; Chromium based. Adding Chrome extensions is a supported feature and when I inspect the global namespace, I can see the
window.nostr
object. In fact, on AstralNinja and iris.to, this works totally fine. Just not on Primal.Do you have any idea how I could debug this, or instructions on how to build a debug version of the extension so I could attempt debugging by installing that instead to maybe get a bit more output?
Thank you and kind regards,
Ingwie :)
The text was updated successfully, but these errors were encountered: