Raul Jordan: Indeed. So as it stands today, Ethereum actually runs on what we call proof of work. People have probably hear about cryptocurrency mining - bad for the environment, killing trees, all sorts of things. Basically, the way that Ethereum and Bitcoin work today is they require people around the world to basically run these machines that are specialized computation circuits that use an extreme amount of electricity to basically solve this brute force math problem, and participate in the consensus of the blockchain.

The paradigm is that you’re putting in a lot of real-world electrical power into this system such that it becomes almost impossible that anyone can collectively try to revert that. You cannot revert the Bitcoin or the Ethereum blockchain without having more electrical power than all these people combined that put their effort into it.

So Ethereum is actually migrating to what we call proof of stake; so instead of expanding a lot of electricity, what you’re doing is that you’re instead locking up a lot of Ether, you’re locking up a lot of this cryptocurrency called ETH, and to participate in consensus, you need to put that up for stake. If you do anything malicious, you can start losing that stake. It changes the paradigm. You don’t need this crazy computational thing; it’s just basically anyone can run it on a home server. You can run it on a consumer laptop.

[58:49] Since Ethereum was already proof of work, the transition into proof of stake is very solid, because we can leverage all the security that Ethereum has already over the years into this new paradigm. So we are one of the teams that’s building proof of stake for Ethereum. Ethereum proof of work - the mining, basically - is planned to go away in less than a year, so basically no more shortage of GPUs on the market. You’ll be seeing a lot of really cool stuff happening, estimated I believe to be like 99.98% more computationally effective, and better for the environment. That’s something that we’re excited about, and just keep an eye out on that.

Jerod Santo: Right. Well, this isn’t an investment show, it’s definitely a show about software, so I’ll stop down that route. But let me just say that we’ve been watching this, and watched loosely some of the alternative coins or the things that are changes to Bitcoin or inspired by Bitcoin, and like I said before the break, there’s lots of things that come and go… I was even mining some CoreCoin for a few months just for fun; that’s at 0.00 at this point, and perhaps is completely just a footnote in history.

One thing that we look for as we invest our time and our skills and perhaps even our money into communities and software projects, because this is a very large software and open source software projects - there’s over 80 projects that the Ethereum Organization has on GitHub… We look for sustainability and long-lasting things, and one of the constant themes in our shows and in our community of developers is the JavaScript fatigue and the constant churn of new frameworks and new ways of doing things - some people see it as a Renaissance, other people see it as ridiculous… I personally don’t buy into new JavaScript frameworks very often because I’m just waiting for the next one, and it seems like with the cryptocurrencies there’s very much that possibility. Aside from Bitcoin, many other ones have come and gone, and of course, Bitcoin itself hasn’t been around for all that long in the grand history… So that’s one of the questions I have about Ethereum, especially as we look at it as app platform - and we’ll get back to that. Looking forward, you’ve survived what would be considered a PR disaster and really a crisis in your community over the summer… Looking forward, what is it about Ethereum that you believe makes it have lasting power, and that we can have trust, not just in the currency, but in the platform as something that we can invest in?

Tim Coulter: Yeah, sure. The short version of it is when the Bitcoin boom hit in 2013 when it went from $5,000 to $1,000, I got into cryptocurrency after that, and got really excited about what it is and what it could do. In early 2014 I started mining, I mined on a bunch of different altcoins at the time now worth nothing… It was a fun experience for me, and I did it mostly on the side. I was working for startups and have worked for startups my whole career coming out of college, and the startup I was working at I eventually got laid off, and by that time I had been doing other work in cryptocurrency, I had built an application on my own time to track all of the price data for a bunch of different trading pairs; basically, every trading pair on ever exchange available at the time. I was trying to aggregate all those and eventually sell that data…

In any case, that whole thing got me in interested in the blockchain world itself, so when I got laid off from this company, I told myself “You know what, I’m gonna go work in blockchain.” So I searched around, I eventually found a post on angel.co, and that led me to consensus. That was around April of 2015. The post was actually for a web designer job. Excuse me, not web design, a graphic designer job… And I can’t actually do graphic design, but I sent them a message anyway and said “Hey look, I could try this. I’m really excited to work in the blockchain world, I’d love to work with you”, and they responded the next day.

