#gplv2 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gplv2, aggregated by home.social.
-
#Perplexity does not let you export your data, but if you live in #Europe, you can request it anyway appealing to the #GDPR.
It takes over a month to have your data, but once you do... you notice that they give you a json, an excel file, and an assets directory.
My wanted use case, was to have the conversations in a readable format, and in particular, wanted to import some of them into my #Obsidian vault.
Have so generated a #script to convert these exports into #markdown files.
Unfortunately, they do not give us the references used to generate the responses on the GDPR export... which are present when exporting from the web interface. Massively disappointed on that... It's one of the main reasons why I use their service... references 😅 have so made the script remove those empty links`[n]`.
The script was created making massive use of #AI #LLM, but it works, and have made it so it is an easily usable script. It uses the `uv` #python package manager.
It's on version 0.0.1 so super #experimental, but has already converted successfully all my 626 notes. (except for assets, need to work on that part)
feel free to clone it, modify it, improve it 🙂 The license is #GPLv2 . #FOSS #FLOSS
-
#Perplexity does not let you export your data, but if you live in #Europe, you can request it anyway appealing to the #GDPR.
It takes over a month to have your data, but once you do... you notice that they give you a json, an excel file, and an assets directory.
My wanted use case, was to have the conversations in a readable format, and in particular, wanted to import some of them into my #Obsidian vault.
Have so generated a #script to convert these exports into #markdown files.
Unfortunately, they do not give us the references used to generate the responses on the GDPR export... which are present when exporting from the web interface. Massively disappointed on that... It's one of the main reasons why I use their service... references 😅 have so made the script remove those empty links`[n]`.
The script was created making massive use of #AI #LLM, but it works, and have made it so it is an easily usable script. It uses the `uv` #python package manager.
It's on version 0.0.1 so super #experimental, but has already converted successfully all my 626 notes. (except for assets, need to work on that part)
feel free to clone it, modify it, improve it 🙂 The license is #GPLv2 . #FOSS #FLOSS
-
#Perplexity does not let you export your data, but if you live in #Europe, you can request it anyway appealing to the #GDPR.
It takes over a month to have your data, but once you do... you notice that they give you a json, an excel file, and an assets directory.
My wanted use case, was to have the conversations in a readable format, and in particular, wanted to import some of them into my #Obsidian vault.
Have so generated a #script to convert these exports into #markdown files.
Unfortunately, they do not give us the references used to generate the responses on the GDPR export... which are present when exporting from the web interface. Massively disappointed on that... It's one of the main reasons why I use their service... references 😅 have so made the script remove those empty links`[n]`.
The script was created making massive use of #AI #LLM, but it works, and have made it so it is an easily usable script. It uses the `uv` #python package manager.
It's on version 0.0.1 so super #experimental, but has already converted successfully all my 626 notes. (except for assets, need to work on that part)
feel free to clone it, modify it, improve it 🙂 The license is #GPLv2 . #FOSS #FLOSS
-
#Perplexity does not let you export your data, but if you live in #Europe, you can request it anyway appealing to the #GDPR.
It takes over a month to have your data, but once you do... you notice that they give you a json, an excel file, and an assets directory.
My wanted use case, was to have the conversations in a readable format, and in particular, wanted to import some of them into my #Obsidian vault.
Have so generated a #script to convert these exports into #markdown files.
Unfortunately, they do not give us the references used to generate the responses on the GDPR export... which are present when exporting from the web interface. Massively disappointed on that... It's one of the main reasons why I use their service... references 😅 have so made the script remove those empty links`[n]`.
The script was created making massive use of #AI #LLM, but it works, and have made it so it is an easily usable script. It uses the `uv` #python package manager.
It's on version 0.0.1 so super #experimental, but has already converted successfully all my 626 notes. (except for assets, need to work on that part)
feel free to clone it, modify it, improve it 🙂 The license is #GPLv2 . #FOSS #FLOSS
-
To all Linux aficionados
Ah, for fuck's sake ....read....read....and importantly understand the implications....
cc: Linus Torvalds ....👍 ...you rock!!
-
To all Linux aficionados
Ah, for fuck's sake ....read....read....and importantly understand the implications....
cc: Linus Torvalds ....👍 ...you rock!!
-
To all Linux aficionados
Ah, for fuck's sake ....read....read....and importantly understand the implications....
cc: Linus Torvalds ....👍 ...you rock!!
-
To all Linux aficionados
Ah, for fuck's sake ....read....read....and importantly understand the implications....
cc: Linus Torvalds ....👍 ...you rock!!
-
To all Linux aficionados
Ah, for fuck's sake ....read....read....and importantly understand the implications....
cc: Linus Torvalds ....👍 ...you rock!!
-
Endlich führt die Uni #WireGuard über #EduVPN ein – und wir sind sehr begeistert! 🎉 Danke an das URZ, dass die Uni aus der #Cisco‑ASA‑Monopol‑Abhängigkeit löst und damit mehr Sicherheit & #Freiheit für uns Studis schafft. Open‑Source‑Lösungen stärken Transparenz und #Unabhängigkeit. 🙏🚀
#ciscoASA #CVE202520333 #CVE202520362 #StaySafeOnline #SecurityAwareness #UniVPN #CampusNetwork #GPLv2 #URZ #AntiMonopoly
-
Endlich führt die Uni #WireGuard über #EduVPN ein – und wir sind sehr begeistert! 🎉 Danke an das URZ, dass die Uni aus der #Cisco‑ASA‑Monopol‑Abhängigkeit löst und damit mehr Sicherheit & #Freiheit für uns Studis schafft. Open‑Source‑Lösungen stärken Transparenz und #Unabhängigkeit. 🙏🚀
#ciscoASA #CVE202520333 #CVE202520362 #StaySafeOnline #SecurityAwareness #UniVPN #CampusNetwork #GPLv2 #URZ #AntiMonopoly
-
Endlich führt die Uni #WireGuard über #EduVPN ein – und wir sind sehr begeistert! 🎉 Danke an das URZ, dass die Uni aus der #Cisco‑ASA‑Monopol‑Abhängigkeit löst und damit mehr Sicherheit & #Freiheit für uns Studis schafft. Open‑Source‑Lösungen stärken Transparenz und #Unabhängigkeit. 🙏🚀
#ciscoASA #CVE202520333 #CVE202520362 #StaySafeOnline #SecurityAwareness #UniVPN #CampusNetwork #GPLv2 #URZ #AntiMonopoly
-
Endlich führt die Uni #WireGuard über #EduVPN ein – und wir sind sehr begeistert! 🎉 Danke an das URZ, dass die Uni aus der #Cisco‑ASA‑Monopol‑Abhängigkeit löst und damit mehr Sicherheit & #Freiheit für uns Studis schafft. Open‑Source‑Lösungen stärken Transparenz und #Unabhängigkeit. 🙏🚀
#ciscoASA #CVE202520333 #CVE202520362 #StaySafeOnline #SecurityAwareness #UniVPN #CampusNetwork #GPLv2 #URZ #AntiMonopoly
-
Endlich führt die Uni #WireGuard über #EduVPN ein – und wir sind sehr begeistert! 🎉 Danke an das URZ, dass die Uni aus der #Cisco‑ASA‑Monopol‑Abhängigkeit löst und damit mehr Sicherheit & #Freiheit für uns Studis schafft. Open‑Source‑Lösungen stärken Transparenz und #Unabhängigkeit. 🙏🚀
#ciscoASA #CVE202520333 #CVE202520362 #StaySafeOnline #SecurityAwareness #UniVPN #CampusNetwork #GPLv2 #URZ #AntiMonopoly
-
In one hour, there will be a hearing in the VIzio law suit!
It's about a motion VIzio made, asking the court to rule (without any discussion at trial) that there is no installation right in #gplv2. The "tentative" ruling published this morning denies VIzio's request! The parties will discuss further at the hearing to see if the tentative becomes final.
If you're comfortable using proprietary software (zoom via browser), you can watch:
https://occourtsapp.occourts.org/aci/checkin-results?dept=C33
-
In one hour, there will be a hearing in the VIzio law suit!
It's about a motion VIzio made, asking the court to rule (without any discussion at trial) that there is no installation right in #gplv2. The "tentative" ruling published this morning denies VIzio's request! The parties will discuss further at the hearing to see if the tentative becomes final.
If you're comfortable using proprietary software (zoom via browser), you can watch:
https://occourtsapp.occourts.org/aci/checkin-results?dept=C33
-
In one hour, there will be a hearing in the VIzio law suit!
It's about a motion VIzio made, asking the court to rule (without any discussion at trial) that there is no installation right in #gplv2. The "tentative" ruling published this morning denies VIzio's request! The parties will discuss further at the hearing to see if the tentative becomes final.
If you're comfortable using proprietary software (zoom via browser), you can watch:
https://occourtsapp.occourts.org/aci/checkin-results?dept=C33
-
In one hour, there will be a hearing in the VIzio law suit!
It's about a motion VIzio made, asking the court to rule (without any discussion at trial) that there is no installation right in #gplv2. The "tentative" ruling published this morning denies VIzio's request! The parties will discuss further at the hearing to see if the tentative becomes final.
If you're comfortable using proprietary software (zoom via browser), you can watch:
https://occourtsapp.occourts.org/aci/checkin-results?dept=C33
-
In one hour, there will be a hearing in the VIzio law suit!
It's about a motion VIzio made, asking the court to rule (without any discussion at trial) that there is no installation right in #gplv2. The "tentative" ruling published this morning denies VIzio's request! The parties will discuss further at the hearing to see if the tentative becomes final.
If you're comfortable using proprietary software (zoom via browser), you can watch:
https://occourtsapp.occourts.org/aci/checkin-results?dept=C33
-
This song is released under the GPL-2.0 license as part of the Battle for Wesnoth game and the music is located at
https://github.com/wesnoth/wesnoth/tree/master/data/core/music
Also described at:
https://wiki.wesnoth.org/Available_Music
Title:
Battle EpicAuthor:
Doug Kaufmanofficial filename:
battle-epic.oggIf you like this song maybe you want to follow @wesnoth
#wesnoth #WesnothMusic #GameMusic #music #GPLv2 #soundtrack #WesnothSoundtrack #FediMusic #DougKaufman #BattleEpic
-
I wrote to the address in the #GPLv2 license notice and received the #GPLv3 license | Mendhak / Code
-
I wrote to the address in the #GPLv2 license notice and received the #GPLv3 license | Mendhak / Code
-
I wrote to the address in the #GPLv2 license notice and received the #GPLv3 license | Mendhak / Code
-
真的有人寄信要 GPL 授權的 copy...
Hacker News 上看到 2022 年的文章：「I wrote to the address in the GPLv2 license notice (2022) (mendhak.com)」，原文在「I wrote to the address in the GPLv2 license notice and received the GPLv3 license」。 作者在 GPLv2 看到這段： You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 5…
#copy #fsf #gnu #gpl #gplv2 #gplv3 #hard #license #mail #public
-
真的有人寄信要 GPL 授權的 copy...
Hacker News 上看到 2022 年的文章：「I wrote to the address in the GPLv2 license notice (2022) (mendhak.com)」，原文在「I wrote to the address in the GPLv2 license notice and received the GPLv3 license」。 作者在 GPLv2 看到這段： You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 5…
#copy #fsf #gnu #gpl #gplv2 #gplv3 #hard #license #mail #public
-
I wrote to the address in the GPLv2 license notice
https://code.mendhak.com/gpl-v2-address-letter/
#HackerNews #GPLv2 #OpenSource #SoftwareLicensing #HackerNews #TechCommunity #GPL
-
I wrote to the address in the GPLv2 license notice
https://code.mendhak.com/gpl-v2-address-letter/
#HackerNews #GPLv2 #OpenSource #SoftwareLicensing #HackerNews #TechCommunity #GPL
-
I wrote to the address in the GPLv2 license notice
https://code.mendhak.com/gpl-v2-address-letter/
#HackerNews #GPLv2 #OpenSource #SoftwareLicensing #HackerNews #TechCommunity #GPL
-
Have the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
-
Have the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
-
Have the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
-
Have the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
-
Have the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
-
We wonder if anyone is up for the challenge of figuring out how to repurpose the new NPU chips for simulating DNA structures and other interlinked bioinformatics simulation tasks instead of "AI" LLMs...
#dna #bioinformatics #bioinformatic #transhumanism #technology #tech #science #npu #simulation #freedomofform #opensource #gnugpl #gplv2 #biohacking
-
@OS1337 Honestly, it really looks like your description is skewed in a very anti-GPL way... ugh...
> Interestingly, all the people that say "#Copilot is violating my #Copyright!" and fanboy #BusyBox's hamfisted approach to #GPLv2 enforcement are really quiet when it comes to enforcing #GPLv2 against #RedHat or #grsecurity...
Not true.
- For Red Hat, they are allowed to sell copies - See: https://www.gnu.org/licenses/gpl-faq.html#DoesTheGPLAllowMoney
- For grsecurity, people have complained... a lot. -
Interestingly, all the people that say "#Copilot is violating my #Copyright!" and fanboy #BusyBox's hamfisted approach to #GPLv2 enforcement are really quiet when it comes to enforcing #GPLv2 against #RedHat or #grsecurity...
#NotLegalAdvice but maybe it's because only those that bought the final product are entitled to the #SourceCode and #learning isn't #CopyrightInfringement because otherwise we'd all be lifelong #DebtPeons to #Schoolbook- & #Textbook #authors or rather their Copyright-holding #publishers!
https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/
-
@geraldew @RTP @linux @torvalds @landley
The whole #GPL & #GPLv2 issue for example makes it basically illegal to build a #Linux kernel that can boot straight from #ZFS because #OpenZFS's code inherited from #OpenSolaris (now #illumos) is under #CDDL and thus when you install zfs-#dkms it gives you a big warning saying 'this is basically illegal so we've to make it a loadable module instead'...
And that's just out of the top of my head...
-
@geraldew @RTP @linux @torvalds @landley
The whole #GPL & #GPLv2 issue for example makes it basically illegal to build a #Linux kernel that can boot straight from #ZFS because #OpenZFS's code inherited from #OpenSolaris (now #illumos) is under #CDDL and thus when you install zfs-#dkms it gives you a big warning saying 'this is basically illegal so we've to make it anloadable module instead'...
-
@geraldew @RTP @linux @torvalds @landley
The whole #GPL & #GPLv2 issue for example makes it basically illegal to build a #Linux kernel that can boot straight from #ZFS because #OpenZFS's code inherited from #OpenSolaris (now #illumos) is under #CDDL and thus when you install zfs-#dkms it gives you a big warning saying 'this is basically illegal so we've to make it a loadable module instead'...
And that's just out of the top of my head...
-
@geraldew @RTP @linux @torvalds @landley
The whole #GPL & #GPLv2 issue for example makes it basically illegal to build a #Linux kernel that can boot straight from #ZFS because #OpenZFS's code inherited from #OpenSolaris (now #illumos) is under #CDDL and thus when you install zfs-#dkms it gives you a big warning saying 'this is basically illegal so we've to make it anloadable module instead'...
-
@geraldew @RTP I think #Linux being #GPLv2 is good.
Would a lot of people prefer it to be #BSD?
Yes, myself included.Are some neckbeards angry it's #GPLv2only and not #GPLv3 or #AGPLv3?
Yes, but I don't think they matter beyond needing to quarantine them for their toxicity.
https://www.youtube.com/watch?v=R2SKenHRhMgFact is: @linux is a good project and solid product as well, and @torvalds managed to get both businesses and individuals behind it, resulting in a very versatile common denominator of kernel.
That's why I chose if for #OS1337...
-
@geraldew @RTP I think #Linux being #GPLv2 is good.
Would a lot of people prefer it to be #BSD?
Yes, myself included.Are some neckbeards angry it's #GPLv2only and not #GPLv3 or #AGPLv3?
Yes, but I don't think they matter beyond needing to quarantine them for their toxicity.Fact is: @linux is a good project and solid product as well, and @torvalds managed to get both businesses and individuals behind it, resulting in a very versatile common denominator of kernel.
That's why I chose if for #OS1337...
-
@geraldew @RTP I think #Linux being #GPLv2 is good.
Would a lot of people prefer it to be #BSD?
Yes, myself included.Are some neckbeards angry it's #GPLv2only and not #GPLv3 or #AGPLv3?
Yes, but I don't think they matter beyond needing to quarantine them for their toxicity.Fact is: @linux is a good project and solid product as well, and @torvalds managed to get both businesses and individuals behind it, resulting in a very versatile common denominator of kernel.
That's why I chose if for #OS1337...
-
@geraldew @RTP I think #Linux being #GPLv2 is good.
Would a lot of people prefer it to be #BSD?
Yes, myself included.Are some neckbeards angry it's #GPLv2only and not #GPLv3 or #AGPLv3?
Yes, but I don't think they matter beyond needing to quarantine them for their toxicity.Fact is: @linux is a good project and solid product as well, and @torvalds managed to get both businesses and individuals behind it, resulting in a very versatile common denominator of kernel.
That's why I chose if for #OS1337...
-
The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).
-
The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).
-
The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).
-
The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).
-
The whole #OpenGameLicense debacle reminds me a lot of when version 3 of the #GNU #GPL came out, except that this time it's being done by a for-profit company that may make use of the new terms to go after other for-profit companies, so it's much more difficult to support the decision on intent (regardless of wording).
-
Wenn ihr zufällig auf der Suche nach einem erweiterbaren und flexibel einsetzbarem Lernmanagementsystem seid, das für den deutschsprachigen Raum und dessen Anforderungen entwickelt wurde und zudem freie Software ist, dann schaut euch doch mal Stud.IP an:
(Transparenzhinweis: Ich arbeite beruflich an Stud.IP)