Yes I was refering to the C bindings as I know we can use C code from Elixir. There is also a rust library that uses the C bindings. I guess Rustler would be easier to use.
I am not really interested working on a library right now as I do not need that functionality. Maybe in the future. Also I do not really know how to write proper C code or to integrate C code with the BEAM.
Hi everyone, 
I wanted to give a general update on when I would start sending out Early Access invite codes to people who have signed up (you still can!):
I’ve been going through a major life event that is requiring all of my heart and soul, and so I’m pushing back sending out invite codes until 1H 2022.
I had originally intended to have finished getting the Letters feature into a beta stage this month, but due to current events I have not been able to work on it yet. And I didn’t want to send out any codes until Letters was also in a beta stage.
Thank you to everyone that has signed up, it’s beyond exciting and encouraging for me and I appreciate your support. I am also super excited to be able to share another way to connect and share online that I really hope and believe will make our lives better. And if that’s not the case for you, then you can share your feedback, request new features, and vote on features, all in real-time too! 
I’m sorry for the delay. I was really hoping people would be able to spend this holiday season sharing with their loves ones without worry on Metamorphic — but you’ll have to wait until 1H 2022 now (but I think it’ll ultimately end up making the Early Access experience better).
Thank you so much for your support and happy holidays 
Hi again everyone
Happy to say that I’ve begun work on the Letters feature finally. I know this has been a long time coming, especially those who’ve waited at least 8 months now since signing up for Early Access. 
Excited to say that the beta version of Letters is making quick progress now. Here’s a behind-the-scenes screenshot of our LiveView powered “at-mentions” in progress. This will be initially how you determine who to send your letter to. Disclaimer: nothing is set in stone and open to change.
Also, made some updates to the landing page including the launch date for the first round of Early Access invites (finally 
). I will be rolling invites out in batches and beginning with people that I think will be the most patient and willing to stick around through the ongoing development process and UX evolution. Once I’ve finished with the round 1 invites, then I will update the landing page with the date for the next round. At this point, I’m foreseeing about 3 rounds and possible month or two in between rounds depending on how it goes.
Thank you so much for your patience, interest, and support. So close!
PS — If anyone’s been following closely, then you’ll notice that I’ve closed down the old company (Core Theory) and will be opening a new company for Metamorphic in the near future. Also, the podcast has transitioned branding over to just being about Metamorphic. I haven’t released any new episodes yet, due to everything that’s going on in my life. But, I will be getting back to the podcast later this year once things settle down a bit.
Hi everyone,
Wow, what a road it has been.
It’s been 8 months since the first person signed up for invite codes to our Early Access launch at Metamorphic and tonight, through the rest of this month, I am sending out the first round of emails to people.
In 2020, I had a crazy idea to make an alternative way for people to connect and share online. Inspired by becoming a father (“Dada”), my own observations and intuitions about the effects of current platforms, and culminating with Shoshana Zuboff’s latest book on surveillance capitalism, I set off to not only build Metamorphic but also learn how to build it too.
After Paper Space Arcade, I turned to web development to make a website for my partner-at-the-time to assist with her job applications and resume. This led to me discovering the Django framework and I began work building a job search for architects website called The Grid (wayback machine).
Switching from game development to web development was like turning the dopamine switch on high. The gap between code and “useable” shrank to almost nothing. Suddenly I could imagine turning an idea into a reality before the sun went down. It was an empowering feeling made intoxicating by its immediacy.
When Covid hit, I felt both inspired and powerless to help. Day after day I’d read updates on the increasing numbers and wonder what I could do. Ultimately, not that much, but it drove me to add a search feature to The Grid that was updated with the Covid data from Johns Hopkins and enabled people to quickly and easily search by county around the world.
While The Grid failed, it was a great exercise in learning and avenue for channeling my creative energies and desire to help (it mostly just stressed people out whenever I commented on the latest numbers for their county).
As I immersed myself more and more in Python and Django, I inevitably discovered Ruby and Ruby on Rails. My first impression of Rails was “syntax confusion”, but I found myself charmed by the passion and philosophy of its fans and kept coming back to it.
So, I began building a portfolio site for my same partner-at-the-time using Ruby on Rails and I like to believe that it helped play a small role in landing her a job (the architects commented on how impressed they were with her site — though largely due to her design is my guess).
Around the end of 2020, the idea that my company with my co-founder-at-the-time would raise money and successfully develop video games came to an end. I had also been the primary-caregiver to my incredible little one and found myself realizing how much I valued my role as such.
While I was demoralized about the end of the “video game dream”, I found myself increasingly inspired to do something that would have a positive effect on the world for my little one. That’s when I decided to commit to building another way to connect and share online — insulated against the raging surveillance economy.
Since Ruby was the latest language I had been working in, I embarked to build Metamorphic with Ruby and Ruby on Rails. It’s hard to imagine or even remember these early versions, but I do recall consistently bumping up against the need to do so much more with so much less.
While I was stumbling over the same development hurdles with Ruby and Rails, I learned about Elixir and Phoenix from that similarly momentous Chris McCord Twitter clone.
However, I was initially turned away again from my first impression of the syntax and feeling my brain explode every time I saw symbols moving through other symbols:
# From Chris McCord's demo
def inc_likes(%Post{id: id}) do
from(p in Post, where: p.id == ^id, select: p)
|> Repo.update_all(inc: [likes_count: 1])
end
But, destiny beckoned, and I sat down one night and followed along — throwing out any attempt to understand and just going along for the ride.
And what a ride it was. When I played with the finished demo on my own laptop it was like hitting reset on the dopamine switch. I didn’t know much of anything about Elixir and Phoenix, but I knew I had found the tools that would give me the best shot I had at making Metamorphic come true.
And now, nearly 2 years later, I am finally “ready” (ohhh boy…) to start sending out the first round of Early Access invites. I had no idea that it would take me this long when I first set out to make it.
My naivete was a blessing because I probably wouldn’t have attempted Metamorphic if I had realized what I would go through along the way. I still don’t know.
The community around Elixir is simply phenomenal. Whether it’s a podcast or this forum, people are compassionate, kind, and inspiring (not to mention brilliant and skilled — seriously, wow). And it goes without saying, but I’ll keep saying it, that Metamorphic wouldn’t be possible without the community.
With luck and work, I’ll be able to keep contributing and giving back to the community even more (so far that Ecto guide and simple HaveIBeenPwned? alt-library).
I mentioned I’ve been going through a challenging time outside of Metamorphic, which had delayed my original launch plans.
And it’s true, as a father and primary-caregiver going through a… nightmare of a divorce… going through all sorts of court/legal fights (family and criminal)… being isolated with the little one from our family and support network on the other end of a large country… while moving in our first blizzard… I’ve had to handle more than I ever thought I was capable of.
So, I cross my fingers that Early Access members will be patient and understanding with any hiccups or “bugs” as I work to make Metamorphic as awesome as it can be for everyone, while also working to make sure my little one’s life is as awesome as it can be for them too.
I’ve been so fortunate to have such incredible support in my personal life and in this community, and so from the bottom of my heart, thank you to everyone.
I’m so excited to welcome people on this crazy journey with me.
To a better future together,
Mark
Congratulations on your journey, the perseverance and passion you show is a clear inspiration to everyone!
Mark,
I received 3 early access codes today, so I signed up. However, everything in the left navigation bar except home and support gave me 500 internal server error.
Hi Derek,
Oh sorry to hear that! Thanks for letting me know. Working on this right now, just saw its an error when you don’t have a subscription.
Update
Okay, this error has been fixed and pushed up. Should be good to go. Now when you click on features in the left navigation bar you are redirected to start a 14-day free trial subscription if you don’t have an active subscription or free trial.
There’s one more kink now I’m updating actually.
Update
It appears the bug exists in Firefox but not in Brave browser (which makes me think Chrome is okay too but haven’t tested).
In Firefox, it isn’t reading the CSP config (issuing an error that it is blocking the Stripe script). This is preventing proper syncing between Stripe and Metamorphic.
On Brave, the CSP config is being read correctly and this bug doesn’t occur and everything syncs correctly.
Looking into why this is happening in Firefox.
Update
Appears the Privacy Badger extension was blocking some of the Stripe network connections. Disabling or allowing Stripe in the Privacy Badger extension gets rid of the CSP block in Firefox.
Currently, working on updating the subscription synchronizing to handle some potential edge cases that I’m still noticing with Firefox. Will update soon (also there’s an announcement on your Metamorphic dashboard about this current bug and will update there too when I have something new to report).
Thank you for your patience and understanding and sorry about this 
Update 3/26/2022 
It appears the webhooks timing out issue on new subscription sign ups has been resolved!
You should now be able to sign up for 14-day free trial (in Firefox or otherwise) and start using the app. Let me know if you are still having an issue.
From what I had been reading, it seemed that there was some kind of delay causing no responses to be returned on webhooks that I thought would be returning responses.
Attempts
I did a few things to get to where it appears to be working:
Task.Supervisor to call the function that calls into the webhooks supervised genserver (webhooks genserver handles the events and notifying subscribers via PubSub of the events)200 "ok" response to StripeStripe.WebhookPlugMetamorphicWeb.StripeHandler with stripity_stripe’s @behaviour Stripe.WebhookHandlerThe challenge for me was that the webhooks would consistently work in development with the Stripe CLI (considering ngrok for future). So, I would first check that things work there and then have to test in production on my own account and go back and forth.
I think this really was the difference-maker for me and I’d recommend anyone to default to this body parser method if using stripity_stripe:
# endpoint.ex
plug Stripe.WebhookPlug,
at: "/webhooks/stripe",
handler: MetamorphicWeb.StripeHandler,
secret: {Application, :get_env, [:stripity_stripe, :webhook_signing_key]}
plug Plug.Parsers,
...
So, now the StripeHandler simply broadcasts out to the supervised webhooks_processor.ex GenServer to handle further processing and broadcasting:
# stripe_handler.ex
...
@behaviour Stripe.WebhookHandler
@impl true
def handle_event(event) do
notify_subscribers(event)
end
def notify_subscribers(event) do
Phoenix.PubSub.broadcast(MetamorphicWeb.PubSub, "webhook_received", %{event: event})
end
def subscribe_on_webhook_received() do
Phoenix.PubSub.subscribe(MetamorphicWeb.PubSub, "webhook_received")
end
Thank you to @stefanchrobot (response to another thread), @andreaseriksson (stripe course), Conner Fritz blog and Simon Rydell’s blog post.
