daniel:// stenberg://I looked at the first ten minutes of the GitHub Universe intro yday and the frequency of AI getting mentioned exhausted my ears immediately and I had to shut down the stream and go do something useful. For health reasons.
nebby 
@bagder why do you still host your code on microsoft github then?
@banaanihillo easy: because it is the best available option for us.
@bagder ah, well, i guess we have fundamentally different meanings for the word best then 
@banaanihillo best for our case:
1. reach - almost everyone has a GitHub account and know how to work with it
2. CI performance. We do almost 200 CI jobs per commit. No other hosting sponsors us with that.
3. support. I get excellent support and have good communication with GitHub for whenever that is needed
@bagder all very valid points, but with some counterarguments too,
1. reach could be even better if you had, say, a self hosted git forge and a codeberg mirror too, and encouraged email patches too, instead of being locked into one proprietary unethical provider - i mean, if *almost* everyone has a microsoft github account, surely **everyone** has an email account, right?
2. forgejo actions seem a pretty valid alternative to that these days, but unfortunately i don't know enough of the details to suggest if it would be considered *better*, *equal*, what have you - if it's about money, yes, completely understandable! if it's about performance, the point could be moot?
3. double edged sword, i guess. you get the corporate support, sure, but imagine the community support you'd be getting instead, if you were committed to fighting the corporate status quo instead
1. reach could be even better if you had, say, a self hosted git forge and a codeberg mirror too, and encouraged email patches too, instead of being locked into one proprietary unethical provider - i mean, if *almost* everyone has a microsoft github account, surely **everyone** has an email account, right?
2. forgejo actions seem a pretty valid alternative to that these days, but unfortunately i don't know enough of the details to suggest if it would be considered *better*, *equal*, what have you - if it's about money, yes, completely understandable! if it's about performance, the point could be moot?
3. double edged sword, i guess. you get the corporate support, sure, but imagine the community support you'd be getting instead, if you were committed to fighting the corporate status quo instead
@banaanihillo it seems you don't know the kids of today: they don't want to use email. Doing "email too" at the same level as over git forge is a high price to pay for the three users who prefer that. Plus self-hosting is a huge cost/timesink.
The CI performance is not a small thing. The sponsored jobs we run are worth thousands of USD/month.
@bagder yeah no don't get me wrong, i don't like email patches either, but i would still prefer it over the alternative of having to use microsoft's github ecosystem exclusively 
thank you for the discussion anyway, i really liked hearing your thoughts!
@banaanihillo we still have occasional patches provided over email and we take care of them as well. Like one every other month or so.