- You’ll need to sign it before publishing it to Nostr. I recommend using nos2x or the Alby browser extension or nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmnymvpm86 For iPhone/android
- For the media, it's currently using the Twitter original media.
That doesn't make sense, it can't auto post using extensions. I would have to give it my nsec for it to auto post?
I've just signed the 4 posts it has just picked up. But I had to manually select them and sign them.
This isn't auto posting, or am I missing something?
You definitely don’t want to set your nsec anywhere for auto-posting, so you’ll still need to securely sign for it before posting to nostr
So this doesn't
"Automatically sync your tweets to Nostr"
As the site says?
I'm not having a go, but this is VERY misleading and it only occurred to me that this is impossible without storing my nsec within your site and configuring a media server.
This is basically pointless and useless. If I want to cross post, I can copy and paste far easier than manually logging on to a third party website every hour or so and manually post an hour or three later rather than doing it directly.
I absolutely accept that it's a REALLY bad idea for me to store my nsec on the xnostr site, but without doing this, the site has no purpose.
I was also hoping to cross post all my X posts since I joined in Twitter in 2010, I appreciate that the API would be rate limited, but I was hoping to make my tweets self sovereign on my own relay.
Also, there is the previously reported problem of not copying across URL's from the tweet to the NOSTR post, this makes it unusable, even if I did want to use the site to manually post.
Do you have a road map for building this into a proper service or is this just an experiment?
This is just an experiment, but I definitely don’t want to store your nsec. It can save time if you’re posting like nostr:nprofile1qqs2t6f6a78gyr9u02mmvgzls49c0tk5kjx976eslwlt5hyeusxu70cpr3mhxue69uhkummnw3ez6un9d3shjtnhd3m8xtnnwpskxegpzpmhxue69uhkummnw3ezuamfdejsesh6dm
Understood.
This isn't for me as it is, but I can imagine how you can evolve it by using remote key signing like the nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyw8wumn8ghj7un9d3shjtngd9nksmrfva58getj9e3k7mf0qqs8u5uf0rd2p9wmdxxaznpn54tkq8wwspmljy0cjqw6jdgm5kv84ds3selle remote signer, or key rotation, which I'm currently write a NIP for.
Delegated authority is coming soon to NOSTR, I think this is when your service will be feasible.
I would definitely fix the URL inclusion issue, even for you Bitcoin Archive client, that definitely makes it unusable.
