Thanks so much. Yes you're right I chopped some of the audio too close together. Bit of a learning curve. I think it will get better on that front. Talking to a mic in an empty room is super hard but I hoping that will get easier too.
I make no promises on the singing. :)
I recorded an interview for episode 3 yesterday so more coming.
@gray That's great - thanks a lot :)
Also make sure to check in on who James chats to next as he "looks at the maverick renegades of the internet who are pushing back against big tech monopolies, surveillance capitalism and climate change".
@self I think it's gotten worse. HTML is used to make things pretty now, not to, oh I don't know, markup content like it was originally designed to do. And operating systems, like Linux and Android, with poor accessibility don't help either. Now, blind people usually prefer mobile apps and desktop clients because they feel *clean* compared to the sometimes very verbose, linear web, where keyboard commands are few and far in between, non-standard (look at Gmail then Twitter, or even Gmail compared to Google Voice.) And there are so many sites where headings could be used but aren't, and lists to facilitate things which can be skipped, like alternative language options for articles, replies to a comment, things like that. It's just poorly done, and even the "simple" layered approach of mobile apps are easier to use for us than the flat (to us) representation that is the web.
Oh and screen readers aren't magic, either. They're really quite dumb. They gather as much information as they can by the OS accessibility API's, which can be pretty good, like Windows, fairly okay, like Apple's, or pretty neglected, like Linux because no one wants to actually work on the core OS accessibility. Like I always say, accessibility starts with the OS.
I'm sure many already know about Mozilla's hypocracies, but this is a nice compendium of transgressions:
So use what? Crome? *barf* I think the problem goes deeper. We need a web that isn't so confounded to the point where no one, besides large corporations, can maintain a performant, usable and accessible web client. As long as it's this way we will continue to pay for the web with our privacy.
Paid in Dec 2018 and was told it will come April 2019. Several delays since which they never inform me of I'm expected to work it from their blog.
I've been uncomfortable with the way they seem to operate. They suggested the phone was nearly ready when I paid but clearly it never would have been. It's so far behind schedule but they continuing to take cash and invest energy in pushing other, new products.
It doesn't seem like a level playing field https://www.bloomberg.com/news/articles/2019-05-28/google-s-chrome-becomes-web-gatekeeper-and-rivals-complain
I dont trust them either ;)
What about the meta data?
Is the data actually deleted from their servers permanently? Normally the say it is too complex to do so and they just make it invisible to end users.
As you say, 18 months is plenty of time for them to use it however they want.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!