[04:13] The rest from there is kind of history, but as far as Truffle is concerned, my past history in software development is actually in the software testing world. In college – I have a software engineering degree, but I worked a lot with a professor in software testing, and that was big in the software testing community… So when I came out of college, I used that network to find jobs in the software testing world.

What that means is that for most of my career, effectively 8 years leading up to coming into the Ethereum world, I was doing developer support. This is everything from performing manual testing, to writing software testing frameworks around new technologies. When I came to Ethereum, it was very clear that there were no tools at all; you had a compiler and a JavaScript library for interacting with the Ethereum blockchain, and that was about it. From there, it seemed very easy to fall back into this developer support role, and I ended up building tools through the Ethereum ecosystem.

Mikeal Rogers: [32:14] Right. So if you wanna create one, you do what’s called minting. To mint an NFT means you take the data, you put it into IPFS… You can use this project that I talked about, NFT.storage, and that’ll handle getting all of the data in IPFS, creating the metadata file, getting you what you need to work with an NFT. But then you’ve gotta pick a blockchain you’re gonna use, and what you’re gonna do is you’re gonna develop a contract around how that NFT is used, and then you’re gonna reference that IPFS address for that metadata in that NFT. And then you’re going to use the user’s wallet. So the user that is minting the NFT, not the developer - this is the user’s wallet - will then sign that transaction and put that on the network.

We can link to an example of how this all works, actually. That’s probably a little bit better. There’s a blog post about this little project called Minty, that we wrote at Protocol Labs, that does some minting. If you’re pulling apart these different components, there’s parts of this that are on the developer, and parts that are on the user; so the user has to have a wallet around, and there’s different ways that different applications have approached having that wallet. There’s a project called Metamask, which is a very popular wallet for Ethereum… You can use Ethereum wallets on a lot of other chains as well. It’s a public-private key. But Metamask is really nice in that that stays in secure storage on people’s devices. It’s never shared with the application. So there’s no man in the middle stuff, there’s no custody issues. It’s always the user’s address. That’s a really great one.

But a lot of these projects that are getting people to set up Metamask, getting people to set up these wallets is actually a big barrier to entry, so a lot of the NFT minting sites that you might go to will just create a wallet for you, and they’ll hold on to the public-private key pair. And that can be problematic, because if they get hacked, your private key’s gone… And also, they can kind of run off with it. You really want to have custody of your wallet in this ecosystem… But again, it’s really young, it’s really immature. The user experiences around wallet custody are not entirely worked out very well. There’s a bunch of sites where you have an account with them and they have that wallet, and then they’re handling a lot of the signature stuff for you when you mint these NFTs.

Nader Dabit: Some of the DAOs allow you to just join for free, some of them ask you to mint some type of token… But either way, you have to have, for the most part, some type of token to get in. And the reason that that’s the case is to kind of give ownership to everyone that’s there, and also provide them a way to liquidate that ownership.

So for a token, you can basically sell that, either on some digital exchange, or maybe like an NFT would be like OpenSea, or some type of NFT marketplace… But yeah, most of the time you can get a token or buy a few ERC20 tokens, or work for those tokens by participating in the Discord, and then you can participate in that way.

For the Developer DAO, which is the DAO that I have created for developers, the token is completely free. All you have to do is just go to the website and mint the token. And you do have to pay the Ethereum transaction costs. When you pay that cost, you get that token sent to your wallet.

And really, the reason that there is any type of cost at all is to kind of have some type of way to prevent civil resistance… Because if this token is gonna be worth money at some point, what’s to stop someone from minting all 8,000 of those for themselves? Like, how do we equally distribute ownership between a large number of people? Well, there is some type of way that we can do that with needing someone to mint.

But what I’ve been doing is actually setting aside a few thousand of my own dollars, and just minting those and sending them to people around the world that can’t afford even the $20 minting cost. But that way I know that that person is real, and that they’re kind of in it to be part of the community, and they’re not just in there to kind of speculate.

Jon Kuperman: It’s really interesting, because we offer gateways, like for Ethereum… So you can hit one of our public gateways, or whatever… But we haven’t done a ton in the cryptocurrency space. We do a ton in the cryptography space, but…

