coolliquidcode

Cool. Now do google, amazon, fb, Verizon, att, chevron, exxon, gp, oracle, microsoft, etc.

> But there are substantial reasons to believe that the phone number does not provide the same level of independence and convenience as does the website and the mobile app. In particular, as the district court noted, "callers may experience delays and be placed on hold." Pet. App. 24a. Ambient noise may distract from and interfere with the accurate taking of orders. See p. 8, supra. And giving a credit card number to a live human being over the phone may create a greater risk to privacy than does submitting that information through a secure website. See DCt. Dkt. No. 33 at 15.

This is pure nonsense. So what if you may experience delays or be put on hold. Just because something exists doesn't mean you're obligated to provide it.

"credit card number to a live human being over the phone may create a greater risk to privacy" is absurd, it's the way people been taking credit cards from inception to very recently, either it's not good enough and should be banned all together or it's an acceptable means of charging a card. Plus there is protection from the CC company.

Look at way back machine

You are arguing they should have been forced to pay 58k for unnecessary site improvements when each place has a phone line that can be called. They did have alt text but it was deemed not good enough. What real value did disabled customers miss out on?

As you are using a site that is almost black text against a tan/grey background? For most copy I agree with you. But requiring that level of high contrast for titles, informational text, text over images, or some measure of flair so your site stands out a little it's too much of a requirement.

It's very high contrast. The comment meta on these posts fail it. I'm pretty any text against the orange in this site fails it too.

> find a barrier-free entrance to a building, and a curb cut at an intersection I disagree with this too. It's a social nicety but shouldn't be a requirement.

> It should be on us, the developers, to ensure our apps work with the tools of the trade to enable people with limitations Why? I argue it should be on the disabled person.

> The bar is so low. Not really. There are groups of lowers running around looking for people to shake down for ADA misses. To really protect yourself it takes a lot of time.

It sucks to be disabled and this is why it sucks. People shouldn't be wasting lifetimes of time to so that visually disabled people can be slightly more convenienced to browse the internet or play with an app. Especially with alt-text. Minimal effort is fine. Well structured HTML is all that should be needed.

> How can buying a specialty browser solve a problem of a blind person needing alt text for images? If a picture is worth a thousand words you're never going to get the alt text right. There can always be complaints it's not good enough. Look at what happened to Dominoes. They made efforts but it wasn't good enough.

You should see how ADA requirements are practically impossible or completely break design. The high contrast of font to background requirement is so extreme that most major sites and even ADA related sites fail. Things like alt text is so time consuming it would be incredibly expensive to label all the images. Facebook has long resorted to using AI descriptions.

Really it shouldn't be up to the developer it should be up to the disabled person to buy tools. Just like someone may need to buy a wheelchair to move around, they should have to buy a specialty browser that handles their limited visibility needs or brail tool interface.

I get it. It'd be nice if all these major companies used both in and cm. Americans have to go back and forth with metric a lot and it would be useful to think of every day items in terms of both inches and cm.

Honestly it's a mistake I would make too.

I think you think I'm someone else.

Not at all. It was still a really cool writeup. Worth the read but just wanted to see an electronics project.

Then I wouldn't use Roundcube either.

You saying I'm flamebaiting? I doubt anyone is going to be offended by PHP being trash, especially anyone that has spent any serious time working with it.

I remember looking at some new features and was so hopeful the language would get better but they had some super cargo culty take on something borrowed from another language that completely missed the point. It's a horribly done me too language where the developers don't fully understand what they are "me too"ing.

7.0 had some issues so bad it's almost impossible to find anymore. Seems like they tried to erase it from the internet. The language itself is an attack vector.

Isn't it PHP based. I worry about anything written in that turd of a language.

Same. Cool project but way less interesting.

I guess by community support is if you want to build something you'll find 100 tutorials on how to do it or it will even be part of the GitHub project. I never visit the official forums. These community mods are crazy with the little bit of power given. I had similar issues with arstechnica.com before it became an echo chamber.

If you are hobbling with a PI it's all about the community support, form factor, low power and the header pins. Hopefully if you are buying a Pi you already have a specific project in mind.

For example: I use a few zero 2 w's with shairport-sync to make Airplay stereos. I use the header pins to control a relay to turn on and off an audio amp. Pi 4+ would actually work a lot better for this especially when playing audio on multiple of these setups at once. A Lenovo mini pc wouldn't be as easy to hide.

NYT is the biggest trashiest rag out there. Why is anyone linking that paid subscription to see their nonsense of a site.

I really wish W3C never got rid of the <blink> tag. It's such a minor UI offender these days.

LOL, I write emails like this to ensure they get read.

I was wondering how he didn't get shutdown immediately and read his post about it linked in the top right. https://phoboslab.org/log/2023/08/rewriting-wipeout

This part is great: > If anyone at Sony is reading this, please consider that you have (in my opinion) two equally good options: either let it be, or shut this thing down and get a real remaster going.

> I'd love to help!

I was wondering how he didn't get shutdown immediately and read his post about it linked in the top right. https://phoboslab.org/log/2023/08/rewriting-wipeout

This part is great:

> If anyone at Sony is reading this, please consider that you have (in my opinion) two equally good options: either let it be, or shut this thing down and get a real remaster going.

> I'd love to help!

pinterest has it's place. It's bad rep is because you have to be logged in to see anything.

Fox News is the same level of journalism as guardian, verge and nytimes. As well as Wapo and CNN. I guess people are choosing to be in a bubble of the trash they like. Maybe because they don't know the billionaires that own the other media they think they are decent news sources.

Other surprising trash to me is people want to see: rtings.com and goodreads.com.

I really tried hard with Goodreads and never found good book recommendations there.

ALL abstractions are leaky - this is an objectively true statement.

As others said it's not for beauty, it to make sure if there is abstraction it fits the problem. If there is encapsulation it doesn't get in the way. For some coders they can get it on the first try and there is no reason for them to rewrite code. For the rest of us mid coders we need to explore first as well as make sure all cases we desire for Lib/API work.

I think sometimes it's a good idea to use a language the company doesn't use internally to prototype. Like we don't use python or node in production, but a lot of stuff can be POCed in those languages/frameworks without a learning curve.

It forces you to throw out the old code and forces you to think the problem out in different ways.

Also, in my experience the POC does enough that it turns into just use POC because of the illusion that it would be faster to use than to rewrite. Then it's a span of time fighting edge cases and added features thought of afterwords till it passes all testing. Then you have a battle tested piece of code you can't get rid of, difficult to understand, and ridged for changes.

COVID was one place where their lack of skepticism really came through. Early reports of how COVID spread would have been deemed unrealistic quickly based on a basic understanding of statistics. The early reports of how long the virus lived and how easily transmittable it was should have meant the virus would have spread to a high percentage of the population immediately. Pfizer saying the vaccine prevented transmission even though it is a leaky vaccine should have raised skepticism to incredible heights. Instead, media used these reports to create panic, fear and division. I highly doubt it takes too much work to regurgitate other news outlets, Pfizer, and government organization talking points.