Avatar
⚡️🌱🌙
7560e065bdfe91872a336b4b15dacd2445257f429364c10efc38e6e7d8ffc1ff
Former Youngest Person in the World!! stuartellison.com fantactico.com knostr.io zairk.com 🪴

Americans: Whaoh, OMG! What the hell is going on in Paris?

Brits: They call it “Juin”

Have you thought about adding an account management URL?

You could go to a page that listed many iOS wallets and instructions on how to add them.

Have you explored this at all?

There was a significant change in Apple's App Store policies that occurred in response to regulatory pressure and lawsuits, most notably from Epic Games. As part of this change, Apple announced that "reader" apps would be able to provide a single link to a website for account management, including payment setup.

"Reader" apps are a category of apps defined by Apple that provide previously purchased content or subscriptions for digital magazines, newspapers, books, audio, music, and video. Examples include Netflix, Spotify, and Kindle. Before this change, Apple's policy was to disallow any links or instructions that explained to users how to pay for their subscriptions outside the app, which allowed Apple to enforce its 15-30% commission on in-app purchases.

Has anyone considered adding the 1 allowed URL to external payment setup?

Seems like a simple loophole for Will. Just curious why nobody seems to have explored it?

Sounds like there is no legal advice during any of these engagements?

FYI…

*****

There was a significant change in Apple's App Store policies that occurred in response to regulatory pressure and lawsuits, most notably from Epic Games. As part of this change, Apple announced that "reader" apps would be able to provide a single link to a website for account management, including payment setup.

"Reader" apps are a category of apps defined by Apple that provide previously purchased content or subscriptions for digital magazines, newspapers, books, audio, music, and video. Examples include Netflix, Spotify, and Kindle. Before this change, Apple's policy was to disallow any links or instructions that explained to users how to pay for their subscriptions outside the app, which allowed Apple to enforce its 15-30% commission on in-app purchases.

A situation between Apple and Basecamp originated with the launch of Basecamp's new email service, "HEY". Basecamp didn't want to use Apple's in-app purchasing system (which would require them to give Apple a significant cut of the subscription fee), but Apple initially rejected updates to the HEY app because it did not offer in-app purchases.

Apple's revised policy could potentially benefit companies like Basecamp by allowing them to link their users to an external website for payment setup, thereby bypassing the App Store's commission.

*****

Why not provide 1 URL to a website that lists a number of BTC wallet apps and instructions on setting up wallets with Damus?

Seems like this would be quite easy to implement?

I was expecting something noisy that had to be setup every Saturday and nursed to the finish line.

Nope.

90 minutes one time setup, plus three 5 minute interventions in week 1 to adjust my rookie setup after spotting it stuck.

Now it silently cuts my grass between 1am and 4am every night and I have 35mm lawns 24/7.

GPT’d it:

There was a significant change in Apple's App Store policies that occurred in response to regulatory pressure and lawsuits, most notably from Epic Games. As part of this change, Apple announced that "reader" apps would be able to provide a single link to a website for account management, including payment setup.

"Reader" apps are a category of apps defined by Apple that provide previously purchased content or subscriptions for digital magazines, newspapers, books, audio, music, and video. Examples include Netflix, Spotify, and Kindle. Before this change, Apple's policy was to disallow any links or instructions that explained to users how to pay for their subscriptions outside the app, which allowed Apple to enforce its 15-30% commission on in-app purchases.

The situation between Apple and Basecamp originated with the launch of Basecamp's new email service, "HEY". Basecamp didn't want to use Apple's in-app purchasing system (which would require them to give Apple a significant cut of the subscription fee), but Apple initially rejected updates to the HEY app because it did not offer in-app purchases.

Apple's revised policy could potentially benefit companies like Basecamp by allowing them to link their users to an external website for payment setup, thereby bypassing the App Store's commission. However, the exact specifics of the interaction between Basecamp and Apple post-2021, and whether further disputes arose, would require up-to-date information beyond my current training data.

For the latest information on this topic, I recommend checking the most recent news sources or official statements from the companies involved.

I automated 90% of my gardening with this one weird trick… !!

On a serious note, this experience dramatically changed my understanding of robot labour and how people will adapt (people will get used to it very quickly).

Robots don’t need to be sentient or super intelligent, I actually doubt that will be popular because it will feel like a privacy invasion.

