- Many anonymous users seeking help from open source developers fail to introduce themselves or disclose their identity, which is considered rude.
- Anonymity often leads to lack of accountability, such as abandoning bug reports after initial contact, wasting developers' time.
- Developers may be concerned about enabling unethical uses of their software (e.g., censorship infrastructure) without knowing the user's identity.
- Pseudonymous users with a community reputation (like @SwiftOnSecurity) are welcomed, as they contribute positively and are accountable.
- Corporations hiding their use of open source software hinder credibility and support; developers cannot offer free help without acknowledgment.
- Anonymous bug reports lack context, as seen in the Cloudflare-PowerDNS incident, leading to overlooked severity.
- Providing support in open, public forums benefits the community through search indexing and collective problem-solving, contrasting with private, anonymous requests.
- Genuine anonymity for safety (e.g., oppressed regimes) is recognized and supported, unlike most cases driven by convenience.
- The developer sets a policy: anonymous users without a visible track record will generally receive no help.