#licensing

5 posts · Last used 5d

Back to Timeline
In reply to
@kkarhan@jorts.horse · 5d ago
@petrillic@hachyderm.io Worse is when you have folks in other juristictions use a "non-license" that isn't legally accepted like "#PublicDomain". #0BSD is by far the most permissible for #Software, but #licensing may have good reasons for beibg chosen.#CC0 is the closest to "public domain" (except the authorship disavowal part) for creative works (incl. writing)I'm not a lawyer and AFAIK there's only #downstream forward compatibility for #copyleft, so yeah, not easy if impossible!
0
0
0
In reply to
@kkarhan@jorts.horse · Apr 20, 2026
@nixCraft@mastodon.social And to add insult to injury: One cannot get new #OnPremise #licensing for these products! I hope @eucomission@ec.europa.eu do ban this shite or ban #Atlassian across the #EU for violating #GDPR.Cuz only #accountability and #consequences can help!
0
1
1
@cmars@infosec.exchange · Mar 01, 2026
Are there more software licenses like these out there? #opensource #licensing #NoAI GitHub - non-ai-licenses/non-ai-licenses: This repository contains software licenses that restrict software from being used in AI training datasets or AI technologies. https://github.com/non-ai-licenses/non-ai-licenses
3
0
2
@knoppix95@mastodon.social · Apr 18, 2026
FSF says OnlyOffice cannot use AGPLv3 to add extra fork restrictions, including mandatory branding retention in Euro-Office dispute. ⚖️ It argues AGPL guarantees downstream freedom, so forked versions may remove logos or attribution constraints beyond license terms. 🔓 @fsfe@mastodon.social @fsf@hostux.social @ONLYOFFICE@fosstodon.org 🔗 https://linuxiac.com/fsf-says-onlyoffice-cannot-use-agpl-to-restrict-forks/ #TechNews #FSF #FSFE #OnlyOffice #AGPLv3 #OpenSource #FOSS #Licensing #EU #Europe #EuroOffice #SoftwareFreedom #Forks #Copyleft #Legal #Linux #Transparency #DigitalRights
3
0
16
Boosted by Peter Cohen @flargh@mastodon.social
@universalhub@mastodon.online · Dec 04, 2025
1
0
0

You've seen all posts