Or they live in a country where genocide denial is legal. I live in Canada and my server is in Canada. I’m not willing to take the risk so my users can interact with assholes.

All responsible server admins have them defederated. Hate speech and genocide denial, that is almost certainly against the law in Canada, Germany, and other places. We defederated lemmygrad for the same reason.

So most modern activitypub servers backfill threads and profiles. My single user instance processes 30000 notes a day. If I was actually trying, I’m sure it’d be easy to grab much more while appearing well behaved.

How does that help? My personal instance currently has a database of several million posts thanks to the various Mastodon relays. I don’t need to scrape your instance to sell your posts. I don’t, of course, but it’d be easy for some company to create friendlycutekittens.social and just start collecting posts. Do you really have time to audit every instance you federate with?

So does Reclaim The Internet still involve purchasing an advertising company, letting multiple employees go, and generally behaving like a VC-backed startup? Just checking!

When watching a movie or tv show by ourselves, blind people can’t see the picture. So unless we are watching with a sighted friend, we would rather save on storage and bandwidth by only downloading the audio.

Audiovault.net is the website you want. Made by and for blind folks, it has thousands of AD tracks in mp3 format. You should be able to just sync them with the video. Though blind folks never bother; we only care about audio anyway.

From the article:

The TLS-SNI header is used by CDN servers to route requests based on the Server Name in the header. However, a typical front end server, or even a load balancer (LB), belongs to a single app or organization, and does not typically need to handle the SNI header. The easy and reasonable way to configure TLS certificates on such a server, is to either:
 Serve all requests with a single TLS certificate that has SANs (Subject Alternative Names) for all the domains that are used Have multiple certificates, chosen according to SNI, with one of them as the default. In both of these common cases, sending a HTTPS request directly to the IP of a front end server, without any SNI, will present us with a default server certificate. This certificate will reveal what domains are being served by this server.

So apparently the real issue is that people aren’t using SNI correctly.

The tech blog is much better: https://www.zafran.io/resources/breaking-waf-technical-analysis

It boils down to scanning all IPV4 space, and grabbing the SSL certificate returned by any webservers on port 443. If the server is incorrectly configured the fields in the SSL cert will tell you what domains it serves. And using Certificate Transparency logs to figure out what domains you want to target. I wouldn’t really call this a flaw that breaks anything. It’s just a byproduct of how SSL, IPV4, and WAFs work.

Let me check out the Lemmyverse website for accessibility, and if it doesn’t have any major problems, I’ll add it! Thanks! I’d heard of LemmyApps, but I was unaware that it allowed filtering by accessibility. I’ll also go and add that.

We had some hosting problems back in September. However, we have that resolved, we’ve vastly improved the reliability of email delivery, and in more exciting news, we have a designer working on a more accessible custom theme that we intend to contribute to the Lemmy community overall as well as make our default. It’s taken us a while, but better email deliverability and a custom theme were the two things on our list we felt we needed before we could start actively promoting the instance. This post was one of the steps in preparing for that promotional work.

Your post showed up here just fine.

Yes and no. I left during the API drama and the blackout. First, moving communities wholesale just never works. Community archives don’t migrate, the affordances are different from site to site, etc. That’s why we (speaking for all the folks who run the ourblind.com set of communities) run a Reddit, a Discord, and of course the rblind.com Lemmy. The members and culture are wildly different between the three. And that’s fine. Though because of moderation issues, these days all posts to /r/blind need approval, and sometimes approval can take a day or more. However, Reddit’s decision to exempt the accessibility focused clients (Luna and Dystopia) that most blind folks use meant that a lot of blind people preferred to stay on Reddit, especially those who just consume content from other communities.

Second, creating a home for a new community, and doing it properly, takes a lot of time and effort! It’s taken us over a year to get the server infrastructure for rblind.com to a place I’m happy with. We had almost a week of downtime a while back, and until recently email delivery was extremely dodgy. While those things are fixed now, we’re still in process of creating a custom (more accessible) theme for our Lemmy. So even over a year later, I would still consider the rblind.com Lemmy to be in an alpha state. Signups are more than welcome, but we’re not actively working to push people over from elsewhere. Despite that, we’ve got a couple active daily users (mostly in off-site communities), folks make regular posts to our main community from Mastodon, and we’ve got a couple hundred registered users. It took the Reddit about five years to really take off, and even the Discord took a couple years before it started popping. So I’m happy for Lemmy to slowly build at its own pace, into whatever it decides to become, without trying to make it a clone of Reddit or something else, or forcing the existing communities to move over.

As well, of course, if Reddit does decide to cut off the accessible clients, or do something else that makes it completely screen reader inaccessible, our Lemmy means that no single service can hold our community hostage. Unlike when the API stuff happened, now we wouldn’t be in the position of racing to find a new home. We’ve got somewhere that’s mostly built and ready for people to move in when they need it.

There’s also a list here, though last updated in 2020: https://distributedcomputing.info/projects.html

Most of those projects remain active in some form.

For those of us using screen readers, this is a way bigger deal. Honestly I probably shouldn’t use a bluetooth headset and a bluetooth keyboard for my banking. We focus so much on SSL/HTTPS and wifi security, but I wonder how much effort goes into wireless keyboard security? Not nearly as much, I’d bet.

I never did that, my connection was too slow to want to take up someone’s DCC slot for like a day to get an entire movie. Remember all the frustrating idiots who would share .lit files, but forget to remove the DRM from them?

Ah, good to know. Back in my day, when we had to walk a hundred miles to school in the snow, up hill both ways, IRC was the only place to get ebooks. I’m guessing it’s just the old users clinging on now.

Man, I’m getting flashbacks to my days running omenserve on undernet. I had no idea people were still doing this! How does the content compare to places like Anna’s archive these days?

Can Mistral describe images yet? Not sure if it’s multi-modal or not. If it could that would be a super useful feature for those of us over on rblind.com. And/or is the code available somewhere for us to hack in something like openrouter and spin up a copy?