social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

489
active users

#AGPLv3Compliance

0 posts0 participants0 posts today
Replied in thread

@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] gnu.org/licenses/agpl-3.0.html
[1] overleaf.com
[2] search.ononoki.org/search?q=ov
[3] search.ononoki.org/search?q=ov

www.gnu.orgGNU Affero General Public License - GNU Project - Free Software Foundation

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

GitHubmisskey/packages/backend/migration/1000000000000-Init.js at develop · misskey-dev/misskey🌎 A completely free and open interplanetary microblogging platform 🚀 - misskey-dev/misskey
Replied in thread

@joeo10

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

Replied in thread

@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.

Replied in thread

@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