fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software.
If you wish to join, contact us for an invite.
@t3rr0rz0n3@feoh GPL doesn't stop corporations from using your code any way they want, they have more and better lawyers than you.
With BSD/MIT, you still own your software, the version you released is still free, and anyone who wants can use it. That's real user freedom, without petty jealousy.
Muhaha: #Kommunismus killt #AI Heißluftballon Geschäftsmodell. Wenn #China das weiterhin so clever spielt, ist absehbar, dass die #TechBros#Trump nutzen werden, um die #EU zu ihren Freudenhaus-Produkten zu zwingen. Nur wie wollen sie #MITLicense verbieten?
@Red The MIT license is not proprietary. Just because it isn't a copyleft license, which the MIT license is not, just because it explicitly has "Copyright" in its license text, which the MIT license does, it is not automatically proprietary and non-free.
The MIT license is compatible with the Debian Free Software Guidelines which means that software under the MIT license is allowed into main on Debian and not forced into non-free. It is approved both by the Free Software Foundation and the Open Source Initiative, and it is compatible with the GPL.
In other words, both Debian and the FSF have officially declared the MIT license a free license.
It is possible and legal by license to pass your MIT-licensed software on to your user community so they can maintain and develop it, and then for the new developers to re-license your MIT-licensed software under the GPL. Exactly this has happened to Friendica.
Mike Macgirvin knew that the Friendica community wanted to re-license Friendica under the GPL. It wasn't a secret. (Proof: the short-lived Free-Friendika fork from very early 2012 that was created for there to always be an MIT-licensed Friendika.)
Also, both the X Window System, the Wayland protocol and the Sway window manager are MIT-licensed. X11 actually has its own variant of the MIT license. curl is MIT-licensed. Both Gitea and GitLab are MIT-licensed. Linux From Scratch is MIT-licensed. The XMPP server Prosody is MIT-licensed. And Ruby on Rails, which Mastodon is built with, is MIT-licensed, too, as is Rust.
The MIT license allows for just the same liberties as all variantes of GPLv2 and GPLv3, but without the restrictions that make all GPL variants viral.
You may argue that the GPLv3 is literally the only free license that has ever existed because all derivatives of GPL-licensed material are automatically GPL-licensed themselves and therefore free software when published.
I'm more on the side that the MIT license is actually freer than any versions and flavours of the GPL because it does not have any such restrictions and grants more liberties.
But it was the intention of the creator, @Mike Macgirvin , for all his works to be under the MIT license. The current Hubzilla maintainers, @Mario Vavti and @Harald Eilertsen, certainly won't relicense Hubzilla under the GPL in any shape or form, otherwise they would have done that.
It isn't even worth doing so just to have code from Friendica. After all, Friendica's backend is vastly different from Hubzilla's. Friendica is based on a mixture of ActivityPub and its own DFRN whereas Hubzilla is based on Zot with ActivityPub available through an optional add-on. On Friendica, your account is your identity; it doesn't have Hubzilla's channel model, nor does it have nomadic identity.
Red came to exist by Mike forking Friendica and rewriting the whole thing against his new Zot protocol. Hubzilla hardly has any old Friendica code left over. So it's safe to assume that Friendica's code is incompatible with Hubzilla anyway.
Generally, there's nothing on Friendica that'd be worth taking over for Hubzilla. Not even themes because theming works entirely differently on Hubzilla.
Asking Mario and Harald to relicense Hubzilla under any form of the GPL is as likely to succeed as asking them to implement all kinds of proprietary Mastodon stuff to make Hubzilla more compatible with Mastodon and Mastodon apps:
also I have a hot take about copyright assignment CLAs. it's a bit of a meme in the FOSS community to not sign them because then your code can be proprietarized. but like, isn't contributing to an MIT-licensed (or any pushover license-licensed) project the same thing?
read "MIT-licensed" below as meaning any pushover/permissive license. Apache, BSD, etc. if you are very close to one of these options, but make an exception every once in a while for Reasons(tm), pick the option you're closest to instead of "voting down" (but leave a reply because I am SO interested in what folks do here)
Farei mais testes, mas a primeira impressão foi boa: permite tanto a captura de artigos inteiros como a de grifos feitos no navegador.
Dica: se você não usa Obsidian ou não quiser importar a nota para este app, saiba que o texto capturado fica no clipboard (área de transferência), com todas as marcações em Markdown! De maneira que você pode colar o texto no seu aplicativo favorito!
Infelizmente, ainda não permite anotações... Mas vamos com calma! ;-) Só o fato de ele ir direto para o Obsidian já é uma mão na roda, permitindo a manipulação total do texto!
" Kaspersky Unveils Scripts for Detecting Pegasus Spyware on iPhones "
#Kaspersky has developed scripts to detect #Pegasus, #Reign, and #Predator spyware on iPhones. These scripts, written in Python (100% Python according to GitHub), analyze the Shutdown.log file in the #iPhone's sysdiagnose archive for forensic artifacts indicative of these spywares. Infections leave traces in Shutdown.log, especially in the path "/private/var/db/". These scripts, available for #macOS, #Windows, and #Linux, simplify spyware detection by extracting, analyzing, and parsing Shutdown.log. Open-source and under an MIT license, you can find them on GitHub.
" Kaspersky Unveils Scripts for Detecting Pegasus Spyware on iPhones "
Kaspersky has developed scripts to detect Pegasus, Reign, and Predator spyware on iPhones. These scripts, written in Python (100% Python according to GitHub), analyze the Shutdown.log file in the iPhone's sysdiagnose archive for forensic artifacts indicative of these spywares. Infections leave traces in Shutdown.log, especially in the path "/private/var/db/". These scripts, available for macOS, Windows, and Linux, simplify spyware detection by extracting, analyzing, and parsing Shutdown.log. Open-source and under an MIT license, you can find them on GitHub.
Have you ever needed to download an insanely large #AGIS#basemap as a #png?
Maybe you need to make a print of a map on your AGIS server, but no longer have the original. Or maybe you want a really hi-res image for a film zoom effect.
Here's a tool to do just that.
It uses your public facing AGIS MapServer endpoint to download each tile, then assembles them into one large PNG image.
If you're writing open-source software, please do yourself and other software developers a favor and familiarize yourself with how software licensing works. As an Ubuntu Developer, much of my work involves auditing the source code licensing of various applications. Most of these applications have miserably complicated licensing situations, sometimes with licensing violations involved. I also occasionally run into licensing or copyright terms that an author probably didn't intend to specify, but that they did specify unambiguously nonetheless.
For instance, did you know that if you state that a file is "under the GPL license" without specifying what version, that means that the user of your file can use it under *any* version of the GPL they want to? Look at GPLv1 Section 7, GPLv2 Section 9, and GPLv3 Section 14 if you don't believe me. I found a file written in 2017 with these licensing terms. Did the author *mean* to do this? Probably not, they probably wanted to use GPLv3 (or maybe GPLv2). But since they didn't specify a version, I'm within my legal right to use this code under GPLv1's terms if I care to. I'm not going to do that since I have no interest in using this file for anything, but it goes to show you how a slip-up in your licensing specification can cause people to have rights or be free of restrictions you didn't want to give them or let them be free from.
Another (very very common) slip-up is for most of the source code in a repository to have license headers specifying GPLv2 *or later*, but with no repository-wide license specified in an AUTHORS or README file, and with a GPLv2 license in a LICENSE or COPYING file. What you probably *think* this does is license your program under GPLv2 or later, but what it *actually* does is give you a messy mixed-licensing situation with some files licensed GPLv2 only and some files licensed GPLv2 or later. Why? Because the default repository-wide license is GPLv2 as set by the LICENSE or COPYING file, and all of the headers that specify GPLv2 or later are overriding that default license.
You may think, "Why can't someone just infer that because most of the files are GPLv2 or later, that all of them are?" Great question! There's two answers. One, if you unambiguously specify something you didn't mean to specify, whatever you specified is what's legally binding. There's not room for "well that's what I said, but what I meant was..." in licensing. Secondly, many projects *actually use multiple licenses in one project* (for instance you'll have GPL, BSD-2-Clause, BSD-3-Clause, and MIT licenses all in one application). So how does one know if you just "accidentally" specified the wrong license, or if you meant to make a mixed-license application? They can't determine your intent with 100% certainty, so they have to obey what you said, *not* what you meant to say.
I am not a lawyer and this is not legal advice. This is just advice on how to help keep software developers from having headaches and problems reusing code.
️ 
#DeepSeek #v3 now sports an MIT license because who doesn't love yet another 641 GB of indistinguishable AI soup? 
Their README is emptier than a politician's promise, and it takes a $9,499 #Mac to run it at the blistering speed of 20 tokens per second—truly redefining "consumer-grade" technology. 
Microsoft opensources its 14B-parameter AI model, Phi-4, and its weights on Hugging Face under the MIT License! Released in December 2024, this move boosts accessibility for developers and researchers. 
#Microsoft #AI #OpenSource #Phi4 #HuggingFace #MITLicense #AIInnovation #TechNews
, for all his works to be under the MIT license. The current Hubzilla maintainers, @Mario Vavti and @Harald Eilertsen, certainly won't relicense Hubzilla under the GPL in any shape or form, otherwise they would have done that.
![Print de uma nota do Obsidian, mostrando um artigo importado cujo título é: "Archiving My Blog Posts in Obsidian". Há um retângulo verde destacando as propriedades (metadados) e setas indicando "source", "tags"
source: "https://jamierubin.net/2024/09/08/archiving-my-blog-posts-in-obsidian/"
author:
- "[[Jamie Todd Rubin]]"
published: 2024-09-08
created: 2024-11-11
description: "Lately, I have been working on a series of small archiving projects. I have been gathering 35 years of digital data, and organizing it locally, mostly in Obsidian. I’m working toward a single…"
tags:
- "clippings"
---
**Lately, I have been working** on a series of small archiving projects. I have been gathering 35 years of digital data, and organizing it locally, mostly in [Obsidian](https://jamierubin.net/category/practically-paperless/). I’m working toward a single, text-based archive that can serve as the source of a personal LLM that will take over the role of traditional search. I want to be able to converse with an LLM about everything and anything I have ever produced. Archiving is a first step in that process.
My most recent venture was to archive into Obsidian all of the blog posts I’ve written over the last 19+ years. I did this in two discrete steps:
1. Generate markdown files from the WordPress export of my blog.
2. Replace any markdown links to other blog posts with Obsidian-style links
After my cleaning process, which included de-duping posts (some early post [...]](https://cdn.bolha.us/bolhaprod/media_attachments/files/113/465/752/838/638/980/original/a8b9ef650448be36.png "Print de uma nota do Obsidian, mostrando um artigo importado cujo título é: \"Archiving My Blog Posts in Obsidian\". Há um retângulo verde destacando as propriedades (metadados) e setas indicando \"source\", \"tags\"
source: \"https://jamierubin.net/2024/09/08/archiving-my-blog-posts-in-obsidian/\"
author:
- \"[[Jamie Todd Rubin]]\"
published: 2024-09-08
created: 2024-11-11
description: \"Lately, I have been working on a series of small archiving projects. I have been gathering 35 years of digital data, and organizing it locally, mostly in Obsidian. I’m working toward a single…\"
tags:
- \"clippings\"
---
**Lately, I have been working** on a series of small archiving projects. I have been gathering 35 years of digital data, and organizing it locally, mostly in [Obsidian](https://jamierubin.net/category/practically-paperless/). I’m working toward a single, text-based archive that can serve as the source of a personal LLM that will take over the role of traditional search. I want to be able to converse with an LLM about everything and anything I have ever produced. Archiving is a first step in that process.
My most recent venture was to archive into Obsidian all of the blog posts I’ve written over the last 19+ years. I did this in two discrete steps:
1. Generate markdown files from the WordPress export of my blog.
2. Replace any markdown links to other blog posts with Obsidian-style links
After my cleaning process, which included de-duping posts (some early post [...]")
H3lium@infosec.exchange/:~# 
FREE PALESTINE 