Matti Ranta: Of course, yeah. I’ve contributed to drone.io, the CI/CD. There’s a fork of it called Woodpecker that I’ve also contributed to. I maintain several Golang libraries for automation. Probably the biggest thing outside of Gitea that I do is something called xgo, that lets you cross-compile Golang binaries on two different platforms. Normally, Go lets you do this with just like changing a few environment variables, and like “Hey, this is like targeting Windows now.” And just say “go build target windows.” Unless you’re using cgo, which is pretty common for the SQLite library for Golang; it’s using cgo, so you can’t use all those just fun tricks of the Go command line just to build a binary for – if you’re on Linux, building it for Windows, or for Mac, and vice-versa. So xgo as a project was originally created for the Ethereum Go project, but it went by the wayside; the maintainer wasn’t able to support it, so I picked it up, I added support for different targets… PowerPC, FreeBSD, Linux/PowerPC, FreeBSD/AMD64. Because it’s not just the OS, it’s the CPU architecture you need to target as well. And built in automations to be able to – when a new Go version is released, then a new version is taken and built. Because the way that it works is you’re actually just distributing the headers of the development library. So you’ll have the kernel headers, the GCC stuff for Multilib, and whatnot. And so it’s a great, big, beefy binary or Docker container that takes a ton of time to build… So I just have a cron job that checks go.dev whenever a new version of Go is out, builds it, pushes it, and…

Preethi Kasireddy: That’s one of the solutions that for example Ethereum is looking into right now. The fundamental thing is you need to figure out a mechanism where you can – let’s say you shard, there still needs to be some way such that every node can still validate every transaction, because that’s the fundamental premise of a blockchain. Every node should still be able to validate it.

So if you shard it and only make some transactions available to some nodes, then it’s not possible for that node to validate every transaction. You have to create a mechanism so that even if you shard, every node is still able to validate the blockchain. That’s why it’s hard.

Jay Phelps: Yeah, that’s exactly right. That’s one of the most exciting things about WebAssembly to me… It’s not tied to the future of browsers and all that stuff per se. There already are places and people who are using WebAssembly in completely unrelated web cases. The Ethereum Virtual Machine, for example, is being rewritten to use WebAssembly as their instruction set. And there’s other use cases, as well.

[11:55] There’s even a person who’s on the community group who is trying to create an actual micro-kernel, the core functionality of an operating system, that runs WebAssembly natively, without needing to use system calls for – like, if you know a lot about OS stuff, they have different rings to the security privileges of an operating system… And with WebAssembly, the way it’s sandboxed, you actually don’t need those rings if all applications were written and compiled to WebAssembly. So you could do some very interesting optimizations.

There really is not a lot of precedents for this. The long-term viability of it is an open question, but it’s kind of a really cool and exciting thing… Because I would love to see WebAssembly be that gap, that bridging of native applications to web applications and making it so that eventually the browser just gets absorbed into the operating system and there’s no distinction.

Chrome OS is the perfect example of what does the future maybe look like, where the browser and the OS are one and the same. I think WebAssembly really helps bridge that gap. I could see – this is a huge bet type of thing, but I could see companies like Apple and Google, with their Android and iOS, deciding to eventually support WebAssembly as a first-class application format, instead of their proprietary solutions. Because they both have to do sandboxing, and they both came up with their own proprietary way of doing that.

Mikeal Rogers: [19:50] One thing that you figure out really quickly is that if you’re taking in all of these high-quality audio channels, and you’re taking them into one of the peers who is the host of the call, while the call is going on, then there’s not enough bandwidth for the actual audio quality to be good… So you can really saturate your connection really quickly. So what you actually wanna do is just buffer that kind of locally, and then send it at the end of the call. But then if somebody closes the browser, then you don’t have the audio… [laughs]

So actually, what it turns out that you wanna do is send this to a server. This is actually a place where a central server would be quite nice… And there are some products now that do this really well, where it’s using a real-time audio channel, but then sending all of the background channel to a server… And then at the end you’ll see that it’s like “No, no, no. Don’t stop yet. We’re still uploading.” So there’s some UI around that that’s really nice. I never really got to that part of it… And I looked into solving some of those issues with some other technologies. I looked at potentially using WebTorrent to do the file portion of it, and that didn’t quite work, so I started looking at IPFS, and at that time - this was three years ago - IPFS wasn’t quite ready.

