Podcasts about paul not

Paul Frazee is the CTO of Bluesky. He previously worked on the Beaker browser and the peer-to-peer social media protocol Secure Scuttlebutt. Paul discusses how Bluesky and ATProto got started, scaling up a social media site, what makes ATProto decentralized, lessons ATProto learned from previous peer-to-peer projects, and the challenges of content moderation. Episode transcript available here. My Bluesky profile. -- Related Links Bluesky ATProtocol ATProto for distributed systems engineers Bluesky and the AT Protocol: Usable Decentralized Social Media Decentralized Identifiers (DIDs) ActivityPub Webfinger Beaker web browser Secure Scuttlebutt -- Transcript You can help correct transcripts on GitHub. [00:00:00] Jeremy: Today I am talking to Paul Frazee. He's the current CTO of bluesky, and he previously worked on other decentralized applications like Beaker and Secure Scuttlebutt. [00:00:15] Paul: Thanks for having me. What's bluesky [00:00:16] Jeremy: For people who aren't familiar with bluesky, what is it? [00:00:20] Paul: So bluesky is an open social network, simplest way to put it, designed in particular for high scale. That's kind of one of the big requirements that we had when we were moving into it. and it is really geared towards making sure that the operation of the social network is open amongst multiple different organizations. [00:00:44] So we're one of the operators, but other folks can come in, spin up the software, all the open source software, and essentially have a full node with a full copy of the network active users and have their users join into our network. And they all work functionally as one shared application. [00:01:03] Jeremy: So it, it sounds like it's similar to Twitter but instead of there being one Twitter, there could be any number and there is part of the underlying protocol that allows them to all connect to one another and act as one system. [00:01:21] Paul: That's exactly right. And there's a metaphor we use a lot, which is comparing to the web and search engines, which actually kind of matches really well. Like when you use Bing or Google, you're searching the same web. So on the AT protocol on bluesky, you use bluesky, you use some alternative client or application, all the same, what we're we call it, the atmosphere, all one shared network, [00:01:41] Jeremy: And more than just the, the client. 'cause I think sometimes when people think of a client, they'll think of, I use a web browser. I could use Chrome or Firefox, but ultimately I'm connecting to the same thing. But it's not just people running alternate clients, right? [00:01:57] Paul: Their own full backend to it. That's right. Yeah. Yeah. The anchoring point on that being the fire hose of data that runs the entire thing is open as well. And so you start up your own application, you spin up a service that just pipes into that fire hose and taps into all the activity. History of AT Protocol [00:02:18] Jeremy: Talking about this underlying protocol maybe we could start where this all began so people get some context for where this all came from. [00:02:28] Paul: For sure. All right, so let's wind the clock back here in my brain. We started out 2022, right at the beginning of the year. We were formed as a, essentially a consulting company outside of Twitter with a contract with Twitter. And, uh, our goal was to build a protocol that could run, uh, Twitter, much like the way that we just described, which set us up with a couple of pretty specific requirements. [00:02:55] For one, we had to make sure that it could scale. And so that ended up being a really important first requirement. and we wanted to make sure that there was a strong kind of guarantees that the network doesn't ever get captured by any one operator. The idea was that Twitter would become the first, uh, adopter of the technology. [00:03:19] Other applications, other services would begin to take advantage of it and users would be able to smoothly migrate their accounts in between one or the other at any time. Um, and it's really, really anchored in a particular goal of just deconstructing monopolies. Getting rid of those moats that make it so that there's a kind of a lack of competition, uh, between these things. [00:03:44] And making sure that, if there was some kind of reason that you decided you're just not happy with what direction this service has been going, you move over to another one. You're still in touch with all the folks you were in touch with before. You don't lose your data. You don't lose your, your your follows. Those were the kind of initial requirements that we set out with. The team by and large came from, the decentralized web, movement, which is actually a pretty, large community that's been around since, I wanna say around 2012 is when we first kind of started to form. It got really made more specifically into a community somewhere around 2015 or 16, I wanna say. [00:04:23] When the internet archives started to host conferences for us. And so that gave us kind of a meeting point where all started to meet up there's kind of three schools of thought within that movement. There was the blockchain community, the, federation community, and the peer-to-peer community. [00:04:43] And so blockchain, you don't need to explain that one. You got Federation, which was largely ActivityPub Mastodon. And then peer-to-peer was IPFS, DAT protocol, um, secure scuttlebutt. But, those kinds of BitTorrent style of technologies really they were all kind of inspired by that. [00:05:02] So these three different kind of sub communities we're all working, independently on different ways to attack how to make these open applications. How do you get something that's a high scale web application without one corporation being the only operator? When this team came together in 2022, we largely sourced from the peer-to-peer group of the decentralized community. Scaling limitations of peer-to-peer [00:05:30] Paul: Personally, I've been working in the space and on those kinds of technologies for about 10 years at that stage. And, the other folks that were in there, you know, 5-10 each respectively. So we all had a fair amount of time working on that. And we had really kind of hit some of the limitations of doing things entirely using client devices. We were running into challenges about reliability of connections. Punching holes to the individual device is very hard. Synchronizing keys between the devices is very hard. Maintaining strong availability of the data because people's devices are going off and on, things like that. Even when you're using the kind of BitTorrent style of shared distribution, that becomes a challenge. [00:06:15] But probably the worst challenge was quite simply scale. You need to be able to create aggregations of a lot of behavior even when you're trying to model your application as largely peer wise interactions like messaging. You might need an aggregation of accounts that even exist, how do you do notifications reliably? [00:06:37] Things like that. Really challenging. And what I was starting to say to myself by the end of that kind of pure peer-to-peer stent was that it can't be rocket science to do a comment section. You know, like at some point you just ask yourself like, how, how hard are we willing to work to, to make these ideas work? [00:06:56] But, there were some pretty good pieces of tech that did come out of the peer-to-peer world. A lot of it had to do with what I might call a cryptographic structure. things like Merkel trees and advances within Merkel Trees. Ways to take data sets and reduce them down to hashes so that you can then create nice signatures and have signed data sets at rest at larger scales. [00:07:22] And so our basic thought was, well, all right, we got some pretty good tech out of this, but let's drop that requirement that it all run off of devices. And let's get some servers in there. And instead think of the entire network as a peer-to-peer mesh of servers. That's gonna solve your scale problem. [00:07:38] 'cause you can throw big databases at it. It's gonna solve your availability problems, it's gonna solve your device sync problems. But you get a lot of the same properties of being able to move data sets between services. Much like you could move them between devices in the peer-to-peer network without losing their identifiers because you're doing this in direction of, cryptographic identifiers to the current host. [00:08:02] That's what peer-to-peer is always doing. You're taking like a public key or hash and then you're asking the network, Hey, who has this? Well, if you just move that into the server, you get the same thing, that dynamic resolution of who's your active host. So you're getting that portability that we wanted real bad. [00:08:17] And then you're also getting that kind of in meshing of the different services where each of them is producing these data sets that they can sink from each other. So take peer-to-peer and apply it to the server stack. And that was our kind of initial thought of like, Hey, you know what? This might work. [00:08:31] This might solve the problems that we have. And a lot of the design fell out from that basic mentality. Crytographic identifiers and domain names [00:08:37] Jeremy: When you talk about these cryptographic identifiers, is the idea that anybody could have data about a person, like a message or a comment, and that could be hosted different places, but you would still know which person that originally came from. Is that, is that the goal there? [00:08:57] Paul: That's exactly it. Yeah. Yeah. You wanna create identification that supersedes servers, right? So when you think about like, if I'm using Twitter and I wanna know what your posts are, I go to twitter.com/jeremy, right? I'm asking Twitter and your ID is consequently always bound to Twitter. You're always kind of a second class identifier. [00:09:21] We wanted to boost up the user identifier to be kind of a thing freestanding on its own. I wanna just know what Jeremy's posts are. And then once you get into the technical system it'll be designed to figure out, okay, who knows that, who can answer that for you? And we use cryptographic identifiers internally. [00:09:41] So like all the data sets use these kind of long URLs to identify things. But in the application, the user facing part, we used domain names for people. Which I think gives the picture of how this all operates. It really moves the user accounts up into a free standing first class identifier within the system. [00:10:04] And then consequently, any application, whatever application you're using, it's really about whatever data is getting put into your account. And then that just exchanges between any application that anybody else is using. [00:10:14] Jeremy: So in this case, it sounds like the identifier is some long string that, I'm not sure if it's necessarily human readable or not. You're shaking your head no. [00:10:25] Paul: No. [00:10:26] Jeremy: But if you have that string, you know it's for a specific person. And since it's not really human readable, what you do is you put a layer on top of it which in this case is a domain that somebody can use to look up and find the identifier. [00:10:45] Paul: Yeah, yeah, yeah. So we just use DNS. Put a TXT record in there, map into that long string, or you could do a .well-known file on a web server if that's more convenient for you. And then the ID that's behind that, the non-human readable one, those are called DIDs which is actually a W3C spec. Those then map to a kind of a certificate. What you call a DID document that kind of confirms the binding by declaring what that domain name should be. So you get this bi-directional binding. And then that certificate also includes signing keys and active servers. So you pull down that certificate and that's how the discovery of the active server happens is through the DID system. What's stored on a PDS [00:11:29] Jeremy: So when you refer to an active server what is that server and what is that server storing? [00:11:35] Paul: It's kinda like a web server, but instead of hosting HTML, it's hosting a bunch of JSON records. Every user has their own document store of JSON documents. It's bucketed into collections. Whenever you're looking up somebody on the network you're gonna get access to that repository of data, jump into a collection. [00:11:58] This collection is their post collection. Get the rkey (Record Key), and then you're pulling out JSON at the end of it, which is just a structured piece of stuff saying here's the CreatedAt, here's the text, here's the type, things like that. One way you could look at the whole system is it's a giant, giant database network. Servers can change, signing keys change, but not DID [00:12:18] Jeremy: So if someone's going to look up someone's identifier, let's say they have the user's domain they have to go to some source, right? To find the user's data. You've mentioned, I think before, the idea that this is decentralized and by default I would, I would picture some kind of centralized resource where I send somebody a domain and then they give me back the identifier and the links to the servers. [00:12:46] So, so how does that work in practice where it actually can be decentralized? [00:12:51] Paul: I mentioned that your DID that non-human readable identifier, and that has that certificate attached to it that lists servers and signing keys and things like that. [00:13:00] So you're just gonna look up inside that DID document what that server is your data repository host. And then you contact that guy and say, all right, I'm told you're hosting this thing. Here's the person I'm looking for, hand over the hand over the data. It's really, you know, pretty straightforward. [00:13:18] The way that gets decentralized is by then to the fact that I could swap out that active server that's in my certificate and probably wanna rotate the signing keys 'cause I've just changed the, you know. I don't want to keep using the same signing keys as I was using previously because I just changed the authority. [00:13:36] So that's the migration change, change the hosting server, change out the signing keys. Somebody that's looking for me now, they're gonna load up my document, my DID document. They're gonna say, okay, new server, new keys. Pull down the data. Looks good, right? Matches up with the DID doc. [00:13:50] So that's how you get that level of portability. But when those changes happen, the DID doesn't change, right? The DID document changes. So there's the level of indirection there and that's pretty important because if you don't have a persistent identifier whenever you're trying to change out servers, all those backlinks are gonna break. [00:14:09] That's the kind of stuff that stops you from being able to do clean migrations on things like web-based services. the only real option is to go out and ask everybody to update their data. And when you're talking about like interactions on the social network, like people replying to each other, there's no chance, right? [00:14:25] Every time somebody moves you're gonna go back and modify all those records. You don't even control all the records from the top down 'cause they're hosted all over the web. So it's just, you can't do it. Generally we call this account portability, that you're kinda like phone number portability that you can change your host, but, so that part's portable, but the ID stays the same. [00:14:45] And keeping that ID the same is the real key to making sure that this can happen without breaking the whole system. [00:14:52] Jeremy: And so it, it sounds like there's the decentralized id, then there's the decentralized ID document that's associated with that points you to where the actual location of your, your data, your posts, your pictures and whatnot. but then you also mentioned that they could change servers. [00:15:13] So let's say somebody changes where their data is, is stored, that would change the servers, I guess, in their document. But [00:15:23] then how do all of these systems. Know okay. I need to change all these references to your old server, to these new servers, [00:15:32] Paul: Yeah. Well, the good news is that you only have to, you, you got the public data set of all the user's activity, and then you have like internal caches of where the current server is. You just gotta update those internal caches when you're trying to contact their server. Um, so it's actually a pretty minimal thing to just like update like, oh, they moved, just start talking to update my, my table, my Redis, that's holding onto that kind of temporary information, put it on ttl, that sort of thing. Most communication won't be between servers, it will be from event streams [00:16:01] Paul: And, honestly, in practice, a fair amount of the system for scalability reasons doesn't necessarily work by servers directly contacting each other. It's actually a little bit more like how, I told you before, I'm gonna use this metaphor a lot, the search engines with the web, right? What we do is we actually end up crawling the repositories that are out in the world and funneling them into event streams like a Kafka. And that allows the entire system to act like a data processing pipeline where you're just tapping into these event streams and then pushing those logs into databases that produce these large scale aggregations. [00:16:47] So a lot of the application behavior ends up working off of these event logs. If I reply to somebody, for instance, I don't necessarily, it's not, my server has to like talk to your server and say, Hey, I'm replying to you. What I do is I just publish a reply in my repository that gets shot out into the event logs, and then these aggregators pick up that the reply got created and just update their database with it. [00:17:11] So it's not that our hosting servers are constantly having to send messages with each other, you actually use these aggregators to pull together the picture of what's happening on the network. [00:17:22] Jeremy: Okay, so like you were saying, it's an event stream model where everybody publishes the events the things that they're doing, whether that's making a new post, making a reply, that's all being posted to this event stream. And then everybody who provides, I'm not sure if instances is the right term, but an implementation of the atmosphere protocol (Authenticated Transfer protocol). [00:17:53] They are listening for all those changes and they don't necessarily have to know that you moved servers because they're just listening for the events and you still have the same identifier. [00:18:10] Paul: Generally speaking. Yeah. 'cause like if you're listening to one of these event streams what you end up looking for is just the signature on it and making sure that the signature matches up. Because you're not actually having to talk to their live server. You're just listening to this relay that's doing this aggregation for you. [00:18:27] But I think actually to kind of give a little more clarity to what you're talking about, it might be a good idea to refocus how we're talking about the system here. I mentioned before that our goal was to make a high scale system, right? We need to handle a lot of data. If you're thinking about this in the way that Mastodon does it, the ActivityPub model, that's actually gonna give you the wrong intuition. Designing the protocol to match distributed systems practices (Event sourcing / Stream processing) [00:18:45] Paul: 'cause we chose a dramatically different system. What we did instead was we picked up, essentially the same practices you're gonna use for a data center, a high scale application data center, and said, all right, how do you tend to build these sorts of things? Well, what you're gonna do is you're gonna have, multiple different services running different purposes. [00:19:04] It gets pretty close to a microservices approach. You're gonna have a set of databases, and then you're going to, generally speaking for high scale, you're gonna have some kind of a kafka, some kind of a event log that you are tossing changes about the state of these databases into. And then you have a bunch of secondary systems that are tapping into the event log and processing that into, the large scale, databases like your search index, your, nice postgres of user profiles. [00:19:35] And that makes sure that you can get each of these different systems to perform really well at their particular task, and then you can detach them in their design. for instance, your primary storage can be just a key value store that scales horizontally. And then on the event log, you, you're using a Kafka that's designed to handle. [00:19:58] Particular semantics of making sure that the messages don't get dropped, that they come through at a particular throughput. And then you're using, for us, we're using like ScyllaDB for the big scale indexes that scales horizontally really well. So it's just different kind of profiles for different pieces. [00:20:13] If you read Martin Kleppman's book, data Intensive applications I think it's called or yeah. A lot of it gets captured there. He talks a lot about this kind of thing and it's sometimes called a kappa architecture is one way this is described, event sourcing is a similar term for it as well. [00:20:30] Stream processing. That's pretty standard practices for how you would build a traditional high scale service. so if you take, take this, this kind of microservice architecture and essentially say, okay, now imagine that each of the services that are a part of your data center could be hosted by anybody, not just within our data center, but outside of our data center as well and should be able to all work together. [00:20:57] Basically how the AT Proto is designed. We were talking about the data repository hosts. Those are just the primary data stores that they hold onto the user keys and they hold onto those JSON records. And then we have another service category we call Relay that just crawls those data repositories and sucks that in that fire hose of data we were talking about that event log. App views pull data from relay and produces indexes and threads [00:21:21] Paul: And then we have what we call app views that sit there and tail the index and tail the log, excuse me, and produce indexes off of it, they're listening to those events and then like, making threads like okay, that guy posted, that guy replied, that guy replied. [00:21:37] That's a thread. They assemble it into that form. So when you're running an application, you're talking to the AppView to read the network, and you're talking to the hosts to write to the network, and each of these different pieces sync up together in this open mesh. So we really took a traditional sort of data center model and just turned it inside out where each piece is a part of the protocol and communicate it with each other and therefore anybody can join into that mesh. [00:22:07] Jeremy: And to just make sure I am tracking the data repository is the data about the user. So it has your decentralized identifier, it has your replies, your posts, And then you have a relay, which is, its responsibility, is to somehow find all of those data repositories and collect them as they happen so that it can publish them to some kind of event stream. [00:22:41] And then you have the AppView which it's receiving messages from the relay as they happen, and then it can have its own store and index that for search. It can collect them in a way so that it can present them onto a UI. That's sort of thing that's the user facing part I suppose. [00:23:00] Paul: Yeah, that's exactly it. And again, it's, it's actually quite similar to how the web works. If you combine together the relay and the app view, you got all these different, you know, the web works where you got all these different websites, they're hosting their stuff, and then the search engine is going around, aggregating all that data and turning it into a search experience. [00:23:19] Totally the same model. It's just being applied to, more varieties of data, like structured data, like posts and, and replies, follows, likes, all that kinda stuff. And then instead of producing a search application at the end. I mean, it does that too, but it also produces a, uh, you know, timelines and threads and, um, people's profiles and stuff like that. [00:23:41] So it's actually a pretty bog standard way of doing, that's one of the models that we've seen work for large scale decentralized systems. And so we're just transposing it onto something that kind of is more focused towards social applications [00:23:58] Jeremy: So I think I'm tracking that the data repository itself, since it has your decentralized identifier and because the data is cryptographically signed, you know, it's from a specific user. I think the part that I am still not quite sure about is the relays. I, I understand if you run all the data repositories, you know where they are, so you know how to collect the data from them. [00:24:22] But if someone's running another system outside of your organization, how do they find, your data repositories? Or do they have to connect to your relay? What's the intention for that? Data hosts request relays to pull their data [00:24:35] Paul: That logic runs, again, really similar to how search engines find out about websites. So there is actually a way for, one of these, data hosts to contact Relay and say, Hey, I exist. You know, go ahead and get my stuff. And then it'll be up to the relay to decide like if they want it or not. [00:24:52] Right now, generally we're just like, yeah, you know, we, we want it. But as you can imagine, as the thing matures and gets to higher scale, there might be some trust kind of things to worry about, you know? So that's kind of the naive operation that currently exists. But over time as the network gets bigger and bigger, it'll probably involve some more traditional kind of spiraling behaviors because as more relays come into the system, each of these hosts, they're not gonna know who to talk to. Relays can bootstrap who they know about by talking to other relays [00:25:22] Paul: You're trying to start a new relay. What they're gonna do is they're going to discover all of the different users that exist in the system by looking at what data they have to start with. Probably involve a little bit of a manual feeding in at first, whenever I'm starting up a relay, like, okay, there's bluesky's relay. [00:25:39] Lemme just pull what they know. And then I go from there. And then anytime you discover a new user you don't have, you're like, oh, I wanna look them up. Pull them into the relay too. Right. So there's a, pretty straightforward, discovery process that you'll just have to bake into a relay to, to make sure you're calling as much the network as possible. ActivityPub federation vs AT Proto [00:25:57] Jeremy: And so I don't think we've defined the term federation, but maybe you could explain what that is and if that is what this is. [00:26:07] Paul: We are so unsure. [00:26:10] Jeremy: Okay. [00:26:11] Paul: Yeah. This has jammed is up pretty bad. Um, because I think everybody can, everybody pretty strongly agrees that ActivityPub is federation, right? and ActivityPub kind of models itself pretty similarly to email in a way, like the metaphors they use is that there's inboxes and outboxes and, and every ActivityPub server they're standing up the full vertical stack. [00:26:37] They set up, the primary hosting, the views of the data that's happening there. the interface for the application, all of it, pretty traditional, like close service, but then they're kind of using the perimeter. they're making that permeable by sending, exchanging, essentially mailing records to each other, right? [00:26:54] That's their kind of logic of how that works. And that's pretty much in line with, I think, what most people think of with Federation. Whereas what we're doing isn't like that we've cut, instead of having a bunch of vertical stacks communicating horizontally with each other, we kind of sliced in the other direction. [00:27:09] We sliced horizontally into, this microservices mesh and have all the different, like a total mix and match of different microservices between different operators. Is that federation? I don't know. Right. we tried to invent a term, didn't really work, you know, At the moment, we just kind of don't worry about it that much, see what happens, see what the world sort of has to say to us about it. [00:27:36] and beyond that, I don't know. [00:27:42] Jeremy: I think people probably are thinking of something like, say, a Mastodon instance when you're, when you're talking about everything being included, The webpage where you view the posts, the Postgres database that's keeping the messages. [00:28:00] And that same instance it's responsible for basically everything. [00:28:06] Paul: mm-Hmm [00:28:06] Jeremy: And I believe what you're saying is that the difference with, the authenticated transfer protocol, is that the [00:28:15] Paul: AT Protocol, Yep. [00:28:17] Jeremy: And the difference there is that you've, at the protocol level, you've split it up into the data itself, which can be validated completely separately from other parts of the system. [00:28:31] You could have the JSON files on your hard drive and somebody else can have that same JSON file and they would know that who the user is and that these are real things that user posted. That's like a separate part. And then the relay component that looks for all these different repositories that has people's data, that can also be its own independent thing where its job is just to output events. [00:29:04] And that can exist just by itself. It doesn't need the application part, the, the user facing part, it can just be this event stream on itself. and that's the part where it sounds like you can make decisions on who to, um, collect data from. I guess you have to agree that somebody can connect to you and get the users from your data repositories. [00:29:32] And likewise, other people that run relays, they also have to agree to let you pull the users from theirs. [00:29:38] Paul: Yeah, that's right. Yeah. [00:29:41] Jeremy: And so I think the Mastodon example makes sense. And, but I wonder if the underlying ActivityPub protocol forces you to use it in that way, in like a whole full application that talks to another full application. [00:29:55] Or is it more like that's just how people tend to use it and it's not necessarily a characteristic of the protocol. [00:30:02] Paul: Yeah, that's a good question actually. so, you know, generally what I would say is pretty core to the protocol is the expectations about how the services interact with each other. So the mailbox metaphor that's used in ActivityPub, that design, if I reply to you, I'll update my, local database with what I did, and then I'll send a message over to your server saying, Hey, by the way, add this reply. [00:30:34] I did this. And that's how they find out about things. That's how they find out about activity outside of their network. that's the part that as long as you're doing ActivityPub, I suspect you're gonna see reliably happening. That's that, I can say for sure that's a pretty tight requirement. [00:30:50] That's ActivityPub. If you wanted to split it up the way we're talking about, you could, I don't know, I don't know if you necessarily would want to. Because I don't know. That's actually, I think I'd have to dig into their stack a little bit more to see how meaningful that would be. I do know that there's some talk of introducing a similar kind of an aggregation method into the ActivityPub world which I believe they're also calling a relay and to make things even more complicated. [00:31:23] And NOSTR has a concept of a relay. So these are three different protocols that are using this term. I think you could do essentially what a search engine does on any of these things. You could go crawling around for the data, pull them into a fire hose, and then, tap into that aggregation to produce, bigger views of the network. [00:31:41] So that principle can certainly apply anywhere. AT Protocol, I think it's a little bit, we, we focused in so hard from that on that from the get go, we focus really hard on making sure that this, the data is, signed at rest. That's why it's called the authenticated transfer protocol. And that's a nice advantage to have when you're running a relay like this because it means that you don't have to trust the relay. [00:32:08] Like generally speaking, when I look at results from Google, you know, I'm trusting pretty well that they're accurately reflecting what's on the website, which is fine. You know, there's, that's not actually a huge risk or anything. But whenever you're trying to build entire applications and you're using somebody else's relay, you could really run into things where they say like, oh, you know what Paul tweeted the other day, you know, I hate dogs. [00:32:28] They're like, no, I didn't. That's a lie, right? You just sneak in Little lies like that over a while, it becomes a problem. So having the signatures on the data is pretty important. You know, if you're gonna be trying to get people to cooperate, uh, you gotta manage the trust model. I know that ActivityPub does have mechanisms for signed records. Issuers with ActivityPub identifiers [00:32:44] Paul: I don't know how deep they go if they could fully replace that, that utility. and then Mastodon ActivityPub, they also use a different identifier system that they're actually taking a look at DIDs um, right now, I don't know what's gonna happen there. We're, we're totally on board to, you know, give any kind of insight that we got working on 'em. [00:33:06] But at, at the moment, they use I think it's WebFinger based identifiers they look like emails. So you got host names in there and those identifiers are being used in the data records. So you don't get that continuous identifier. They actually do have to do that hey, I moved update your records sort of thing. [00:33:28] And that causes it to, I mean, it works like decently well, but not as well as it could. They got us to the point where it moves your profile over and you update all the folks that were following you so they can update their follow records, but your posts, they're not coming right, because that's too far into that mesh of interlinking records. [00:33:48] There's just no chance. So that's kind of the upper limit on that, it's a different set of choices and trade-offs. You're always kind of asking like, how important is the migration? Does that work out? Anyway, now I'm just kind of digging into differences between the two here. Issues with an identifier that changes and updating old records [00:34:07] Jeremy: So you were saying that with ActivityPub, all of the instances need to be notified that you've changed your identifier but then all of the messages that they had already received. They don't point to the new identifier somehow. [00:34:24] Paul: Yeah. You run into basically just the practicalities of actual engineering with that is what happens, right? Because if you imagine you got a multimillion user social network. They got all their posts. Maybe the user has like, let's say a thousand posts and 10,000 likes. And that, activity can range back three years. [00:34:48] Let's say they changed their identifier, and now you need to change the identifier of all those records. If you're in a traditional system that's already a tall order, you're going back and rewriting a ton of indexes, Anytime somebody replied to you, they have these links to your posts, they're now, you've gotta update the identifiers on all of those things. [00:35:11] You could end up with a pretty significant explosion of rewrites that would have to occur. Now that's, that's tough. If you're in a centralized model. If you're in a decentralized one, it's pretty much impossible because you're now, when you notify all the other servers like, Hey, this, this changed. How successful are all of them at actually updating that, that those, those pointers, it's a good chance that there's things are gonna fall out of correctness. that's just a reality of it. And if, so, if you've got a, if you've got a mutable identifier, you're in trouble for migrations. So the DID is meant to keep it permanent and that ends up being the anchoring point. If you lose control of your DID well, that's it. Managing signing keys by server, paper key reset [00:35:52] Paul: Your, your account's done. We took some pretty traditional approaches to that, uh, where the signing keys get managed by your hosting server instead of like trying to, this may seem like really obvious, but if you're from the decentralization community, we spend a lot of time with blockchains, like, Hey, how do we have the users hold onto their keys? [00:36:15] You know, and the tooling on that is getting better for what it's worth. We're starting to see a lot better key pair management in like Apple's ecosystem and Google's ecosystem, but it's still in the range of like, nah, people lose their keys, you know? So having the servers manage those is important. [00:36:33] Then we have ways of exporting paper keys so that you could kind of adversarially migrate if you wanted to. That was in the early spec we wanted to make sure that this portability idea works, that you can always migrate your accounts so you can export a paper key that can override. [00:36:48] And that was how we figured that out. Like, okay, yeah, we don't have to have everything getting signed by keys that are on the user's devices. We just need these master backup keys that can say, you know what? I'm done with that host. No matter what they say, I'm overriding what they, what they think. and that's how we squared that one. [00:37:06] Jeremy: So it seems like one of the big differences with account migration is that with ActivityPub, when you move to another instance, you have to actually change your identifier. [00:37:20] And with the AT protocol you're actually not allowed to ever change that identifier. And maybe what you're changing is just you have say, some kind of a lookup, like you were saying, you could use a domain name to look that up, get a reference to your decentralized identifier, but your decentralized identifier it can never change. [00:37:47] Paul: It, it, it can't change. Yeah. And it shouldn't need to, you know what I mean? It's really a total disaster kind of situation if that happens. So, you know that it's designed to make sure that doesn't happen in the applications. We use these domain name handles to, to identify folks. And you can change those anytime you want because that's really just a user facing thing. [00:38:09] You know, then in practice what you see pretty often is that you may, if you change hosts, if you're using, we, we give some domains to folks, you know, 'cause like not everybody has their own domain. A lot of people do actually, to our surprise, people actually kind of enjoy doing that. But, a lot of folks are just using like paul.bsky.social as their handle. [00:38:29] And so if you migrated off of that, you probably lose that. Like your, so your handle's gonna change, but you're not losing the followers and stuff. 'cause the internal system isn't using paul.bsky.social, it's using that DID and that DID stays the same. Benefits of domain names, trust signal [00:38:42] Jeremy: Yeah. I thought that was interesting about using the domain names, because when you like you have a lot of users, everybody's got their own sub-domain. You could have however many millions of users. Does that become, does that become an issue at some point? [00:39:00] Paul: Well, it's a funny thing. I mean like the number of users, like that's not really a problem 'cause you run into the same kind of namespace crowding problem that any service is gonna have, right? Like if you just take the subdomain part of it, like the name Paul, like yeah, only, you only get to have one paul.bsky.social. [00:39:15] so that part of like, in terms of the number of users, that part's fine I guess. Uh, as fine as ever. where gets more interesting, of course is like, really kind of around the usability questions. For one, it's, it's not exactly the prettiest to always have that B sky.social in there. If we, if we thought we, if we had some kind of solution to that, we would use it. [00:39:35] But like the reality is that, you know, now we're, we've committed to the domain name approach and some folks, you know, they kind of like, ah, that's a little bit ugly. And we're like, yeah that's life. I guess the plus side though is that you can actually use like TLD the domain. It's like on pfrazee.com. [00:39:53] that starts to get more fun. it can actually act as a pretty good trust signal in certain scenarios. for instance, well-known domain names like nytimes.com, strong authentication right there, we don't even need a blue check for it. Uh, similarly the .gov, domain name space is tightly regulated. [00:40:14] So you actually get a really strong signal out of that. Senator Wyden is one of our users and so he's, I think it's wyden.senate.gov and same thing, strong, you know, strong identity signal right there. So that's actually a really nice upside. So that's like positives, negatives. [00:40:32] That trust signal only works so far. If somebody were to make pfrazee.net, then that can be a bit confusing. People may not be paying attention to .com vs .net, so it's not, I don't wanna give the impression that, ah, we've solved blue checks. It's a complicated and multifaceted situation, but, it's got some juice. [00:40:54] It's also kinda nice too, 'cause a lot of folks that are doing social, they're, they've got other stuff that they're trying to promote, you know? I'm pretty sure that, uh, nytimes would love it if you went to their website. And so tying it to their online presence so directly like that is a really nice kind of feature of it. [00:41:15] And tells a I think a good story about what we're trying to do with an open internet where, yeah, everybody has their space on the internet where they can do whatever they want on that. And that's, and then thethese social profiles, it's that presence showing up in a shared space. It's all kind of part of the same thing. [00:41:34] And that that feels like a nice kind of thing to be chasing, you know? And it also kind of speaks well to the naming worked out for us. We chose AT Protocol as a name. You know, we back acronymed our way into that one. 'cause it was a @ simple sort of thing. But like, it actually ended up really reflecting the biggest part of it, which is that it's about putting people's identities at the front, you know, and make kind of promoting everybody from a second class identity that's underneath Twitter or Facebook or something like that. [00:42:03] Up into. Nope, you're freestanding. You exist as a person independently. Which is what a lot of it's about. [00:42:12] Jeremy: Yeah, I think just in general, not necessarily just for bluesky, if people had more of an interest in getting their own domain, that would be pretty cool if people could tie more of that to something you basically own, right? [00:42:29] I mean, I guess you're leasing it from ICANN or whatever, but, [00:42:33] yeah, rather than everybody having an @Gmail, Outlook or whatever they could actually have something unique that they control more or less. [00:42:43] Paul: Yeah. And we, we actually have a little experimental service for registering domain names that we haven't integrated into the app yet because we just kind of wanted to test it out and, and kind of see what that appetite is for folks to register domain names way higher than you'd think we did that early on. [00:43:01] You know, it's funny when you're coming from decentralization is like an activist space, right? Like it's a group of people trying to change how this tech works. And sometimes you're trying to parse between what might come off as a fascination of technologists compared to what people actually care about. [00:43:20] And it varies, you know, the domain name thing to a surprising degree, folks really got into that. We saw people picking that up almost straight away. More so than certainly we ever predicted. And I think that's just 'cause I guess it speaks to something that people really get about the internet at this point. [00:43:39] Which is great. We did a couple of other things that are similar and we saw varied levels of adoption on them. We had similar kinds of user facing, opening up of the system with algorithms and with moderation. And those have both been pretty interesting in and of themselves. Custom feed algorithms [00:43:58] Paul: So with algorithms, what we did was we set that up so that anybody can create a new feed algorithm. And this was kind of one of the big things that you run into whenever you use the app. If you wanted to create a new kind of for you feed you can set up a service somewhere that's gonna tap into that fire hose, right? [00:44:18] And then all it needs to do is serve a JSON endpoint. That's just a list of URLs, but like, here's what should be in that feed. And then the bluesky app will pick that up and, and send that, hydrate in the content of the posts and show that to folks. I wanna say this is a bit of a misleading number and I'll explain why but I think there's about 35,000 of these feeds that have been created. [00:44:42] Now, the reason it's little misleading is that, I mean, not significantly, but it's not everybody went, sat down in their IDE and wrote these things. Essentially one of our users created, actually multiple of our users made little platforms for building these feeds, which is awesome. That's the kinda thing you wanna see because we haven't gotten around to it. [00:44:57] Our app still doesn't give you a way to make these things. But they did. And so lots of, you know, there it is. Cool. Like, one, one person made a kind of a combinatorial logic thing that's like visual almost like scratch, it's like, so if it has this hashtag and includes these users, but not those users, and you're kind of arranging these blocks and that constructs the feed and then probably publish it on your profile and then folks can use it, you know? [00:45:18] And um, so that has been I would say fairly successful. Except, we had one group of hackers do put in a real effort to make a replacement for you feed, like magic algorithmic feed kind of thing. And then they kind of kept up going for a while and then ended up giving up on it. Most of what we see are actually kind of weird niche use cases for feeds. [00:45:44] You get straightforward ones, like content oriented ones like a cat feed, politics feed, things like that. It's great, some of those are using ML detection, so like the cat feed is ML detection, so sometimes you get like a beaver in there, but most of the time it's a cat. And then we got some ones that are kind of a funny, like change in the dynamic of freshness. [00:46:05] So, uh, or or selection criteria, things that you wouldn't normally see. Um, but because they can do whatever they want, you know, they try it out. So like the quiet posters ended up being a pretty successful one. And that one just shows people you're following that don't post that often when they do just those folks. [00:46:21] It ended up being, I use that one all the time because yeah, like they get lost in the noise. So it's like a way to keep up with them. Custom moderation and labeling [00:46:29] Paul: The moderation one, that one's a a real interesting situation. What we did there essentially we wanted to make sure that the moderation system was capable of operating across different apps so that they can share their work, so to speak. [00:46:43] And so we created what we call labeling. And labeling is a metadata layer that exists over the network. Doesn't actually live in the normal data repositories. It uses a completely different synchronization because a lot of these labels are getting produced. It's just one of those things where the engineering characteristics of the labels is just too different from the rest of the system. [00:47:02] So we created a separate synchronization for this, and it's really kind of straightforward. It's, here's a URL and here's a string saying something like NSFW or Gore, or you know, whatever. then those get merged onto the records brought down by the client and then the client, you know, based on the user's preferences. [00:47:21] We'll put like warning screens up, hide it, stuff like that. So yeah, these label streams can then, you know, anybody that's running a moderation service can, you know, are publishing these things and so anybody can subscribe to 'em. And you get that kind of collaborative thing we're always trying to do with this. [00:47:34] And we had some users set up moderation services and so then as an end user you find it, it looks like a profile in the app and you subscribe to it and you configure it and off you go. That one has had probably the least amount of adoption throughout all of 'em. It's you know, moderation. [00:47:53] It's a sticky topic as you can imagine, challenging for folks. These moderation services, they do receive reports, you know, like whenever I'm reporting a post, I choose from all my moderation services who I wanna report this to. what has ended up happening more than being used to actually filter out like subjective stuff is more kind of like either algorithmic systems or what you might call informational. [00:48:21] So the algorithmic ones are like, one of the more popular ones is a thing that's looking for, posts from other social networks. Like this screenshot of a Reddit post or a Twitter post or a Facebook post. Because, which you're kinda like, why, you know, but the thing is some folks just get really tired of seeing screenshots from the other networks. [00:48:40] 'cause often it's like, look what this person said. Can you believe it? You know, it's like, ah. Okay, I've had enough. So one of our users aendra made a moderate service that just runs an ML that detects it, labels it, and then folks that are tired of it, they subscribe to it and they're just hide it, you know? [00:48:57] And so it's like a smart filter kind of thing that they're doing. you know, hypothetically you could do that for things like spiders, you know, like you've got arachniphobia, things like that. that's like a pretty straightforward, kind of automated way of doing it. Which takes a lot of the spice, you know, outta out of running moderation. [00:49:15] So that users have been like, yeah, yeah, okay, we can do that. [00:49:20] Those are user facing ways that we tried to surface the. Decentralized principle, right? And make take advantage of how this whole architecture can have this kind of a pluggability into it. Users can self host now [00:49:33] Paul: But then really at the end of the day, kind of the important core part of it is those pieces we were talking about before, the hosting, the relay and the, the applications themselves, having those be swappable in completely. so we tend to think of those as kind of ranges of infrastructure into application and then into particular client side stuff. [00:49:56] So a lot of folks right now, for instance, they're making their own clients to the application and those clients are able to do customizations, add features, things like that, as you might expect, [00:50:05] but most of them are not running their own backend. They're just using our backend. But at any point, it's right there for you. You know, you can go ahead and, and clone that software and start running the backend. If you wanted to run your own relay, you could go ahead and go all the way to that point. [00:50:19] You know, if you wanna do your own hosting, you can go ahead and do that. Um, it's all there. It's really just kind of a how much effort your project really wants to take. That's the kind of systemically important part. That's the part that makes sure that the overall mission of de monopolizing, social media online, that's where that really gets enforced. [00:50:40] Jeremy: And so someone has their own data repository with their own users and their own relay. they can request that your relay collect the information from their own data repositories. And that's, that's how these connections get made. [00:50:58] Paul: Yeah. And, and we have a fair number of those already. Fair number of, we call those the self hosters right? And we got I wanna say 75 self hoster going right now, which is, you know, love to see that be more, but it's, really the folks that if you're running a service, you probably would end up doing that. [00:51:20] But the folks that are just doing it for themselves, it's kind of the, the nerdiest of the nerds over there doing that. 'cause it doesn't end up showing itself in the, in the application at all. Right? It's totally abstracted away. So it, that, that one's really about like, uh, measure your paranoia kind of thing. [00:51:36] Or if you're just proud of the self-hosting or, or curious, you know, that that's kind of where that sits at the moment. AT Protocol beyond bluesky [00:51:42] Jeremy: We haven't really touched on the fact that there's this underlying protocol and everything we've been discussing has been centered around the bluesky social network where you run your own, instance of the relay and the data repositories with the purpose of talking to bluesky, but the protocol itself is also intended to be used for other uses, right? [00:52:06] Paul: Yeah. It's generic. The data types are set up in a way that anybody can build new data types in the system. there's a couple that have already begun, uh, front page, which is kind of a hacker news clone. There's Smoke Signals, which is a events app. There's Blue Cast, which is like a Twitter spaces, clubhouse kind of thing. [00:52:29] Those are the folks that are kind of willing to trudge into the bleeding edge and deal with some of the rough edges there for pretty I think, obvious reasons. A lot of our work gets focused in on making sure that the bluesky app and that use case is working correctly. [00:52:43] But we are starting to round the corner on getting to a full kind of how to make alternative applications state. If you go to the atproto.com, there's a kind of a introductory tutorial where that actually shows that whole stack and how it's done. So it's getting pretty close. There's a couple of still things that we wanna finish up. [00:53:04] jeremy so in a way you can almost think of it as having an eventually consistent data store on the network, You can make a traditional web application with a relational database, and the source of truth can actually be wherever that data repository is stored on the network. [00:53:24] paul Yeah, that's exactly, it is an eventually consistent system. That's exactly right. The source of truth is there, is their data repo. And that relational database that you might be using, I think the best way to think about it is like secondary indexes or computed indexes, right? They, reflect the source of truth. [00:53:43] Paul: This is getting kind of grandiose. I don't tend to poses in these terms, but it is almost like we're trying to have an OS layer at a protocol level. It's like having your own [00:53:54] Network wide database or network-wide file system, you know, these are the kind of facilities you expect out of a platform like an os And so the hope would be that this ends up getting that usage outside of just the initial social, uh, app, like what we're doing here. [00:54:12] If it doesn't end up working out that way, if this ends up, you know, good for the Twitter style use case, the other one's not so much, and that's fine too. You know, that's, that's our initial goal, but we, we wanted to make sure to build it in a way that like, yeah, there's evolve ability to, it keeps, it, keeps it, make sure that you're getting kinda the most utility you can out of it. Peer-to-peer and the difficulty of federated queries [00:54:30] Jeremy: Yeah, I can see some of the parallels to some of the decentralized stuff that I, I suppose people are still working on, but more on the peer-to-peer side, where the idea was that I can have a network host this data. but, and in this case it's a network of maybe larger providers where they could host a bunch of people's data versus just straight peer to peer where everybody has to have a piece of it. [00:54:57] And it seems like your angle there was really the scalability part. [00:55:02] Paul: It was the scalability part. And there's great work happening in peer-to-peer. There's a lot of advances on it that are still happening. I think really the limiter that you run into is running queries against aggregations of data. Because you can get the network, you know, BitTorrent sort of proved that you can do distributed open horizontal scaling of hosting. [00:55:29] You know, that basic idea of, hey, everybody's got a piece and you sync it from all these different places. We know you can do things like that. What nobody's been able to really get into a good place is running, queries across large data sets. In the model like that, there's been some research in what is, what's called federated queries, which is where you're sending a query to multiple different nodes and asking them to fulfill as much of it as they can and then collating the results back. But it didn't work that well. That's still kind of an open question and until that is in a place where it can like reliably work and at very large scales, you're just gonna need a big database somewhere that does give the properties that you need. You need these big indexes. And once we were pretty sure of that requirement, then from there you start asking, all right, what else about the system [00:56:29] Could we make easier if we just apply some more traditional techniques and merge that in with the peer-to-peer ideas? And so key hosting, that's an obvious one. You know, availability, let's just have a server. It's no big deal. But you're trying to, you're trying to make as much of them dumb as possible. [00:56:47] So that they have that easy replaceability. Moderation challenges [00:56:51] Jeremy: Earlier you were talking a a little bit about the moderation tools that people could build themselves. There was some process where people could label posts and then build their own software to determine what a feed should show per a person. [00:57:07] Paul: Mm-Hmm [00:57:07] Jeremy: But, but I think before that layer for the platform itself, there's a base level of moderation that has to happen. [00:57:19] Paul: yeah. [00:57:20] Jeremy: And I wonder if you could speak to, as the app has grown, how that's handled. [00:57:26] Paul: Yeah. the, you gotta take some requirements in moderation pretty seriously to start. And with decentralization. It sometimes that gets a little bit dropped. You need to have systems that can deal with questions about CSAM. So you got those big questions you gotta answer and then you got stuff that's more in the line of like, alright, what makes a good platform? [00:57:54] What kind of guarantees are we trying to give there? So just not legal concerns, but you know, good product experience concerns. That's something we're in the realm of like spam and and abusive behavior and things like that. And then you get into even more fine grain of like what is a person's subjective preference and how can they kind of make their thing better? [00:58:15] And so you get a kind of a telescoping level of concerns from the really big, the legal sort of concerns. And then the really small subjective preference kind of concerns. And that actually that telescoping maps really closely to the design of the system as well. Where the further you get up in the kind of the, in that legal concern territory, you're now in core infrastructure. [00:58:39] And then you go from infrastructure, which is the relay down into the application, which is kind of a platform and then down into the client. And that's where we're having those labelers apply. And each of them, as you kind of move closer to infrastructure, the importance of the decision gets bigger too. [00:58:56] So you're trying to do just legal concerns with the relay right? Stuff that you objectively can, everybody's in agreement like Yeah, yeah, yeah. You know, no bigs don't include that. The reason is that at the relay level, you're anybody that's using your relay, they depend on the decisions you're making, that sort of selection you're doing, any filtering you're doing, they don't get a choice after that. [00:59:19] So you wanna try to keep that focus really on legal concerns and doing that well. so that applications that are downstream of it can, can make their choices. The applications themselves, you know, somebody can run a parallel I guess you could call it like a parallel platform, so we got bluesky doing the microblogging use case, other people can make an application doing the microblogging use case. So there's, there's choice that users can easily switch, easily enough switch between, it's still a big choice. [00:59:50] So we're operating that in many ways. Like any other app nowadays might do it. You've got policies, you know, for what's acceptable on the network. you're still trying to keep that to be as, you know, objective as possible, make it fair, things like that. You want folks to trust your T&S team. Uh, but from the kind of systemic decentralization question, you get to be a little bit more opinionated. [01:00:13] Down all the way into the client with that labeling system where you can, you know, this is individuals turning on and off preferences. You can be as opinionated as you want on that letter. And that's how we have basically approached this. And in a lot of ways, it really just comes down to, in the day to day, you're the moderation, the volume of moderation tasks is huge. [01:00:40] You don't actually have high stakes moderation decisions most of the time. Most of 'em are you know pretty straightforward. Shouldn't have done that. That's gotta go. You get a couple every once in a while that are a little spicier or a policy that's a little spicier. And it probably feels pretty common to end users, but that just speaks to how much moderation challenges how the volume of reports and problems that come through. [01:01:12] And we don't wanna make it so that the system is seized up, trying to decentralize itself. You know, it needs to be able to operate day to day. What you wanna make is, you know, back pressure, you know, uh, checks on that power so that if an application or a platform does really start to go down the wrong direction on moderation, then people can have this credible exit. [01:01:36] This way of saying, you know what, that's a problem. We're moving from here. And somebody else can come in with different policies that better fit people's people's expectations about what should be done at, at these levels. So yeah, it's not about taking away authority, it's about checking authority, you know, kind of a checks and balances mentality. [01:01:56] Jeremy: And high level, 'cause you saying how there's such a high volume of, of things that you know what it is, you'd know you wanna remove it, but there's just so much of it. So is there, do you have automated tools to label these things? Do you have a team of moderators? Do they have to understand all the different languages that are coming through your network? [01:02:20] Yes, yes, yes and yes. Yeah. You use every tool at your disposal to, to stay on top of it. cause you're trying to move as fast as you can, folks. The problems showing up, you know, the slower you are to respond to it, the, the more irritating it is to folks. Likewise, if you make a, a missed call, if somebody misunderstands what's happening, which believe me, is sometimes just figuring out what the heck is going on is hard. [01:02:52] Paul: People's beefs definitely surface up to the moderation misunderstanding or wrong application. Moderators make mistakes so you're trying to maintain a pretty quick turnaround on this stuff. That's tough. And you, especially when to move fast on some really upsetting content that can make its way through, again, illegal stuff, for instance, but more videos, stuff like that, you know, it's a real problem. [01:03:20] So yeah, you're gotta be using some automated systems as well. Clamping down on bot rings and spam. You know, you can imagine that's gotten a lot harder thanks to LLMs just doing text analysis by dumb statistics of what they're talking about that doesn't even work anymore. [01:03:41] 'cause the, the LLMs are capable of producing consistently varied responses while still achieving the same goal of plugging a online betting site of some kind, you know? So we do use kind of dumb heuristic systems for when it works, but boy, that won't work for much longer. [01:04:03] And we've already got cases where it's, oh boy, so the moderation's in a dynamic place to say the least right now with, with LLMs coming in, it was tough before and