The service Apple provide is hosting. You soon notice when their service is revoked.

But yes all these clients are browsers in my opinion, none of them own/control their network. Browsers have separate requirements/rights guidelines in the App Store.

nostr clients are literally connecting to public IP addresses and domains that are determined by the user. I never really understood why you would claim to be a media app? It makes no sense to me, but we don’t know the dev’s strategy so they are free to choose.

The process is highly arbitrary / discretionary.

Depends which reviewer you get, depends what day of the week, time of day, etc, etc.

Just a handful of employees in an extremely repetitive business process following their interpretation of a guideline document and trying to meet some KPI’s.

It largely depends on how you self-categorise your app when you submit.

You can submit a nostr client as a browser and probably avoid this outcome.

There will be nostr clients on iOS with zaps, just not Damus. There already are.

People who think this is Apple acting as a strategic corporate entity and not 5 rando employees grinding through another Tuesday should submit apps more often.

Native apps = native byelaws.

Nothing wrong with this, but eyes wide open.

You can’t easily install PWA’s on iOS. It’s an OS function and there is no public API. The only path is via Safari.

One option is an app store that also runs full screen app instances on the server. Then create a tonne of user friendly SSH clients to connect to it.

It’s annoying that Apple will force Damus to remove zaps.

It’s super annoying for JB55, who has put a lot of effort into this.

But I think it’s a mistake to turn an uphill battle into an uphill war. When faced with an uphill battle often it’s better to concede quickly and cheaply, and just chart another path around the back of the hill.

If native iOS has a headwind, has friction, just flow around that into the areas of least resistance.

There is an entire vista of opportunity here. Twitter clones are but 2% of the landscape.

Just keep building stuff.

Ecosystems will not yield on their monopolies until they bleed users. Users won’t move to a desert.

Just keep building stuff.

Replying to nobody

There are a lot of suggestions to switch to Graphene right now. I tried Graphene twice for weeks at a time on a Pixel 6 Pro. Here are my observations/thoughts.

* None of my banking apps worked.

* Ended up using Google anyways for maps because the "free" alternatives took me miles out of the way or had no clue where things were.

* I never got the full zoom capabilities of my phone's camera to work, despite installing - you guessed it - Google's camera app.

* Swipe to type might as well have been non-existent.

* RCS never activated despite days of trying - oh, and that required installing Google Messages. Most people in the US still use text.

* There feels like a dearth of FOSS photo galleries with competitive editing features. I ended up installing.... Google Photos.

* Backing stuff up automatically... you going to also self-host NextCloud? Are you going to set up SyncThing? This is not a simple software swap - it requires a whole lifestyle.

I'm a software engineer and competent with Linux, etc... and I felt like I had reduced a $800 phone to the equivalent of something I could buy on prepaid for $150.

I'm sure there was a way to "fix" it - but that's the point. I do this for a living, and I don't have time to fix it. My phone has to work. Period.

You guys realize that basically *nobody* outside of this small echo chamber is willing to deal with that right?

I don't even hate the project - I follow several of the developers and they're fucking *awesome human beings* doing amazing work. Essential work that is needed and used by probably 10's or even 100's of thousands of people with high threat profiles. But almost nobody is going to do this unless they have significant other factors contributing to their threat profile, or they're nerds like us who are willing to tinker for hours to get less than what they get by pulling a stock phone out of a box.

The year of the Graphene Phone will happen at the same exact time the year of the Linux Desktop happens. When it just works. 99% of the time. With no sacrifices in feature set or performance.

Isn’t it better to just SSH out to a VPS?

eg Shelly?

Treat your phone like a terminal?

On iOS your terminal is fully containerised, keys can live on secure enclave, etc, etc.

Only downside is connectivity, but in 2023 is that really an issue?

It used to be that industrial technology far exceeded consumer technology. But in the space of personal electronics, consumer tech is light years ahead.

Replying to Avatar Tony

Hey, nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f, we’re in a bit of a pickle here with the NIP-07 login on a PWA. Is there a workaround to enable extension to support NIP-07 login in an app added to the home screen (not in the browser itself)?

cc nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn

On iOS, PWA’s run in a separate WebKit instance which does not support extensions.

So yeah, a challenge.

Probably Web Cryptography API or such is required to minimise XSS risk of localStorage or IndexedDB.