Thread by @TfTHacker

1/ Showing appreciation for developers of open-source plugin developers

Gratitude! A powerful tool that helps those who express it and those who receive it.

Let me provide context. #TfT

2/ I have built plugins for many Tools for Thought. Obsidian, Craft, Roam, Readwise & Office (Excel, Word, SharePoint -- if you consider them to be TfT).

This opens doors to meeting many wonderful users and developers of Tools for Thought. I learn so much from each conversation.

3/ Many of us use plugins for our tools and don't think much about the effort that goes into them. We know there is a lot of effort, but we know we don't really know.

Let me give an example.

4/ One plugin I developed for Obsidian is called BRAT. It isn't important what it does, but I likely have over 100 hours of effort put into that project, along with occasional updates.

I built this tool for myself as a learning exercise, and well, I did it for the community.

5/ BRAT is not a big plugin compared to others that are very popular. I think @zsviczian, who develops VERY popular Excalidraw plugin, first for Roam, then for Obsidian, surely has 2 to 300 hundred hours into that project.

The point is: lots of love and hours go into a plugin.

6/ I am not personally looking for anything with this tweet, but I do worry long-term about the maintenance of plugins we come to depend on. Without support, it's difficult for plugin devs to justify continued long-term efforts.

So how can we show gratitude?

7/ First, think about the plugins you use frequently. Do those developers deserve your support or do you assume they know you appreciate their free labor?

Does your mate appreciate hearing you "love" them or do you assume they know that? Actions and Words show your appreciation.

8/ So how can you show gratitude? Let me list a few ways:

Idea 1: Publicly declare appreciation. For example, today @EleanorKonik posted a really nice tweet about SNW. I didn't ask for it, didn't expect it: but it sure made my day to wake up to these kind words.

https://twitter.com/EleanorKonik/status/1587935366476353538

9/ Idea 2: Star the project on GitHub

Many projects are hosted on GitHub. For example, the Kanban plugin for Obsidian. It has 1,200+ stars. Starring a project costs NO money but a minute of your time to open the page and click the star button. But dev's really appreciate that!

10/ Idea 3: Send them a DM with a word of gratitude. Many DM's I get start this way:

"Thank you for your great plugin. I use it every day. By the way the following is broken...."

So first, I am super happy when people reach out and let me know a plugin has an issue. But....

11/ This is an expression of gratitude with a request to do more work. Again, this is totally cool, and keep it coming.

Sometimes it's nice to send a message of gratitude that doesn't require the dev to do something. Only expectation is for them to enjoy the moment of gratitude.

12/ Finally, many devs do make it possible for us to $$$ contribute to their projects financially.

The shocking truth is most developers of large projects get very little financial support from the community.

What do you think about that? Is that fair?

13/ Idea 4: Buy these devs a cup of coffee, or even go further and support their projects regularly. Even giving 1 dollar or euro a month is a big deal, especially if many individuals help out.

14/ Understandably we can't support every project, and we may be unable to help financially. This is totally cool. but if we are in a position to help, we should.

Especially companies who benefit from community plugin work.

15/ I don't work with Roam anymore, but one of the great things they did recently was to create a plugin store in their app and do profit-sharing with their plugin authors. (Great idea, about 1+ years too late).

16/ Idea 5: Those who build Tools for Thought must support their developer and content creation community. These "free" resources are a big contributor to their success.

But is anything really free? there is always a cost at some point in the near or distant future.

17/ Questions these companies ask:
1) Can we provide creators with priority support to make their job easier?
2) Can we help offset costs with free access to our tools or other tools they need?
3) Can we build a distribution channel that provides them with financial incentives?

18/ Why am I talking so much about this: abandoned plugins are harmful to the community of a TfT Tool.

Frankly, I want a future where we are less dependent on plugins. But we will always need plugins and integrations.

If we lose the devs/creators behind these tools....

19/ we erode the future.

Lack of gratitude today produces a "tax" that will eventually need to be paid.

So let us show gratitude. There are many free ways to do this and some very practical and low costs ways to do this.