Atlassian Enables Default Data Collection for AI Training

Atlassian has implemented default data collection settings across its product suite to gather user data for AI model training. The change appears to be opt-out rather than opt-in, meaning data collection is active unless users explicitly disable it.
Key Details
The source material indicates this news was shared on Hacker News where it received significant engagement: 312 points and 75 comments. The discussion likely covers technical implementation details, privacy implications, and developer reactions to this policy change.
For developers using Atlassian products like Jira, Confluence, or Bitbucket, this means usage patterns, content interactions, and workflow data may be collected by default for AI training purposes. While the specific data types aren't detailed in the source, typical enterprise software telemetry includes feature usage frequency, error patterns, and interaction sequences.
This type of data collection is increasingly common in enterprise software as companies seek to improve AI features through real-world usage data. The opt-out nature raises questions about user consent and data privacy that are likely being discussed in the Hacker News comments.
📖 Read the full source: HN AI Agents
👀 See Also

AI Is Too Expensive: Hyperscalers Need $3 Trillion to Break Even
Hyperscalers have invested over $800B in AI capex, with $1T more planned for 2027. Microsoft alone spent ~$100B on OpenAI infrastructure, yet AI revenue covers only ~20% of its capex.

Claude Code v2.1.202: Dynamic Workflow Sizes, /review reverted, and 20+ fixes
Adds dynamic workflow sizing in /config, reverts /review to single-pass, fixes mTLS handshake failures, voice dictation loops, session resume with many git worktrees, and more.

Agent SDK vs Claude CLI: A user's perspective on the practical difference
A Reddit user questions the practical difference between the new Agent SDK for Claude and using Claude CLI to wire Opus 4.7 locally.

OpenClaw Early User Reports Telegram Issues, Agent Profile Hardcoding, and Session Reset Problems
A user's first three days with OpenClaw revealed several practical challenges: Telegram responses disappearing, agent profiles hardcoded to 'messaging' in source code, and Wacli becoming unavailable after session resets. The user ran micro tests on Docker, connected Telegram and Wacli, and set up a heartbeat.