Third blog post on the proposed new Frontex Regulation
Critique of the level of human rights protection, by Mariana Gkliati and Marloes Streppel
https://eulawanalysis.blogspot.com/2026/11/bigger-frontex-smaller-fundamental.html
Search
9 results for “stevepeers”
-
-
Second blog post on the proposed new Frontex Regulation
Analysis of the proposed new role on returns to non-EU countries, by Salvo Nicolosi https://eulawanalysis.blogspot.com/2026/11/refashioning-frontex-and-return.html
-
Three blog posts on the proposed new Regulation on Frontex, the EU border control agency First of all, a critical overview, by Laura Salzano https://eulawanalysis.blogspot.com/2026/11/the-2026-recast-proposal-for-frontex.html
-
US and EU copyright law principles state that only a "natural person" may copyright their creative work.
When AI creates, does it own the copyright? No, it's not a natural person.
Can an AI company lay claim to the work you create using their tool? Yes. It doesn't mean they'll prevail, but can you afford legal defense?
How does this affect software foundations whose contributors warrant that they reassign title and rights of their contributions to the foundation?
Interesting times ahead.
-
Is your FOSS license not getting recognized by GitHub? Try using the tool that GitHub uses to detect your license, licensee.
https://licensee.github.io/licensee/
Apparently, reStructuredText headings are not ignored in its analysis. This is a remnant of when icalendar included its license in its documentation, a pattern that many projects in @plone and the Collective GitHub organization copy-pastad for over a decade.
https://github.com/collective/icalendar/issues/2064#issuecomment-6671612815
-
My take: disclosure of AI use has no relevance in this context. It's a waste of time and effort, and gives free advertising to corporations and their shareholders that will gladly take your money, and don't care about the negative impacts from the use of their product.
-
If you care about whether your AI-generated code is copyrightable, I urge you to read "Copyrightability of LLM-generated code: Can we license “vibe code” into Free Software?" https://fsfe.org/news/2026/news-20260825-01.html or watch the webinar "Copyrightability of LLM-generated code by FSFE" https://nlnet.nl/events/20261029/index.html
-
Documentarians can smell when AI wrote your technical documentation without you editing its output.
AI misuses and overuses "so" as a conjunction, resulting in run-on sentences where the sentence's first clause is neither directly related to nor causal to the second.
In most cases, it's better to use two shorter sentences and remove "so".
