Philosopher John Searle has died.

We've now generated over $136M from free, open source software with @ghost.org 📈 $36M in revenue from managed hosting $100M in platform revenue for indie publishers The ecosystem is growing really quickly at this point, and really excited about where things are heading next:

As a short introduction to the project, Jan Ainali from Wikimedia Sweden has created a superb and lovely video that you should definitely watch. You will see the first ISCC bot in action :) www.commonsdb.org/blog/connect... 2/2

CommonsDB is an initiative funded by the European Commission to develop a prototype registry of public domain and openly licensed works. Commonsdb.org 1/2

Watch a short #FAIA explainer video to understand how users or platforms can provide, detect, resolve, and verify provenance and AI disclosure using ISCC fingerprints: youtu.be/MlRWYMuejVg?...

Users can choose from a set of clearly defined Attribution Flags that reflect the degree and nature of AI’s contribution. faia.liccium.com/technology/v...

FAIA now has a @bsky.app account. Please consider following: @faia.io FAIA – FAIR AI Attribution – an open, structured framework to disclose the role of artificial intelligence in content creation. faia.liccium.com

As generative AI becomes standard in content creation, transparency isn’t optional — it’s essential for trust and compliance. FAIA – FAIR AI Attribution offers a clear way to indicate if and how AI was involved. 🔗 faia.liccium.com

At the @wipo.int Conversation On Intellectual Property (IP) And Frontier Technologies (April 2025) we introduced the TDMAI.org protocol, developed by @liccium.com — a practical alternative to current AI opt-out methods. 1/4

Excellent! This is the way. – @liccium.com is providing content-based IDs / fingerprints (ISCC codes) to that ecosystem allowing authentic and original digital media to be digitally signed by self-sovereign accounts (DIDs) – or synthetic content to be properly labeled.

Funded by @ec.europa.eu, #CommonsDB creates a prototype registry for Public Domain/openly licensed works. Driven by Open Future, the initiative is a joint effort with @liccium.com @europeana.bsky.social @wikimediase.bsky.social and @ivir-uva.bsky.social. Learn more: www.commonsdb.org

We have provided an update for the Liccium documentation pages: docs.liccium.com 🤓 Visit liccium.com to become a test user of the Liccium app. We are getting closer to the launch 🚀

Third parties, such as AI model providers, can identify the user intent only by having access to the media assets by generating the ISCC, matching nearest neighbours and resolving the manifest. – We presented our approach at the IETF conference on AI control.

How it works: ISCC codes are generated from text or other media assets in blobs, the user intent is added to form a manifest, which is digitally signed and publicly declared on federated registries. Verifiable credentials bind did:key, did:plc and other attestations to provide proper attribution.

With @liccium.com we are working on a way to bind rights and metadata ("intend") to the actual content, resp. The content-derived ISCC (ISO 24138). These declarations may include AI preferences: tdmai.org. Your RFC could becime a Liccium plugin.

🆕 Check out CommonsDB, an @ec.europa.eu-funded project creating a prototype registry for public domain and open-licensed works. We are working with @liccium.com, @europeana.bsky.social, @wikimediase.bsky.social and @ivir-uva.bsky.social to strengthen #DigitalCommons. openfuture.eu/blog/open-fu...

🎉 Join the 2025 #PublicDomain celebrations on January 9! @paulk.bsky.social and @posth.me will present the upcoming EU Repository of PD and open-licensed works, alongside experts from @communia.bsky.social @creativecommons.bsky.social and other leading voices. Program: meemoo.be/en/training-...

We have changed the handle to @liccium.com. – DNS verification is a fairly simple, efficient and secure way to establish trust in handles and posts. For this reason, we use DNS verification as one method to ensure this level of attribution for content declarations on Liccium.com.

A publisher/repository could bind this information/update to the ISCC and make a public declaration. Then it this update for one version could potentially reach a user for all versions.

Thanks for your interest. I would not claim that @liccium.bsky.social prevents illegal misappropriation. However, it allows to inseparably bind your rights and licences to your content. So e.g. your creator name and copyright notice can't be stripped away (without using watermarking).