Anika and Liz beam down to Trill, don their finest red cloaks and hoods, and discuss the third episode of Star Trek: Discovery's season 5, "Janaal". Including... This is a perfectly fine episode, but it seems a shame to waste our limited time this season on something that is merely competent RIP Star Trek: Lower Decks Introducing the beta shift when fans are still under the impression that the alpha shift bridge crew should be the leads: brilliant trolling We have always been Wilson Cruz Appreciators, but we are appreciating him extra hard! We are concerned about Paul "Not to be a Rayner apologist, but I am definitely going to be a Rayner apologist." The Vulcan alt-right sure does endure!  Adira and Grey are cosplaying maturity (and that's okay)

I met the Yonder Oak Wood team back in March to discover how this landscape will be transformed for people and wildlife, and what designing a new wood involves. The vision is to attract plentiful wildlife with healthy habitat that offers refuge from weather extremes and fights climate change. The local community has been involved from the off - volunteer Sally Burton joins us to explain what she gets up to, how excited everyone is about the future and what volunteering means to her. We also hear of efforts to make the site more sustainable, from re-usable fences to tree guard trials, and I get my hands dirty planting a tree. Don't forget to rate us and subscribe! Learn more about the Woodland Trust at woodlandtrust.org.uk Transcript You are listening to Woodland Walks, a podcast for the Woodland Trust presented by Adam Shaw. We protect and plant trees for people, for wildlife. Adam: Well, today I'm off to, well, the wonderfully named Yonder Oak Wood. And although it's called a wood, it's not really a wood yet. This is a very exciting project, but it's in the very early stages of creation. It's near Exmouth in Devon. The Woodland Trust plans on planting, I think something like 13,000 trees there, creating a new environment for nature and wildlife to bounce back. Sounds a great place to go, I'm going to meet a few people there. First off, though, is my contact at the Woodland Trust today, Rachel Harries. Rachel: So this site is Yonder Oak Wood, it's not quite a wood yet, as you can see, but the Woodland Trust bought it in March last year with the aim of creating, creating a new wooded landscape here. So it's 54 hectares, we think it is the biggest woodland creation site that the Trust has done in the South West in in 20 years, so 54 hectares, that's equivalent to about 100 football pitches, and it sits on the sort of two sides of a hidden valley, just a couple of miles inland from the South Coast of Devon. So where we're stood, we can actually see out to the mouth of the Exe estuary, to Dawlish and and possibly to Torquay there as well. Adam: I I think you can just see the estuary over there can't you, just beyond that last bunch of trees is that right? Rachel: You absolutely can, yeah, you absolutely can. And actually the other day when I was here, I saw a white bird fly over that was an egret that was obviously based in the estuary, so really exciting. Adam: And why, now this site, I happen to know is, it it's quite important because of the anniversary and just explain to me, explain to me a little bit about that. Rachel: That's right. Last year was the 50th anniversary of the Woodland Trust and the first site that our founder Ken Watkins ever bought was in Devon. So it's really emblematic that we are now creating a new woodland, probably I think it's about 30 miles away as the crow flies from the Avon Valley Woods where we were started. But we're now creating a new woodland in the county of our birthplace, which is incredibly exciting, and we wanted to create something that would have meaning for local people and it would like, it would be tied into the local environment, so we did things like we looked at the name of the stream, we looked at old field names and we came up with a shortlist of names that we could then offer out to the local community and ask them which one, which one they wanted and what they wanted to call this new site. And one of the field names was Yonder Oak Park. And that's really quite special because as you look across the site, you can see all these incredible old oak trees over yonder, off in the distance. So I have to admit that was my favourite but we let the community choose and they voted for Yonder Oak Wood. Adam: Right well you're gonna take me on a little walk around here, so just explain to me a little bit about what we're gonna see. Rachel: OK. Well, we're starting here on a sloping field that has old oak trees dotted about the landscape. Some of these are a couple of hundred years old and there's one in particular which we can see just off in the distance, which is one of my, one of my favourites that is standing almost on on stilts. And the stilts are actually its roots that would have once been embedded in a Devon bank, which is a sort of a solid hedgerow that we find in Devon that has trees planted on the top and the hedgerow and the bank has been taken away. So the tree now kind of stands about a metre above the height that it would have once been. Adam: Which one, I can't tell which one that is? Rachel: So can you see there's two in that field over there, we'll walk past it so we can have another look at it. Adam: Yes, I see that, I see that. OK, maybe my eyesight's not very good. So and this goes, these are currently separate fields and there's what a field and then a hedgerow, another field, then another hedgerow, then the tree supposedly on stilts and beyond that what looks like a solar panel farm. So is this the, what will be the new woodland all the way up to the solar panels? Rachel: We've worked to design a mixture of of habitats here, so we have about 5 different fields where we're doing much more intensive planting and that's what people would kind of imagine that would grow into what people would imagine a woodland would look like, but then in some of these other fields, so the field that we're stood in and a couple of other fields that you can kind of see off in the distance there, we're going to do a mix of open space, glades and groves. We'll plant some more of these kind of trees that will be allowed to to thrive and to spread on their own, but we'll also plant a mixture of of scrub and shrubs, so that's more lower growing trees, things like blackthorn, hawthorn dogrose, spindle, just to create a really good mix of habitats for all the birds and insects and bats that we, you know, we know are going to thrive here. Adam: And you, you've arranged for us to meet a a couple of people, haven't you? Rachel: Yeah. So we're going to be walking around with Paul Allen, he's our site manager and we're going to meet Sally Burton, who is one of our volunteers here. Adam: The weather's been kind to us so far, but it is a little nippy so we shouldn't keep them waiting. So do you wanna lead on and we'll go meet them. Rachel: Yes, let's go. Adam: And I'm told there there was some sea shantying going on here, which strikes me as odd because we're not, we're not in the middle of the sea or anything. So what's the story behind that? Rachel: Well, we're not far from the sea. We can see, we can see the, we can see the sea here. But we were contacted by a a group of local acapella singers who were inspired by what we're doing here and had decided to take some modern folk songs and to rewrite them to to reference the wood. So they came out one weekend and they sang to our to all of our planters, but we also talked a little bit about sea shanties, which I like the idea of becoming tree shanties. So they took a traditional sea shanty and they changed the lyrics. So we now have a song all about Yonder Oak Wood that we could sing along to. Adam: Great. And that we're going to hear that now from from you. So here's Rachel with her tree shanty. Is that right? No? Rachel *laughs* I don't think so. Adam: Do you have a recording of it? Rachel: I we do have a recording of it actually, yes. Adam: You never know. I don't know. Maybe a couple of teas or beers later, I might persuade you to sing. Alright. Brilliant, Rachel. Thank you very much. Rachel: Thank you. That's great. So here's Paul. He's the site manager and he's going to take us on a little walk down through Yonder Oak Wood. Adam: Paul, thank you very much. Nice to see you. So you are the site manager. Paul: Hello there. I am. Yes, I'm responsible for turning these fields into a wild, wildlife rich area. Adam: OK. Well, go on. Let's lead on. We can have a chat about that. Brilliant. So yeah. So these are early days, Paul. I understand you you are responsible for designing the woodland. What does that actually involve? Paul: So really, I mean the the the first place you you start is is kind of kind of getting a sense of where the place is and what the place is and the the key bit here as we walk through it is you can see these big old oak trees and so we've based a lot of the design on that. So you can picture in the future lots more of these big old trees that will have lots of deadwood, lots of rot holes where birds can nest, and invertebrates burrow in. And the way we're kind of going to maintain it is we're we're going to put animals in and have low intensity grazing and then you kind of build in where the views are. Adam: I mean it must be really exciting because it can't be that often that you you get actually a green field or literally a greenfield site. But it's more or less bare. It's a plain piece of paper for you to design. That's quite, I mean, it's exciting, quite an honour, perhaps a little daunting? Paul: I've I've done probably 30 years of nature conservation and most of what you do is you take bits of habitat and you try and restore them, you try and protect them. You very rarely get a chance to actually create something brand spanking new. It is really phenomenally exciting for all of us, because if you think about it in the future, 100 years time, this place will be on maps. It will be on aerial photographs, you know so not only are we doing stuff that's great for wildlife and great for climate, we're effectively creating history as well, which is an awesome thing to be a part of. Adam: Yeah, so on the map it should say Yonder Oak Wood, brackets Paul Allen. *both laugh* Rachel's in the background going it's my wood, it's my wood. There might be a battle for the name. Paul: I'm I'm doing the design that says it from the sky it'll say Paul was here. *both laugh* Adam: Yes, yes very good, on Google Maps you can, you know, in 100 years time they'll go well how did those trees get planted in the shape of Paul? *laughs* So, OK, look, we're, we're, I've paused because we're at the we're at the top of the hill, almost. So what will happen around us? At the moment there are three or four trees in a line and not much else. So what will be here? Paul: So if you if you picture it in the future, what we'll have is we'll have a a, a a scattering of big old oak trees like we can see across the site and if you look over to our left, you can see an area that actually was the former quarry on the site. But if you look at it, you can see gorse that's currently in flower, even though we're in a freezing day at the beginning of March. And all of that is really good for wildlife. It's got lots of pollen and and nectar and lots of edge that birds and insects really like. And essentially what we're gonna get in the future is a combination of these big old oak trees and that lovely scrubby stuff that's great for wildlife. Adam: So here not too dense? Paul: Not too dense here no, not at all. Adam: So you get the view, you get a nice view and it's a mixed habitat. Paul: You, you, you, you get a view, it's it's very, we've we've constantly said we're creating a kind of a wooded landscape not a wood. Adam: Right. Well, we should carry on walking out, I have a tendency, just not to walk. I can see right over there some white poles which look like tree guards. Which does raise this issue I mean of how you're going to protect the trees because plastic tree guards have become quite controversial. Do you have a plan around that? Paul: Yeah, so we've got we've got, last year the the Woodland Trust decided that it would stop using the virgin plastic tree guards on its sites, which is actually a bit problematic because there aren't really any other types of tree guard that are commercially available at scale, so we're doing a combination of things here. The the main way is we're going to deer fence the site to stop the deer coming in and then we're also in some places we're trialling different types of tree tubes, so we're looking at one at the moment that bizarrely, has been made of sugar beet so it smells like golden syrup when you walk up to it, which is quite weird, and the ones you can see over there are actually recycled from another site. So we're, we're still, we're still using the tree guards that are effectively usable. Adam: Right. You talk about trying to protect the trees from deer. Which does raise the issue of other wildlife. I mean, clearly, we're gonna be hoping that wildlife get attracted into the area once this starts growing. At the moment though, have you have you seen much evidence of sort of new wildlife or any wildlife? Paul: It's still very early days yet. But we've seen lots of buzzards there's there's actually quite a lot of hornets nests in, in the existing oak trees. Adam: Is that a good thing? That sounds terrifying. Paul: *laughs* I I I personally I quite like it. Adam: You're pleased about that, OK. I think a lot of people always feel it takes generations and generations to plant trees. I know I have been at planting events where some young people have planted and said, oh, I think my children and my grandchildren might come to see this tree and then are surprised, actually, they come back to see their own tree and it grows quicker than they might expect. How quickly is this going to develop into anything recognisable as woodland? Paul: So I mean, with within 10 years, it will absolutely look like a woodland, although obviously still a young woodland and different tree species grow at different rates. So the silver birches and the rowans will actually be 6 foot high within two or three years potentially, whereas the the oak trees clearly will grow a lot slower. Adam: Wow, silver birch and rowan, 6 foot high in how long? Paul: Two or three years, if they if they take well. I mean it it it it varies depending on the soil type and all that sort of stuff, but they do grow very, very quickly. Adam: Blimey. And tell me a bit about how you got into all of this. I mean, I know you say you've been doing this a while. Paul: I started well I started off volunteering actually with the British Trust for Conservation Volunteers a long time ago, and I got known by the Norfolk Wildlife Trust and rather randomly, I was having a beer in a pub and they went, do you fancy a job, and I went, alright then. Adam: Very good. So you've learnt on the job about trees? Paul: I I reeducated a few, some time ago but yeah a lot of it was learned as I went along. Adam: I've been very insulting, you've you've probably got a PhD in trees or something. But I do like the idea of, I got my job from a pub, I think I think that's always, I remember a story, so I don't know if you remember a film critic called Barry Norman, he always used to say, I I remember him telling a story, there's a pub around the BBC called, I think it's the White, White Horse or something like that. And he went when he was unemployed, he used to sit there pretending he was writing scripts so that BBC producers would come in for a lunchtime beer, which they don't do anymore, but they used to and they would go, oh, Barry, yeah there's a job we have and he wasn't working at all, he was just trying to be in the pub around and that's how he got his work, so that's clearly not just media, it's it's the tree world as well. Paul: It's it's it's very much very very clearly, a lot harder now than it was, because at that point in time, I guess nature conservation really wasn't a career. Adam: Yeah. We've come across a locked fence, but Paul has a key, there we are. There we are. Into the next next field. Ah, right away. Here's a very different type of fence, and I presume this is to keep the deer out. So first of all, massive fence, is this to keep the deer out? Paul: This is to keep the deer out. Yes, absolutely. And what will happen where we're standing, the hedgerow will creep out into the fence and obviously the wood that we're planting inside will also start to hide the fence. So the fence over time will disappear apart from the gateways. Adam: So I mean, there's a good 7 odd foot here between the hedgerow and the fence. You're saying that that hedgerow will naturally grow another 7 foot? Paul: Yep. So what what what we've got in this hedgerow, actually it's it's it's quite specific to this area is we've got a lot of a lot of small leaved elm and we've also got a lot of blackthorn in it and both of those sucker. So as as we've taken the the the intensive farming off the land the the shrubs will just sucker out and gradually spread into the field. Adam: And look, and we're standing by the main gate and there's a huge tree trunk here, which is holding the post. And I can see the bark coming off. Now is that is that deer trying to get in there do you think? Paul: No, that that's actually that's just part of the process of actually creating the post. Adam: Ohh, that's just that's just me being an idiot. OK, I thought I was being a clever nature detective *laughs* Paul: I mean what one of the one of the key bits about this fence though, is that that the Woodland Trust is now focusing very heavily on sustainability with everything it does. The, the, the reduction in use of plastic is one of those key bits. But these are sweet chestnut posts, so they there's no chemical preservatives in them or anything like that, and they're kind of the the the main posts at the corners, if you like, of the fence. And then we're using a metal fence with metal posts and and the idea is that when the trees have grown up after 20 years and they're no longer a threat from the deer, we can take this and reuse it elsewhere, so we're constantly thinking about that sustainability stuff all the time. Adam: Right. So we're in this more protected field. Which I can see has been laid out actually. Is this for the planting scheme, little posts and sort of lines of rope? Paul: Yeah. So one of the issues with going plastic free is it becomes very difficult to actually see what you've planted. Because if you look at here it just still looks like a field but actually there's somewhere in the region of well around 2 to 3000 trees already in there. Adam: Oh gosh, I didn't realise that. So yes, with the plastic safe, plastic guards on a tree you see these white telescopes sticking up all over the field, so there's thousands of trees here, we just can't see them. Right and a a lot of that has been planted by volunteers? Paul: We've had somewhere in the region of 400-500 members of the public come over four days, so we've got a a set of volunteers who have who've have have they've been brilliant actually, they've come and they've helped kind of manage all the public and they've helped work with the schools, they've helped us set out where the trees are going, we couldn't have done it without them at all. And here is one of our volunteers now, here's Sally. Adam: Brilliant. Alright, well, let's go over and chat to Sally. So Sally. Sally Burton. Hello. So I've heard lots of lovely things about you. So just tell me you're a volunteer, which in this context means what? Sally: Hello. That's nice. All sorts of things. I've helped this in during February with the public planting days and with the school planting days, helped children dig holes, some of the children are too small to get the spade in the ground very easily. I've planted quite a lot of trees myself. Adam: And why why did you get involved? Sally: I'd been looking for a while to volunteer for an organisation that does things outdoors and something a bit physical and so when the Woodland Trust appeared in the village hall I just went up and said do you need volunteers and they said yes please so I signed up straight away. Adam: And I mean, what does it offer you? Why is it a fun thing to do? Sally: I enjoy working with the other people. The staff are great and the other volunteers have been great fun. In fact, I've reconnected with someone I knew a few years ago and she's been helping up here as well, so that's been great. I like being outside, I love being outdoors. I don't mind about the weather. I like doing physical things and it's it's great to see, to make a difference. Adam: So yeah, so what what sort of difference do you feel you're making then? Sally: Well contributing to turning this basically what looks like an empty field into a forest. That's really amazing. People have been very excited about it. Lots of local people came up and planted on the public open days. Everyone's looking forward to being able to come up here and experience it themselves and enjoy the trees and the views obviously the views across the estuary and out to sea are beautiful. And there are lots of birds already. It's a very beautiful place. Adam: And so how much of your time does it actually take up? Sally: Well, during February and the beginning of March, quite a lot, I've been coming up for days, getting here about 8:15 and going home about 4 o'clock. Adam: Right. So why is that, why is that the the busy period? Sally: Because that's when the tree planting has been going on. Adam: First time you've ever planted a tree? Sally: I've planted a couple on my allotment, but certainly the first time I've planted on such a scale. Adam: Right. Have you kept count, how many trees are you in? Sally: No. Well, on one of the public planting days, I'd finished registering people and I planted 25 I kept count of those and on Wednesday this week, a school was in and when they cleared off, I finished planting the trees in their little area. And I think there was about 30 there. I'm not sure I lost count after about 12. Adam: There should be scouts or sort of brownie badges, shouldn't there, I'm I'm 100 tree-er, you know. Very good. Fantastic. Well, look, thank you very much. I can't believe this is the the the the field in which you've planted. Sally: It is, you can't see many of the trees. Adam: I I can't see any of the trees, what do you mean many of them. Ohh a couple yes. Sally: Across there you can see some with leaves on those are sessile oaks which were planted a little while ago, and they show up. Adam: Any of those yours? Sally: Possibly *laughs* They show up because of the leaves. But over there, most of the area there is planted. Adam: OK, brilliant. You're talking about planting, Rachel has appeared over the hill. She's brandishing a erm Sally: A spade. Adam: A spade *laughs* I forgot the name. You can see how ill equipped I am to do this. I forgot the name of what she's, so I think she's tempting us to go plant so let's go off. Adam: *coughs* Sorry, I'm already having a heart attack from the idea of physical exercise, I haven't done anything yet. OK, so we we have a spade and this is a virgin bit of land, no, no trees planted yet? Sally: No trees in this section yet. Adam: So I get the honour of planting the first tree. Sally: The first one. Adam: So you're gonna talk me through this and I'm gonna. Sally: So the first job... Adam: Oh yes alright, I'm already jumping ahead of myself. Sally: The first job is to screef? To screef the area... Adam: What what is what is screefing? Sally: ...which is where you do this to kick away the grass with your shoe to make a square or an area to get rid of the grass, doesn't have to be too big, not much wider than the blade of the spade, put the spade in there, and then don't lift it yet come round that side and make a square on that side. Yeah, cut it down. Then on that side... Adam: I feel I've hit the... Sally: One of the pebbles. And then the final side and then you could probably lever out a lump of turf. Adam: Then I can lift it out. Sally: OK, here's a tree. And we need to make sure when it's in the hole, the soil covers up to just above the top of the the highest root. So if we test that, that's not deep enough, so need to go deeper. Adam: It's not deep enough. Overall, I'm not doing particularly well I have to say. Sally: Let's have a look. That's looking good there. Adam: You think that's all right? Sally: Yeah, that's OK. So the next job is to crumble the soil. Adam: With our hands? Sally: With our hands, back into the hole, loose bits first. Adam: They didn't say I was actually gonna get my hands dirty. Sally: *laughs* And then if you've got any clods that have got grass on them make sure they go in with the grass facing down. Adam: Ok do you know why? Sally: So that the grass will die and then it won't be in competition with the tree as the grass uses a lot of the water. Adam: It's a bit leaning a bit, isn't it? Sally: It is a bit, let's push some more soil in. Adam: You see, it's fine now, in 20 years time, someone will come and go, who the hell planted that tree, it's at 45 degrees! Sally: Then the last job is you stand up. Adam: Yeah, stand up. Sally: And use your heel to press the soil down to push out all the gaps so that it doesn't dry out if it's sunny. Adam: And how compact, we don't want to make it too compact. Sally: Quite firm, quite firm. Adam: Yeah? Do you know what I don't, I feel that's leaning, that's no good. Sally: Don't worry, it'll straighten itself up. And the final thing is you do the tug test. Where you just get hold of it and just pull it gently. And if it stays where it is, then it's planted properly. Adam: I name this tree, well and truly planted. Sally: Congratulations. Adam: Thank you very much. Very good. That's brilliant. Well, I have to say although me and Sally were planting, Rachel and Paul were looking were looking on. So Paul's still here, how did I do? Paul: Well, let me just check, shall I? Adam: *laughs* You're doing the tug test. Paul: It's it's been really fun actually with with, with the the the public when you come and kind of just check it, you can see them all hold their breath to make sure they're doing it right. Adam: And it comes out *laughs* Is it alright? Paul: No, it's grand. Absolutely brilliant. Dog rose it, it's a little bit crooked, but you know dog rose will naturally straighten itself up. Adam: Will it correct itself? Paul: Yeah and it's kind of you can already see it's a bit of a straggly thing and it'll do its thing and it'll be fine. Adam: Fantastic. What is your sense, really, of of what this might be in the future and how exciting is that for you? Paul: I think in the future, you know, we're we're we're we've got something here that at the very beginning that is gonna be hopefully really important for wildlife and that most of the design is about trying to get as much wildlife here as possible because we're close to the pebblebed heaths it will it will act as a little bit of a refuge in the heat as potentially the climate heats up in the future and that's all really brilliant. And then the other exciting bit is the fact that we've started from the beginning with people involved. That, that, that scenario, but when you look in the future, the you know the the trees that we're planting today are going to be like these big old oak trees in 3-4 hundred years time that when you get your head around it is really quite amazing. And these trees and this wood will be on maps in in the future, and you know, we're creating history, we're changing landscapes and it's all such a a positive thing to be involved in. Adam: That is amazing that in 3-4 hundred years there'll be a woodland here, the history of who planted it, the history of us being here today will be lost. They won't know who planted these trees perhaps, they won't know the story, but the trees will be here. They'll be there, they'll tell their own story in the future. It's an amazing thing to be part of isn't it. Paul: Yeah and you know if if you think about how many times do you get to do something that will still be here in three, four, 500 years time? That's just incredible. Adam: Well, if you want to find a wood near you and don't have any idea of where to look, do go to the Woodland Trust website and its woodlandtrust.org.uk/findawood, so that's woodlandtrust.org.uk/findawood. Until next time, happy wandering. Thank you for listening to the Woodland Trust Woodland Walks with Adam Shaw. Join us next month, when Adam will be taking another walk in the company of Woodland Trust staff, partners and volunteers. Don't forget to subscribe to the series on iTunes or wherever you're listening to us and do give us a review and a rating. And why not send us a recording of your favourite woodland walk to be included in a future podcast? Keep it to a maximum of five minutes and please tell us what makes your woodland walk special or send us an e-mail with details of your favourite walk and what makes it special to you. Send any audio files to podcast@woodlandtrust.org.uk. We look forward to hearing from you.

