Mastadon is so shit, i don't get why they do this instead of having a 'real' nostr account
Discussion
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq2rrvutnfeu9677d4yjytypqccjn0njnm6zkx2j6xyn2uqfw02ldsl7kgqj nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwsv8hw7e6vprpjl47rfq7k8qsrlscnm7vzkwlzf3kvyf8xnmk4cqnpm40s We didn't make a bridge. We plan to eventually make a Nostr account but lack the time to deal with another platform.
I guess most of the engagement of the Graphene account is actually coming from nostr.
There's no need for you to post on nostr too, that gets handled automagically by the existing bridge.
What is missing however is a lightning address for easy donations on each post. nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp033tada is there a way to do this for a bridged account?
A lot does actually come from Fediverse, but the bridge doesn't show everything. Even in my end the threads break apart. What most people here reply to usually aren't directed towards Nostr users and is just a bridge.
Nostr has always been a thought, but it's worth understanding some team members know little to nothing about it because they come from a different subject matter. At the moment some who are affiliated who are familiar have separate keys to represent independently to put the work off. At first, I don't even think it was understood that these posts were bridged from another platform - but now everyone is aware.
GrapheneOS can't just "get" Nostr immediately. There is infrastructure that would need to be built to use it in a highly secure manner. Just HODLing a singular private key for a shared project account is unacceptable. It would also be limited to just posting. Rotating npubs is also something to avoid entirely. A hardware signer could fit but you also need a client supporting it and it's costly. It needs to be discussed more.
Same also goes for accepting Lightning payments in general. The project would want a secure Lightning node with lnurl and BOLT12. We also need to make sure we have proper accounting for all the money the node is receiving, inbound capacity and backups.
Last I remember the project couldn't figure out a good way to set up lnurl without using sketchy or excessive software. We want to set it up ourselves on top of the usual server setup we use rather than using a premade OS or container setup, and with channel backups. We'd need to set high fees for routing and figure out getting inbound capacity regularly.
At the moment there's a lot of work on the table with other stuff though.
Totally understandable.
One consideration is to use npub.cash for a custodial but private receiving node, then frequently sweep it to your existing onchain wallet.
Keycast is a remote signing server for teams, alternatively use amber on a spare phone.
This might be helpful in the future nostr:nevent1qqs27smral6k7lzw7zhp0mylw6gxgy8lvr486qxu8yd3wvslzuvedzczyzqh9wfq2framl5ek7pnypuz6qcjlgc95xvlk2lg50n9v03qkncwyqcyqqqqqqg3eqct2
I was aware of Frostr and intended to send it, although I don't know anything beyond the idea, zero testing.
Private keys and key shares can also be handled completely offline. Once generated, you can distribute individual shares to trusted people involved in running the social media account. For connectivity, you can either connect through Tor relays or run your own Citrix on GrapheneOS for added isolation.
P.S. According to the video I shared earlier, it looks like Frostr should work in this setup. I haven’t tested it myself yet, though.
That's awesome, thanks!
tl;dr: Just add a custom profile field in the "Edit profile" screen in mastodon, using a lightning bolt emoji (⚡) as the label, and your Bitcoin Lightning address as the content.