Hi atomicpoet@atomicpoet.org, in that case I shall strive to be even more of a diva next time

dansup@mastodon.social I'm really glad we had the chance to chat about this topic. It's one of the most direct ways we can improve the day-to-day experience of a lot of fediverse users! cc jesseplusplus@mastodon.social

karenkeiller@indieweb.social young at heart

deadsuperhero@social.wedistribute.org ‍

jaz@toot.wales this is a fantastic resource. I'll be using it when I reach out to those local news orgs!

@mastodonmigration@mastodon.online while this is a known workaround, I don't think it's a tenable long-term solution. You can have "real decentralization" without the quirks, too.

@thisismissem@hachyderm.io ah understood. I didn't quite get how the fund worked, but it makes more sense now (and is much simpler—organizationally—for Nivenly!) I don't think we'll add exclusions for security fund recipients I would say, though, that one of the requirements has to be that the affected software accepts the vulnerability. Plenty of self-proclaimed "security researchers" have filed reports, and some go as far as to publish CVEs (against our own software!) without our permission. Quite the opposite of responsible disclosure.