The next bucket of projects, the peer-to-peer projects that use this because it’s the only thing to use - there’s a lot of cool stuff in that category. Feross was talking about WebTorrent, and WebTorrent is amazing… IPFS is something that I work on a little bit - it’s really nice now; it uses that channel as well. And then IPFS is really built on some primitives that also take advantage of this. I work on IPLD, which is like the data structures… And we don’t do anything specific with WebRTC, but if you wanna take our data structures and decentralize them, you would have to use WebRTC in the browser.

The whole networking layer behind IPFS is a project called libp2p, and this is really like a peer-to-peer networking stack. If what you’re looking at is the whole problem of peer-to-peer networking, and content discovery on a peer-to-peer network, and if you wanna run this in the browser, in Linux, everywhere, and every kind of environment, you’re gonna need all these kinds of fallback logic, and all these different protocols on different devices, and you’re gonna have to think about this in a much bigger way than you would if you were just targeting one system. That’s what libp2p kind of does.

So yeah, if you have that whole problem, it’s a really good project. I think that if you wanna hack together a cool little web project, it’s a little bit heavy for that one thing. Ethereum 2 is gonna be built on top of libp2p, because they have this whole problem…

Kevin Owocki: Okay. Web 3.0 is – oh man, I’ve gotta take a deep breath, because once you start going into blockchain, you’re just in the rabbit hole of this whole world… Yeah, hold on to your butts, because we’re about to go there. [laughter] So Web 3.0 is what the Ethereum community calls “our vision for the web when the web is blockchain-enabled.” Just to unpack that a little bit, when you browse the web, you’re using a web browser - I’m a big fan of Google Chrome, but I also have Brave, and I have Opera and Safari installed, and those applications are great at making HTTP requests to a server, and then receiving a response and rendering all of the HTML, CSS, JavaScript, that kind of stuff.

In the Web 3.0 model of the world, specifically the Ethereum Web 3.0 model of the world, your browser will become blockchain-enabled. What that means is that they can read from and write to the Ethereum blockchain. That’s an important capability for a browser to have in the Web 3.0 world, because the Ethereum blockchain is a store of value and a store of information that can be shared across the entire internet. It allows for something called fat protocol, which is just basically a way of saying that Gitcoin can share bounties information with – The Bounties Network is another bounties project that’s out there… And what this does, the reason why it’s pretty neat for it to be on the blockchain is that it prevents us from having vendor lock-in for our data.

[39:51] If you think about some of the problems with Web 2.0, or at least in my opinion some of the problems with Web 2.0 is that your social network is locked into Facebook. Your search history is locked into Google, and if you wanted to transfer them to somewhere else, then it wouldn’t – it’s not self-sovereign; you can’t just go to a different social network and take your Facebook social graph with you. And I think that this is a real problem if you look at the prevalence of hacks that happened, particularly if you look at the Equifax hack that happened about six months ago… You as a consumer don’t have self-sovereign control over your identity, and in the Web 3.0 world you will, because there’s these fat protocols where the data is stored on the blockchain in a way that can be migrated from site to site, and you as a user have control over your identity and who you wanna give that information to through your Web 3.0-enabled browser.

I know I just took you all through the rabbit hole of what some of this means and what it could potentially mean, but the TL;DR, the sum is that if you install a browser extension called Metamask on your Chrome, Brave or Opera browser, then that will give you Web 3.0 capabilities in the web browser that you already know and love.

Jerod Santo: Right. Whenever you talk to or read from the real builders, the ones who are there for principles and for technology and not for gains, and ponzis, and like quick things - which many people just come for that - they like the down markets, because all of the hype and all of the noise and all the scammers kind of just go away, and they can just put their head down and build cool stuff… Which is what they were doing the whole time anyways. But all of this stuff surrounded them. And so they tend to like times like this, because they say “Okay, we can just quit explaining it to everybody, quit talking about it, and we can build, build, build”, and eventually, show us to the Promised Land.

It’s getting to the point now for me where it’s like – I remember when we first had Gavin Woods on the Changelog talking about Ethereum, and I asked him “Where’s the application?” And I’m still waiting for the killer app; and we had ICOs, and we had NF Ts, and neither of those had been killer enough. So it’s like, “When’s it gonna hit?” Is it gonna be the Twitter replacement? Well, it seems like we’re going federated for that, not full blockchain for that. All those people trying to do it, but… I don’t know. I’m still waiting for real-world, “How’s this gonna make my life better?”

