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

201–210 of 259 posts

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

#201

Post by throwaway287391 »

TheNewAndy wrote: post #181
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…

There is some evidence of this - if you can log in to app store connect (need a developer account) there is this page: https://appstoreconnect.apple.com/apps/pricingmatrix/1539646... It shows the tiers from 0 (free) to 87 (USD 999). Then come the party tiers: 510, 530, 550, 560, 570, 580, 590 which are just repeats of the other tiers, probably for some good historical reason which I'm not aware of.

Huh, so $999 is the max -- and here I was all this time thinking the I Am Rich [0] dev had generously chosen an affordable price point.

[0] https://en.wikipedia.org/wiki/I_Am_Rich

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

#202

Post by jsjohnst »

xmprt wrote: post #122
zeusk wrote: post #96

Earlier quoted context omitted.

inb4 refeer (should've used referr?er)

I also feel like this is a buffer overflow waiting to happen. If somehow someone makes the header length way longer than expected (eg. referrrrrrrrrrrrrrer).

? is 0 or 1 instances of the preceding character, so referrrrrrrrrrrrrrer wouldn’t match /referr?er/, only referer or referrer.

Proof: https://regex101.com/r/s56ebD/1

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

#204

Post by Abishek_Muthian »

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…

Here's another possible entry for a class action suit, I had a arachnoid type game on Appstore under 'Arcade' category for couple of years and one night I received an email telling Apple is moving my game from 'Arcade' category to some X category because it's naming it's new game subscription as 'Apple Arcade'.

I'm sure every other game in the Arcade category was bolted out unless it could be part of their subscription service. I'm in that part of the world where I can do nothing about it, But was hoping those in U.S. or EU sued the Apple for this.

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

#205

Post by bogwog »

Is this enough to open a competing store?

* Put your app for free on the appstore, but with a paywall

* In order to activate the app, you must buy it on an external site

* A web-based store allows users to browse and purchase apps, and "download" links send them to the appstore

* Customers can link their Apple IDs (or another account) so that purchases can be confirmed without having to sign in to every app individually

Or is there still something in the developer contract that prevents this?

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

#206

Post by tambourine_man »

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.

Magento 1.9X used to have a typo in the database that lasted for years because so much stuff already relied on it and it wasn't user facing. I do not miss those days.

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

#207

Post by dhosek »

guerrilla wrote: post #179
mike_hock wrote: post #159

Earlier quoted context omitted.

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.

> well ... the only namespace in C Technically there are several namespaces since you can, for example, name a struct the name as its type.

After many years in Javaworld, seeing this sort of thing in C++ really freaked me out.

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

#208

Post by jfk13 »

asddubs wrote: post #173
Someone wrote: post #138

Earlier quoted context omitted.

Unicode also documents its mistakes in technote 27 “Known Anomalies in Unicode Character Names” ( https://unicode.org/notes/tn27/ ), with remarks such as “U+034F COMBINING GRAPHEME JOINER The name does not describe the function of this character. Despite its name, it does not join graphemes” “The use of the spelling lamda derives from ISO 10646. This does not mean that it is more correct than lambda, merely that the…

Why can't unicode change the names of the glyphs?

Just a note in passing: Unicode doesn't name glyphs; it names characters.

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

#209

Post by dhosek »

Razengan wrote: post #170
btilly wrote: post #116

Earlier quoted context omitted.

The most important example of that class of error is REFERER. It should have been spelled REFERRER. But nobody caught it, and you really can't change something that is part of the HTTP standard...

At this point I think it may be question whether the problem lies with English itself. Such an error prone language.

You don't know the half of it. Many contemporary and common words are the results of misspellings.

“a nickname” was originally “an ekename” (eke being an old English word meaning also)

conversely, “an apron” was originally “a napron.”

English is a weird agglomeration of different languages, with things like the application of French-style plurals (-s) to Anglo-Saxon words (but not always, cf. ox -> oxen) and a generally Germanic syntax with a large fraction of Romance root words.

As part of my Dewey Decimal Project¹ https://www.dahosek.com/category/dewey-decimal-project/ I ended up reading some interesting books on English linguistics (scroll down to the 500s for those).

———

1. I’m not quite done. I have two read books to blog about before I read the last book in the series which will be the book my local library has at its highest Dewey Decimal call number. Alas, it's not a 999 Extraterrestial Worlds book, but I think it's either Antarctica or Australia (I looked when I first started on this seven years ago, but I've since forgotten).

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

#210

Post by johnrbent »

pazimzadeh wrote: post #24

I don't understand the fund. Who would receive the funds, and how? Is this a one time check to all developers who gross less than $ 1 million?

I was wondering about this too... From the actual press release:

"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."

Post reply on HN