Live and recent posts from across the Fediverse tagged #agplv3compliance, aggregated by home.social.
I have a complicated #opensource #AGPLv3Compliance question:
Let's say I bought a closed-source WordPress plugin for a public website.
Then, WordPress (or a fork) changed its license to AGPLv3 and I updated to that.
Does the AGPLv3 now apply to the proprietary plugin I purchased?
If not, under what circumstances would it trigger?
@ouvaton Je ne savais pas que le code source d'Overleaf soit sous l' #AGPL . Ce qui implique que chaque instance doit de façon *évidente* informer ses utilisateurs de cela : "a convenient and prominently visible feature" [0]
A coup d'oeil et par #SearXNG j'ai l'impression qu'Overleaf.com viole grossièrement l' #AGPLv3 . La licence est hyper-cachée.
#AGPLViolation #AGPLv3Compliance
[0] https://www.gnu.org/licenses/agpl-3.0.html
[1] https://www.overleaf.com
[2] https://search.ononoki.org/search?q=overleaf+agpl
[3] https://search.ononoki.org/search?q=overleaf+affero
Any license experts want to weigh in from a legal and moral perspective?
I want to be as close to Misskey compatible as I can with my database; the Misskey project has the actual SQL commands for initializing the database in the Misskey repo (seen here: https://github.com/misskey-dev/misskey/blob/develop/packages/backend/migration/1000000000000-Init.js and in other files).
If possible, I would like to use their SQL commands. Normally when I use other people's code, I try and fork to maintain history; however, in this case, I just want the queries. I also won't be hosting on GitHub.
Would it be appropriate for me to copy/paste the queries into my own file, mark the location where they're coming from to give credit (and include the original copyright, of course), then license (at least) that file as AGPL? Would I need to license the whole project as AGPL? I'm not opposed to that; I just want to make sure I'm as transparent as possible about where these queries and code are coming from.
(For the record, the plan is to embed them into Rust functions because I don't want to load SQL queries from arbitrary text files; that is, all the SQL I want to be run will be internal).
#openSource #gpl #agplv3 #agplv3Compliance #misskey #sql #openSourceLicense #licensing
My (animal) predator alert software using camera surveillance is licensed under #AGPLv3
Can I or other people walking in front of the camera, demand a copy of the source code?
Does having your (visual) information processed by the software, count as interacting with the software through the internett?
https://gitlab.com/papiris/predator-detect-and-notify
#AfferoGPL
#AGPLv3Compliance
@mjg59 @jenniferplusplus @blogdiva
Do not #Copyleft licences, like #GPLv3, work by ensuring that **any** software that includes the FOSS code be #FOSS also?
What the above describes is #softwareTheft, right?
For example #MastodonDevs by allowing #HellaDoge to not provide source code for years, with a notification of such by us, are allowing software #theft, right?
> Fediverse has NOTHING to do with cryptocurrency
True, but #Mastodon however has been failing to enforce the #AGPLv3Compliance against apparent software thieves at #HellaDogeDotCom.
We have been calling for compliance for a long time now.
Difficult to know for sure whether some #collusion between #memecoin peddlers and a #MastodonDev exists.
Dunno.
> Appears on the scene to take control of fedi at some might say a very sensitive and opportune time,
> Gets a disproportionate amount of funds to develop fedi software,
> continues to not enforce #AGPLv3Compliance against #HellaDoge.com,
> Magically comes to support #antiFeatures like forced #javascript, Explore Tab, showing interaction counts, etc
> #JoinMastodon.com is CloudFlare,
> But says 'no' to #ventureCapital out of #SiliconValley.
Hmm.
@Gargron
@witchescauldron
We need to retain what'll keep Fediverse ethical.
The #infiniteScroll, javascript timeline appears to be forced upon users, with no way to enjoy the previous JS-free interface. This exposes users to #tracking.
To those opposing #Muskrat, mastodon team still don't enforce #copyLeft on a #dogecoin-pumping instance! (See #AGPLv3Compliance)
If a fork is the way forward, back-port security fixes to a version of #Mastodon that doesn't require JS and removing #2FA would be a start.
@Gargron
Thanks for responding,
That memecion server has been a highly visible perpetrator for a long time. All we ask is they be served the same compliance notice as TruthSocial. Picking and choosing who we enforce the license with will not fly in any future legal preceding.
We must nip this in the bud, the next weeds will be worse.
This should not be controversial.
1/2
#AGPLv3Compliance @eric @Gargron @emergeheart @sadiedoreen @KK0000000000 @lohang @atomicpoet @BillySmith @Suiseiseki