更多英语知识，请关注微信公众号: VOA英语每日一听 Amy: How about you? Have you ever been in an accident?Paul: Not a car accident. I was in a bicycle accident.Amy: Yeah?Paul: I laugh now but at the time, it was pretty bad.Amy: What happened?Paul: It was dark and it was Christmas day. And I was on my bicycle going down a quite steep slope and my telephone rang. And I looked at my mobile phone and I took it out of my pocket whilst riding my bike. And looked at it and noticed it was my dad and he was ringing to wish me a happy Christmas.So I felt sort of compelled to answer the phone. So answering the phone, still going down the hill, probably gathering speed. It's dark and I'm trying to get my dad off the phone as soon as I can. And before I knew it, I drove straight into the back of a parked black car.Amy: Oh no.Paul: I saw it at the very last minute. So I hit the back of it and my body slammed into the ground, and I broke a few bones, yeah. Yeah.Amy: Oh no.Paul: Yeah, yeah. It was a pretty miserable Christmas to be honest with you.Amy: I'd say it's terrible. That's the worst.Paul: Yeah.Amy: Did the owner of the car see what happened? Did you damage the car?Paul: I didn't stay long enough. I got out of there pretty quickly.Amy: And went to the hospital.Paul: No, I was a bit stubborn. I don't know why. I was the worst night sleep I've ever had but yeah, I didn't go to the hospital until the next day.Amy: What bones did you break?Paul: I broke my collarbone, the clavicle.Amy: Oh, a nightmare.Paul: And I broke a few ribs.Amy: Oh no, ribs. That's the worst because they can't do anything for it. They just send you on your way and you just have to cough in pain.Paul: Hmm.Amy: Oh no.Paul: Yeah. But it could have been a lot worse, you know.Amy: Hmm, that's true.Paul: Yeah. I could have broken my neck.Amy: So how long did it take you to recover?Paul: It took me about probably six weeks, I suppose.Amy: Hmm.Paul: Yeah, because then—actually, in the following —it happened on Christmas day, so three months later in the March, I was lucky enough to win a place in the Tokyo marathon. And I really wanted to do it because it's quite difficult to get. It's like a lottery now. There's so many people who apply to get a position.So I wasn't going to let this accident stop me from running the Tokyo marathon. So I was trying to rush it, really and I shouldn't have. But I did. I've run there.Amy: Did you?Paul: Yeah.Amy: Oh, my goodness.Paul: Yeah, I finished it but—Amy: Congratulations. But how were you? That must have really hindered your recovery.Paul: It hindered my training period for the marathon, yeah, so.Amy: But you finished it though.Paul: I finished it, yeah.Amy: Well done.Paul: I wouldn't do it again. Marathons are miserable things to be. Really. Why put yourselves through that pain? I still like running so maybe in the future, I'd do a half marathon or something, yeah. But a full marathon—my marathon days are over, I think. Yeah.

