u/sukhoi77

One of the best things about Thunderbird has always been its extensions. They gave the community flexibility, customization, and features that made Thunderbird stand out from other mail clients.

But lately, many extensions are dying. Every major update seems to break compatibility, forcing developers to rewrite their add-ons again and again. Many smaller projects just don’t survive these transitions, and users are left without the tools they relied on.

I understand the need for progress, security, and modernization, but why does the development team keep breaking extension compatibility over and over? Couldn’t there be a more stable path forward that preserves the ecosystem instead of dismantling it piece by piece?

I’d really like to hear from others — do you feel the same way? And does anyone know if the Thunderbird team has explained why they keep pushing changes that make extensions unusable?

Many creators are reporting a worrying trend since Patreon rolled out the new update that floods members' feeds with posts from random creators they don't follow.

From a member's perspective, this is effectively spam. People subscribe to support the creators they chose—not to receive a feed filled with unsolicited recommendations.

Unfortunately, the consequence seems to be that many paid members are cancelling their subscriptions altogether because of the poor user experience. That hurts creators directly, especially smaller ones who depend on Patreon as a stable source of income.

If Patreon wants to help users discover new creators, it should be an opt-in feature, not something forced into everyone's feed. Members should have full control over what they see.

Is anyone else seeing an increase in cancellations since this change?

Has Patreon acknowledged the impact this update is having on creators?

Listenbox has been gone since last year.

So, what options are available to play YouTube audio in a podcast app?

Is PodTube Me a good choice?

And what other non–self-hosted solutions are available?

Hey folks,

I’ve been digging into the current requirements for signing commits/PRs, and I’m wondering about the workflow when using the GitHub web interface.

Right now, the recommended way to sign is something like:

Signed-off-by: Your Name <your.email@example.com>

This is required for DCO compliance and similar checks. But here’s the issue: when I use the GitHub web interface, I’m already logged in with my verified account. That login should be enough to validate the PR as coming from me. Forcing me to expose my email in the commit message is redundant and unsafe.

My argument:

• The web interface login is a strong identity check.
• Adding a plaintext email in the commit body doesn’t add meaningful security, it just leaks personal info.
• GitHub could treat a commit made via the web UI as implicitly signed, equivalent to the Signed-off-by line.

Has anyone found a way to handle this? Or is there a way to avoid exposing your email while still passing DCO checks when committing through the web interface?