iPhone implications

BUR #3156 has been rejected.

create implication iphone_x -> iphone
create implication iphone_11_pro -> iphone
create implication iphone_11 -> iphone

iphone x is currently used when the distinct front of iPhone X (and later) is visible, or when the distinct back camera housing of iPhone X / iPhone XS is visible, but it doesn't currently implicate iphone.
iphone 11 pro is currently used when the distinct triple cameras on the back of the high-end iPhone 11 Pro (and later) are visible, but it doesn't currently implicate iphone.
iphone 11 is used for the lower-end one which has two cameras. It doesn't currently implicate iphone.

Alternatively, iphone 11 (2 posts) and iphone 11 pro (24 posts) could be collected under the same tag. However, iphone 11 pro is usually used to indicate wealth or high-class; I personally wouldn't ever want to see any iphone 11 images under iphone 11 pro as they give off completely different feelings.

There could be more tags for distinct iphone designs (primarily based on the back of the device), but this is good enough for now.

EDIT: The bulk update request #3156 (forum #170523) has been rejected by @evazion.

There are no posts under iphone xi, so the mass update is redundant.

Good point, thanks. I get how it works now; edited.

I'm not favorable to this implication, it's similar to game console cases, where we don't implicate Playstation 4 for Playstation, instead we implicate them to game console, so it would be better to implicate them to Smartphone instead in my opinion.

I think that approach is also favourable, so long as it doesn't cause too much mistagging. It's not clear if or when a user should tag playstation if they've already tagged playstation 5, or if playstation is just for the PSone or appearances of the PS logo. iphone already implicates smartphone, but maybe specific iPhone models should still have iphone as a broader tag due to the form factor being much more similar. Not sure, but here's an separate proposal:

BUR #3159 has been approved by @evazion.

create implication iphone_x -> smartphone
create implication iphone_11_pro -> smartphone
create implication iphone_11 -> smartphone
mass update iphone_x -> iphone_x -iphone
mass update iphone_11_pro -> iphone_11_pro -iphone
mass update iphone_11 -> iphone_11 -iphone

Alternate proposal. iphone (which already implicates smartphone) is still used when the post depicts the iOS interface, the model can't be identified, or depicts an iPhone design that doesn't have its own tag. Scenarios like post #3626141 where there's iphone 11 pro and another iphone would have to be be retagged manually after the fact (or iphone could just be removed manually), but there <3 such instances.

EDIT: The bulk update request #3159 (forum #170534) has been approved by @evazion.

The problem with implying smartphone (and this is a pre-existing problem, since iphone already implies smartphone) is that it means phone screens with the iPhone UI get incorrectly tagged as smartphone. Fake screenshots of an iPhone screen shouldn't be tagged as smartphone, in the same way that fake screenshots of a television or computer screen shouldn't be tagged as television or monitor.

Yeah, I've always felt that posts that are only fake iOS screenshots should just be tagged phone screen and not iphone, which seems to imply a depiction of a physical device. There could be an "ios" tag instead, but I think phone screen & no other phone tags is fine.

iOS tag for those cases makes sense actually, and an accompanying andoid_(os) tag as well would work. Only issue is there's already an android_(os) tag as a copyright, but it seems to be mostly being used alongside depictions of the mascot and personifications, with only one post being of the phone OS, so I'm not sure if we should make a new tag for android-based fake screenshots or place them into that same tag.

The bulk update request #3156 (forum #170523) has been rejected by @evazion.

The bulk update request #3159 (forum #170534) has been approved by @evazion.

Created iOS (OS) for fake iOS screenshots.