171–180 of 279 posts
Earlier quoted context omitted.
Hahaha on Yahoo we called it booting.
On AOL we called it "punting", and the apps that facilitated it were the first reason I ever wanted to code.
Those must've been some scary code bases.
bplist00Ô X$versionX$objectsY$archiverT$top † ¦U$nullÓ WNS.keysZNS.objectsV$class¢ €€¢€€€RanVldtext¢ËqÒZ$classnameX$classes\NSDictionary¢XNSObject_NSKeyedArchiverÑ Troot€#-27>DKS^ehjloqsux„‰”ª¶ÈËÐ Ò
Earlier quoted context omitted.
Back in the day AOL parsed HTML for it's instant messages, a would blue screen any client running windows. It was quite easy to empty chat room(s) using this.
Hahaha on Yahoo we called it booting.
Just post in the general chat area.
“Hey, to speed up Yahoo Games, press alt-f4.”
Earlier quoted context omitted.
Considering it's enabled by default, i'm really curious why you would want to do that.
It costs money to activate it (or so says the pop up that appears when you set up an iPhone). Also if I switch to Android I don’t have to worry about disabling iMessage before. (Not that anybody in my country would ever send an iMessage or an SMS though...)
Not sure what pop-up you're talking about then.
Earlier quoted context omitted.
I never understood this, why would anyone want to deal with ANOTHER app to do messaging? iMessage is built in, integrated, and has end to end encryption. What more functionality are people clamoring for?
People want to use one app to do all their messaging. iMessage is not that app unless 100% of the people you message use iPhones. For a lot of people Whatsapp or Telegram can be that app.
While there are a lot of reasons not to want to use iMessage but only being able to talk to other iOS users isn’t one.
Earlier quoted context omitted.
Considering it's enabled by default, i'm really curious why you would want to do that.
It costs money to activate it (or so says the pop up that appears when you set up an iPhone). Also if I switch to Android I don’t have to worry about disabling iMessage before. (Not that anybody in my country would ever send an iMessage or an SMS though...)
Earlier quoted context omitted.
That's not really a coupling issue, but a matter of GPU drivers not generally being hardened against shader/usage bugs. Similar issues have existed on Windows, Linux, etc. browsers with WebGL support.
> That's not really a coupling issue, but a matter of GPU drivers not generally being hardened against shader/usage bugs. You shouldn't be able to crash the whole operating system (not just the display server, display driver, etc.) with an ordinary shader, even if it crashes the shader compiler or causes the GPU not to halt. It's not as though I wrote these shaders in an attempt to crash iOS.
Sure, you could patch the app to avoid sending what's known as bad data to the next layer but I'd argue that that's the wrong place to do it.
Earlier quoted context omitted.
Hahaha on Yahoo we called it booting.
On AOL we called it "punting", and the apps that facilitated it were the first reason I ever wanted to code.
Earlier quoted context omitted.
>If you can recover in any way Physically replacing every single component, one by one, will lead to a recovery. >I stand by words mean things. They are an abstraction of thought to enable communication and external storage. A very leaky abstraction.
A bricked device can be recovered - usually - by replacing hardware, that's the limit of the definition. The GP comment is right, bricked is bricked and there's no way to recover a bricked device with any software means. It means the hardware is fucked and it's usefulness is equivalent to a brick.
At the end of the day language is (for all pragmatic purposes) finite but possible states of the universe are not, so you can't have a perfect definition of that catches all possible states you want while excluding all others with perfect accuracy.