Sign in

Liccium

@liccium.com
284 followers 1.7K following 10 posts

Liccium content certification – digitally sign your original creative works. Claim your content. Regain control. Protect your copyright. Register at liccium.com.

PostsRepliesMedia
Reposted by Liccium
Gabriella Nonino @gabriellanonino.com · 28/07/2026
This is great for anyone creating original content published on the net. Far more powerful than the standard © copyright symbol, it registers and declares you as the irrefutable owner of your work.
072
Liccium @liccium.com · 26/07/2026
What if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
liccium.leaflet.pub
From Personal Data Server to Personal Metadata Server
161
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 25/05/2026
Pope Leo XIV issues encyclical, ‘Magnifica humanitas: On Safeguarding the Human Person in the Time of Artificial Intelligence.’ Calls on AI developers to develop AI for good chatgptiseatingtheworld.com/2026/05/25/p...
chatgptiseatingtheworld.com
Pope Leo XIV issues encyclical, ‘Magnifica humanitas: On Safeguarding the Human Person in the Time of Artificial Intelligence.’ Calls on AI developers to develop AI for good
On the 135th anniversary of Rerum novarum, Pope Leo XIV issued an encyclical letter on ‘Magnifica humanitas: On Safeguarding the Human Person in the Time of Artificial Intelligence.’ While recogniz…
051
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 20/05/2026
Let me share with you the latest post by @mirkolorenz.bsky.social on DW Innovation that covers some of our recent work on content provenance and AI transparency. innovation.dw.com/articles/why...
innovation.dw.com
Why Content Needs a Fingerprint, Not Just a Watermark
Mirko Lorenz on how to prove what content is yours, how to declare what AI did to it, and how to set sovereign terms of usage.
001
Reposted by Liccium
FAIA – FAIR AI Attribution @faia.io · 21/03/2026
Do you like the icons/ flags? Certainly not just another contribution: FAIA – FAIR AI Attribution: faia.liccium.com The framework – developed by @liccium.com, Leiden University and the GO FAIR Foundation provides machine-readable vocabulary for AI involvement based on ISO and W3C standards.
112
Reposted by Liccium
FAIA – FAIR AI Attribution @faia.io · 09/03/2026
„𝗧𝗿𝗮𝗻𝘀𝗽𝗮𝗿𝗲𝗻𝘇 𝘄𝗶𝗿𝗱 𝘇𝘂𝗺 𝘇𝗲𝗻𝘁𝗿𝗮𝗹𝗲𝗻 𝗤𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝘀𝗺𝗲𝗿𝗸𝗺𝗮𝗹“ Vielen Dank an den Digital Publishing Report für die Gelegenheit, #FAIA – FAIR AI Attribution in einem Interview vorstellen zu dürfen. ai-at-media.de/de/2026/faia
ai-at-media.de
Transparenz wird zum zentralen Qualitätsmerkmal“
Sebastian Posth, Gründer von Liccium, über den FAIA-Standard zur strukturierten KI-Kennzeichnung in Verlagen.
012
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 26/02/2026
REPORT on copyright and generative artificial intelligence – opportunities and challenges www.europarl.europa.eu/doceo/docume...
europarl.europa.eu
REPORT on copyright and generative artificial intelligence – opportunities and challenges | A10-0019/2026 | European Parliament
REPORT on copyright and generative artificial intelligence - opportunities and challenges (2025/2058(INI)) Committee on Legal Affairs Rapporteur: Axel Voss
021
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 23/02/2026
Making digital signatures a standard practice for creators will take some time, but we're getting there. – First, we had to establish the ISO standard for the content fingerprinting / pHashing, because signing cryptographic hashes doesn't work for long form content. ISCC solves that. @liccium.com 1/
163
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 13/02/2026
Content use, monetisation, trust, and transparency start with robust, open, standardized content identification – without robustly identifiable digital assets, attribution, licensing, and compliance cannot be reliably automated or enforced across systems. ISCC (ISO 24138) provides the foundation.
001
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 13/02/2026
Entire communities of media and tech professionals are debating content provenance, rights and metadata, PIDs – yet often without addressing the basic question: what asset are we even talking about? ISCC (ISO 24138) addresses this "Asset-Vergessenheit" by providing the reference to the file.
101
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 09/01/2026
First Draft Code of Practice on Transparency of AI-Generated Content digital-strategy.ec.europa.eu/en/library/f...
digital-strategy.ec.europa.eu
First Draft Code of Practice on Transparency of AI-Generated Content
This first draft of the Code addresses key considerations for providers and deployers of AI systems generating content falling within the scope of Article 50(2) and (4).
012
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 31/12/2025
Instagram chief: AI is so ubiquitous 'it will be more practical to fingerprint real media than fake media' www.engadget.com/social-media... Liccium.com – Digitally sign (the fingerprints of) your original works! #ff @liccium.com
engadget.com
Instagram chief: AI is so ubiquitous 'it will be more practical to fingerprint real media than fake media'
Adam Mosseri offered a notably candid assessment on how AI is upending Instagram.
152
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 29/10/2025
My short, 4 min intervention is available, now: FAIA – FAIR AI Attribution: Flagging Synthetic Media Using Open Standards webcast.wipo.int/video/WIPO_I... Follow @faia.io and FAIA.liccium.com
webcast.wipo.int
WIPO Webcast
The WIPO Webcast is a portal for video conferences in live streaming and video on demand
012
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 16/08/2025
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
001
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 16/08/2025
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
commonsdb.org
CommonsDB
We are building a public registry for Public Domain and openly licensed works
101
Reposted by Liccium
FAIA – FAIR AI Attribution @faia.io · 29/06/2025
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?...
youtu.be
Detecting AI-Generated Content with Liccium: FAIA Plugin Demo
YouTube video by Liccium
022
Reposted by Liccium
FAIA – FAIR AI Attribution @faia.io · 29/06/2025
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...
Top-level FAIA flags: 
1) HCC
Human-Created Content;
2) AAE AI-Assisted Editing;
3) AAC AI-Assisted Contribution;
4) ACO AI-Human Co-Creation;
5) AGC AI-Generated Content
034
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 29/06/2025
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
faia.liccium.com
FAIR AI Attribution (FAIA) | FAIA – FAIR AI Attribution
001
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 13/06/2025
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
faia.liccium.com
FAIR AI Attribution (FAIA) | FAIA – FAIR AI Attribution
021
Liccium @liccium.com · 26/04/2025
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
tdmai.org
TDM·AI
Providing registry-based opt-out declarations for individual assets to providers of generative AI.
111
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 05/04/2025
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.
041
Reposted by Liccium
Open Future @openfuture.bsky.social · 18/03/2025
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
commonsdb.org
CommonsDB
We are building a public registry for Public Domain and openly licensed works
031
Liccium @liccium.com · 12/03/2025
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 🚀
docs.liccium.com
Introduction | Liccium
051
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 08/03/2025
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.
121
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 08/03/2025
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.
111
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 08/03/2025
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.
tdmai.org
TDM·AI
Providing asset-based opt-out declarations to providers of generative AI
111
Reposted by Liccium
Open Future @openfuture.bsky.social · 13/02/2025
🆕 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...
Introducing CommonsDB image with branded Open Future's background.
01210
Reposted by Liccium
Open Future @openfuture.bsky.social · 07/01/2025
🎉 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-...
meemoo.be
Public Domain Day in Europe
Mark your calendars for 9 January 2025, when the annual Public Domain Day is taking place in collaboration with international partners. More information will be available soon!
0167
Liccium @liccium.com · 30/11/2024
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.
031
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 12/11/2024
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.
012
Reposted by Liccium
Sebastian Posth 🇪🇺 @posth.me · 09/10/2023
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).
032