This week we chat with Jory Burson and Myles Borins of the OpenJS Foundation. Javascriptlandia is a new initiative from the foundation that allows passionate fans and contributors to help fund and maintain the Javascript ecosystem. And yes, there was once a plan to acquire a private island and certify it as a nation state so that they could start giving out top level .js domains.
You can read more about Javascriptlandia here. It is part of larger conversation happening on Google's Open Source Blog and through initiatives like Github allowing corporations into their Sponsors program.
For a delightfully old school and interactive website about Myles, click here. For his Twitter, go here.
You can find Jory's website here and her Twitter presence here.
This week's lifeboat badge goes to Marijn van Vliet for answering the question: How do I return a char array from a function?
Myles Borins So to me like that's the beautiful place that a foundation serves, it's a vendor neutral place that can kind of own this property that can create like an air gap to protect the collaborators. And this is a huge thing that I don't know that a lot of people think about is like there's a lot of risk that you're taking on by owning the software, by collaborating on the software and the foundation offers that cap.
[INTRO MUSIC]
Ben Popper Are you struggling to deploy cloud native applications to a hybrid cloud? Do you want to become familiar with Kubernetes and Istio? IBM cloud has a set of free, hands on training, ebooks, and an always on free tier of services to help you learn. Visit IBM.biz/StackOverflow to learn more, that's IBM.biz/StackOverflow.
BP Hey, everybody, welcome to the Stack Overflow podcast. I'm Ben Popper, Director of Content here at Stack Overflow with my co host, Sara Chipps. Hi, Sara!
Sara Chipps Hey Ben, how's your day going?
BP Oh, it's alright, Sara, I know, you are always here to share the relevant XKCD. And there was a big Google post last week that featured one of your favorite favorites cartoons.
SC One of my favourites!
BP Tell us a little bit about it. And then I think that'll help us transition into today's guest and episode.
SC Yeah, so this, this is my very favorite XKCD is because it comes up all the time. And it's talking about how the entire web is kind of built on a, there's new open source projects coming along all the time. But after a while, the majority of the web starts using one of them. And one thing to look out for is, you know, there might be an open source project that everyone uses that the maintainer, you know, moved to Idaho to start farming. And now there's this open source project that everyone is depending on, and with no one to work on it. So Google talked through their how they're thinking about funding these projects, and how to identify these important projects that are holding up the web and making sure they're maintainable.
BP "Thank you for your pull request. I now live in the woods and make furniture out of wood. However..." [Ben laughs] Somebody must be working with the code.
SC Yes, "I sold this to a crypto hedge fund 10 minutes ago."
BP Exactly. Exactly. "I'm on an island without any extradition treaties." No. Why don't you introduce our guest? Today, we can chit chat a little bit and then talk about interesting blog posts that follow some similar lines about how folks can support things that they're interested in that are distributed across the web.
SC Yeah, super excited to welcome Myles Borins with us today, who's the staff developer advocate at GitHub, and on the Cross Project Council at The Open JS Foundation. Welcome Myles.
MB Hello, thank you so much for having me today. I'm so excited to participate in the conversation.
SC And then also Jory Burson who is the community manager at the open JS Foundation, and therefore is dragged into all of our cross project counsel. Enthusiastically.
Jory Burson Yeah, it's fun. You're not dragged if you're willing right? Hi, Sara. Hi, Ben. It's good to be here.
BP Welcome. Jumps willingly into all cross project counsel meetings.
JB Heartily, happily. That's also one of my favorite XKCD comics too, Sara, by the way, it's a great one.
SC It's a really good one. My real my real favorite one is the one with the bobcat, ordering the bobcat from eBay. Okay, we'll add that to the list. We'll add it to the shownotes. Well, related to, [Jory laughs] very related to all this, can you tell our listeners what the open JS foundation is and does?
JB The open JS foundation is a nonprofit, software foundation. It's a member driven organization, and all of our member companies come together because they find the caretaking of the JavaScript, open source ecosystem extremely important, for lots of reasons, you know, which I think that, that XKCD comic really speaks to, it's really important for us to work together to take care of the knitting, if you will, that supports our industry, right. And that's what the open JS foundation does in a nutshell. And we do that through providing different programs for our open source maintainers and their projects. And we have events, we try and pull people together to work on cross cutting problems. It's the cross project council is about that. That's kind of what we're talking about earlier. And yeah, we're going to open up a new way for people to get involved here really soon. And I think that's what we're going to talk about today. So.
BP I'm looking at it here, it says "open JS foundation individual supporter program now available, join us in JavaScript landia" [Myles laughs] put a bird on it. So tell us a little bit about this. This is interesting because of that Google post, which was kind of talking about how they were going to support things. And then recently GitHub universe, they announced some new ways for corporations to support open source projects that they believe in. So it feels like this is a broader conversation that's happening in the industry. Maybe we talk about why that is, and then what's your blog post is aiming to accomplish? Or what should this new initiative, I should say.
SC Myles and Jory can speak to this as well, I think that similar to kind of what Google and all the big companies are thinking, Microsoft, GitHub, for example. And then they write these big old checks, they can, you know, write bigger checks, but they want to support open source, but also, there's a lot of people out there that write JavaScript, and they might, like contribute to one of our member projects or not, but want to get more involved and want to know what's going on and want to know how to get involved, and how to support the foundation. So the 50,000 foot view, this is a way for people to get more involved in open source as it regards to the foundation in general.
JB Yeah, and I would add to that, you know, I think for a while software foundations, like the open JS Foundation, have had pretty standard ways for big companies, you know, as Sara points out, those are typically your, they can write bigger checks, and I can, I don't have just like $50,000, lying around to give to eslint as much as I would like to give that money to Nicholas Zakas. So instead, I give him $5 a month through GitHub sponsors, and that's great. But it's not necessarily the kind of fiscal sponsorship that you know, a bigger company can give, but even still, as a financial supporter, you know, I want to feel a connection to that project, I want to feel like I'm doing my part to give, you know, love. And then also, you know, hopefully to get additional benefits, which in some cases, the foundation provides to its corporate members, in terms of like marketing programs and things like that, that that we have for for those sponsors. We're not talking about, you know, doing marketing programs for individuals here. But there, we are talking about some pretty fun ways to expand community for these people who, who want to get deep in their involvement in projects, and to do that, hopefully in a, in a way that allows them to support all of our awesome projects.
MB Yeah, I think I think one of the things that is a real challenge here is sustainability. And like defining what sustainability is, and then like thinking through it. So, you know, I think if you look at stuff like open collective or GitHub sponsors, or what's the name of the program from the Linux Foundation Jory?
JB It is lF Insights now.
MB And so you know, there's all these different projects that exist as a way to say like, "I've got money in my pocket, and I want to put it in your pocket, developer." And, you know, I think for someone like myself, who has like, I've been working kind of in corporate open source for almost five years now. I personally am not new in need of those specific dollars. But I know that there's a lot of independent people. And like when we think of kind of like the "indies" as a way of thinking of it, like where they need that support to help kind of like fund themselves. And so that's one end of the sustainability spectrum, which is like the individuals and sustaining their livelihood. Then on the other side of it, too, is like, these very large projects are often not always but often not an individual. It's not like you can look at node JS, and say, "Oh, this is the person node, let's support them." Node is made up of, yeah, like 100, plus different collaborators, many different working groups, it's completely volunteer led, no one organization owns it. And when you think about the size of this as if it was a business, there's a lot of needs, that a project of that size has. From marketing needs from like, "Hey, like, we need to get the word out about the thing." PR needs like, "Hey, we have found a security vulnerability. And we need to figure out how do we talk to the press about this, because there's press cycles." To like lawyers, like "Oh, my god, there's export control guidelines, what even are those? How do we make sure that our collaborators are not committing treason?" Which is like, I'm pretty sure no one like got on GitHub incentive, wanting to commit treason. But like, you could accidentally do that in the open source world without even knowing you did. So like having a lawyer on retainer who's ready to support you. Or like you get a copyright violation. Like there's all these different things, that it's like if you were working for a business, from HR, to marketing to all the different departments that you'd have to support you, like, how do you get that kind of infrastructure? And so to me, like, that's the beautiful place that foundation serves, it's a vendor neutral place that can kind of own this property that can create like an air gap to protect the collaborators. And this is a huge thing that I don't know that a lot of people think about is like there's a lot of risk that you're taking on by owning the software, by collaborating on the software and the foundation offers that gap. We have a staff on hand to help with things. We've got an amazing group of people including jewelry that are like ready to go to help with all the different things that our projects may need. And so like how do we Keep those things running. And like corporations obviously can cut big checks. But the JavaScript community itself has this massive long tail. And a huge thing that we've been trying to figure out is like, well, like, I don't want to say how do we capitalize on that? Because it's, we're not trying to like make a profit here. But it's like, hey, if there's people who are interested in spending a couple bucks a month to help us out, we're like, what can we do to offer them value? And this is one of the hardest things of the foundation is altogether even for corporate sponsors, like, how do we offer an a value that folks feel like they can chip in a bit?
BP Yeah, I mean, I'm curious, like stepping back and looking at this with a little bit of historical perspective, as the software industry been through a sea change in the last decade where the intersection between as you're saying corporate and open source has really shifted where a lot more corporations are relying heavily on open source stuff that came from outside or sort of in the reverse, creating projects internally, and then open, open sourcing them, and a lot of people are playing with them in different ways. And that's what's creating these sort of new tensions and new requirements for support. Like, how come this infrastructure hasn't been so well built out yet, and we're seeing, you know, a bunch of people coming up a bunch of different companies now coming up with new ideas for how to make it work. Why is this XKCD cartoon, especially seemingly more relevant by the day, I guess, is the question.
JB I mean, my personal take is that it's not this isn't new, you know, that this XKCD comic was relevant 20 years ago, it just in a different sort of population, right. It's, it's new to us, because we are web developers. And this in our space is JavaScript and HTML and CSS. And now with the web, we're able to deliver things at a scale and pace, which is pretty extraordinary. Whereas before, we were talking about swapping software packages via email, or hard disk, like literally mailing them, but they still in the mail, literally in the mail. But they still have those problems, then as well. It's just now it's happening in like a bigger on a bigger scale. And Ben, I think, you know, your point you were asking about, like the sea changes, I think we've seen a couple, and they are kind of in alignment with what you're saying where, you know, initially, it was on the web anyway, like, populations of curious JavaScript developers who were coming together and sort of working on interesting problems and like, creating open source from that curiosity, you know, from that space, and then, you know, you get this influx of people relying on them, companies creating products on top of that, producing their own open source, that they would like to get the lift from the community, you know, so it's, I think there's several interesting aspects of it, you can't just pinpoint to one.
BP I mean, I think what you're saying there is what occurs to me as sort of a non developer, just, you know, thinking this through over the last couple of episodes is that there's this feedback loop, right, where companies want to appeal to developers. And so they pick open source, you know, languages that are popular to support it, because that way anybody can get involved even often at that, you know, early level, people are encouraged to build their career in their resume, by doing something in that space, right. Like, "before you have a job, maybe go work on an open source project" is a tip I see a lot in, like how to get my career started as a software developer. And so everybody within the ecosystem has these different incentives that are pushing them towards this open source idea. But right, it's still lacking maybe some of the financial infrastructure, or as Myles was saying, maybe the the governance side of things, you know, when you're trying to work with it at scale inside of a corporation as well. I don't know, Sara, what do you think?
SC Yeah, no, I think one thing about open source work in general, if you've done it or done it for a long time, is that if you don't have these frameworks and structures, you just start to hate it. Like you start to hate your project, you start to resent the people sending you issues, you start to, you know, just be like, I really can't stand doing this. And so organizations and efforts like this, I think are so important to make sure that people aren't burning out so much.
JB Yeah, a lot of like, I think what guides my work in community management is actually focused on the maintainers themselves and make and checking in on their well being. And, you know, like, what can we do as a software foundation to make your life a little better today, because that's sort of, at the end of the day, you know, taking care of those folks who drive so much of the value in our ecosystem is really, really important. And yeah, we want to find ways to spread that love.
MB I think a good thing to point out here as a distinction, though, Ben to the question that you were asking about all these different things popping up, is, you know, like, being a maintainer is is not easy by any means. And like, especially if you're not working for a company that's like supporting you doing that work in your hours, then the question of compensation always comes up like you know, I'm not doing this out of the goodness of my heart. Well, a lot of people are but like at a certain point, like being a maintainer is not the same as a drive by PR, it's its work. And so one of the things with open JS that I think is worth pointing out, is like, open JS as a foundation does not exist, to pay salaries to maintainers. It exists to be like an infrastructure to support projects. And while there are other foundations that do have people on staff who do technical work, the staff of the open JS foundation tend to be in support roles. So it's like program managers to help make sure that like, you know, things actually get done. Folks, like Jory, who are helping with community stuff to make sure that the projects have the support that they need, that they know what they have access to that that like things are actually getting followed up on. And I know that some foundations have actually had poor experiences with directly paying maintainers. And that's not to say that maintainers shouldn't be compensated, I actually think that, you know, every company who relies on open source should be carving out time of their whole work staff to contribute back. That's maybe another podcast for another time, but I did want to point out that that distinction, because a lot of people if you're going to an open collective, or GitHub sponsors, they're kind of putting money directly into the maintainers pockets as a way of kind of supporting them as individuals, whereas the open JS exists much more as kind of like a neutral place to collaborate on projects and give support to those projects, but not directly compensate the maintainers.
SC That makes sense. So it's been so long since we've started working on JS landia. That I now forget the origin of JS landia. We've been really fun. It's been a fun thing to workshop with the cross project council. So the cross project council just to explain what the cross project council does, you know what I say this really affectionately, it's like the bureaucratic arm of open source. And I've found that like, I love open source bureaucracy on some levels, just the things that you know, need to be done to help the projects, different initiatives from the foundation, things like that. I believe it reports up to the board, Myles, you're on the board. Is that correct? I believe.
MB That is correct. Yes.
SC And so we've been working on this for a bit. So MYles, can you tell the story? Because my story is going to be disjointed.
MB Yeah, so a number of years ago, when people were hanging out in person, we were at this conference, which was a thing we used to do, where people get together. [Myles laughs]
SC Crazy. In person?
MB In person! In the same place! At a location that isn't where anyone lived. It's, it's wild. And so this particular one, I believe, was in Tahoe, but it may have been anyways--
JB It was Half Moon Bay.
MB So we're in Half Moon Bay, having some drinks afterwards, I believe Jory was there and you know, what, I just won't name all the people because I don't know if they want to be implicated in this. But we started talking about how when we merged the node foundation and the JS Foundation, the note foundation originally had three board seats specific for community elected positions. And when they emerged, we kept all three seats, but the third seat wasn't activated yet. And it would only activate when a certain number of individual members had joined what we were at the time calling an individual membership program. And I believe it's something like 2000 people that we needed signed up before we would activate that seat. So a bunch of us were sitting around and trying to scheme like, well, we want this community representation. How do we get like that much traffic? What could we offer, that would actually be valuable enough that people would do it. And for we're separately actually looking at teasing apart, like and bringing back that third seat without requiring this like watermark of people joining. So I'm adding that only for historic reasons not to pressure people into joining. And so we came up with this wild idea of like, well, what if we could get the .JS, top level domain? And then we could make we could make domain registration a benefit of the membership? I'm like, we'll sell 5000 domains on day one if we let people register .JS.
SC Yeah! I would buy Sara.js.
MB Yes. And if all you needed to do was like sponsor the open JS foundation for $20 a year, and you would get a domain we would sell like hotcakes. But it turns out that two digit tlds are only for nation states. So we started scheming how we could create our own nation state, which we call JavaScript landia. And apparently, someone's friend's father had like, fought off the British on an island, which says so we tried to see if we could like create a sovereign nation of JavaScript landia on this island, so we could get the .js tld. The fallback was three digit tlds can be registered by more people. So we were maybe going to do .mjs. But we figured the JavaScript community might hate that. So we haven't done it yet.
SC Yeah, wait, why mjs?
MB Oh, cuz that's the file extension from es modules in node that everyone hates. [Sara & Myles laugh] Also, it's Myles JavaScript.
BP Sara, I feel like this is where your crypto experience is going to come in handy. You must have at least a few islands that you own, ungoverned, somewhere.
SC Yeah, we can get like four JavaScript electoral votes. [Jory & Ben & Sara laugh]
MB Yeah, I was gonna say we are joking. But it did go far enough that I actually went through and like look through the governance of the UN to figure out like, what's the process of becoming a nation state? To which it was amazing to find out how much are the governments of ECMA, the standards body that the JavaScript language is standardized, that is actually based on the governance of the UN, through having a general assembly, executive committee and like some of the ways in which like you add new members to ECMA is actually like a abridged version of the process of adding new nation states to--anyways that's what I do for fun. [Myles & Sara & Ben laugh]
SC It would be the most poorly defended nation state. People would be like "we challenge you" and everyone would be like, "eh"
BP Oh, yeah, great cyber though. I mean, the cyber, the cyber offense--
MB You want malware, we got that malware? We got so much malware.
BP Yeah, just sort of getting back to that big conversation you're having before, Jory, you were saying, you know, this is existed for a long time, it used to be that you swap this stuff over, you know, physical or whatever. I guess, like, it was interesting to me to hear Sarah say she kind of loves the bureaucracy of some of this stuff. And then here, miles say Actually, this came out of the UN. I mean, is some of this, like, in some ways, you know, for better or worse, the formalizing the ossifying, the institutionalizing of open source, which I guess, you know, people have associate with like a more free willing, you know, anybody can enter.
JB Yeah, oh, my gosh, and yeah, you're picking up on a really important theme, and which is, and there's a whole sort of group of folks in tech, under like the maintainers, they have like a program called Halo maintainers. Like, and basically, it's a continuation of that of that theme, where there's a new innovation that comes along, people get really excited about it. And most of whatever that is, is gonna work, like the community is going to move on from pretty quickly. But there may be a couple of like, key pieces of technology, a couple of key ideas that are very important, and they become over time, like the bedrock upon which other things innovate. And we saw that like with grunt, the task runner, right, which was really kind of took our community several steps forward in terms of like, automated tasks, and things like that, but, and a lot of people like, adopted that pretty quickly. Within a couple of years, there were other tools that came along that were a little bit more innovative, and maybe kind of were a little bit more clever, or whatever. But those central ideas stayed around. And so I think, you know, over time, what happens is, you know, there's this project that comes along, and it does become a staple, and something else comes along, and it's cooler, so a lot of people move on to it. And what's left is a very important piece of technology like grunt that has to continue to be maintained, it has to continue to be supported, because so many people are still using and consuming it. But it's not necessarily getting that traction, it's not necessarily getting that attention that it used to get when it was the new hotness. It happens that still, like 50% of developers are using it. So we damn well better make sure that it's you know, like, there's nothing, you know, critical. So I think one of the roles that the foundation plays is to continue to ensure projects like that are getting the attention, and the love and the maintenance. And ultimately, the goal was kind of to make it boring. Like I'm not trying to be like, cute about it or anything. But you know, me maintaining things is not necessarily like the most exciting thing. But boring is cool, like boring is important. You know, and so yeah, we're the bureaucrat that I actually take it as a compliment. Like, it's not exciting.
SC Boring is cool.
JB Boring is cool! Boring is cool. Halo maintainers. You know, yeah.
BP This has been my message about politics for a long time. Yeah, we want things to be more boring than they were for the last couple of years. Myles, tell me a little bit about NPM. I know every time Paul is on, he talks about how it's a cheat code that he uses on a regular basis. So for the noobs explain a little bit about how it works. And then I know you just gave a talk at GitHub universe. Tell us a little bit about what's happening with it now and what you were talking about?
MB Yeah, absolutely. So, you know, like NPM is one of if not the largest repository of software on the planet. We have just under 1.5 million packages on there and over 100 billion downloads a month. It's a lot of JavaScript, and sometimes some other things too, sneak on there. Also. But you know, that's cool. But the talk that I was giving at GitHub universe is I joined GitHub in June. switching jobs during a pandemic is definitely interesting. GitHub acquired NPM this year, and it closed, I believe, you know, like a month or so before when I joined. But I don't remember the exact dates, that so I've joined, as you know, the teams are integrating, and we're doing all of the remediation work that you need to do when acquiring a company, because GitHub is owned by Microsoft. So there's like this really interesting, like GitHub has all its things you need to do and then Microsoft has all the things you need to do. And so you know, there's a lot of work that we're doing on kind of like general remediation on security audits on just making sure kind of like everything is up to snuff. So I'd say that's like a lot of kind of reactionary work, while at the same time still wanting to make general improvements to the service and to our tools to show folks like, hey, GitHub's here, we're listening, one of the things that we did launch that I'm the most excited about is a new public roadmap and feedback process. So you can go to github.com slash NPM, slash roadmap or NPM, slash feedback. And those are two places where you can come and engage with us. And the roadmap will show you at a high level, like some of the things that we'll be working on over the next couple months. And then we've also got the feedback repo where you can come and use GitHub discussions to make suggestions. And then we have these bi weekly, although in the new year, we may move them to monthly, we're still kind of figuring it as we go. But we've been doing live streams of the NPM teams, like our leadership team, internally, reviewing these discussions and talking about what we want to prioritize or not prioritize. And we're trying to do a lot of work on as much as possible, like democratizing our decision making process to like, to an extent, and we're still a company, it could never truly be a democracy, sadly, for some folks. But I mean, well, now I'm going on a tangent about like bfl versus like consensus. But I do think that, especially for companies, there's a lot of benefit in the speed that you can work when you have individual decision makers, kind of saying this is what we're doing and moving forward. Consensus as well, it's great as an open model, especially for open source also comes with its own costs. But we're trying as much as possible, because we're so you know, involved in the open source world, to have a model that reflects what people are used to, it's heavily inspired by what we've done in open js. And we're trying to, you know, make it so like, Hey, if you're a person who doesn't work for GitHub, and you have an amazing idea of something that we should be working on, you know, there's a clear path where you can make those requests where you can get direct direct feedback from us where you can go and actually see a video recording, or a live video of the team discussing what we're going to do and then see it end up on the roadmap. And one example is like markdown rendering was something I talked about where, you know, we for a while, have gotten kind of feedback privately that we'd love to see more accurate markdown rendering for NPM. On the landing pages, we're actually now using GitHub flavored markdown for rendering all packages once they're published. And in the talk, I kind of go through showing how this starts as a discussion makes its way onto the roadmap, and then comes out as an actual feature. So you know, for folks at home. Yeah, please come and join us on the feedback repo. If you've, if you've got ideas, we'd love to hear from you.
SC That's very cool. First of all, at Stack Overflow, we have a cheer-ocracy. So that's how we work things internally. And then what kind of feedback do you get from those meetings? Like, do you have people watching your videos and being like, oh, now I kind of get you know that I think that's one of the most difficult things when you're really invested in a product and you see them prioritizes like, crazy feature, and you're like, no one wants this. Everyone wants this other thing. So do you see people like watching your meetings and being like, "Oh, that's why!"
MB So we've only done three of the meeting so far. And there has not been a ton of engagement directly with it. But what I found it's really useful for and this was something that we did over a node when we were designing es modules was that like, by making this process more transparent by making it something where we're empowering others to participate in it, even if it's not directly all the time, we kind of have the receipts about why we're where we're at. And so while we may not be getting, like tons of immediate engagement on the live feeds, we are getting like a decent amount of engagement over on the discussions leading up to them. My hope is that like, you know, when someone's does come and say, "Hey, I have this thing I really care about why aren't you prioritizing it?" We have a lot of receipts that we could say it's like, well, you know, we have all these other things that have come in, we had all these discussions. Here's what we have prioritized. Like we could say we're tracking it, but like we and this is something I'm learning as a product manager is like, you know, you only have like so many levers you can pull, right? We've got headcount, we've got time and we've got scope. And so like each one of those plays off to each other. So unless like GitHub like "Hey, here's 100 new engineering. And we can talk about the mythical man month." Like we have limited time that we can spend on things. So as much as we'd like to do everything that people asked for, we can, but hopefully at the very least, they can see, hey, this is what we're working towards. And here's what we prioritize and why.
[MUSIC]
BP Alright, yeah, it's that time of the episode. Speaking of giving credit to the wider community, every week, we try to shout out one lifeboat badge winner, that's somebody who came on Stack Overflow and answered a question that had a score of negative three, got an approved answer up to a score of 20 or more. Oh, this one has my favorite. "How do I return a TCHAR array from a function?" Love that one. I love to just say that word. So this lifeboat was awarded December 8, two margin vanvleet. Thanks very much margin. I'm Ben Popper, Director of content here at Stack Overflow. You can find me on Twitter at Ben Popper, or email us podcast@stackoverflow.com.
SC I'm Sara Chipps, Director of Community here at Stack Overflow. And you can find me at @SaraJo on GitHub. Myles and Jory. Who are you and where can people find you online?
JB I'm @jorydotcom on all of the all of the medias on Twitter and GitHub and all of that but yes, say hello, @jorydotcom.
MB I'm Myles Borins everywhere and Myles is with a Y, just to make sure that that is clear. You maybe can't tell from the way I enunciate, I'm rowbit on Soundcloud if you want to hear my jams. And yeah, like my DMs are open but in general like if you're not followed by me, it ends up in this like message request folder that I always forget to check. So heads up if you do DM me and I don't follow you. And I don't get to you for a couple of weeks. It's because of object permanence and ADHD. Not because of you. [Myles laughs]
BP Fair enough.
[OUTRO MUSIC]