更多英语知识，请关注微信公众号: VOA英语每日一听 Amy: How about you? Have you ever been in an accident?Paul: Not a car accident. I was in a bicycle accident.Amy: Yeah?Paul: I laugh now but at the time, it was pretty bad.Amy: What happened?Paul: It was dark and it was Christmas day. And I was on my bicycle going down a quite steep slope and my telephone rang. And I looked at my mobile phone and I took it out of my pocket whilst riding my bike. And looked at it and noticed it was my dad and he was ringing to wish me a happy Christmas.So I felt sort of compelled to answer the phone. So answering the phone, still going down the hill, probably gathering speed. It's dark and I'm trying to get my dad off the phone as soon as I can. And before I knew it, I drove straight into the back of a parked black car.Amy: Oh no.Paul: I saw it at the very last minute. So I hit the back of it and my body slammed into the ground, and I broke a few bones, yeah. Yeah.Amy: Oh no.Paul: Yeah, yeah. It was a pretty miserable Christmas to be honest with you.Amy: I'd say it's terrible. That's the worst.Paul: Yeah.Amy: Did the owner of the car see what happened? Did you damage the car?Paul: I didn't stay long enough. I got out of there pretty quickly.Amy: And went to the hospital.Paul: No, I was a bit stubborn. I don't know why. I was the worst night sleep I've ever had but yeah, I didn't go to the hospital until the next day.Amy: What bones did you break?Paul: I broke my collarbone, the clavicle.Amy: Oh, a nightmare.Paul: And I broke a few ribs.Amy: Oh no, ribs. That's the worst because they can't do anything for it. They just send you on your way and you just have to cough in pain.Paul: Hmm.Amy: Oh no.Paul: Yeah. But it could have been a lot worse, you know.Amy: Hmm, that's true.Paul: Yeah. I could have broken my neck.Amy: So how long did it take you to recover?Paul: It took me about probably six weeks, I suppose.Amy: Hmm.Paul: Yeah, because then—actually, in the following —it happened on Christmas day, so three months later in the March, I was lucky enough to win a place in the Tokyo marathon. And I really wanted to do it because it's quite difficult to get. It's like a lottery now. There's so many people who apply to get a position.So I wasn't going to let this accident stop me from running the Tokyo marathon. So I was trying to rush it, really and I shouldn't have. But I did. I've run there.Amy: Did you?Paul: Yeah.Amy: Oh, my goodness.Paul: Yeah, I finished it but—Amy: Congratulations. But how were you? That must have really hindered your recovery.Paul: It hindered my training period for the marathon, yeah, so.Amy: But you finished it though.Paul: I finished it, yeah.Amy: Well done.Paul: I wouldn't do it again. Marathons are miserable things to be. Really. Why put yourselves through that pain? I still like running so maybe in the future, I'd do a half marathon or something, yeah. But a full marathon—my marathon days are over, I think. Yeah.