Quinn Slack: I think that a single person writing code can have a huge impact on the world… And I worry that we have lost that, or forgotten that. There were some cases where that’s been really clear, like with the creation of Bitcoin, and Ethereum… But what you see more of is people that can write code being pushed to go and build a software business, usually an enterprise software business around it… And in many ways, there have been successes, but I think there’s so many people out there that just through their code can have a huge impact on the world. And I don’t want to just have two data points from that, I want people to be able to build big businesses, and build products that tons and tons of people can use just on their own. And that happens today if you’re a writer.

If you’re a writer, you can write a book, you can write articles that have a huge impact on people. And when you do that, no one says “Hey, you should go start a publishing company.” But if you’re a coder, that’s what people tell you to. And I worry about the skill and ambition and enthusiasm we’re losing from those people, and also from all the people that say “Well, I don’t wanna get in the business. All I wanna do is code”, and knowing that that doesn’t seem possible, they don’t even get started.

[01:11:56.21] So if one impact we can have at Sourcegraph is making it so that a single coder can have a much bigger impact on the world, that would make me very happy. And certainly, I feel this as someone who loves to code, and who is now a CEO of an enterprise software business… There’s so many things I love about that too, but sometimes I think “How can that single person coding have even more distribution, even more impact? How can we celebrate that as something that someone can do for their whole life?”

Matthew Hodgson: …I don’t think you’d want me to. So the core team, when we set up New Vector as the spin-out in 2017 was 11 people. Since then we have scaled up to 41, I think, as of this morning. So we’ve taken on funding, as well as the revenue I mentioned earlier. We’ve taken on funding, both seed and from Status, the Ethereum decentralized communication project. They wanted to support us, because they like decentralization and wanted the project to survive.

And then more recently from VCs in London, specifically Notion, Dawn Capital and firstminute, who – I think we’re very lucky to have these investors, because they get the mission and the idea, as well as see the commercial possibility, in that we could become the Netscape of the Matrix ecosystem… And if Matrix takes off properly… It’s a bit of a long shot – as we said, it’s a bit of a slightly hamstrung moonshot, but we’re quite close to the moon at this point, and assuming we don’t overshoot or crash into it, hopefully we’ll have a beautiful landing… And that’s allowed us to scale up the team significantly.

For the foundation we don’t hire anybody; it’s just the directors basically looking after the governance and the IP and the evolution of the protocol… But for people paid to work full-time on Matrix, that’s what we do, is New Vector… And then lots of other contributors from other companies, and individual open source contributors. Probably 600-700 into the core project, and easily thousands into the wider projects which people happen to have built on top.

Brian Bondy: The way that ICOs work is basically – for an ICO funding, when I say 36 million, it’s not 36 million in BAT that we have; it’s 36 million that people used in Ethereum to buy BAT with. At that point, we’re not speculators, so most of this is converted to USD in fiat to run the company.

Paul Frazee: But I think they had a different concept of it. I tried it out, and whenever you went to a torrent, it actually sort of acted like a typical torrent client, as opposed to behaving like a website. I don’t know if they were quite tried to use it as a drop-in replacement to HTTP, which is what we started doing with Dat and that was one of the differences…

But back to Feross’ original question, the good news is that there’s a lot of projects out there right now that are attacking this problem. So for anybody that’s really into decentralizing the web, you should be happy to hear that. A lot of it has to do with blockchains. Beaker and Dat - we don’t use any blockchains; we’re really actually just seeing how far we can get with Dat… And there’s some technical similarities, because Dat has this append-only log behind every Dat archive, which retains all the history and it uses signatures on that log… But unlike almost every other blockchain, there’s no decentralized consensus, which is the major feature of a lot of the cryptocurrencies.

[16:23] But the Ethereum project has been really explicit about how they wanted to build a next iteration of the web with their tech; they even started, I believe, the Web 3 Foundation.

You know, I guess almost all of the blockchain-based solutions have payments at the core of what they’re trying to add to the web, which is cool… Payments are important; it’s important that people can make money off of their work, and it’s all sustainable… But the main difference, I feel like, between what we’re doing and what the cryptocurrency-based projects are doing is that by not using the blockchain, by not having decentralized consensus, we actually reduced costs even more. You can do this all with hardware that already exists, you don’t have to pay any money to transact on this network, and you end up getting a lot of the same kind of benefits, where you’re detached from any proprietary cloud, which is really what’s at the heart of all this.

