Fun fact about the license under which the Mastodon source code is published (AGPL) is that it requires any modifications to it to be published.
No secret sauce, no proprietary features possible. Which is why commercial companies hate this license.
Want to paywall "pro" features? You can, but anyone can take your code and run it on a different server for free.
Anyway, that's quite an interesting financial choice for Gab, a for-profit entity that sells "pro" features
Because Mastodon does not have a Copyright License Agreement (CLA) that contributors have to sign before submitting code, I am not the sole copyright holder of the Mastodon source code--rather, contributors keep rights to their parts. As such, violation of AGPLv3 is not just a violation of my own rights, but of all past contributors to Mastodon.
@Gargron Awesome! I've been wondering if anyone used the AGPL in practice. Good on you.
@Gargron Wonder if you could get around that with a sort of proxy. Like the requests go through a proxy with the "pro" stuff then hands it off to the original. Wouldn't be touching the sources that way.
@Gargron as far as I’m concerned, @dansup considered the same model to fund his Pixelfed instance, that’s a great model, because it also encourages people to set up their own instances and that’s what Gab devs say they are going to make as easy as possible (managed hosting of course, but installer was mentioned too afair)
@Gargron I mean, for more storage, not additional features
@Gargron the most goofy thing will be witnessing gab userbase tear itself apart over the pro features
@Gargron doesn't that imply it'll have to be re-implemented clean in the future anyways?
@kaniini @Gargron Actually, that was the problem Christoph Hellwig had in its attempt to sue VMware: The German court wasn't willing to believe Hellwig had created a significant part of the Linux kernel.
@Gargron if you want to set up the liberapay/catarse/etc. legal fund now let us know so we can start contributing for legal fees.
Taking the pro features and merging them into Mastodon would be the ultimate lol. (If they are worth it.)
right now: creating lists, verification, creating groups and bookmarking posts
develop.gab.com has mastodon lists in its free version, verification is going to be a pro thing, there’s a PR for bookmarks on tootsuite/mastodon, I’m curious about the groups
that’s more of a way to support your favourite platform
they stated they are going to PR their improvements
@MonkeyDRufi I could explain it more clearly
@Gargron lol shut the fuck up gargron u never enforced that shit for garbage like counter.social I doubt you'll start now
@Gargron for profit social media in general is destined to end up having the same issues as youtube and facebook. Trying to make money by pleasing advertisers and commercial entities etc.
especially once they become publicly traded companies
@Gargron There are many, many freeloaders who will take anything that is seen as 'free' just because they can. If you make something 'free' but actually has some cost to you as the provider, you have to find some way of keeping the freeloaders out... If you can't keep them out, then (at any time) the commercial competition can freeload just to destroy you...
@Gargron hmm... AGPL doesn’t work if the SaaS product modifies Mastodon to, say, make an external request to a proprietary service. They’re obligated to release that modification, but not the service it calls out to. So, yeah, I am glad mastodon uses AGPL, but it’s not a panacea of protection.
@clacke @Gargron I am pretty sure that “external process munges database to add proprietary feature” is also totally possible, and likely a way around it. But yeah, you’re right. Maybe someone could argue that REST is just a distributed linker. Of course, the feature could be built to “link” against, say, a micro formats API, and the propriety one does more fancy...
@Gargron in fact you can host Gab yourself and have all the pro, verified and sponsor badges
@Gargron Yes, but then do something! You can… so well…
@Gargron that's a slippery slope. Proprietary "pro" features are never good for open source projects.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!