更多英语知识，请关注微信公众号: 英语每日一听 Paul: So, we were talking about climates, Amy. Uhm, you know are there any sort of climates that you'd like to live in?Aimee: I would like to live in Iceland or Scandinavia.Paul: Interesting. Why would you like to live in that sort of climate?Aimee: Uhm, The snow is just so beautiful and my image of those countries is that their infrastructure is sufficient enough to keep you warm when you're inside. You know? But I'd say it's just so beautiful. The snow is amazing, It quietens everything. I think it's glorious. I just really like it. I used to ski when I was younger. So I always ... I like skiing and I like the hills, and yeah, and the snow on hills is just beautiful for me. How about you?Paul: Well I, I love snow too, but I don't like it when it gets so slushy and sloppy you know, and your feet are freezing. You know I think like, the ideal of snow is really appealing. I'm not sure about, you know, living in it. I prefer, I don't know maybe the climate of like Southern Italy, kind of Mediterranean, climate I think that would be really quite pleasant. You know? Not too hot, by the sea, although yeah, in the summer, it does gets hot. But I don't think it's the humidity.Aimee: Right, I was just thinking about that. What kind of heat is it? Is it a dry heat?Paul: I think it is a drier heat. Yeah, yeah, whereas the heat we obviously we get here is unbearable at times, right?Aimee: Yeah, it's really bad. Yeah.Paul: So, uhm….Aimee: What's the highest temperature? What's the range of temperature in Southern Italy, what kind of climate, do you know?Paul: Not sure, I guess maybe at this time of year it starts getting up towards 20 degrees C.Aimee: That's nice.Paul: And then I think it does you know places like Sicily, I think it does get pretty hot, probably like the high 30s? Yeah, yeah, so and I think the winters are probably quite mild, unless you're from the North of Italy of course, near the mountains.Aimee: Yeah.Paul: Down in the south it remains kind of pretty mild, you know?Aimee: Aha, if it's in the Med... It's my images of that. I've never been to Italy so I don't know. I've been to the South of France and it got really hot. That was a nice temperature. It was dry, and yeah the nighttime wasn't too hot either, it was really nice during the day. That was a nice climate, I think.

