“There is no interpreter. There is no compiler. When a request comes in, your PHP source is handed to an AI that reads it, runs it in its head, makes up whatever it needs to (the database, the clock, the network, the truth), and hands back the HTTP response it reckons the code would have produced.
It is not deterministic. It is not cheap. It is not correct. It is, however, very vibe.” -- @mnapoli
Ireland’s is the world’s first permanent basic income program sending direct, unconditional cash payments to professional artists, and it enjoys overwhelming public support – of 17,000 public survey respondents, 97% supported the program becoming permanent... an independent study of the pilot found that artists didn't just get more work done – basic income reduced their levels of anxiety and alleviated depression, too. https://rgmii.org/blog/thousands-more-artists-join-irelands-basic-income-plan/
I'm pretty amazed how much "Move away from GitHub" is becoming a serious conversation popping up outside of the usual circles. Perceived product quality has dropped so hard that it's not just the usual moral argument anymore.
A good time for free and open source software solutions to compete.
Like, I'm talking "It's a topic in management level circles of multinationals".
@mauve @bscross32 Yes, using Wayland is exactly the problem. Speakup only works on the plain virtual terminal, and it will not work under X or Wayland. Speakup is a kernel module (so no package is necessary for it because it is in the Arch kernel), and espeakup is the program that connects to speakup on /dev/softsynth and speaks its output using eSpeak NG. Just make sure you are on a real virtual terminal (plain TTY), make sure the speakup_soft module is loaded, and start the espeakup service, and it should work. Also make sure sound can play as root. If you use Pipewire or PulseAudio, you may have to do some work for that, but if you use plain ALSA, it should be fine. Personally I use speechd-up instead, because even though it hasn't been maintained in many years, I still prefer it because it uses Speech Dispatcher instead of directly using eSpeak NG, meaning its a lot easier to increase the maximum speech rate, and I can use Pipewire and run Speech Dispatcher as my user, run speechd-up as root, and point it to the Speech Dispatcher socket for my user with the SPEECHD_ADDRESS environment variable, so I can still use Pipewire with Bluetooth audio and its other advantages, and still use speakup.
#linux #accessibility question: How the heck do I actually use `espeakup`? I have it running as a system service but I'm not sure how to make it do anything. e.g. I don't hear anything when it starts and my terminals aren't reacting any different. The man page is very sparse without any guide on how I'm supposed to actually use it.
Occult cyberpunk. Yap with me about decentralized systems, wearable computing, and biohacking.