x0x0

I used to run a hybrid mobile app + webapp company.

Private emails regularly lead to awful customer service interactions because people cannot tell us the email they used to register. Fastmail at least is off the beaten path enough that people probably can understand. Apple, especially using sign in with Apple, is horrid. And not just people unable to tell us the email; they then create multiple accounts; try to sign in on web and use their actual email and then have 2 accounts and flip shit that their stuff is gone; etc. Oh, and regularly blame us for their confusion.

Deliberate bad faith is about right.

Apple was not the problem for rcs; the carriers are and were.

That's flatly not true. imessage interop means not just the person who installs the other app, but the data of everyone with whom they message loses the security/privacy guarantees created by imessage and Apple as a corp. Including massive resources pointed at securing the app itself.

That doesn't necessarily mean it's a bad idea from a competition point of view, but good ideas can be discussed w/ an honest view of the quite real downsides.

> What problem is solved by putting a data center in orbit?

Applying standard financial metrics (do they make money? Will they ever? What valuation does that justify?) to certain companies.

The idea that a package can be updated and with a deploy at the right time could be live on your servers in prod 10 minutes later has always been crazy, and the last years have just reinforced that.

People are encouraged by package managers to treat any bit of code someone tosses onto a package manager as equivalent in reliability to the core language and sdk.

I'd bet good money this is mostly related to Europe's GDPR / DMA actions against Facebook. Ironically, I think Facebook would be in the clear to just charge everyone in Europe and dump ads altogether. :shrug:

> native apps a plenty in the 90s and 2000s

And 1/100th the feature footprint.

> feeling that the convenience from ignoring the "deep expertise" and piling on hacks and lazy abstractions

But again, accidental complexity. The web platform is utterly rotten. So the people we should blame are chrome et al for not providing a standard lib or anything approaching a reasonable UI framework, which forces people to reimplement what a competent platform provides.

Electron is an artifact of the richest companies in the world prioritizing their platform monopolies and trying to increase their stranglehold on businesses by forcing them to write platform specific code, which is hysterically expensive to build and maintain. When I'm confronted with writing for web then reimplementing for mac and win... the answer is electron. I don't think anybody likes building in Electron; it's just it's that or +200% (or more) eng headcount to build 3 apps, one per platform.

> Probably the best choice but doesn't change the structural problem.

The structural problem is that we are destroying trading relationships built with Europe over generations.

In 2008, Softlayer did monthly rental with provisioning of baremetal servers in hours. They quite likely did it earlier, but I used them in 2008.

If it were google's bug as Railway has certainly at least insinuated, then yes. I would also be fine with them saying "blah blah blah abuse was detected; we're working through it with our customer and we apologize to those impacted."

I'd also expect a story around how it is this happened w/o a human spending at least an hour working his/her way through a call list to reach someone at Railway. Starting with ops and escalating to the ceo if necessary.

That assumes a competent org. If this were aws, I fully believe that. At gcp it's entirely plausible.

When I've written similar services, there was a (low) hard cap on how many fraud decisions they could action before they quit and paged. If we were getting hit with a wave of something, a human had to temporarily bump that limit.

"we did not have the monitoring or controls to prevent our anti-fraud from hard killing 3% of workloads, including many instances of pg"

Oof.

"Speed with Quality"

Having been in some of these values meetings, I really imagine it went like this: someone wanted speed, and someone else wanted quality. Sorry, I mean Speed and Quality. Many people said there is a tradeoff between those two things, and only one thing can be first.

Some brilliant businessman: "I know, we'll combine them. We want Speed _and_ Quality." Thus, "Speed with Quality." Tada!

Values are a tradeoff: only one thing can be first. Trying to duck that is stupid.

I'm pretty sure it's one of the revenue models for those free tv/movie boxes. You can even see them at best buy. Absurd.

It's coming.

The Poshmark morons demanded government id to buy a $35 shirt. On an established account, an address that matched my credit card, etc.

The only answer is delete your account.

"A thing is being implemented."

Liars only: Apple is doing nothing.

If a single non-malicious code change can break a thing like that with nobody noticing that's a catastrophic failure in testing, QA, and operations (nobody noticed 20% of euros transacted just stopped). It's hard to blame that on IC engineer.

combined with 30-50% token inflation too. hmm.

Yeah, this article is written by liars.

First paragraph

> 56 interoperability requests under the Digital Markets Act have produced no concrete solutions by Apple,

The chart, stupidly created as a pie chart and with percentages rather than numbers: 21% of requests are in Phase III, ie implementation by Apple.

When liars make clear their intent is to deceive, the correct reaction is to ignore them entirely. You can fairly quibble about what requests are approved or not, but honest people fairly communicate the state of things.

The endless excuses and lies.

It was the same page, both on old.

reddit tab, firefox: 428mb. same tab, chrome: 78mb.

I disagree. It's great that you can get a Wen track saw with 100 in of track for $200 with tax and a Makita with 100 in for $800. People who just want to cut a sheet of plywood aren't stuck paying $800, or more likely, using an inferior tool because the cost doesn't match value to them.

> have everyone believe that trivial feature requests take time to implement.

This could not be more wrong. Features do, because telling a user they can do X comes with a standing promise that it works, the results are correct, the ui is accessible, the feature cleanly interacts with all other features in the system (both now and in the future), corner cases are worked out, etc. And that burden is where prod+eng spend time.

> It is not entitlement to expect operating systems, package managers, browsers, etc to be following good practices.

It is the definition of entitlement, because what you are claiming is "good practices" is actually "ongoing labor and active management."

And, again, contravenes the license you agreed to. If you don't like that, you should execute a contract that does offer the support you want.

Sorry, but that's really absurd entitlement and also contravenes the license.

Open source is fundamentally a gift culture from the authors: here's a thing. You can use it for free; it may or may not meet your needs; but I do not owe you anything either way.

I think it's more just the normalization of deviance. Which makes it very easy for an attacker to sneak in.

I got a modestly-similar situation resolved by buying a support package and spending 4+ hours across ... not sure, but probably 4-5 support calls? It's been 5 years. If memory serves it was the $200/mo support package for Azure.

In retrospect, I should have not spent 3 weeks trying to get their incompetent software to work and just gone straight to phone calls. And at least in my case, the support agents seemed broadly unfamiliar, but seemed to have access to higher-priority internal case submission which did finally get to someone who could fix my issue.

I've gotten business verification for Microsoft before. The kind you need in order to get certain oauth scopes for their O365 platform.

Do not discount complete, total, utter, profound fucking incompetence as the driving reason behind this.

Getting the business verification was an astounding shitshow. With a registered C corp and everything, massively unclear instructions, UI nestled in a partner site with tons of dead ends. And then even after all the docs, it took another week because -- in an action that nobody could possibly have ever foreseen -- we had two different microsoft accounts due to a cofounder buying ONE LICENSE of O365 for excel and doing domain verification because it suggested it.