ISO-morphism

It _should_ be, but when I've tried to use format=flowed text still ends up displayed hard wrapped, especially on major mobile clients.

As I couldn't find the nice page about the IAP policy that I read and found quite clear ~4 years ago (you should verify, don't trust people on the Internet): the old rules prior to the Epic and other court cases would say "Only for those users that set up payment while using the app." From what I gather, the current rules would be more lax, but the old can then serve as an upper bound.

The main rules were:

1) A user making a payment that has any effect on app functionality (this is very broad) from inside your app must go through Apple IAP (paying 30% commission). There were some exceptions, but mainly think buying physical goods - Apple isn't forcing the use of IAP for EBay or Amazon retail.

2) You may not link to, or even mention other payment methods.

Really it comes down to: if there is any difference in what the app will do for a user before and after they pay money then that money paying must go through Apple and then Apple will give it to you (minus 30%). So what a lot of apps did is just open to a login screen. No sign up button, no link to your homepage, heck, no links anywhere. The downside is that users have to know about your app from at least one more channel than searching on the App Store, but that's not a very high bar. Probably less common if you're B2B, but for B2C a lot of them would pay their subscription through Apple if possible, the experience is great: one central place in system settings showing all your subscriptions with easy cancellation buttons and enforced standard refund/proration semantics.

In the US, Zelle vs. Venmo is comparable to debit card vs. credit card. With Zelle/debit, you're basically mailing cash - it might get lost in transit, your money is gone right away. With Venmo/credit, there's a middleman with a big pile of cash that assumes the risk of money being in-flight, and usually eats fraud/errors as a cost of doing business in exchange for selling data about your spending to advertisers.

For things like "there's" vs. "there're", not too much harm besides a loss of precision, Grammer can be sloppy and meaning is still understood. But for "could care less" or "cannot be understated" or "irregardless" they're _literal_ negations of intended meaning used unsarcastically and unironically. How does that not irk you at a visceral level? Learning English is already hard enough, and we want to sprinkle in "sometimes what is meant is the exact opposite of what is said, good luck figuring out when, rely on context I guess?"

Not sure if you're being sarcastic or not, but Windows 11 users who use Google chrome are only really a crowd at the User Agent string level. Chrome allows much deeper fingerprinting.

To hurl means to throw forcefully, and is commonly used as a synonym for vomiting, c.f. "throw up"

I completely agree with you, and I think you've worded this better than I have.

I was trying to advocate for the middle path, where there's healthy communication from both sides, to the point that developers trust when "the business" makes a decision - not to the point of engineering completely blocking the, unquoted, business.

I believe that the engineers are competent at developing software, and think that a lot of the quality issues are due to engineers abdicating authority over the software to managers and never saying "No, adding in that feature at this point in the timeline is going to make this a steaming pile of shit and I refuse to do it and still call myself a software engineer."

I get that we have families to feed, but I've seen far too much of a mindset shift in fellow engineers into thinking that we're warcraft peons rather than professionals. "The business" has engineering feedback as a necessary input, and speaking individually with steakholders they expect this - they'll push until we push back.

  Location: North Dakota, US
  Remote: Preferred
  Willing to relocate: Yes, for the right opportunity
  Technologies: Python (pandas, plotting, *nixy things, keras, flask), C# (asp.net core), Postgres, ZMQ, MQTT, AWS (decently strong IAM), Linux (Arch/Emacs/tiling WM type, embedded/yocto/networking xp, hobby sysadmin), Docker, Typescript, React/Redux, C++ (imitation/simple level), Swift
  Résumé/CV: Upon request
  Email: [email protected]

Looking to work on things that provide value rather than extract it, preferably tangible products.

5 years experience as a software generalist wearing many hats on small teams/solo. Main soft strengths are adaptability, tactful honesty, and general middle child agreeableness - I've been described as a chameleon, blending into the norms and practices of teams and finding the grain of codebases/languages/ecosystems, doing things "the way" instead of "my way". I make the effort to learn things, minimizing the integral of resources spent instead of maximizing the derivative of superficial progress (man pages over tldr). Main technical strengths are data analysis, data modeling, distributed systems, and being useful across a wide spectrum of both the technology stack and product lifecycle.

> ...caused trouble for Mastodon clients on various app stores (i.e. if you can use the generic client to connect to gab, the app could fail the app store's content policies and not get approved

Then they better start banning web browsers. I yearn for that comparison to be the official PR response, for those individuals that find themselves in the position of power to make those decisions at Apple and Google to feel the weight of its responsibility. A federated blogging client should be well above the acceptable threshold on a spectrum from Firefox to CSAM.app.