Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://techpolicy.social/users/maarten/statuses/113514423810601502">Maarten Aertsen (maarten@techpolicy.social)'s status on Monday, 25-Nov-2024 18:35:47 JST</a><a href="https://techpolicy.social/@maarten" title="maarten@techpolicy.social"><img src="https://gnusocial.jp/avatar/286545-48-20241010135303.webp" width="48" height="48" alt="Maarten Aertsen" style="position: absolute; left: 0; top: 0;">Maarten Aertsen</a></section><article><p><a href="https://techpolicy.social/tags/CyberResilienceAct" rel="tag">#CyberResilienceAct</a> published as Regulation EU 2024/2847 in the Official Journal of the EU: <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202402847" rel="nofollow noreferrer">https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202402847</a> <br>Full application at 11 December 2027, reporting obligations at 11 September 2026.</p><p>I wrote on the implications for <a href="https://techpolicy.social/tags/opensource" rel="tag">#opensource</a> and <a href="https://techpolicy.social/tags/foss" rel="tag">#foss</a> in the past, based on last year’s FOSDEM content, including resources by others:<br><a href="https://blog.nlnetlabs.nl/what-i-learned-in-brussels-the-cyber-resilience-act/" rel="nofollow noreferrer">https://blog.nlnetlabs.nl/what-i-learned-in-brussels-the-cyber-resilience-act/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4065705#notice-7945149">In conversation</a><time datetime="2024-11-25T18:35:47+09:00" title="Monday, 25-Nov-2024 18:35:47 JST">about 2 days ago</time> <span>from <span><a href="https://techpolicy.social/@maarten/113514423810601502" rel="external" title="Sent from techpolicy.social via ActivityPub">techpolicy.social</a></span></span><a href="https://techpolicy.social/@maarten/113514423810601502">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: images.unsplash.com</div><h5><a href="https://blog.nlnetlabs.nl/what-i-learned-in-brussels-the-cyber-resilience-act/">What I learned in Brussels: the Cyber Resilience Act</a></h5><div> from <span>@nlnetlabs</span></div></header><div>I want to contribute to a shared understanding of how the CRA will most likely affect developers of open-source software.</div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: eur-lex.europa.eu</div><h5><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202402847">Regulation - 2024/2847 - EN - EUR-Lex</a></h5><div></div></header><div></div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Maarten Aertsen (maarten@techpolicy.social)'s status on Monday, 25-Nov-2024 18:35:47 JST Maarten Aertsen
#CyberResilienceAct published as Regulation EU 2024/2847 in the Official Journal of the EU: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202402847
Full application at 11 December 2027, reporting obligations at 11 September 2026.
I wrote on the implications for #opensource and #foss in the past, based on last year’s FOSDEM content, including resources by others:
https://blog.nlnetlabs.nl/what-i-learned-in-brussels-the-cyber-resilience-act/
In conversationabout 2 days ago from techpolicy.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: images.unsplash.com
  What I learned in Brussels: the Cyber Resilience Act
  from @nlnetlabs
  I want to contribute to a shared understanding of how the CRA will most likely affect developers of open-source software.
2. Domain not in remote thumbnail source whitelist: eur-lex.europa.eu
  Regulation - 2024/2847 - EN - EUR-Lex

Public

Embed Notice

HTML Code

Corresponding Notice