…[the group] has claimed responsibility for similar DDoS attacks on the likes of eBay’s Japan and US divisions, as well as BlueSky in just the past month alone.

Why the group is targeting London-based Canonical remains unclear and no reason was given via its Telegram channel. It is presumably because Ubuntu is one of the most popular Linux distros.

He’s talking about a physical object, something you have on your desk that you can pick up and prove your identity to the person on the other end of the video call.

Reminds me of the ‘totems’ in Inception, except they were to prove to yourself you were not in a dream.

I mention https://lemmy.ca/c/linuxphones in case you’ve not found it already. It’s not like an authoritive, central forum where everyone goes but maybe it’s a start.

The danger being raised with the licensing is that you can’t license something if you’re not considered to be the author. There are growing examples of courts and lawmakers determining AI output to be public domain:

The US Supreme Court recently refused to reconsider Thaler v. Perlmutter, in which the plaintiff sought to overturn a lower court decision that he could not copyright an AI-generated image. This is an area of ongoing concern among the defenders of copyleft because many open source projects incorporate some level of AI assistance. It’s unclear how much AI involvement in coding would dilute the human contribution to the extent that a court would disallow a copyright claim.

https://www.theregister.com/2026/03/06/ai_kills_software_licensing/

This is an evolving, global situation and hard to know what to do right now. I think what you’ve got is fine though - you’ve made it clear your intention is to license with AGPL. It’s just that depending on the jurisdiction it might be public domain instead.

This is another reason to be clear about the use of AI in the README so your users can make an informed decision.