Tootfinder

Opt-in global Mastodon full text search. Join the index!

@mgorny@social.treehouse.systems
2026-05-11 09:17:58

I've been talking before why money won't solve the burnout problem. But let's for a minute assume that you really wanted to help people maintaining #FreeSoftware by paying them. The problem is that:
1. You have to pay them a living wage.
While all monetary help is appreciated by developers, they need a living wage. Not "that should prevent you from starving to death" but the kind of money that can support a honest (but not lavish) lifestyle: pay the bills, feed your family, cover other living costs such as repairs, clothes, appliances, and let you save enough for future emergencies.
It's simple as that. If you can't do that, they're going to need a dayjob. If they're lucky, it won't collide with their #FLOSS work. If they're not, it will kill them. Or they'll fall somewhere in the middle, slowly burning out until they can neither maintain their projects, nor work.
2. You need to guarantee that the payouts will continue.
People need security. They're not going to stay unemployed, let alone quit their job or turn down a job offer, unless they either have good guaranties or substantial savings (or they're in a really bad shape and wouldn't be able to handle the job anyway). The job market is hell, and people just know that when the payments stop, they may not be able to find a job soon, let alone a good job. Even "passively" looking for a job can burn you out.
So yeah, one-off payments and pinky swears won't do. And it isn't even a matter of whether we can trust you; it's a matter if you'll actually be able to continue paying us. And honestly, I don't really know how to solve that. Perhaps by paying up front, but for how long? Finding a job may take more than a year, finding a good job may be once-in-a-lifetime opportunity.
3. It can't end up being a job.
Perhaps most difficult of all, these payments can't really come with explicit obligations. I mean, that's the whole point: you want to support FLOSS, not turn it into a corporate project. You want the maintainer to remain free and enjoy the work. That is unlikely to happen if their livelihood is now dependent on your satisfaction. And even if it isn't, I for example would still feel indebted to whoever's paying me to do FLOSS, even if they really didn't expect anything in return, and would fall into a spiral of guilt-inflicted burnout if I failed to maintain the software satisfactorily.
#OpenSource

@jswright61@ruby.social
2026-05-23 12:59:09

iOs 26.5 (latest). I have chosen to have messages from unknown callers segregated to their own list. Why are you showing this badge on the list selector glyph. For almost 20 years you’ve trained me that badges warrant my attention. In this case I have expressly indicated I don’t want to know about these. So why are you brining it to my attention?
If I’m expecting a message and I don’t see it, trust me, I’ll seek it out. Until then, let it die in obscurity.

Screenshot of a cropped (showing top) iOs 26.5 messages screen. There is a red arrow and the word “WHY?” Pointing at the menu glyph in the upper right of the screen showing the numeral one inside a blue bubble at about 2 O’Clock on the glyph.
Screenshot of iOs Settings App in the Apps -> Messages screen. A red oval draws attention to the Unknown Senders section and encircles the following text. “Hide notifications and move messages to the Unknown Senders list.