I'm not sure you're actually hearing what the author is saying. Colonizing the Outback is not even remotely close to colonizing Mars in its inhospitability, and expense. There is literally no analog you can compare with on Earth. The cost alone would drain the resources we would need to continue maintaining the level of life we all have on Earth to a shocking degree. It's simply not a plausible scenario given our current technology and civilization, nor our conceivable technology in the foreseeable future. It is the very definition of boondoggle.

This article very accurately breaks down why we're not colonizing Mars.

https://defector.com/neither-elon-musk-nor-anybody-else-will-ever-colonize-mars

If sending fiat is your requirement, Wise would probably be your best option.

The idea of colonizing Mars is an absurd boondoggle that fails to grasp just how incompatible with human life the red planet it, and the expense of keeping humans alive on an ongoing basis. Maybe at some point in the future we'll have developed the technology that could cheaply and feasibly support a long-term human colony, but that point isn't on our visible horizon. It's a ludicrous plan once you really consider the necessary logistics and expense.

I like fake Christmas trees. I don't like all the rigamerole that comes with using a real tree. But I've been using a Festivus pole for the past decade.

I wonder if it's pulling that info from njump. Njump has a bug where it doesn't display your updated profile data. Unfortunately, it's also the most widely used source of profile and event data for external applications. 🤔

It's really cool. You sign up with your nostr credentials, and you can create your own personal blog/article website. You can do the free tier where you have a subdomain (slcw.npub.pro), or you can subscribe to one of their paid tiers and use your own domain name. And you can automatically curate which which notes and articles it pulls from nostr for inclusion in your site. It's really nice.

I took one look at the code and I immediately wanted to hang myself.

One thing that makes it difficult is the fact that virtually all of SimpleX is original coding. It hardly borrows from any other projects, or uses anything standard. Add that to the fact that it's 100% Haskell and it's easy to see why it's a very difficult codebase to work with.

I mean, you could probably include some links to some of SimpleX's basic functionality in a nostr client without too much difficulty provided you're proficient in Haskell. But it wouldn't be an actual integration with Nostr. It would basically just be shortcuts to a seperately installed SimpleX client within the Nostr client. Personally, I wouldn't find value in that, but maybe some people would. I certainly encourage you to give it a shot. Frankenstein coding can lead to some amazing results!

nostr:nevent1qqsy97t6nqt0yx0hnzyepy87a62w9yxv050s3clgl0yxr7flmpv7yucprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qgsfchg0mv38q5w558m6schzcf9cdaslegtyy66r93njv7xdgqtweegrqsqqqqqpjyvfh6

Boy, it's a good thing Trump killed the Iran nuclear deal that Iran was complying with, and which prevented them from enriching uranium! The Iranians wouldn't have been able to move forward with this epic construction project if that pesky agreement was still in place! Look at that... He's already cutting the red tape!

I don't know why you're getting defensive. I am also a dev and I've spent a lot of time studying SimpleX and communicating with the lead SxC dev. I'm not saying it's impossible because that would be ridiculous. But what you're talking about is not even close to as easy as you're making it out to be. And understanding the underlying protocol and methodology is essential to understanding what you can do and how you'd have to do it. Knock yourself out.

Cool, thanks! 🐝

I suggest you go to the SimpleX github and read the SimpleX MQ whitepaper that details the messaging system. I know it sounds easy to you, but that's just not how it works. There's no reasonable way to integrate the two systems because they are fundamentally based on two mutually exclusive philosophies and design architectures. But it's all open source so you're certainly free to try!

I just don't see a meaningful integration. There's too much incongruity. The keys are ephemeral and exist only in the user's client, so there's no central mechanism to obtain and exchange keys. Nostr's key system with nsec and npub wouldn't have any relevance in the SimpleX key exchange or chat process. Because again, nostr keys are permanent user identities, and SimpleX exclusively uses ephemeral, local keys. It would be like trying to connect your Blu-ray player to a ham sandwich.

No they're not. One-time connection keys are exchanged off-band. Not the message queues themselves. The message queue is dynamically created when one person's key is connected with another person's key.

It sounds like you're talking about have one app that's actually two apps with no integration. And if that's the case what's the point?

I don't know that would work. Nostr is inherently based on user identities, and SimpleX is inherently based on not having user identities of any kind. I don't know how you'd handle associating an npub with the SimpleX message queue system. And if you did, it would automatically defeat SimpleX's core identity-free functionality.

We need a bridge that pipes our content to Bluesky.

I America, we start eating right after Halloween, and continue straight through New Year. Then, the first day of the new year we lie to ourselves and pledge to never eat again.

I got an error earlier when we were chatting, but it seems to be working well now.