Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple agrees to settle potential class action suit by U.S. developers

axios.com

Post reply on HN
Print view View original

151–160 of 259 posts

Re: Apple agrees to settle potential class action suit by U.S. developers

#151

Post by TedDoesntTalk »

taurath wrote: post #99
noway421 wrote: post #66

Earlier quoted context omitted.

I think this is exactly what is being changed here? Now you can link away to a web portal with your account and alternative payment options. Correct me if I'm wrong.

> Developers can communicate directly with customers about alternative payment options. Customers have to consent and be given the right to opt-out. This is the only statement that might be construed as such from the article, but it doesn't say anything about management, and I'm really not sure what consent means - is it a popup that says "do you want to be informed about non-apple payment methods?". Maybe it is what…

Moreover, communication about alternate payment options is not the same as ALLOWING alternate payment options.

Re: Apple agrees to settle potential class action suit by U.S. developers

#152

Post by saagarjha »

gjsman-1000 wrote: post #10
mortenjorck wrote: post #9

Earlier quoted context omitted.

> A big change would be letting developers make it clear to users how to use alternative payment options, but Apple's press release only says via e-mail It really says something that "allowing" businesses to communicate certain information with their own customers via an independent channel was considered a concession in this settlement. I'm still wrapping my head around it.

I think it's important to wait for the final language from the settlement. After all, the original PR Post from Apple doesn't actually mention the $100 million fund that Axios does.

It's mentioned:

> Apple will also establish a fund to assist small US developers, particularly as the world continues to suffer from the effects of COVID-19. Eligible developers must have earned $1 million or less through the US storefront for all of their apps in every calendar year in which the developers had an account between June 4, 2015, and April 26, 2021 — encompassing 99 percent of developers in the US. Details will be available at a later date.

Re: Apple agrees to settle potential class action suit by U.S. developers

#154

Post by jonplackett »

It’s funny, apple’s share price dropped today, presumable based on this. But I think this is net positive for apple. They are being helped out here by the legal system - forced to make the developer experience and customer experience much better. In the long run this will be good for them.

Re: Apple agrees to settle potential class action suit by U.S. developers

#155

Post by yunohn »

Jcowell wrote: post #120
vxNsr wrote: post #60

Earlier quoted context omitted.

> I would happily pay middle men a lot extra to get fewer unwanted emails, phone calls, or just generally more privacy. My life has changed significantly for the better ever since I signed up for this: http://33mail.com/AQwZJR3 The real trick is using a custom domain so A) They’re very unlikely to add it to their disposable email list (and thus block it) B) If this service ever goes under you can still get the emails…

On the flip side for Apple users we get up 100 Hide My Emails in iOS 15 with the same functionality.

How does Apple’s service handle the main functionality described above?

> B) If this service ever goes under you can still get the emails you want because you own the domain they’re being sent to.

Re: Apple agrees to settle potential class action suit by U.S. developers

#156

Post by wiether »

mynegation wrote: post #54
jrockway wrote: post #48

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.

That's what code reviews are for :)

Re: Apple agrees to settle potential class action suit by U.S. developers

#157

Post by londons_explore »

probably_wrong wrote: post #132
ksec wrote: post #103

>Apple agrees to make sure the search results in the App Store are based on objective criteria. I cant help but laughed when I was reading it. What were they doing before that? I thought the most important part was the next bit, >The settlement, which must be approved by Judge Yvonne Gonzalez Rogers, comes as Apple is awaiting a ruling in a separate lawsuit, brought by Fortnite developer Epic Games, which seeks to fo…

> And let's not forget this is US only. EU are grinding their teeth. Either I am misreading this part of your comment, or you may have overlooked this paragraph: > With the exception of the fund for small developers, the rest of the changes are being made globally.

But the main complaint is "Apple has a monopoly on app distribution for iPhone users", not "Apple won't let me set the price to $1.05"

Re: Apple agrees to settle potential class action suit by U.S. developers

#158

Post by vxNsr »

yunohn wrote: post #155
Jcowell wrote: post #120

Earlier quoted context omitted.

On the flip side for Apple users we get up 100 Hide My Emails in iOS 15 with the same functionality.

How does Apple’s service handle the main functionality described above? > B) If this service ever goes under you can still get the emails you want because you own the domain they’re being sent to.

They actually also allow you to set up your own domain, after reading his reply and writing my own I thought I’d research it some more. They apparently released the doc for it yesterday, I just followed it and while it’s impressive that apple is allowing this level of technical expertise to be handed over to their users (modifying DNS records), their doc itself could use a little work. I have it working now for another domain I own.

I still don’t like the UX though compared to 33mail, I still need to go into the UI, add the email I want to use and then it’ll deliver.

I’m guessing the same is true for removal, only way to turn off the address is through the portal.

If you use gWorkspace or O365, you already have this, it’s called aliases, and at least O365 gives you seemingly unlimited aliases. My big pet peeve with that was needing to go into the O365 portal and manage the aliases.

Re: Apple agrees to settle potential class action suit by U.S. developers

#159

Post by mike_hock »

int_19h wrote: post #143
saagarjha wrote: post #131

Earlier quoted context omitted.

Took a leaf out of the UNIX creat/umount handbook, clearly.

umount() is actually legit - early C limited extern identifiers to 6 chars (or rather it would allow more than that, but the rest would be silently ignored for linking purposes), hence why we also have strlen() etc. creat() is weird because create() would fit that constraint just fine, so there's no obvious reason as to why it had to be shortened. The 1978 K&R C book actually notes it with [sic].

When you're dumping loads of short, generic, common words into the global namespace (well ... the only namespace in C), it's nice to have them misspelled so user code is still free to use the real word.
Post reply on HN