175 lines
34 KiB
XML
175 lines
34 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
||
<?xml-stylesheet href="pretty-atom-feed.xsl" type="text/xsl"?>
|
||
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
|
||
<title>kfitz</title>
|
||
<subtitle>The long-running and erratically updated blog of Kathleen Fitzpatrick.</subtitle>
|
||
<link href="https://kfitz.info/feed/feed.xml" rel="self" />
|
||
<link href="https://kfitz.info/" />
|
||
<updated>2025-08-31T18:34:18Z</updated>
|
||
<id>https://kfitz.info/</id>
|
||
<author>
|
||
<name>Kathleen Fitzpatrick</name>
|
||
</author>
|
||
<entry>
|
||
<title>Success, at Last</title>
|
||
<link href="https://kfitz.info/success-at-last/" />
|
||
<updated>2025-08-31T18:34:18Z</updated>
|
||
<id>https://kfitz.info/success-at-last/</id>
|
||
<content type="html"><p>After a <a href="https://kfitz.info/networking/">whole</a> <a href="https://kfitz.info/networking-continued/">lot</a> of tinkering, I think I have at last managed to get my home server up and running the way I want. Doing so required a change of ISP, which I wanted to do anyway as I'm getting a much better deal (including double the network speed) from my new provider. It also required a day and a half of further frustration, as the port forwarding setup that ought to have worked wasn't working at all, but after further futzing I've managed to get it all working pretty slickly.</p>
|
||
<p>In my current setup, I have Nginx Proxy Manager running in a container on my Proxmox, with a DNS entry set up pointing my IP address to it. Then I have a proxy host pointing to another container in which I'm running Gitea, and I'm successfully pushing and pulling code for this site to and from it.</p>
|
||
<p>Next up is setting the actual hosting of this site and a few others that I've been wanting to pull in house. It's nice to see the end of the network architecture phase of this project near and to have the creative work of writing and building opening up in front of me at last!</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Longevity and Sustainability</title>
|
||
<link href="https://kfitz.info/longevity/" />
|
||
<updated>2025-08-18T15:45:25Z</updated>
|
||
<id>https://kfitz.info/longevity/</id>
|
||
<content type="html"><p>I've been puzzling a bit of late about the relationship between sustainability planning for independent, nonprofit digital projects and the need to provide evidence of that sustainability even as it's being developed. The question has been pitched to me recently as being about <em>longevity</em>: can your project promise potential supporters that it will survive the next ten years?</p>
|
||
<p>It's a valid question, especially when the project is one that is in some sense <em>about</em> longevity, about (for instance) preserving the products of knowledge creation for the future. But it's a hard one to answer in the best of times, and goodness knows that we are not currently living through the best of times.</p>
|
||
<p>How much have the ways that we think about longevity and sustainability been conditioned by our experiences of working with software and platforms that, even when provided without charge, are operated by massive corporations with resources to burn? These companies can afford to move quickly, to respond to rapid growth, to develop robust user support, and to add new features with the kind of agility that very few small nonprofit or community-based groups can muster.</p>
|
||
<p>This is not to say that nonprofit projects should operate freed from any expectations for professionalism, including long-term planning, technical durability and security, attention to user needs, and so on; these are crucial considerations for any piece of infrastructure. But I worry that some of the metrics that we use in thinking about sustainability wind up privileging corporate solutions even when we're seeking values-aligned, non-extractive alternatives.</p>
|
||
<p>It will not shock anyone that I'm mostly thinking about my own project in this context.<sup class="footnote-ref"><a href="https://kfitz.info/longevity/#fn1" id="fnref1">[1]</a></sup> That project has been around for more than ten years, and has over that time demonstrated slow, sustainable growth, but it has been dependent on grant-based, project-oriented funding to support its work. We are now trying to break away from that model and put in place a mature revenue generation model that will allow us to recoup operating costs (and with luck to produce a small margin to support future needs) through membership fees paid by organizations and institutions that want to use our platform. As part of their membership, they get a voice in our governance processes, and thus have the ability to shape the project's future.</p>
|
||
<p>But for very understandable reasons, we're hearing questions about the potential longevity of the project, as folks with decision-making responsibility want to be sure that their investment will be to a good end, and that the work they subsequently entrust to the platform will be available over the long term. It's a Catch-22, though, in that <em>without</em> their investment (and the investment of other institutions like theirs) we absolutely will not survive -- so how can I say that our model will have succeeded before the future anterior becomes simple past?</p>
|
||
<p>At root: can we shift our thinking so that an investment in a non-extractive alternative is understood to be an investment in the community itself, <em>of which the investor forms a part</em>, in a way that doesn't ask small projects just getting underway to demonstrate all of the durability and agility of corporate alternatives? Can we begin to recognize that some aspects of the durability and agility we've been conditioned to demand have been produced precisely through an extractive economic model that is continuing to impoverish the very commons that we're trying to build? How can we turn the question about the project's longevity into a question about mutual commitment to a shared endeavor?</p>
|
||
<hr class="footnotes-sep">
|
||
<section class="footnotes">
|
||
<ol class="footnotes-list">
|
||
<li id="fn1" class="footnote-item"><p>Though I'm posting this in my own personal pondering space rather than over there because I'm hoping that respondents will think with <em>me</em> about these issues rather than immediately associate them with the project, even though such an association is all but inevitable. <a href="https://kfitz.info/longevity/#fnref1" class="footnote-backref">↩︎</a></p>
|
||
</li>
|
||
</ol>
|
||
</section>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Networking Continued</title>
|
||
<link href="https://kfitz.info/networking-continued/" />
|
||
<updated>2025-08-09T20:38:09Z</updated>
|
||
<id>https://kfitz.info/networking-continued/</id>
|
||
<content type="html"><p>As you may recall, I've been experimenting with setting up a home server, and several months ago had gotten stuck on an issue related to <a href="https://kfitz.info/networking/">the structure of my network</a>. <a href="https://kfitz.info/networking/?ht-comment-id=26755687">Taylor hopped in</a> and really helped me understand how everything <em>ought</em> to work.</p>
|
||
<p>But it's not working. And I'm again flummoxed.</p>
|
||
<p>Here's the setup:</p>
|
||
<ol>
|
||
<li>I have my ISP's modem/router/gateway monstrosity (the BGW320) running in IP Passthrough mode, with the WAN IP address being passed to my gateway Eero.</li>
|
||
<li>I have my Eeros set to Automatic DHCP mode; the gateway Eero is successfully getting the WAN IP address and is handing out private IP addresses in the 192.168.4.X range.</li>
|
||
<li>I have a registered domain name (let's say <code>example.net</code>), and I have an A record at my DNS service pointing to my WAN IP address. I have also created a subdomain A record (<code>service</code>) pointing to the same IP address. DNS Checker gives me all green checks for both.</li>
|
||
<li>I have a mini server, running Proxmox.</li>
|
||
<li>I have installed Nginx Proxy Manager in a container on the Proxmox (an LXC), which is running and reachable at the static address 192.168.4.11.</li>
|
||
<li>I have installed the service I'm trying to expose in another LXC, which is running and reachable at the static address 192.168.4.12.</li>
|
||
<li>I have set up port forwarding on my Eero network for ports 80 and 443 to <s>198</s>192.168.4.11.</li>
|
||
<li>I have created a proxy host in NPM, for which all the dots are green:
|
||
<ul>
|
||
<li>Domain Name: <a href="http://service.example.net">service.example.net</a></li>
|
||
<li>Scheme: http</li>
|
||
<li>Forward Hostname/IP: 192.168.4.12</li>
|
||
<li>Forward Port: <code>port</code></li>
|
||
<li>Block Common Exploits and Websockets Support on</li>
|
||
<li>Access List: Publicly Accessible</li>
|
||
</ul>
|
||
</li>
|
||
</ol>
|
||
<p>But <code>http://service.example.net:port</code> refuses to connect, as does <code>http://example.net</code>, either from my local network or through my VPN. And <code>traceroute</code> to either <code>example.net</code> or <code>service.example.net</code> stalls out.</p>
|
||
<p>I've checked the Proxmox firewall and inbound 80 and 443 are both set to accept. I've checked to see whether my ISP's montrosity's firewall could be blocking those ports but... who's to say. The NAT/Gaming (sigh) panel of the admin interface isn't showing the gateway Eero as a device that could need anything in particular sent its way, so my assumption is that IP Passthrough passes inbound requests through for the Eero to sort out, too.</p>
|
||
<p>I've searched around, and the nearest thing I've found to what I'm trying to do and how I'm trying to do it is in <a href="https://www.reddit.com/r/Proxmox/comments/u857x5/nginx_proxy_manager_setup_troubles/">this Reddit thread</a>, but the problem in that case is back at the beginning with the A record, which is definitely not my issue, unless I spelled my domain name wrong at the DNS. (I didn't.) And that person was able to get to the NPM congratulations page; my connections get refused entirely.</p>
|
||
<p>If anybody sees anything that I should adjust, or take a look at adjusting, I'd be grateful to hear. I'm already <em>this</em> close to dumping my ISP anyhow due to some ongoing service issues, and getting rid of their annoying modem/router/gateway would be a bonus, but I'm not entirely certain that it's the problem, and I'd love to find a way through without taking that step.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Distinguished</title>
|
||
<link href="https://kfitz.info/distinguished/" />
|
||
<updated>2025-06-26T12:30:07Z</updated>
|
||
<id>https://kfitz.info/distinguished/</id>
|
||
<content type="html"><p>I'm a little astonished to be writing this, but my college has posted the news, so it must be true: <a href="https://cal.msu.edu/news/kathleen-fitzpatrick-named-a-university-distinguished-professor/">MSU has named me a University Distinguished Professor</a>. I am honored, and filled with gratitude toward the colleagues who nominated me, and frankly still a bit stunned that this recognition has come my way.</p>
|
||
<p>I am grateful to have received so much support for the work I've done over the years, both on campus and off, from publishers and funding agencies, from colleagues and collaborators, from administrators, from friends and family. But my work has always been on the edge of so many fields -- not really literary studies, not really media studies, not really digital humanities, not really higher education studies -- that it has perpetually felt as though it was at risk of falling through the cracks. So this is a career milestone of a sort that I never thought I'd reach.</p>
|
||
<p>I'll also note that my institution, like so many large public R1s, heavily favors engineering, business, medicine, and the sciences; the College of Arts &amp; Letters has been significantly underrepresented in university honorifics in recent years. I am the third University Distinguished Professor to be named in the college since 2003 -- twenty-two years! -- and the two scholars named during that period hold joint appointments with colleges on the STEM side of campus. I collaborate with STEM-leaning folks, and I have been successful in obtaining funding from agencies that are valued in that universe, so I acknowledge that I am recognizable to a university-wide committee in ways that someone more squarely located in a humanities-based discipline might not be. I nevertheless hope that I can find ways to enable this new title to help attune the university at large to the crucial kinds of work being done across the arts and humanities.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>All This</title>
|
||
<link href="https://kfitz.info/all-this/" />
|
||
<updated>2025-05-31T11:22:25Z</updated>
|
||
<id>https://kfitz.info/all-this/</id>
|
||
<content type="html"><p>There's a moment in the 2001 Michael Bay classic, <em>Pearl Harbor</em> (which <a href="https://www.rogerebert.com/reviews/pearl-harbor-2001">Roger Ebert once described</a> as &quot;a two-hour movie squeezed into three hours&quot;), in which Kate Beckinsale, having been reunited with Ben Affleck, is attempting to explain how she could possibly have abandoned him for Josh Hartnett. Ben, of course, had been reported to be dead, and Josh was hunky and sweet and <em>there</em>, so, you know. But a teary Kate says, and I quote: “I didn’t even know until the day you turned up alive — and then <em>all this</em> happened,” waving her hand vaguely over her shoulder at the still-smoking wreckage.</p>
|
||
<p>I have thought about this moment more times than I'd really like to admit over the intervening 24 years, but never more so than in the last four months. &quot;We were already facing budgetary challenges in the college — and then <em>all this</em> happened&quot; (<em>waves hand vaguely over shoulder at the still-smoking wreckage</em>). &quot;I was worried about the future of this project -- and then <em>all this</em> happened.&quot; (You get the point.)</p>
|
||
<p>The <em>all-this</em>-ness of all this is utterly flippant, to be sure, but I'm beginning to understand the utility of <em>all this</em> as a container for the incomprehensible. We are facing circumstances that periodically cause me to lose my vocabulary. I don't know how to name it without breaking down, and I suspect that this is true of a lot of my colleagues. And so we talk about things like &quot;the current moment&quot; or &quot;the federal funding landscape,&quot; ways of signaling what we all know -- that we are living through a fucking horror of our country's own making, the destruction of everything that matters to us, the kidnapping and torture of members of our communities, the completion of the descent into what it no longer makes sense to call anything other than fascism -- without landing our conversation in a place in which it becomes impossible to go on.</p>
|
||
<p>I am trying to reckon with <em>all this</em>, and with the desire to wave my hand vaguely over my shoulder without looking too closely at what it's gesturing toward. I have been doing a bit of writing around it, and am hoping that I'll be able to share some of that in the weeks and months ahead. I'm not sure where it's all headed, but it's at least an attempt to be honest with myself about my reactions to what's happening, as well as an expression of hope that we might find our way through together.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Networking</title>
|
||
<link href="https://kfitz.info/networking/" />
|
||
<updated>2025-05-11T12:39:42Z</updated>
|
||
<id>https://kfitz.info/networking/</id>
|
||
<content type="html"><p>This post is going to put my full nerdiness and my full cluelessness simultaneously on display, but I am building a home network that is going to include a server hosting much of my online presence, and I am running into some issues that are making the limitations in my knowledge all too apparent. (Also the limitations in internet search in the year of our lord 2025: I can find answers for solving issues in specific one-to-one connections within this network, but they leave out other crucial components such that I can't get the whole thing going all at the same time.) So I am here, appealing to you, to help me think this through.</p>
|
||
<p>I have AT&amp;T fiber coming into my house, with a BGW320 modem/router combo. I have a 3-device Eero mesh wifi network, with the gateway Eero connected to the BGW320 via ethernet. I have a Synology NAS connected to the Eero gateway via ethernet, and I'm soon going to have a mini server that... will get connected to all of this somehow that I haven't yet figured out.</p>
|
||
<p>I have turned off the wifi radios on the BGW320, so that I only have the wifi network provided by the Eeros. Right now, I have IP Passthrough turned on on the BGW320, set to DHCPS-dynamic; the WAN IP address is being picked up properly by the gateway Eero and the WAN type on the Eero is set to DHCP (Default). The bajillion devices in my house are being doled out IP addresses appropriately vis DHCP, including the NAS, and are for the most part getting good bandwidth (though the gateway Eero seems to have to reconnect to the internet periodically, so there's clearly some setting in the BGW320 that needs futzing with already).</p>
|
||
<p>But here's where things start to get complicated: I have purchased a block of 5 static IP addresses from AT&amp;T (really 8, but one gets assigned to the router and 2 are unusable), with the intent of assigning the NAS and the forthcoming server a static IP. So in the BGW320 admin interface, I have both a private LAN subnet and DHCP range (of the <a href="http://192.168.1.XXX">192.168.1.XXX</a> variety) and a public subnet that includes my public gateway address, my public subnet mask, and the 5-address DHCP range.</p>
|
||
<p>In passthrough mode, the BGW320 just hands off all DHCP stuff to the Eero mesh, which has the gateway address of 192.168.4.1 (the Eero default). In the Eero admin interface, I can use Reservations &amp; port forwarding to assign a static IP address to a device, like the NAS. However, my static IP addresses are outside the Eero's subnet range, so it won't accept them.</p>
|
||
<p>On the NAS, I can use the admin interface to assign the static IP address right there, and it will accept the address, but doing so breaks a bunch of connections between the NAS and the outside world, like Synology's software updaters, whose IP addresses it cannot resolve. I am guessing that this is because assigning the static IP on the device breaks the DNS connection, but it's also possible that it's got something to do with the way I've set up the NAS's firewall rules, which, ugh.</p>
|
||
<p>Anyhow, I am wondering at this point whether going with IP Passthrough on the BGW320 is at the root of the problem. If instead I let the AT&amp;T device handle all the WAN/DHCP stuff, and put the Eeros into bridge mode, will the static IP addresses become assignable to devices via the BGW320? If so, will devices connected to the private subnet via the Eeros still be able to talk to the devices on the public subnet? And aside from the <a href="https://support.eero.com/hc/en-us/articles/115000825206-What-advanced-features-do-I-lose-access-to-if-I-put-my-eeros-into-bridge-mode">&quot;advanced features&quot; that Eero tells me I'll lose if I go the bridge mode route</a>, are there other drawbacks?</p>
|
||
<p>I think I've talked myself into trying it and seeing what happens... but I'm going to pause for a bit to see if anyone has other suggestions.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Gitea</title>
|
||
<link href="https://kfitz.info/gitea/" />
|
||
<updated>2025-04-20T14:56:45Z</updated>
|
||
<id>https://kfitz.info/gitea/</id>
|
||
<content type="html"><p>This site is running in 11ty and is built locally, after which the live site (which gets built into the _site folder) is pushed to my Reclaim Hosting account, where it's served up as <a href="http://kfitz.info">kfitz.info</a>. As an intermediate step, I have been pushing the code and content that builds the site to a GitHub repository, and then the _site folder to another GitHub repository, kfitz-site, mostly for preservation/backup purposes; if something happens to the server or to my local repo, there's another version-controlled pile of code out there from which things can be rebuilt. (Technically, I pull kfitz-site from GitHub to Reclaim. Similarly, <a href="http://presentations.kfitz.info">presentations.kfitz.info</a>, which runs in revealjs, is built locally, pushed to GitHub, and then pulled to Reclaim.)</p>
|
||
<p>I've had in my head for a while, though, that GitHub is in and of itself a point of failure, partially because of its ownership structure. On top of which, I haven't been delighted knowing that everything I push there is part of the greater Copilot feeding frenzy.</p>
|
||
<p>I'd been thinking for a while about migrating my repos to <a href="https://codeberg.org">Codeberg</a>, a community-governed alternative that -- a key consideration at this hour of the world -- is not hosted in the US. But it turns out that the terms of service on Codeberg highly discourage private repositories, and both <a href="http://kfitz.info">kfitz.info</a> and kfitz-site are private, even though the eventual published site is obviously very public and CC BY 4.0 licensed. I've kept those repositories private because they're not the product I'm trying to share -- the website is -- and I want a little freedom to make mistakes without everything being quite that out there. I totally get why Codeberg's TOS is structured the way it is; they're really focused on building open-source communities around FLOSS development, which is a huge part of why I wanted to support them. It's just not the work I'm doing.</p>
|
||
<p>So I spent a chunk of yesterday exploring the possibility of self-hosting <a href="https://about.gitlab.com">GitLab</a>, but <em>holy cats</em> is it resource-intensive. The instance I spun up on a Digital Ocean droplet would have cost me $32/month to keep in operation, and even so it was pegging 100% memory usage, with just one user. So... no, not unless I were really hosting the service for a bunch of friends who wanted to kick in a little.</p>
|
||
<p>This morning, though, I spun up a <a href="https://about.gitea.com">Gitea</a> instance on a much smaller Digital Ocean droplet, which will run $14/month. It's super zippy and very lightweight, and has allowed me to migrate my repositories from GitHub quite seamlessly. And there's lots of room to grow, resource-wise, so if those friends decide they want to test things out I can invite them to join me.</p>
|
||
<p>The next thing I want to investigate in whether I can run that Gitea instance on a shared server, using one droplet to host multiple applications and sites...</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>On the NEH and Our Path Forward</title>
|
||
<link href="https://kfitz.info/neh-path-forward/" />
|
||
<updated>2025-04-17T13:23:01Z</updated>
|
||
<id>https://kfitz.info/neh-path-forward/</id>
|
||
<content type="html"><p><em>Crossposted from the Knowledge Commons team blog.</em></p>
|
||
<p>Over the last several weeks, we've seen colleagues of ours across the country posting about the direct impacts they're experiencing of the current attacks on the National Endowment for the Humanities, including sudden and extensive terminations of previously awarded grants. We hurt for everyone who's trying to figure out how to <a href="https://rrchnm.org/news/carrying-on-when-the-grants-go-away">carry on</a>, not least because we're in that same space with you right now.</p>
|
||
<p>On April 2, 2025, we received notification that our NEH Infrastructure and Capacity Building Challenge Grant, awarded in 2020, was terminated effective immediately. We had just celebrated in a <a href="https://about.hcommons.org/2025/01/21/digital-scholar-donates-20000-to-support-knowledge-commonsand-helps-us-reach-a-major-milestone">January post</a> the completion of our fundraising match; the NEH grant offered us $500,000 to be released as we certified a 3:1 fundraising match. That combined $2 million in funding was to provide us with the runway necessary to bring the Commons to sustainability.</p>
|
||
<p>Insofar as there is good news here, it's that we'd been certifying gifts annually, and so most of the NEH funds had already been &quot;obligated&quot; (for whatever meaning that term now holds), and we'd been spending the receipts as needed over the last several years, with an expectation that the combined fund would be fully spent down in early 2027. In real numbers, the termination of the grant resulted in something less than $100,000 in losses for our budget – a significant amount for a small team operating on a shoestring, but not an insurmountable figure.</p>
|
||
<p>However, on April 10, 2025, we received further -- if not yet formal -- notification that our contract to provide the <a href="https://about.hcommons.org/2024/12/10/kcworks-named-designated-public-access-repository-of-the-national-endowment-for-the-humanities">NEH's Designated Public-Access Repository</a> was also being terminated, effective on that date. This loss is devastating for us, both for the financial impact it represents (another $200,000 loss over the same two years) but also for the unceremonious end to a goal we'd set for ourselves years ago. There’s also a real, human impact involved: we’d just completed an extensive search to hire a developer to work with us on that project, and were deep in the process of putting together an offer letter to an amazing candidate when the funds disappeared.</p>
|
||
<p>Not to mention the bigger picture here: that designated public-access repository is no longer needed, because it is assumed that the NEH will no longer be funding research, and thus there will be no results of research to make publicly accessible.</p>
|
||
<p>And worse: a huge percentage of our friends and colleagues at the NEH, whose work on our behalf has helped shape knowledge production across our fields, have lost their jobs, and are seeing the decimation of everything that they built and maintained with such care and professionalism.</p>
|
||
<p>Back here on the Commons team, we're mourning our losses, but also trying to carve out a path forward, one that will allow us to keep doing the key work of supporting open-access scholarly collaboration, communication, and preservation. We'll be sharing pieces of this plan with you over the coming weeks, which will include seeking institutions who want to join us (hint: KC Works is ready to host repositories for colleges, universities, and other organizations), and as you might expect, we'll be asking for community support as well. We’re more determined than ever to ensure that we can continue to provide a community-governed, non-profit alternative to the corporate platforms that threaten to capture, <a href="https://about.hcommons.org/2025/03/19/digital-preservation-in-a-time-of-disorder/">or even silence</a>, so much of the work that we care about.</p>
|
||
<p>Please be in touch as you carve your own paths forward, and let us know how we might help.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Writing Again</title>
|
||
<link href="https://kfitz.info/writing-again/" />
|
||
<updated>2025-03-18T13:22:43Z</updated>
|
||
<id>https://kfitz.info/writing-again/</id>
|
||
<content type="html"><p>It happened this weekend.</p>
|
||
<p>In the aftermath of turning in the final manuscript for <a href="https://www.press.jhu.edu/books/title/12787/leading-generously"><em>Leading Generously</em></a>, I <a href="https://kfitz.info/recalibrating-again/">promised myself</a> that I would not start working on a new writing project until I had some idea that absolutely would not leave me alone, that I'd instead spend at least a year reading as omnivorously as I could through the ideas of others and see whether anything worth saying surfaced. <a href="https://kfitz.info/reading/">Almost exactly a year later</a>, I was still delighting in the reading, but feeling the first glimmerings of an urge to write, if not with the focus of a project.</p>
|
||
<p>Right after the second blog post linked above, though, I ended up in my <a href="https://kfitz.info/new-jobs">new position</a> and my program of intensive reading and diffuse writing got utterly derailed. I figured it would be at least another year before things started to coalesce into a project.</p>
|
||
<p>But it happened this weekend. I'm not at all sure that the way I'm framing the idea is right, whether the idea itself will have legs, but I'm starting to do some noodling in a more purposeful fashion.</p>
|
||
<p>And I'm excited about the possibilities, for the first time in quite a while. The whole thing may yet fizzle, of course, but in a conversation yesterday I jokingly said something about quitting my day job and there was this immediate thought bubble that popped up saying &quot;and then you would have time to work on That New Project!&quot; And I felt a rush of excitement in the wake.</p>
|
||
<p>On the one hand, I take this as an encouraging sign: I really do want to work on this thing!</p>
|
||
<p>On the other, I recognize the temptations posed by the alluring project you don't have time for, and the ways that turning that project into your primary point of focus can take a lot of the shine off.</p>
|
||
<p>But right here, right now, I long for a writing project to really wrestle with. And so I'm looking forward to carving out the moments here and there to work on it, even if I don't quit my day job to do it.</p>
|
||
</content>
|
||
</entry>
|
||
<entry>
|
||
<title>Leading Generously, the Audiobook!</title>
|
||
<link href="https://kfitz.info/leading-generously-audiobook/" />
|
||
<updated>2025-02-18T13:39:29Z</updated>
|
||
<id>https://kfitz.info/leading-generously-audiobook/</id>
|
||
<content type="html"><p>I am delighted this morning to share the news that <em>Leading Generously</em> is now available as an <a href="https://www.audible.com/pd/Leading-Generously-Audiobook/B0DW9LHBL8?source_code=AUDFPWS0223189MWU-BK-ACX0-434650&amp;ref=acx_bty_BK_ACX0_434650_pd_us">audiobook</a>,<sup class="footnote-ref"><a href="https://kfitz.info/leading-generously-audiobook/#fn1" id="fnref1">[1]</a></sup> in addition to its <a href="https://www.press.jhu.edu/books/title/12787/leading-generously">print and e-book formats</a>! The audiobook is narrated by the amazing <a href="https://www.linkedin.com/in/kristin-aikin-salada-386a32">Kristin Aikin Salada</a>, who has posted a more enticing excerpt on her <a href="https://www.linkedin.com/posts/%F0%9F%8E%A4kristin-aikin-salada-386a32_we-put-people-first-say-so-many-employers-activity-7297457727751012352-B7vG?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAA8vjagBut77QdZiq1_BYQEcHrmB129syng">LinkedIn announcement</a> than the opening pages that Audible shares.<sup class="footnote-ref"><a href="https://kfitz.info/leading-generously-audiobook/#fn2" id="fnref2">[2]</a></sup></p>
|
||
<p>If you listen to the audiobook, I'd love to hear your thoughts. I'm thinking hard about the form that I might want my next project to take, and I'm wondering how thinking about that project as audio-first (whether audiobook or podcast) might affect my approach.</p>
|
||
<hr class="footnotes-sep">
|
||
<section class="footnotes">
|
||
<ol class="footnotes-list">
|
||
<li id="fn1" class="footnote-item"><p>The audiobook is also <a href="https://www.audible.co.uk/pd/Leading-Generously-Audiobook/B0DW9JDZZK">available in the UK</a>, and I assume elsewhere, though the link doesn't localize on its own. <a href="https://kfitz.info/leading-generously-audiobook/#fnref1" class="footnote-backref">↩︎</a></p>
|
||
</li>
|
||
<li id="fn2" class="footnote-item"><p>My friends at <a href="https://www.rawsignal.ca/">Raw Signal Group</a> might find the opening lines of her excerpt a bit familiar! Which raises an interesting question about citations in audiobooks. I know how that would be handled in an audio-first project, but the translation from print to audio isn't quite as conducive to sharing your sources. <a href="https://kfitz.info/leading-generously-audiobook/#fnref2" class="footnote-backref">↩︎</a></p>
|
||
</li>
|
||
</ol>
|
||
</section>
|
||
</content>
|
||
</entry>
|
||
</feed> |