更多英语知识，请关注微信公众号: 英语每日一听 Paul: So, we were talking about climates, Amy. Uhm, you know are there any sort of climates that you'd like to live in?Aimee: I would like to live in Iceland or Scandinavia.Paul: Interesting. Why would you like to live in that sort of climate?Aimee: Uhm, The snow is just so beautiful and my image of those countries is that their infrastructure is sufficient enough to keep you warm when you're inside. You know? But I'd say it's just so beautiful. The snow is amazing, It quietens everything. I think it's glorious. I just really like it. I used to ski when I was younger. So I always ... I like skiing and I like the hills, and yeah, and the snow on hills is just beautiful for me. How about you?Paul: Well I, I love snow too, but I don't like it when it gets so slushy and sloppy you know, and your feet are freezing. You know I think like, the ideal of snow is really appealing. I'm not sure about, you know, living in it. I prefer, I don't know maybe the climate of like Southern Italy, kind of Mediterranean, climate I think that would be really quite pleasant. You know? Not too hot, by the sea, although yeah, in the summer, it does gets hot. But I don't think it's the humidity.Aimee: Right, I was just thinking about that. What kind of heat is it? Is it a dry heat?Paul: I think it is a drier heat. Yeah, yeah, whereas the heat we obviously we get here is unbearable at times, right?Aimee: Yeah, it's really bad. Yeah.Paul: So, uhm….Aimee: What's the highest temperature? What's the range of temperature in Southern Italy, what kind of climate, do you know?Paul: Not sure, I guess maybe at this time of year it starts getting up towards 20 degrees C.Aimee: That's nice.Paul: And then I think it does you know places like Sicily, I think it does get pretty hot, probably like the high 30s? Yeah, yeah, so and I think the winters are probably quite mild, unless you're from the North of Italy of course, near the mountains.Aimee: Yeah.Paul: Down in the south it remains kind of pretty mild, you know?Aimee: Aha, if it's in the Med... It's my images of that. I've never been to Italy so I don't know. I've been to the South of France and it got really hot. That was a nice temperature. It was dry, and yeah the nighttime wasn't too hot either, it was really nice during the day. That was a nice climate, I think.

