t4t5 / flamingo

a Nostr browser extension focused on UX 🦩

Flamingo

A Nostr browser extension focused on UX

getflamingo.org

---

Flamingo is based on the NIP-07 standard

It's built using:

• Vite
• React
• nostr-tools
• nostr-react
• Stitches

Special thanks to fiatjaf for paving the way for this with NIP-07 and nos2x.

flamingo's Issues

Feature : I'm porting the flamingo extension to `Firefox`

Hey @t4t5 I really do love Flamingo extention's look !

Unfortunatelly, the extention itself isn't available in Firefox. So I decided to port the built version to Firefox.
It needs a little tweaking in the manifest file but because you used Web Extensions instead of classic Chrome framework I t was really easy to migrate

You'll find the built version that you can put on Firefox in Debug Mode to test. The package isn't signed by Firefox so you won't be able to use it outside of Developpement mode. I planned to upload it myself on Firefox for now.
For now, the addon can't be published, it needs approval but you'll be able to get it here :
https://addons.mozilla.org/en-US/firefox/addon/flamingo-nostr-extension/

addon.zip

In the `signEvent` method, the `pubkey` of the `event` should be optional?

I'm signing this event:

window.nostr.signEvent({
  kind: 1,
  created_at: Math.floor(Date.now() / 1000),
  tags: [],
  content: 'hello world'
}).then(console.log).catch(console.error)

Flamingo doesn't popup, but Alby does.
After I've added pubkey to the event object:

window.nostr.signEvent({
  kind: 1,
  created_at: Math.floor(Date.now() / 1000),
  pubkey: 'xxx',
  tags: [],
  content: 'hello world'
}).then(console.log).catch(console.error)

Flamingo does popup.

However, according to the NIPS-07:

async window.nostr.signEvent(event: Event): Event // takes an event object, adds `id`, `pubkey` and `sig` and returns it

pubkey is added after calling the signEvent mothod. So I think the pubkey should be optional to the event object passing to the signEvent method.

Error message when trying to post on Brandle

First of all, I don't know if this is a problem with the extension or with the Brandle client.

When I try to post on Brandle (instance: https://nostr.rocks) I get the following error message:

Did not publish: TypeError: hexToBytes: expected string, got object

I think it has to do with the communication between the client and the extension.
Also, I don't see any errors related to the post in Chrome DevTools.

Adding a tab to show where I'm logged in till now

Multiple Identities?

Any plans to allow storing and using multiple identities at some point?

primal.net does not work

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:

1. 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.
2. 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 :)

flamingo signEvent timeout not working

I'm getting inconsistent results with signing events with the flamingo app.
Is this extension still being maintained? If so, I'm happy to debug/troubleshoot/provide more info.

Essentially my event message looks something like:

const event = {
    created_at: Math.floor(Date.now() / 1000),
    kind: 27235,
    pubkey: pubkey, //tried adding and removing this to no avail.
    tags: [
        ["u", "https://mygamewebsite.com"],
        ["method", "GET"]
    ],
    content: "",
};

The response is a timeout. I won't get an error or anything.
The odd part is I was able to get this working .. but even after removing and adding back I can't seem to get it to work again.