Sometimes Elon stans call me out on Twitter when people post the “cars and rockets” post, demanding to know what stupid things Elon says about software.

Here’s a primo example.

In this exchange, Elon thinks Adam Mosseri is adding rate limits to Threads just like he added them to Twitter, and that he “copied” Elon.

Anyone who understands software knows Adam is talking about WRITE rate limits to curb spam posts. Elon implemented READ rate limits in an application that relies on ad impressions.

@rodhilton

Dear people who don’t understand chronic illness/invisible disabilities –
* believe me when I say I’m too exhausted to absorb what you are saying or discuss something complex
* believe me when I say I’m too tired to put away groceries or walk to something a block away
* understand that things that take you trivial amounts of energy can be exhausting for me
* BELIEVE ME

#disability #fibromyalgia

@meredithw

Hey. So as major platforms start to fall apart, don’t necessarily look for the next big one.

Dust off your blog.

Go back to establishing web-rings.

RSS feeds. Remember those?

This is the way to share good stuff. You don’t need a centralized platform for that.

As hams, we should know that.

@KC8JC

I strongly encourage you to demand your Mastodon instance use AUTHORIZED_FETCH.

The basic story is this:
If you block someone, you can’t see them & their posts, etc. BUT without AF, they can still see you & your posts.

What does AUTHORIZED_FETCH actually do?
https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/

Why AUTHORIZED_FETCH isn’t defaulted on… Knowing what I now know, I would move to a new instance if my admin would not turn AF on. It’s a huge security issue.

It’s a stalkers field day without AUTHORIZED_FETCH.

@Yehuda

Newest Reaper version, right at the top of the changelog, are accessibility items. Oh, but not just the typical accessibility items, the new fixes are all to improve accessibility of the Video Processor. A lot more blind people must be using Reaper as a video editor now, and that’s kind of amazing. “add preference to use standard (screen-reader accessible) OS editing control for video processor code” and “improve keyboard navigation of video processor presets” http://reaper.fm

@bryansmart

Never thought I’d be one of those folks going on about how great their company is on social media but here I am.

We have a web-based terminal that pre-installs/auths our CLI so you can upload code and launch apps from the web. As a blind screen reader user, I don’t often need web-based terminals, but when I need them I need them and usually they’re a11y hot garbage.

Asked in Slack where the code for ours was, pulled it down, discovered it used xterm.js which has a screenReaderMode flag which, I’ve learned, is essentially what VS Code’s terminal uses.

15 minutes later and my PR adding this in is up for review. Waiting for it to get more testing to determine if we’ll need to make it a toggle, but I fully expect this to be live within the week.

I’ve made a lot of small, quick win a11y changes on our platform over the past couple months. Meanwhile I met with the vendor for our collaborative wiki, suggested some very simple landmark changes that they could have made in 15 minutes, and guess whether any of those are in?

Company culture really does make all the difference, and the Fly folks have gone out of their way to empower me to change things, and to make things more accessible for me without me having to ask. A thousand points to them.

@nolan