alpacaillama

If you read what the author said and understood it, you would see that mongodb didn’t open up the firewall and it does have auth protection but the author chose not to enable it.

Was that for all roles or only 5+ years of experience?

I agree with your point about the differentiation being vague and the fact that apple should be more clear.

Also apple does disallow porn. And fanhouse also says no porn but every fanhouse creator’s marketing is around suggestive pics. They get around it by calling it “lewd” instead of nude and the app literally has a pay to view picture functionality which some creators use for NSFW stuff. I wonder when Stripe will catch on to this. Basically marketing != what’s happening.

I can find you 15 fanhouse creator tweets that are suggestive in nature. They get around the PG-13 requirement by calling it “lewd”. Do you want 13 year olds to buy lewds? Lol def not PG-13 whatever they claim. And from personal experience a creator who has offered to let me buy her nudes on fanhouse’s pay to view. I too can claim something is SFW.

Wonder if they will hire more in UK/Canada now?

2. Fanhouse not only has one off transactions but things like pay to view pictures of someone etc

Netflix and Spotify don’t offer in-app purchases and come under the reader rule within the appstore guidelines. At least know about things before you talk about them dude.

I think this might be a part of their strategy. Do a well timer PR push.

Going to jump in and reply. Patreon explicitly doesn’t do Pay to views, doesn’t have interaction gated behind paywalls, and is meant as just a straight transfer of $. Fanhouse does a lot of these things which counts as digital transactions. This differentiation makes sense to me. Also interestingly most people I have seen use fanhouse use it for NFSW stuff but Stripe seems to be fine with it? Specifically the pay to view feature which is people basically selling nudes.

I would pay you a $100 USD if you could consistently get a scam like this into the App Store. And by this I mean: - Low effort - Phishing for data - Pretending to be Microsoft.

Also interesting to note, that some of those APIs are still in W3C drafts. So Chrome just went ahead and wrote its own implementation without the literal standards body agreeing or disagreeing on them. Again, this author is extremely biased and I don't think this article is an informative take for anyone.

Also the author never really addresses if the API is needed or not, or if it provides a good experience. If Chrome has it, it is seen as a positive. Personally, i'm very happy that PWAs can't spam me with "You left something in your cart" notifications on iOS.