STEAM-powered software engineer・@firstgirlsonfire coach・all-around nerd・she/they
77 stories
1 follower

hello Mr. Gaiman! would you please tell my depression to fuck off?

1 Share

I can try.

Dear Depression, please fuck off. Begin by fucking off, continue to fuck off, and about the point where you think perhaps it’s time to stop fucking off and come back, then just fuck off some more.

Read the whole story
40 days ago
Share this story

Three Essential Requirements To Provide an Inclusive QSR Restaurant Experience

1 Share

After years of working with various QSR restaurants types, the Vispero team noticed industry-wide themes regarding the customer experience. Upon further review, we highlighted three essential requirements for fast-casual, quick-service (QSR) restaurants to provide an inclusive customer experience.

There are several common accessibility points of failure related to servicing customers. Some troublesome areas include static digital signage, printed or digital menus, mobile applications, websites, and in-person self-service kiosks. Below are three significant areas that impact the in-person dining experience and may serve as service barriers for people with disabilities.

#1 Build an accessible self-service ordering kiosk

The first thing to remember when developing and deploying an accessible self-service ordering kiosk is to focus on creating a simple user experience. This experience should accommodate all types of users with varied abilities, needs, and demographics. When creating the kiosk application, do not assume any level of skill, literacy, familiarity with technology, or the ability to process complex options or information.

More specifically, consider these features and design suggestions.

  1. Being able to change the voice speed is critical for supporting beginner and advanced users. Select a screen reader (such as JAWS Kiosk) that provides the option to easily speed up and slow down the voice speed.
  2. Using images is essential to support users with cognitive disabilities or language barriers. Appropriately labeling images is also necessary to increase efficiency for users who are blind or have low vision. It is important to mark images as decorative if they do not add useful information that’s critical for placing an order or making a selection.
  3. Speed matters when it comes to the amount of time it takes to complete the task. Anything in the process or application that does not improve efficiency and increase the task completion time should be reconsidered and eliminated.
  4. It is not enough for the kiosk to be accessible; the payment portion of the transaction must also be accessible. If the payment is being processed on a peripheral device or card reader, that process and device must also be accessible.

#2 Use accessible alternative menus

Print menus were, until only recently, a singular point of failure for restaurant ordering accessibility. The primary alternative to a print menu was often a Braille printed menu. Unfortunately, these menus were often difficult to maintain, as menus can change seasonally, and keeping up with a Braille copy could prove challenging due to resources and cost. However, as a direct result of COVID, we have seen many restaurants adopting an online menu-only policy, which is typically accessed via QR code. This new method presents some challenges for accessibility, given that users who are blind or who have low vision need a way to find and capture the QR code. Some methods for improving QR code accessibility include:

  • Add Braille to the area near the QR code.
  • Make sure that the QR code has a tactile frame that identifies the area for camera focus
  • QR code should lead to a website that is accessible. The menu that is pulled up must be navigable and readable via a screen reader.

#3 Make Tabletop order tablets accessible

Some restaurants include tabletop tablets that allow visitors to place an order or add items to an existing order. These tablet kiosks are also used to check out and add a tip; some tabletop tablets even allow users to request assistance from a member of the wait staff. However, tablets are typically not designed to be accessible for users with disabilities. In one case, an agreement was reached between Applebee’s Grill and Bar, E la Carte tabletop kiosk, National Federation of the Blind, and Lighthouse for the Blind and Visually Impaired of San Francisco to make the E la Carte tabletop kiosk solution accessible.


Nothing replaces training restaurant staff and increasing employee awareness on how to interact with people with disabilities, but due to staff turnover and training logistics, structurally accommodating people with disabilities is generally more reliable when it comes to  delivering an accessible dining experience.

Additionally, by using accessible digital technologies (rather than relying on the human element) to improve the QSR restaurant experience for customers with disabilities, restaurants can create a scalable, maintainable, accessible customer experience.

Whether you intend to open a new restaurant or are focused on improving your customers’ experience by adding self-service kiosks, you need to ensure that your customer experience is inclusive.

Speak with a TPGi kiosk accessibility expert about your self-ordering kiosk project today!

Register for a webinar on Setting the Table for Accessibility: Creating inclusive experiences for QSR/Restaurant Customers.

The post Three Essential Requirements To Provide an Inclusive QSR Restaurant Experience appeared first on TPGi.

Read the whole story
44 days ago
Share this story

dwagon-owo:smerzbeliever:baby girl your kitchen floor is littered with garlic sk...

1 Share



baby girl your kitchen floor is littered with garlic skins

die hard broken glass scene for dracula

Read the whole story
57 days ago
Share this story


1 Share

Read the whole story
66 days ago
Share this story

How to be safe(r) online

1 Share

I flatter myself that I am pretty secure online. I’ve written a series of global bestsellers about information security, I’ve worked for EFF for nearly 20 years, I’ve given keynotes at some of the world’s largest infosec conferences. And yet, I have been hacked. It wasn’t even very sophisticated!

