----------------------------------------------------------------------------------
@MSGID: <-N2cnbibRNvuM4X4nZ2dnZfqn_udnZ2d@giganews.com>
0e32c116
@REPLY: 1@paganini.bofh.team>
084a8ce2
@REPLYADDR *Hemidactylus*
<ecphoric@allspamis.invalid>
@REPLYTO 2:5075/128 *Hemidactylus*
@CHRS: CP866 2
@RFC: 1 0
@RFC-References: <knr56nFb112U3@mid.individual.net>
1@dont-email.me> <knrbe3Fc565U5@mid.individual.net> 1@paganini.bofh.team>
<knreqdFc565U10@mid.individual.net> 1@paganini.bofh.team>
@RFC-Message-ID:
<-N2cnbibRNvuM4X4nZ2dnZfqn_udnZ2d@giganews.com>
@TZUTC: 0000
@PID: NewsTap/5.5 (iPad)
@TID: FIDOGATE-5.12-ge4e8b94
Wally J <
walterjones@invalid.nospam> wrote:
> Jolly Roger <
jollyroger@pobox.com> wrote
>
>> I never said Apple blamed anyone.
>
> Ah, but you did.
> For example, you said that Apple blamed "Instagram" (among many others).
>
> HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
> the real cause (which badgolferman understood) behind a long smokescreen.
>
>> You said that, though.
>
> No. You said it.
> For example, you said that Apple blamed "indexing"(among many others).
>
>> What actually happened is Apple investigated the issue and found that
>> the culprit was a bug in iOS (contrary to your troll gang`s claim that
>> it`s supposedly a hardware defect) combined with bugs in some popular
>> third-party apps. Apple also explained that it is normal for iPhones to
>> get warmer after operating system updates, which is true.
>
> It`s no longer shocking that you don`t understand your own threads, JR.
> You posted that Apple blamed pretty much everything that can be blamed.
>
> BTW, the concept of _why_ Apple blamed a dozen things is too complicated
> for you to comprehend - but adults know why Apple likely did that.
>
> HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
> the real cause (which badgolferman understood) behind a long smokescreen.
>
>>> They blamed Instagram, for example, right?
>>
>> Wrong. They identified a bug in Instagram that caused excessive resource
>> usage and in turn generated excessive heat.
>
> Apple blamed Instagram.
>
> Did Instagram exist prior to Apple releasing the defective iPhone 15?
> Yes? or No?
>
>>> Allow me to ask you a simple _adult_ question of your own words, JR...
>>> *Did Instagram exist before the iPhone 15 released?* Jolly Roger?
>>
>> Allow me to ask you some follow-up questions in response:
>
> HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
> the real cause (which badgolferman understood) behind a long smokescreen.
>
>> *Has Instagram been updated before and after iOS 17 was released?*
>
> You`re _desperate_ to blame Instagram, Jolly Roger.
> Let`s say it _is_ the fault of Instagram, then Jolly Roger.
> OK?
>
> Now why then did Apple provide a virtual litany of "other causes" then?
> Think about that.
>
>> *Do you understand that bugs can be introduced during updates?*
>
> Again, it`s clear how _desperate_ you are to blame anyone but Apple.
> But let`s again agree with you that "bugs were introduced", OK?
>
> Now... why then did Apple blame one of those bugs as being in iOS 17?
>
> Do you think maybe Apple _forgot_ to test the iPhone 15 with iOS 17?
> Yes? or No?
>
>> *Do you know that Instagram has had previous bugs that caused excessive
>> resource usage in the past?*
>
> That`s a repeat of your initial desperate attempt to blame Instagram for
> Apple having forgotten to sufficiently test the defective iPhone 15.
>
> Do you think Apple simply _forgot_ to test the iPhone 15 with Instagram?
> Yes? or No?
>
>>>>> iOS 17 has been installed on my work iPhone 11 and I haven?t noticed
>>>>> any problems
>>>>
>>>> Many others echo this. The bug does not effect most people.
>>>
>>> First off, you`re calling it "the bug"
>>
>> It is a bug.
>
> Actually, your own words show clearly that Apple said it was a whole lot of
> things that Apple happened to not test for before selling that iPhone 15.
>
> An intelligent _adult_ might wonder (like badgolferman did), why exactly is
> Apple so desperate to claim it was a ton of things - not just one bug?
>
> I think I know why - because I know Apple`s history of clever lies.
> But time will tell why Apple said it was everything under the sun.
>
> HINT: Apple is (rather slyly) almost certainly (cleverly) trying to hide
> the real cause (which badgolferman understood) behind a long smokescreen.
>
>> You are one of several idiot trolls here who wrongly claimed it was a
>> hardware defect That`s on record. No way to change it now. You`re just
>> making yourself look like the sad, little, squirming man-child you are.
>
> I have clearly claimed that Apple themselves told us what the problem is.
> *Apple did not sufficiently test the iPhone 15 on iOS 17 before selling it*
> <
https://groups.google.com/g/misc.phone.mobile.iphone/c/YKdktNAV7vY>
>
> For the intelligent adults on this newsgroup, I must point out that the
> mere fact Apple stooped so low as to sleazily blame pretty much everything
> that they possibly could think of to blame, that the real problem is far
> more embarrassing to Apple - which - I predict - we`ll find out over time.
>
We shall see, though I hold no bias here. And people who talk down their
noses at others as if adulting aren`t. How many sockpuppets have you
wielded recently uninteresting troll?
--- NewsTap/5.5 (iPad)
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441