So that would be probably the most significant difference between a lot of these projects - is there a cryptocurrency involved or not?

Brian Behlendorf: Exactly. So there’s Sawtooth, which is a different approach to building distributed ledgers… I can go into that if you’re interested. Another one called Iroha, which came from some of our Japanese members, which is tightly-coded C++ design for small systems, mobile clients, that sort of thing. Actually, an interesting project there with the bank of Cambodia, of all places… Then the fourth one is called Burrow, and this is actually an implementation of the Ethereum virtual machine, which is really exciting because there’s a lot of good academic research, as well as a lot of market validation going on around the Ethereum VM and a smart contract language called Solidity. So now being able to graph that on top of the other DLT’s is suddenly much more possible than it was before.

Chris Beams: Yeah, I’m glad you asked that, because definitely, if you’re looking into Bisq UI, you’ll see lots and lots of so-called altcoins, or just other tokens besides Bitcoin. For people who aren’t familiar with this, there’s something of the order of 1,000 of these tokens out there, coins, tokens that go by these different terms, and they can all be traded in more or less the same way that Bitcoin can. They’re all fundamentally similar technologies. So every trade in Bisq, one side of that trade is gonna be Bitcoin, but the other side of the trade might be fiat, it might be Ether (from the Ethereum world), or Monero, or one of these other altcoins.

Mikeal Rogers: Yes, yes. A lot of them aren’t web-based yet, but there are a few that are, and we’re getting much more web support all the time. BcoinJS is like a Bitcoin client library as well. I know that people are working on an Ethereum one… IPFF is working on some blockchain stuff that will work in Go and in the browser at some point.

I think the best way to look at blockchains is that if you wanna have a transaction log, and you wanna have a distributed transaction log, that’s the best way to build it. It’s not the best place to store large amounts of data (it’s actually really intense for that), but if you wanna just store a transaction log, 1) it’s a good, cryptographically secure way to do those transactions, and 2) kind of built into the way that you interact with the transaction log, it has everything that it needs to keep itself alive, and keep its network alive. That’s one of the harder things to engineer, and the thing that we have for, say, BitTorrent, but we don’t have for a lot of other use cases.

Anna Derbakova: And I think I made a very wise choice because I’ve received overwhelmingly positive feedback for my talk and how helpful it was in understanding blockchain. So I essentially started with Bitcoin… I said, “Hey, here’s Bitcoin, you’ve all heard about it. It’s built on blockchain, so let’s dissect that.” I told people about the importance of how blockchain stores its data in terms of hashing its data to produce a fingerprint, a particular block, how blocks are linked together… I went through all of that and talked a little bit about the importance of consensus on the network and what it’s for…

I think the introduction to blockchain in my talk was solid, people very much appreciated that. Then I talked about Hyperledger and that it’s a collaborative effort under the Linux Foundation, and how people can get involved, get on Hyperledger.org, check out the docs, get on Slack and learn about it… I tried to kind of put a plugin for Hyperledger and talk about differences of Hyperledger with let’s say Ethereum or Bitcoin, just to kind of summarize and give people an idea of whether Hyperledger - or Hyperledger Fabric, specifically; it’s what we are working on - is right for them. It may be, but maybe they don’t need what Hyperledger provides, and that’s okay. It just depends on what you’re looking for for your application.

I’m obviously not advocating that Hyperledger Fabric is right for everyone; it just depends on what you’re building. Then I showed how to write a simple app on Hyperledger Fabric, and I pointed people to my tutorial if they want to go and get started, and where to download the Docker images to their machine and how to do that, and how to write a simple app.

That was the synopsis of my talk. People have asked if I maybe can post some slides… I’ll try to figure out how to do that; I’m not sure if the conference has any…

Adam Stacoviak: Very cool stories. Then All Things Open was in Raleigh, North Carolina - that’s like the other OSCON, basically… So we hit both open source conferences, talked about Ethereum, talked about Blockchain, talked about Mozilla (a lot of fun stuff happening there), talked about animation in web design, and then more recently Node Interactive - a lot of fun conversations coming out at Node Interactive. Basically, that series was the future of Node, and that was sponsored by IBM.

Very unique opportunities for us to get out there in the community, make new friends, meet new people, and even the occasional hug.