Upon a cursory read, it sounds like you host a server and then relay all of your data through their centrally controlled system all while also pushing your account data to them.
I'm not sure they understand what "federated" means. Or rather, they know, but they're hoping we don't care.
Finally, a headline calling the tar sands what they are.
I quite like Thunderbird for this.
It's an interesting idea, but the differences between copyright and contract law present quite a hurdle.
Either you release something publicly, licensing it under certain conditions (you can use it this way, but not that), or you cut a contract with a 3rd party for them to use it a certain way -- something that only makes sense in a context where the wider public doesn't already have those rights, otherwise a contract would be unnecessary.
You see it in some Free software projects: they're licensed under something aggressive like the AGPL, but for a few you can buy a proprietary license. This of course limits community participation though, as to contribute, you must agree to these terms. I think React does something like this, forcing you to sign a contract to submit a patch.
He points out a number of problems that I'd like to see solved, so I'd love to hear his ideas, so long as they're similar in spirit to the goals of the FSF.
I'm not him, just someone sharing his story.
Yeah, the whole "you build it, you own it" thing sounds great until you're neck deep in it.
I use this chart when teaching Linux. I think it does a great job of showing Linux's "bazaar" vs. Windows' "cathedral".
cough npm,yarn,grunt,esbuild,webpack,parcel,rollup,lasso,rollup,etc.,etc.cough
I'm not saying that Python's packaging ecosystem isn't complicated, but to paint JavaScript as anything other than nightmare fuel just isn't right.
Honestly I don't care about this. I'd rather we just stop subsidising them and then slap them with a proper carbon tax. If they still manage to make a profit under those conditions, then we can talk.
I spent a year of my life writing an extension to it that allowed you to control various streaming services and Kodi with it. When I released it, a bunch of guys in their developer community bitched me out at length because I licenced it under the AGPL and they wanted MIT.
It pretty much killed any interest I had in the product.
I like it, but it's a dick move to require that the resume be hosted at a remote URL. Lots of developers don't have their CV on a website, and one of the strongest devs I've met doesn't even have a LinkedIn profile.
Support a file upload or just Base64-encoded data and you've got something here though.
Curious how it never occurs to them to block the driving lane, or you know, park around the corner.