Acts 21:1-16 Believe it or not, sometimes good Christians disagree on God's will and intention.  From Acts 21, Joe Kunzeman (an Overseer at our church) contrasts Paul's determined intention to GO to Jerusalem with other believers (including prophets) urging Paul NOT to go to Jerusalem.  The dynamics of the text provide a basis for addressing our own different persuasions as believers.

Who were Philippians?; Understood "Republic"; How deep in dept you are; Not seeing foolishness; Christ changes your mind - daily; Roman Centurians' service; Real Militia; Liturgy defined; Paul's "captivity"; Registering births; "Saints" at Philippi; Saying "I love Christ" doesn't make you a Christian; Deacons and Bishops; Being the "real" Church; vs Fathers of the world; Obamacare not needed for Christians; Paul's lawsuit; You can practice Pure Religion right now!; "Worship Service"; Salvation is an individual process; Caring about neighbors' rights; Marcus Aurelius; Paul advancing the gospel; Strengthening early America; The problem with offices of power; Paul in a palace?; There may be truth you haven't heard; False "churches" giving "Church" a bad name; The way Christ commanded; Transformed Paul; Where is your "conversation"?; Paul NOT a citizen of Rome; Story of Gregory's dad; Kingdom citizenship; Fruits of repentance; Your jobs/responsibilities; Come together, dry bones; Evil wants you subject; Loving one another is the gospel of the kingdom.

