Featured Story: Timothy Murray, the 11-year-old #Brownsville honor student who spent 3 days in solitary confinement after his arrest at the orders of the principal, has a hearing coming up Wednesday to determine if the court will proceed with charges against him. https://www.texasobserver.org/why-was-this-11-year-old-honor-roll-student-put-in-solitary/
#education #Prison #police #Texas #HumanRights #schools #children #news
@hydrandt @glitch @hipsterelectron The AGPL does not do what the FSF claims it does. It is actually against the Open Source Definition to attempt to force people to disclose the source code for merely running the software (as a network service). That would be a proprietary EULA. For this reason, the license instead imposes conditions on modification. It instead states that if you modify the software then your modifications must force the software to offer itself to network users. This is a restriction on how you can modify the software, so it also ends up being against the Open Source Definition and an EULA, just in a different sneakier way. It also does nothing to control what someone merely hosting the software as a service does, which means there are ample ways to work around it without violating it, in practice.
It is almost impossible to actually run a public AGPL project and not violate the license. It is only practical to follow for web-apps that have a built-in feature to serve their own source code directly from the runtime directory (which itself is rare, though not impossible for web apps). I guarantee practically 100% of community-run AGPL projects are violating their own license (as in, every contributor is violating every other contributor's copyright).
For example, merely forking a GitHub project that is AGPL and committing a change is a license violation, unless the software is in the tiny minority where that change would be automatically offered to users via a self-source-code-serve mechanism. You are responsible for updating the code link in the project before you make the change, to point to your forked repo. Of course, that also makes it impossible to then open a pull request against upstream, since that change would tag along. It's really broken and dumb.
For this reason, the AGPL is a toxic license and no corporation will touch it with a 10ft pole - except precisely the case of AGPL source dumps tied to a CLA. The CLA effectively assigns copyright to the company involved, which eliminates the license violation since a single entity owns the copyright (and a single entity cannot violate its own copyright - if you author AGPL software and you are the full copyright owner, you are not bound by the AGPL, only everyone else is).
This is why the AGPL is so loved by sketchy companies that want to pretend to support software freedom but in reality only want to offer a "source available" code dump and take ownership over contributors' code without giving anything in return. They know that no other company will dare touch their AGPL'ed code, but the community will eat up the FSF's nonsense about what the license does and will believe this is FOSS when it isn't.
It is not actually possible to do what the AGPL wants to do and continue being Open Source. Claiming otherwise is dishonest. If people really want to close the "SaaS" loophole, the definition of Free Software needs to change to accomodate that. The AGPL is just a fake free software license pretending to do the impossible without addressing the real problems, to the delight of abusive corporations that want to appear FOSS-friendly.
(Edit: replaced Free Software definition with Open Source definition since that's what I meant to say, and it's specifically a non-FSF document which makes the discordance more relevant)
Everyone thinks, haha, these squirrels don't even remember where they hid 90% of the nuts they store for the winter they are so dumb, but nobody ever asks if the squirrels might be out there thinking, my ancestors planted this forest that provides for us all, and my children's children will know the same of me.
This doesn't look like a good situation for the Matrix ecosystem. We've seen how this ends up too many times before. https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/
I expect #Apple to rush a fix for this issue, as it only affects iOS 17.1 & I believe the beta for 17.2 as well. Prior iOS versions are not affected (just the 17 series apparently).
Folks with an #iPhone or #iPad (running the latest OS) should be wary of potential #Bluetooth attacks from anyone using a #FlipperZero device.
👉🏾 iPhones running iOS 17 can be crashed using a Flipper Zero - The Verge https://www.theverge.com/2023/11/3/23944901/apple-iphone-ios-17-flipper-zero-attack-bluetooth
Acoustics design time!
The MacBook Pro 13" Touch Bar models have two identical speakers on either side, both full range woofers, and very well matched. Surely this means we can just drive them in parallel with the same signal and we're good, right?
Wrong! When you feed the same signal into two speakers close to each other, you get the sum of the signal if you're directly in front of them... but you get cancellation once you go off-axis. In practice, this means that if you calibrate for being in front of the laptop at an angle, changing your angle towards the top makes the highs too bright, while changing your angle towards the front makes the highs disappear.
Solution? A crossover. We drive the full range signal to one woofer with a +3dB shelf at 2kHz, and only a signal lowpassed at 2kHz to the other woofer. The woofers constructively interfere for the lower frequencies, where the physical offset is less important (at 2kHz, the half-wavelength is 8.5cm, and the speakers are a lot closer than that), so you get twice the bass power, but then only one speaker is in charge of the higher frequencies, solving the cancellation problem.
The high end is still relatively directional just due to the geometry/case design (this Mac doesn't have great speakers anyway...), but now it's a lot better than before.
As the CSAR (Chat Control) European regulation tried to mandate scanning of private messages, another European regulation threatens the security of online communication.
335 experts and several NGOs have signed an open letter against the revision of the eIDAS regulation. It would force web browsers to accept root certificates mandated by EU governments, giving them the technical means to intercept encrypted communications.
I have to wonder if YouTube uses accelerometer data to target ads, because whenever I set the phone down to play something while I'm in the shower, they immediately sell me to some scam advertiser who would prefer to put on a twenty minute video about "digital real estate" instead.
After a second ad, they finally started playing my video… and, obscenely, only made it two or three minutes before the next 90sec ad block.
Feel like you're living in the future yet?
The #antisemitism directed at American Jews isn't only vile but it's also totally misplaced. Overwhelming majorities of us oppose settlements and favor the creation of a Palestinian state. Most of us hate Bibi and this Israeli gov. Israel ranks as our 10th most important issue, out of 14, in J Street polling.
It's fucking maddening. But I guess it's always the case that "dumb bigot" is redundant.
"Let's make an audio tape and a floppy disk from scratch!" - part 7.
In this chapter: gamma-Fe2O3 synthesis (finally?!), floppy prototype 4 and 5, gamma-Fe2O3 audio tape, notes on longevity of tapes produced this way. Stay tuned, unroll the thread!
It is probably going to be the last report for the time being, as I am convinced that my little experiments prove that an audio tape and even a poor diskette-like storage can be made with things that are more or less commonly available or easily obtainable in a craft supply store. If I were a real tape/disk inventor, this where I'd stop doing crazy experiments, and start to work on replicating the results and gradually improving them.
If this is the first thread in the series you see, check out the other ones - there's a list at http://www.ninakalinina.com/links.htm
🧵
Hey folks. I just want to say; just because you’re vaccinated against Covid, doesn’t mean you won’t get it and it won’t hit you HARD.
I was vaccinated only a couple of months ago, and as of yesterday I’ve had a 101f fever, my skin hurts, I cannot stop sweating, ridiculously fatigued, and my nose is like a tap. It’s also seemed to have caused an arthritis flare, and my hands are all swollen, and my back hurts so much.
Wear a goddamn mask please.
Scrappy queer