Atlassian recently announced updates to how we use eligible customer data so we can deliver improved AI experiences for all customers. We designed this change with your security and privacy in mind - giving you control over your data contribution with new in-app settings and strengthening our existing privacy-preserving measures - so you can adopt AI confidently. These changes are reflected in our customer terms and will go into effect on August 17, 2026. As part of this change, we are: Updating how we use metadata and in-app data to improve apps and AI experiences for all customers. Introducing new data contribution settings in Atlassian Administration, so you can manage your organization’s contributions. Note: Initially, these settings will apply to data in Jira, Confluence, and Jira Service Management, including data in your Atlassian Platform apps (Rovo, Home, Teams, Projects, Assets, Goals, Analytics, and Administration). Strengthening our existing privacy‑preserving measures

Data contribution default settings follow the highest active plan in each Atlassian cloud organization. Some Atlassian cloud organizations are excluded from data contribution due to their compliance requirements, so default settings are not available. If your Atlassian organization has an active Enterprise plan, you can opt-out of metadata contribution. If your Atlassian organization’s highest active plan is Free, Standard, or Premium, metadata contribution is always on, and you’re not able to opt-out. All metadata is de-identified and aggregated before it is used to improve apps and experiences for all customers. We remove information that directly identifies individuals, such as name and email addresses. You can learn more about what metadata is, how it's protected, and how it's used in the documentation.

New policy from Atlassian:

Unless you opt out by August 17th 2026, data from Jira and Confluence will automatically be used for AI training. Some data cannot be opted out at all on some plans.

nøpe

I have been working on Obsidian Reader for over a year. I didn't want to share it until I felt it was good enough. It's finally there.

Consistent formatting for any article. Outline, syntax highlighting, nice footnotes, adjustable typography.

Runs locally. Just rules, no AI.

anyone? OwO

[sudo] password for natha: Are you on drugs?

sudo insults

WAIT HOW DID THIS GO VIRAL

also, that's how I got it: noctalia.dev/plugins/acti...

either way this is пиздец

data breach versus decentralized surprise backup

The newest version of Spark is too dangerous to release.

what's a guy gotta do to get verified around here

Activate NixOS in the bottom left corner of the screen

Activate NixOS

The application has remained stable since approximately 9 PM PDT, April 16 despite ongoing Distributed Denial-of-Service (DDoS) attacks. We have not seen any evidence of unauthorized access to private user data. We will provide our next update on or before the morning of April 20.

they are humans. they are experiencing issues because of a distributed attack...:

Zip. Zap. Zen. ⚡️

As someone who managed online communities for decades, companies like Doublespeed are fucking evil and should be burned out of the internet by a cleansing fire.

doublespeed | AI Content Automation Create and deploy AI-powered social media content across thousands of accounts. The leading platform for bulk TikTok posting, AI UGC creation, and social media automation.

doublespeed.ai got hacked. they were previously hacked in Dec 2025. unsurprisingly, a16z is their backer

news.ycombinator.com/item?id=4776...

this should *mostly* be done! let us know if you're having any issues 🙂‍↕️

honestly seeing GitHub do stacked PRs earlier than Forgejo/Codeberg is kinda wild to me

Red Hat is about to see what Streisand effect means

❄️

for context - 370 is way beyond obscure in niche Telegram scale

all I *know* I want is for you to not blame Alex for it - I know him personally, he is a person with a schedule of unrivaled intensity, and probably subscribe to @kotlinism Telegram if you speak Russian and enjoy Kotlin. I plan to develop the "general" Slavic Kotlin community there and I'm not alone

I think I'll probably be able to appear on camera (or at least with voice) for the first time during KotlinConf reaction stream, slated for May 21.

I don't know what to say... ask streamers for advice on how to stay calm? consult with experienced dev advocates like @vergauwensimon.bsky.social? (7)

a good amount of people from KMeta agreed to return to the work on Kotlin community under the Kotlinism brand once they figure their busy schedules out. Alex wanted to do more streams, but he couldn't. I am unlikely to match him in frequency, but I just so happen to write decent prose with wits! (6)

there was an idea of transferring the editor's role to everyone in the internal chat (which I was a part of this entire time) but I and @itzephir.bsky.social acted too quickly and independently. we created Kotlinism - an heir to Kotlin Meta that's more like a sibling than a child. (5)

the problem was consistency. Alex had not too much free time and too little content ideas, and I feel a little guilty for that because hey, I am the idea guy usually! so, on December 31, 2025, we got what turned out to be the last stream, and on April 1, 2026 the channel was officially dead. (4)

I fondly remember cheering for @y9san9.bsky.social and @demn.shy.cat at the first stream, where they tried initial Kotlin LSP release. the format of unscripted streams and poorly made green screens clicked with a lot of people - at its peak, @kotlinmeta hit 370 subscribers on Telegram. (3)

these two post mostly about Android - not Multiplatform, not JVM as an ecosystem, just Android.

so, in 2025, a group of people with @y9san9.bsky.social at the lead decided to change this, and so Sokol created Kotlin Meta. this resulted in a cute community of passionate Kotlin devs. (2)

something resonant happened in Russian-speaking #Kotlin community, I happen to stand near the center, and only now I understood what's going on.

so, in Ru-speaking Kotlin infospace, there are basically just two individual creators that capture most of the audience, and small obscure Telegrams. (1)

хто-небудь вбийте тимошенко

PDS MOOver ATProto account migration tool

I did not think I had a migration to #Blacksky in me tonight because I couldn't find documentation specific to custom domains but @baileytownsend.dev's PDS MOOver made it trivial, even with a custom domain. It really helped me level up my understanding of atproto, too.
pdsmoover.com/moover/black...