In reply to .
@objectinspace Thanks for this!
In reply to .
@objectinspace Thanks for this!
Any claims that BlueSky is open or federated are crap. It seems like an effort to cram crypto into a bespoke protocol that feels familiar enough to lure users while building the ad platform it is meant to be.
More technical details:
https://urbanists.social/@sam/110339902538138997
Just a heads up for anyone looking to get #WCUS tickets. Looks like the next round will go live on Monday (May 15) at 10 a.m. Eastern.
(Shout out to Michelle Frechette for the heads up in the Post Status Slack!)
In reply to .
@objectinspace What does that do?
@Homebrewandhacking @bitwarden @1password
You’re right – you have no control over the password policies for third-party services. So with that in mind, let me introduce you to a concept I debuted last summer called #PasswordNihilism .
Password nihilism is understanding that sites have shit complexity requirements and shit password storage, and then not giving a shit because you recognize that none of it matters. Max 8 characters? Doesn’t matter, don’t care. Plaintext storage? Doesn’t matter, don’t care.
Why doesn’t it matter, and why should you not care? Because out of all the attributes a password can have (length, complexity, uniqueness, randomness, etc.), the only one that actually matters is uniqueness. And by “matters”, I mean “actually defends against threats in the overall threat model for password security.”
So, as long as you’re using a password manager to generate and store unique passwords for each site, you too can be a password nihilist!
If you’d like to learn more about password nihilism, check out:
This interview with @thorsheim:
https://www.youtube.com/watch?v=mJkGom-bngsAnd this interview with @todb:
https://open.spotify.com/episode/62kyiCbX8vsx74n94dAT1C
Welp, clearly it’s been a very long day, because I intended to press ctrl+f4 to close a tab, and instead, I pressed alt+f4. Which closed my browser. And all the tabs I had open. Which I needed open. So no restore session for me. And the Rays lost again. Hopefully my Brafes will win later on.
61 °F Clear Sky
Us: Make better products!
Phone Companies: Sure.
Computer Companies: Ok.
Printer Companies: Hey, I have an idea. How about you go fuck yourself?
In reply to .
@DianaThompson There's definitely an opportunity, I just don't know who would have the wherewithall to sustain it.
I’m going to repeat this so it’s clear.
If the fedi fractures around the ideological lines of safety vs. unsustainable growth, I’m okay with that.
I am very comfortable with being part of the fedi that actually gives a shit about people rather than treating them as product.
I have no interest in repeating the same mistakes and creating decentralized rage engines.
I believe this space can be better.
In reply to .
@SingingNala Yay!
In reply to .
@DianaThompson Yeah that's what I'm trying to get at. Definitely modernize WP's editor. Classic absolutely has problems. But do a block editor with accessibility in mind from the get-go. That would be amazing.
In reply to .
@SingingNala I hope you feel better soon.
i wish people would start saying “people who need screenreaders” instead of “visually impaired people” or similar, because:
1. not everyone with low vision needs a screenreader. this leads to people thinking their job making things accessible is done by making things screenreader-friendly, while most of it is still violently inaccessible to hard of sight people like me who rarely use screenreaders and rely on things like large text.
2. not everyone who uses a screenreader does so because of low vision. i have low vision and the main reason i use a screenreader sometimes are visual processing issues. the idea that only people who can’t see (and thus also can’t read) use screenreaders leads to situations like on twitter when we weren’t able to actually read the alt text, leaving lots of things inaccessible for lots of people. i missed out on a lot of stuff before i was able to view alt text.
be specific. it matters.
In reply to .
@DianaThompson Yeah I expect it's pretty awkward for non-screen-reader-using keyboard users too.
In reply to .
@DianaThompson Skiplinks could be helpful, but I honestly think the most helpful thing would be for the block editor to stop trying to be Microsoft Word on the web, because the document object model available for Word, which screen readers absolutely need, will never be available to the browser. So everything in that path is trying to reinvent a wheel you can never have.
In reply to .
@crankingchrisreagan I hope everything goes well with your appointment Chris.
Don’t worry about the voices in your head.. unless they go silent.
That’s when they’re secretly conspiring against you.
In reply to .
@DianaThompson I don't mean to suggest that the accessibility team and others aren't working hard to fix it. But it's such a complex app that trying to bold on accessibility as an afterthought will never be done, because regressions keep happening.
In reply to .
@DianaThompson There have definitely been lots of accessibility improvements, but honestly the whole thing is just an efficiency nightmare while using a screen reader.