Bountysource VS kwin-lowlatency

I used to use BountySource for this, but apparently they have not been honoring withdrawal requests and maybe are insolvent now. Gitcoin used to offer crypto bounties on bugfixes, but apparently they no longer do that and now only do "hackathons". I'm aware of many "bounty" sites, but they all are focused on finding security flaws not fixing specific issues.

It sounds like bountysource, but bountysource seems to have stopped paying bounties. Found these two links on the Wikipedia Article for Bountysource:

[CRITICAL] Bountysource Escrow, Complain @ dfpi.ca.gov, 18.05.2023 - https://github.com/bountysource/core/issues/1539

What is wrong with your support and cash out process?, 20.06.2021 -

Bountysource

Also obvious, and also only one way - sites where repository maintainers ask for feature implementation with a reward. There is no obvious winner here, both sites are good. - BountySource — payments in USD, seemingly more requests - Tip4Commit — payments in BTC, smaller amount of requests but payments are quite bigger.

There were a few companies that tried doing that, if I recall correctly https://www.bountysource.com/ was one of them (seems to still be active). I've been following the area and also tried to run a business in the area. My experience is that while there's some demand, it's either really small, or extremely difficult to grow.

I've pledged for fixes before. I think this is the service I used. https://www.bountysource.com/

There is a website called BountySource that I think is meant to do what you describe. I've never actually used it though.

Involved person commenting on it: https://github.com/tildearrow/kwin-lowlatency/blob/Plasma/5.23/unredirect.md

There's a kwin-lowlatency that has an xorg unredirection (in latest versions) and automatic kwin suspend in kubuntu LTS repo

There is already fullscreen unredirection implementation in kwin-lowlatency but it doesn't work good with multi-monitor and the dev isn't planning to upstream it soon afaik

Maybe attach a bounty offer to a specific feature request in the bug-tracking database, as these guys did: https://github.com/tildearrow/kwin-lowlatency/issues/56 ?

On the github page, the author said that kwin-lowlatency is not dead because of full-screen unredirection capabilities with eliminating stuttering without force composition pipeline (force composition pipeline increase latency and reduce performance I believe).

This didn't go away when disabling full screen unredirection. https://github.com/tildearrow/kwin-lowlatency/issues/95

Piggybacking here: Recent Kwin versions had lots of changes internally. If you're already on newest version, try Kwin-lowlatency or KwinFT.

You can read up on some stuff here regarding KDE: https://github.com/tildearrow/kwin-lowlatency

It used to be there as a feature: fullscreen unredirect. But due to some bugs the kwin team removed it. Last time I checked, https://github.com/tildearrow/kwin-lowlatency supported unredirection and also ran much smoother on high refresh rates.