It was in 2010. My kid had made a fuss about going to day-care so my wife and I were late walking to work. The cafe we always stopped at for a coffee had longer lines at that hour, so I stood in line while she sat down and read a paper.

I had reinstalled my phone’s OS the day before — the same day I’d had three different articles come out. I was hearing from a lot of people about those articles, and I was having to re-key my password in a lot of websites because I’d blown out my browser preferences with the reinstall.

Standing in line, I got a DM from an old friend: “Is this you?” followed by a URL. I clicked it, and my browser opened, then redirected to Twitter. I sighed, thinking that I needed to find the system setting to tell my phone to open tweets in the Twitter app. I typed my Twitter password into my browser, and ordered coffees.

As I was handing my wife her coffee, my phone buzzed three more times. It was three more DMs, from three more old friends: “Is this you?” and the same URL.

My guts twisted. I’d just been phished.

The Twitter worm that got me was simple: they took your Twitter password, logged in as you, and DMed all your friends with “Is this you?” and a phishing URL that looked like Twitter’s login screen. The URL started with, but continued with (my mobile browser only showed me the first part).

I got fooled because of a perfect alignment of vulnerabilities — late, long line, new OS, new publications, bad browser design, inattentiveness. If the first phishing DM had come in 5 minutes later, in the flurry with the three others, I’d never have been caught. If we’d been on time and I’d received the DM while at my desk on my laptop, I wouldn’t have been caught.

It’s easy to sneer at people who get fooled by phishers, but imagine this: you are buying a house. You’ve just gone into escrow. You get an email or a phone call or a text from your bank about your mortgage, telling you that you have to complete another form. It’s probably not even the first time that’s happened — buying a house often requires going back several times to complete new forms! It’s high-stakes, high-tension, and the market is so hot that if you miss a form, the house might go to someone else. Maybe you’ve already given your landlord notice or sold your own house.

Do you triple-check the URL your bank gives you? Does it even matter? Your bank is probably using half a dozen fintech services to close your mortgage and escrow. You’re already routinely transmitting sensitive data to companies you’ve never heard of.

I get dozens of phishing emails like this every day, but I’m not actually buying a house, so I ignore them. But if I got one of these on the morning that I was closing on the deed? While juggling movers and finance and maybe a new job and a new school for the kid in another city? I’m not so sure. If you’re honest, you won’t be so sure, either.

That’s the thing we miss about scams — they’re scattered like dandelion seeds. The cost of adding another email address to an untargeted scam is close to zero, and the scammer doesn’t care whether that email is deleted unread anymore than a dandelion cares whether one of its seeds falls on concrete.

The dandelion’s reproductive strategy isn’t to ensure that every seed takes root — it’s to ensure that every crack in every sidewalk has a dandelion growing out of it.

11 years ago, I got phished. I immediately realized my mistake and changed my Twitter password, but, like many people then (and now!), I’d reused that password elsewhere.

I’d created my Twitter account while standing in line for a Game Developer’s Conference press pass, after Ev Williams sent me an invite to the beta. I didn’t think I needed a good password for it, because it was a toy that sent you updates about other people’s lunches over SMS. Half a decade later, I had tens of thousands of followers and the account was key to my professional life.

The person who phished me hadn’t targeted me. I was fooled by an embarrassingly blunt and transparent ploy. Is there any way I could have avoided this?

Perhaps. But not by maintaining perfect vigilance, or by never being harried or hasty. The blame-the-victim school of unattainable security locates the infosec pandemic’s problem in human frailty, rather than bad systems.

Good security advice transcends this, and Ars Technica has just published an outstanding guide to securing your online life, in two parts, written by Sean Gallagher.

Part One (“The Basics”) lays out both a way of thinking about security (particularly dispelling the notion that criminals won’t target you because you’re no one special), and a set of (mostly) simple steps you can take to defend yourself against opportunistic, untargeted attacks:

Part Two (“The Special Circumstances”) offers advice for people who might be specifically targeted by attackers. That’s not just one percenters and politicians — it can include people whose ex-spouses harass them with stalkerware, middle-schoolers targeted by bullies, and more.

I often get asked what people should do to be more secure, and I offer four basic pieces of advice:

  1. Use a strong, unique password for every service. Get any reputable password manager (including the free one that probably came with your OS) and use it to generate all your passwords. Never use a password that you are capable of remembering — if you can remember it, a computer can guess it (the exception being the password that unlocks your password manager!).
  2. Use two-factor authentication, preferably an authenticator app, like the one that comes with your mobile OS, or an indie like Authy. Turn it on for every account you use regularly, and seek it out when you create a new account. Avoid SMS-based 2FA.
  3. Keep your OS and software up to date. When your OS or app asks you whether you want to update, do it.
  4. Turn on full-disk encryption. It’s free, it came with your device, and it protects your data.

