Why you should stop donating to wikipedia.
TLDR; They are loaded with cash. They took your donations and still sold wikipedia to AI companies. They are sacking workers who try to unionise. They fired the people who most know how wikipedia actually works.
"The Wikimedia Foundation closed last fiscal year with $208.6 million in revenue. It holds $296.6 million in reserves, 17.1 months of operating expenses. The Wikimedia Endowment, a separate fund, sits on $169.4 million in net assets, up $25 million in a single year. Wikimedia Enterprise, the team that provides high speed, high volume API access to AI labs, just turned profitable on $8.3 million in revenue, a 148% jump from the prior year... The point is the Foundation is rich. Seventeen-plus months of operating runway in the bank. Revenue diversifying, not shrinking. They can afford six engineers. Whatever this fight is about, it is not about money."
As if wikipedia selling the work of volunteers to AI companies was not enough, now they are coming for the workers.
"In ten days last month, the Wikimedia Foundation fired the longtime lead developer of MediaWiki and disbanded the team whose entire job was to listen to volunteers. Most of the people they fired were union organizers. Wikipedia’s editors are now threatening to strike in solidarity. The Foundation is sitting on $296 million in reserves and a freshly profitable AI revenue stream. This is a confrontation with global implications."
If you have a wikipedia account you can sign the solidarity petition here https://en.wikipedia.org/wiki/Wikipedia:Wiki_Workers_United_solidarity#Signatures
https://medium.com/@jakeorlowitz/wikipedia-is-doing-the-capitalist-thing-56a393232943
@pixelate @TheQuinbox Ha ha, edbrowse is way more fancy than my setup.
I just have a custom electron based browser with some extensions in it for privacy protection.
Really not sure what triggers cloudflare to infinitely loop their captcha checking thing on it since it should be equivalent to chromium. 🤷
Did you know science can now castrate "farm animals" using mrna injections instead of invasive surgery?
Saskachewan is burning up and there's a bunch of little ones around Ontario/Quebec?
@suricrasia May it extend to the heavens a la "BLAME!".
@suricrasia The real pro strat is to reduce the number of extant human cities.
Abomination!
@esoteric_programmer @TheQuinbox No git repo yet, I'm just writing notes on how I'd like to interact with the system and figuring out how to get wayland to run without a physical monitor. I'm down to collaborate though! What's your new screen reader called? Is this that new Rust one that's been bouncing around?
@TheQuinbox Yeah of course! The tl;dr is the Twiddler 4 keyboard and a Khadas Edge 2 glued to a random USB-C powerbank. Orca for screen reader for now but I'm gonna slap together something else. Mostly geares towards jumping around the accessibility tree with fuzzy search. Maybe also speaking live regions in multiple voices to get more data through?
@TheQuinbox I'm sighted but I've been working on making a portable audio based desktop environment for these exact same reasons. I use a one handed keyboard and bluetooth headphones with a single board computer hooked to a portable battery bank. Sadly I found linux screen readers have been too slow to use so I'm designing my own. IMO screen reader first setups could be better than dedicated linux phones if you focus on keyboard access and ignore the rendering entirely.
I absolutely hate touch screens! I love my current phone, a Pixel 9A. It has good battery, good speakers, a flat back, etc. But I am so fucking inefficient on a touch screen, no matter if its iOS or android. Want me to google something? Okay, let me look around for the web browser, double tap on it, explore by touch until I find the address bar which might or might not have been moved or altered in a recent app update, double tap there, type way slower than on a physical keyboard, hit search, switch my rotor/reading control to headings, and very slowly start reading through results. Touch screens are remarklably efficient for people with functioning eyeballs, and I've seen people who can text on a phone almost as fast as I can type on a computer. But for me, a metal slab with a glass screen and way more computing power than I would've ever thought possible, no matter how fucking cool it is that we can drop that in our pockets like its nothing, will never ever be as efficient as win+r, browsername, enter, start typing, enter, press h, boom first result. This is not helped by the mainstream screen readers on both mobile operating systems having agrivating bugs. On Android scrolling locks up your screen reader while it refreshes the screen, because we're apparently still living in 2005, and VO has just started getting worse and worse with every iteration. I see the downsides to this approach, but I'm really starting to think the best solution for mobile devices for blind people is custom hardware/software. There are plenty of examples of getting this wrong, but I think that's mostly due to people not eating their own dog food as opposed to it being an impossible task. Paperback for Android has shown me that you can make as polished of Android software as you want, but there are still no physical buttons on the front of your phone. For a truly efficient reading and usability experience, I'd personally want both blind-centric software and hardware with physical buttons. That's not at all realistic, though. Welcome to being blind in a world made for sighted people.
i made a new game called js crossword where you have to solve it by literally writing javascript code that eval()'s into the correct values!
check it out if you're into ctfs or wanna challenge your javascript skills
Occult cyberpunk. Yap with me about decentralized systems, wearable computing, and biohacking.