The free software foundation is doing everything they can to kill the free software movement.

It's time to reevaluate the landscape, and time for new ideas and organizations to pick up the torch for human freedom and justice as it relates to software and technology.

cooperativetechnology.codeberg

The reptile timer is even worse. It dies almost every day when plugged into it, usually halfway through a sunset. I suspect the contact brushes are causing power fluctuations as the thing physically rotates around its timer switches.

¯\_(ツ)_/¯

Show thread

I'm ready to give up on this project, it's so frustrating that it just won't stay up.

My last idea is to get a stupid reptile timer and just cut the power to it every morning for half an hour. Feels like giving up, but at least *if* that works, I *might* end up with something to show for all my work, finally.

Show thread

Anyone out there have experience running a headless always-on raspberry pi zero w?

I'm trying to set one up to do sunset time-lapses (lab.burn.capital/chaz/daily-su) but frustratingly the pi frequently ceases to function — drops off the wifi, cronjobs don't run, etc. Every other day-ish.

I thought it might be power issues, but it's hooked up to a correctly-rated usb adapter plugged into a battery ups. I've tried a different power adapter and even a different pi.

This can't be normal... can it?

Or maybe I'm just confused. If you access it via the fontcdn.toolforge.org/ URL, it seems to provide a non-google URL for you to use on your website, which would mean it *is* proxying from google, a good thing.

It's also available via the author's website, which just gives you google URLs. Dunno!

I'm going to stop tooting about it now before I confuse myself even more 😔

Show thread

Ha, I should have looked closer at fontcdn before tooting! Turns out they don't proxy anything, they're just a search interface for google web fonts. Use fontlibrary.org instead!

Show thread

For anyone else looking to reduce google's stranglehold on the internet in this small way, I found some nice google web fonts alternatives:

fontlibrary.org/ has a small but decent library of free fonts, and they deliver the css similarly to how google does, so you can use it without offering the fonts for download yourself.

fontcdn.toolforge.org/ is a service that proxies google web fonts while preserving your privacy, so you can use it as a direct drop-in replacement.

Show thread

google web fonts is one small way the adtech behemoth uses its monopoly powered network effect to surveil people across the internet.

I was guilty of using it out of convenience on my old vanity website and stagnant blog, but last night I spent a little time excising it (see lab.burn.capital/chaz/chazomat and lab.burn.capital/chaz/blog.cha).

@jdormit of course, happy to help! I'll be keeping an eye on your db, sounds really interesting. Cheers

@plausible @jdormit that's why the AGPL is great. It levels the playing field for the big players like amazon and google, who are increasingly acting in bad faith toward the projects on whose backs they built their empires. Their monopoly positions are less powerful if any "secret sauce" additions they make to the open source services they offer must be released to the world, and doing so would actually help the little guys by letting them offer the same sauce. Free software, not open source.

@jdormit heh and I don't want to go full "well, actually" on you here, but one more bit of nuance: the AGPL doesn't dictate that changes to your code must be contributed back to you, just that those changes must also be made available under the AGPL. They can fork it all day, as long as the license remains the same. Of course hopefully they're friendly developers and would try to get changes incorporated into your project to avoid a fork!

@jdormit your first bullet is right on the money, but your second bullet illustrates the big difference between SSPL and AGPL. Under the SSPL you're right that any software supporting the main service offering must also be released under the SSPL, which is impossible if it's 3rd party code (hence its toxicity). Under the AGPL, only the AGPL'd service itself must be made available, and they're free to stand up any code they want around it, under its own license terms.

@jdormit the big difference between the AGPL and SSPL (other than the free software underpinning of the AGPL vs whatever mongo came up with) is that the SSPL attempts to make it so that if you offer the project as a service, you have to release your *whole stack* under the SSPL too. Any code that interacts with the SSPL project as part of your offering. That's why the OSI was like "no way". The AGPL only affects the AGPL'd project and any derivatives.

@jdormit to attempt to answer your question though, if someone just *uses* your AGPL db, over a network or not, they're under no obligation to release anything. It's only if they offer your db as a service directly that the extra clause kicks in and they're required to provide a link to the code. And if they provide a modified version as a service they have to release their changes under the AGPL too.

@jdormit no worries, it's complicated... I wouldn't call myself an expert either, so, you know, grain of salt ☺️

Here's a good AGPL explainer post I came across recently, it lays out your rights and obligations in a few situations: medium.com/swlh/understanding-

Also you might hit up @plausible, they recently changed their web analytics product from MIT to AGPL and might have some good insight for you.

Heh I didn't mean for this account to become a free software advocacy single-issue bullhorn. I promise I'll toot about other stuff too!

@jdormit the AGPL has a well-established track record of adoptability (minus a few anti-free software biz types, who also balk at the SSPL), and you can achieve the same "source-available, charge for hosting" model using it. You'd likely want to dual-license AGPL and something else for paying customers, which is what all the big SSPL dbs do.

Kudos for thinking about this up front! It's hard to change licenses.

@jdormit one of the main reasons dbs choose open source licenses is to boost adoption. I don't think the SSPL will do that for you. We haven't seen many *new* projects using the SSPL yet to test that, but so far everyone seems to treat it as toxic.

I recommend the AGPL instead, a free software license similar to the SSPL in that it requires the source to be available for hosted versions, but without "infecting" the whole hosted stack like the SSPL does.

Either way, forcing giants like amazon and google to play by the rules of free software, requiring them to release their proprietary modifications back to the public, makes their monopoly positions less valuable as they steal (or use, more generously) others' code for their own profit. Open Source licenses do not have this property.

5/5

Show thread

The SSPL tries to retroactively thumb its nose at amazon and other bad faith actors by making anything touching your code in their SaaS offering also source-available, which is where the OSI says "hell no". The AGPL doesn't include that provision, so it's true amazon might still be able to offer your project as a service in a better package than you can. Amazon being the behemoth that it is, I'm not sure any license can prevent that.

4/5

Show thread
Show older
burn.capital mastodon

Toots for friends