karmiclychee

WROUNGG

But I am le’ tired.

Then take a nap, THEN FIRE ZE MISSILES

DEEP CUTS damn I flashbacked hard

As a web dev myself, I know the sheer amount of money that would have to go into monkey patching together all these disparate protocols and ancient APIs, plus the regulatory requirements, and that’s BEFORE worrying about consumer AND vendor adoption. The only reason to get into it is if the service is secondary to chasing a lucrative buyout before you get crushed by some multinational online retail cartel you never knew existed (but always suspected), or Google AEEs you.

Fintech blows.

If I’m being honest, the only thing stopping me from shopping at other sites is having to put my personal and payment details in yet another site for it to go stale, or fall out of my memory, or get leaked in the next big hack.

Some sites have “pay with Amazon” (more likely PayPal, but… ugh. I don’t remember why, but I hate it), but I’d love to see some universal adoption of some sort of payment and shipping details lockbox. Like SSO where you can revoke access to subscribers or something.

Yes, well, my spoon is too big.

Served as “flat files” - filesystem, object store, what have you. No server logic generating content, just passing around of strings and binary data. Files are the representation are the source of truth. Counter to a web app, where the content response is ephemeral and the “source of truth” is scattered across a writeable DB and recombinated (potentially) on every request.

Interesting question though, I (a web dev) just take the term for granted.