The corporate overlords at Google are flexing their dystopian powers and removing all Danish music from YouTube, because the corporation refuses to come to a fair agreement on paying Nordic songwriters
Its conditions are: accept our pennies or be censored https://www.koda.dk/about-us/press-release-google-removes-all-danish-music-from-youtube
@cassidyjames if you use secure boot to restrict what can run (e.g. as described at https://www.linuxjournal.com/content/take-control-your-pc-uefi-secure-boot ) this vulnerability could circumvent that.
For 'standard' machines indeed it seems the default CA's have signed 'swiss army knife' tools that are so open it's hard to imagine attacks that aren't simply allowed through those, but I'm no expert either.
Just stumbled across Erik and Martin Demaine's 'mathematical and puzzle fonts/typefaces' collection, delightful:
Ripe bananas glow blue in ultraviolet light.
Like many fruit, unripe bananas are green because they're still full of chlorophyll. In bananas, that chlorophyll breaks down into a UV reactive pigment.
Some birds and insects are tetrachromats, and can see UV light. To them, bananas which are ripe and ready to eat are super obvious, and easy to see from the air.
@philipwhite somewhat like etherpad? https://github.com/ether/etherpad-lite/wiki/Sites-that-run-Etherpad-Lite
Interesting thought: many FOSS projects' leadership are often a very ephemeral concept defined by the list of people who currently have a vested interest in the project being maintained. Contributors swing by when they need something changed, and the maintainers review it if and when they have the time and need. If a contributor sticks around, shows some competence and earns some trust, then it's an easy task to make them a maintainer. It's also very easy to quit being a maintainer, just stop doing it as it stops being in your interest to be involved. A maintainer often needn't actually be a contributor, too. And if a contributor comes by wanting to make some changes, but there are no maintainers, it's a simple matter to fork the repo - and as more people come by the project and find the fork, it gradually replaces the original project, and everyone is happy. Sometimes the original maintainers become contributors to the new project.
Some people view this as a sign that a project is on life support, but I think this is a very healthy lifecycle for a project. Many of my own projects exhibit this behavior. With sway & wlroots, I'm hardly involved at all these days, just making the rare executive decisions when they need making, but the project is still chugging along thanks to the work of those who still have a vested interest in improving it. scdoc is "done", but I still use it and want it to remain simple, so I review patches from the occasional contributor but write effective no new code for it myself. Sourcehut on the other hand is still 99% written by me, but receives frequent contributions from all kinds, and some subsystems are maintained by !me. And I have basically nothing to do with aerc today, but it's still receiving new features all the time.
Taking a very flexible, informal approach to governance has been pretty rewarding in my experience.
@kf yeah it's really cool!
I'm sad it seems stuck in "don't help me, I'm rewriting"-mode though, there's some fixes already on master that are really helpful.
I still regularly get bitten by the fact that when you cut a segment, both parts stay selected - so when you then edit the 'right' segment, the 'left' segment is also affected. That's fixed since.
@musicmatze toml looks pretty reasonable as well, nice!
@musicmatze what format would you recommend? I have a soft spot for HOCON (https://github.com/lightbend/config/blob/master/HOCON.md) but it's kinda obscure...
Programming is sometimes like playing twister.
Sure, you can probably pull off that weird hack work to implement that new feature, but it'll make everything harder next round.
@terceranexus6 did you get a lecture about the virtues of emacs?
Turns out the elliptic arc support I contributed to inkcut (vinyl cutter software) earlier wasn't quite correct for non-90⁰ arcs... fixed it though!
@nolan HTTP/3 still does flow control (https://tools.ietf.org/id/draft-ietf-quic-transport-29.html#name-data-flow-control), so there will still be something similar, but at least it'll be something that can be determined by the client on a per-connection (and per-stream) basis rather than once globally by the OS.
Perhaps there will no longer be such a 'magic value' to target, but putting the most important information at the head of the line will of course still be useful.
@sindastra out of curiosity, what do you recommend instead?
There's Telegram, but I'm not sure that's materially better or worse than Signal.
I want to like Matrix, but at this point I'm not sure I dare recommend it to non-techies yet: the clients are still rough around the edges and the matrix.org server seems rather slow. Hosting a separate server might help, but I don't think there's a mobile app that supports multiple servers side-by-side... this seems like a promising long-term bet though.
I never got into XMPP, perhaps I should.
Compilation series tries to establish a practice of thinking critically about access to, and distribution of, art. It poses a question: what is the frame through which we are allowed, and able, to access culture? How is it created, by whom, and can such frame of access be modified and transgressed?
LIVE STREAM TONIGHT 20:00 CET!
Welcome to quey.org! quey is a general and moderated Mastodon instance. Publish anything you want: links, pictures, text, mp3 & video. All on a platform that is community-owned and ad-free.