pull down to refresh

https://pidgeon.lol/pidgeon-wordmark.svg

Hey folks, I am honestly a bit excited to post this. Pidgeon is live at https://pidgeon.lol

https://blossom.yakihonne.com/caf71424073608137be48cb37c1d7b167790351b78f428df59c4436022396874.webm

What it does right now is pretty straightforward. You can write a post and schedule it for later, keep a queue so you can actually see what is coming up, and check your history so you do not lose track. Media uploads work too via NIP 96, and you can log in with common signers like NIP 07, Nostr Connect through Amber.

“Privacy first”… what does that actually mean here?“Privacy first”… what does that actually mean here?

all comunications between you and the DVM are encrypted. Relays and third parties do not know you are scheduling anything. We made a lot of work to implement an architecture that would work smoothly with a good user experience, if you are technical, you can head over the project Github repo to check how it works in code, otherwise .... Just relax and enjoy it :)

Extra privacy/control and transparency: run your own DVMExtra privacy/control and transparency: run your own DVM

You can actually selfhost your own DVM, you can point Pidgeon to it and keep the whole scheduling pipeline under your control. We open sourced the DVM code in the repo. You can override the default DVM, just by simply putting your own pubkey.

What I would love feedback on, for realWhat I would love feedback on, for real

If you try it, I would love feedback on signer compatibility, relay weirdness, and the UX. Does scheduling feel calm and obvious, or do you get lost and click around until it works. Also tell me what features you would expect from a scheduler that are missing here.

shoutout to @isolabellart whom has been patiently giving me feedback as I have been building this app.

Anyway If you run into bugs, screenshots and a quick note like “what signer” and “what relays” helps a ton. I am shipping changes fast and trying to keep it stable.

App: https://pidgeon.lol (open to all Nostr users)

Repo: https://github.com/MaviLabArt/Pidgeon

If you give it a spin and it feels useful, tell me what you would want next. And if it feels not useful, also tell me, I can take it. I would rather hear the honest version than silence.

0 sats \ 2 replies \ @OT 8h

I like this idea. Scheduling for US time probably gets more engagement.

I'm unable to log in with Nsec Bunker.

reply

Thanks! Uhmm, what relays are you using with your bunker? Would it be possible to add at least of of these and try again?

wss://nos.lol wss://relay.primal.net wss://nostr.mom wss://relay.damus.io

Anyway, I am gonna add the nsec app bunker .... Might help user using that!

reply
0 sats \ 0 replies \ @OT 6h

I managed to get it working. I copied a string from Nsec Bunker and it worked (usually with Aqstr it automatically closes Nsec Bunker and opens Aqstr).

view on njump.to

This was the note I tried. Good to see that it works!

reply

This actually makes a lot of sense, and I wonder why the main clients never had such functionality. Thanks!

reply

Thanks for your kind words!

reply
0 sats \ 1 reply \ @Taj 9h

First impressions looks crisp 👌 excellent work 👏

reply

Thank you

reply
0 sats \ 2 replies \ @dtonon 10h

Very cool!

Some UX suggestions:

  • Improve the onboarding showing a modal explaining what the service does
  • Simply the interface moving the quick status on the top, in a more compact form
  • When saving a draft, don't remove it from the composer, often the user just want to backup what is writing
  • When a draft is used, completed and sent, remove it from the recent drafts (or at least propose it interactively)
  • Disable buttons that have a not applicable action in that context, instead of returning a "nothing to do" message (e.g. saving a draft with an empty editor)
  • Offer a light theme option
  • Add the github repo to the page footer
  • Add you npub to the page footer

Publishing to NIP-65 relays should be the default, why forcing the reccomanded?

Really important feature request: use user's Blossom server for uploads

reply

Woow .... This is a gold mine for me... Gonna come back later, to see what we can implement to improve UX further.... Thanks!

As for Blossom Server, users can already add their own under settings ;)

reply

All'ultima request posso risponderti io: è la prima cosa che gli ho chiesto ed è già possibile farlo :)

reply