From 2016 to today, two of the top ten buzzwords in Digitial Marketing have been Native Advertising and Artificial Intelligence. They are very important topics and will help drive the future of Digital Marketing as we know it. However, for most marketers, and those who are attempting to reach marketers with online content, these two topics are misunderstood. In this episode of Marketer-to-Marketer, Chad Pollit, Author of the Native Advertising Manifesto, and Paul Roetzer, CEO of PR 20/20, dive deeper into these topics and give us a State of the Field for each Native Advertising and AI. The conversation does a great job and driving insights and connecting these topics together in the context of Content Marketing.Full Show: https://enterprisemarketer.com/podcasts/m2m/season-01-show-11/Transcript:- Yeah, you got me doubled up. You got me doubled up. So we've been in this space a long time, we've dealt with lots of different companies from SNBS to enterprise companies and we've seen the evolution of marketing and digital marketing, content marketing, so on so forth. What's the hottest thing on the horizon that's here today that's going to be even bigger tomorrow?- It's so fascinating when I was actually, Travis Wright, we both know Travis. Travis was just talking to me about Blockchain which I still just don't comprehend. And in three years we can come back and watch this and laugh that I have no comprehension of it right now. But that's one of those things that I just don't get. And I've tried now to get into that space. I think that one's still a ways off. Like I think from a marketer perspective and really caring about it and seeing it effect our daily lives, that one's really out on the horizon. Artificial intelligence to me is the one that's kind of here now. It's where I've been spending most of my time and you and I have talked a little bit about this with your work at the Native Advertising Institute and we had launched the Marketing Artificial Intelligence Institute, so our focus there was really just trying to figure out what is going on. Because you start looking around even here at the exhibit hall, you see AI over here on Acrolinx, and you go running and see artificial intelligence now being promoted on a lot of these companies, but as the average marketer, people one, don't really know what that means, and two, even if they do, it's hard to know how intelligent the software really is becoming. Like is it still a human telling the software what to do? Or is the software actually starting to learn and get better on its own? And eight months ago or so when we launched the Institute, that was the thing I didn't know. Like we would look at 100 companies that all said they did AI, and I had no way of knowing whether they truly did or not. And now we're at the point we're trying to actually start help marketers filter through that. Figure out what is AI actually capable of doing today to make your job easier, more efficient, more productive, and where is it gonna take us in the future? That's my talk on Thursday's machine assisted narrative. It's in terms of creating and promoting content how can artificial intelligence today make your job as a marketer more efficient? Which tools do you need? What should you be looking for? So that's where we're spending the majority of time now. So we still have our core agency but most of my time's in the AI space tryin' to learn about that.- So would you say that for something to be truly AI, it has to have machine learning? Or is it more than that?- Yeah, so the basic on, AI is the umbrella. It's like the collective of technologies and processes that machines become smarter basically. So Watson is the one everybody knows or everybody's like familiar with Watson. Machine learning and deep learning are kind of the two main subsets within artificial intelligence. And the basic way to look at what is machine learning is does the software get smarter on its own? So an example would be, if you use a software to tell you when to schedule your social media shares. If there's some tools here that'll do it, say, "Hey send it at 3 p.m." Jay mentioned in his talk this morning, send it at 3 p.m. Well that's a data scientist. They just looked at a data set and said, "Okay the optimal time to send it is this." And until that data scientist or the programmer updates that rule, it will continue to be a human based rule that said when the best time is. In machine learning, the algorithms actually in real time monitor when that optimal time to share changes and what the optimal share time may be for your specific company. And it would, so today it might say 3 p.m. tomorrow it might say 1:44. That's machine learning. It's actually the machine with no human guidance getting smarter and updating what it recommends you to do. That is very rare to find in marketing software today. So there are marketing tools that are using types of artificial intelligence, very few of them are actually getting smarter on their own and thereby changing what they would guide a marketer to do. So that's the machine learning thing I thought a year ago was much further along than it really is in the marketing space. There are lots of really interesting things being done with AI and really interesting companies, but not much in the way of machine learning.- Gotcha. So what do you think of Salesforce's Einstein?- Salesforce is interesting they've made massive bets, so they I think bought about nine AI companies, couple billion dollars worth and then they mashed them together into Einstein and it's basically a layer over the core CRM product. So that's the other thing in AI's. There's no platform. There are narrowly built use cases. There's software built for narrow use cases and in Salesforce's case they try to mash these all together. Early feedback I've heard is it's really interesting it probably helps a lot with efficiency, but it's not fully baked yet and it's, like a lot of software companies it was probably announced before was truly what it's capable of doing, so I think, I wouldn't they're by no means in a beta form, but they're in very early stages of realizing AI's potential and actually integrating it into the software.- Gotcha. Very interesting.- [Paul] How bout you? What's the thing you're focused on?- Well, so I took, I felt very European this summer. I took a--- [Paul] Were you in Europe?- No, well I did spend a little bit of time in Europe, but no, I actually took a lot of time off. Spent it with my kids. In fact for over a month I didn't touch my desktop, which is where I do all of my work, so, I lied actually I think I touched it four, three or four times. But I, that's the first time I've done that in 17 years in the business.- [Paul] And that's from agency world--- Yeah.- [Paul] to the academic world to--- Yeah, yeah. Exactly. Because as you know I teach at the Indiana University Kelley School of Business and the summer is my real time off where I don't have to deal with students, and not that that's a bad thing, but I don't have to grade papers, lecture, things like that. So if I wanna take a significant amount of time off, I have to do it in the summer, so I did. Which by the way, if you haven't taken three to four weeks off in a long time, I recommend trying.- [Paul] Not since college.- So yeah, I'm still tryin' to lead the way in thought leadership when it comes to content promotion and distribution, both paid and earned. I feel like a lot of people have sort of hogged up that influence or marketing earned side, of earned content promotion through influencer marketing. So I focus most of my attention on the paid side. So earlier in the year I spent nearly a month just researching the native advertising tech landscape. And what I discovered was there's over 272 companies that are involved in native advertising, someway on the technology side.- [Paul] And define native advertising for me, like what do you--- So native advertising is content that matches the form, feel, and function of the media that surrounds it. Okay, so a good way to think about it and to get clarity around native advertising is anything in feed that looks like it's supposed to be there. It can say sponsored. So Facebook's a perfect example. You see sponsored posts there, but it's in feed and it looks just like everything else, it just annotated as sponsored.- So sponsored content, native advertising, same thing or are they, is there distinctions?- So this is a big problem in native advertising. You also have something called long-form native advertising. And the most famous example of that is Netflix's Orange is the New Black in the New York Times.- [Paul] I met the lady last night that wrote that article--- Melanie. Melanie wrote that article, she's here. So that's native advertising too.- So the reason I bring that up is because to your average person that Facebook ad and that entire article in the New York Times, are totally different things. But they're not. They're both sponsored, they're both in feed, in the natural feed of the website, and they're both paid for. Okay so there's really, there's four categories, there's long-form, programmatic, non-programmatic, the fourth one is social media.- Okay.- Those are not the IAB categories, those are the categories that I've come up with because I don't like the IAB's categories.- [Paul] Interactive Advertising?...

As the Enterprise explores a nebula, a little girl’s imaginary friend becomes terrifyingly real. Today James and Lou discuss (Imaginary Friend) and what we think of it, with tonight’s guest host Paul (Not a director) Finch. Credit: Main Title Theme (TV Edit) was arranged by Dennis McCarthy and composed by Gerry Goldsmith and Alexander Courage […]

This week Paul from England and Aimee from Scotland discuss where they would like to live. Go to elllo.org for the full lessons with audio, video, vocabulary, and more.  See transcript of interview below: Paul: So, we were talking about climates, Amy. Uhm, you know are there any sort of climates that you’d like to live in? Aimee: I would like to live in Iceland or Scandinavia. Paul: Interesting. Why would you like to live in that sort of climate? Aimee: Uhm, The snow is just so beautiful and my image of those countries is that their infrastructure is sufficient enough to keep you warm when you’re inside. You know? But I’d say it's just so beautiful. The snow is amazing, It quietens everything. I think it’s glorious. I just really like it. I used to ski when I was younger. So I always ... I like skiing and I like the hills, and yeah, and the snow on hills is just beautiful for me. How about you? Paul: Well I, I love snow too, but I don’t like it when it gets so slushy and sloppy you know, and your feet are freezing. You know I think like, the ideal of snow is really appealing. I’m not sure about, you know, living in it. I prefer, I don’t know maybe the climate of like Southern Italy, kind of Mediterranean, climate I think that would be really quite pleasant. You know? Not too hot, by the sea, although yeah, in the summer, it does gets hot. But I don’t think it’s the humidity. Aimee: Right, I was just thinking about that. What kind of heat is it? Is it a dry heat? Paul: I think it is a drier heat. Yeah, yeah, whereas the heat we obviously we get here is unbearable at times, right? Aimee: Yeah, it’s really bad. Yeah. Paul: So, uhm…. Aimee: What’s the highest temperature? What’s the range of temperature in Southern Italy , what kind of climate, do you know? Paul: Not sure, I guess maybe at this time of year it starts getting up towards 20 degrees C.  Aimee: That’s nice. Paul: And then I think it does you know places like Sicily, I think it does get pretty hot, probably like high 30s? Yeah, yeah, so and I think the winters are probably quite mild, unless you’re from the North of Italy of course, near the mountains.  Aimee: Yeah. Paul: Down in the south it remains kind of pretty mild, you know? Aimee: Aha, if it’s in the Med ... It's my images of that. I’ve never been to Italy so I don’t know. I’ve been to the South of France and it got really hot. That was a nice temperature. It was dry, and yeah the nighttime wasn’t too hot either, it was really nice during the day. That was a nice climate, I think.   Thanks for listening.