All of this is in Gallagher’s advice, along with something I don’t recommend enough, though I’m obsessive about it myself:

5. Back up your data, offsite, and keep multiple backups.

The easiest way to do this is with an encrypted cloud service. I do some of that, but my first line of defense are cheap, encrypted 1TB thumb drives that I back up to every day. Once a week, I take a disk to an offsite location and swap it with one that’s already there.

Gallagher also offers solid privacy advice:

  • get a tracker-blocker (like Privacy Badger) and an ad-blocker
  • change the permission on all of your apps so they can only get your location while you’re using them
  • change your mobile device’s Bluetooth name to something other than your own (e.g., not “Fred’s phone”)

He’s also got some specific advice I hadn’t really thought about:

  • beware of a stranger who wants to move a conversation from one app to another (say, from Tinder to Whatsapp), as this is a “signature move” of fraudsters
  • claim an IRS account for your Social Security Number (warning: this is complicated and I failed in my attempt because my information wasn’t recognized)

One of the most common questions I get is “Which VPN should I use.” Gallagher’s answer? None of them: “for everyday Internetting, you just don’t need VPNs that much anymore. Transport Layer Security now encrypts a vast majority of Internet traffic, and it’s unlikely that someone is going to grab your credit card data or other personal information off a public Wi-Fi network.”

But that’s for “everyday internetting.” If you’re a whistleblower or someone else likely to be targeted, “use Tor.” He also advises using Signal for encrypted chat, which is good advice for everyone, not just people in high-risk situations.

Another piece of advice offered in Part Two that everyone should follow is locking your credit report.

For people at risk of domestic violence and stalkerware (the two are highly correlated), he suggests Operation Safe Escape:

All in all, this is excellent advice. If I’d followed it when I was phished, my recovery would have been a lot simpler. 2FA would have defended me, and if it hadn’t, I would only have needed to change a single password.

But some of the advice is less realistic, even if it’s sound: telling people not to click on email links, or to turn off wifi and Bluetooth when they’re out of the house (especially in an era in which the headphone jack is nearly extinct) may be good advice, but realistically, no one’s going to follow it.

As with much in information security, a sound defense requires both technology and policy. You shouldn’t have to turn off Bluetooth and wifi, because both the standards that define them and the implementations in your device should defend you from information leakage. Likewise, mobile OSes shouldn’t default to naming your device after you, and app vendors shouldn’t be able to get your location when you’re not using their apps, period.

Of course, most of us aren’t in a position to do anything about policy. We’re not FCC commissioners, we don’t work in an EU Information Commissioner’s Office or for a state Attorney General.

But that doesn’t mean that we should ignore policy, or give tech advice that no one will follow. A good deal of the threat to our privacy and security doesn’t come from criminals, it comes from large corporations adhering with bad, or out of date, laws.

America trails the world in privacy law. It is long overdue for a federal privacy law, with a private right of action — something ferociously resisted by telcos, ad-tech, and Googbook:

Before the FDA was founded, people were routinely sickened and killed by “medicine” that was literally poisonous. I imagine that people got advice then that sounds a lot like our infosec advice today: “Only take medicine from doctors you trust,” “read the labels carefully,” etc.

Today, we have a better system: we make it a crime to poison people or lie to them about what’s in medicine or what they can expect of it.

The advice in Gallagher’s guide is essential, and much of it would apply even in a world where we had good tech policy. But even if you follow all that advice, it won’t protect you from the choices made by governments and corporations that put their priorities ahead of your welfare.

Today is Aaron Swartz Day. One of Aaron’s most memorable quotes is from the fight over SOPA, an idiotic, internet-destroying legal proposal that Aaron helped kill a decade ago: “This is the 21st century. It’s not OK for politicians not to understand the internet anymore.”

The awful state of tech policy is a scandal that puts us all at risk. Security is a team sport, after all. No matter how careful you are, you can still be compromised by someone else’s badly configured technology — the emails you send to someone else may leak, a company may suffer a breach and put your home address on the internet forever, etc.

Aaron fought for better tech policy. A lot of orgs do that today: EFF, of course, but also Public Knowledge, Software Freedom Conservancy, FSF, Creative Commons, Internet Archive, Fight for the Future, SFLC, EDRI, Open Rights Group, and many, many others.

We should all take some measure of responsibility for our technological safety and security, sure — but until we get better tech policy, we’ll just be sticking bandaids on tech’s gaping wounds.

Read the whole story
70 days ago
Share this story

percethecurse:mousemilf:i like to go in the bathroom and splash water on my face...

1 Share



i like to go in the bathroom and splash water on my face and pretend im a male protagonist under a lot of stress

the masculine urge to stare at your own wet face in the mirror, haunted

Read the whole story
77 days ago
Share this story
Next Page of Stories