AidenShaw
Sep 10, 11:48 PM
I've owned SMP machines in the past and often found it more useful to force CPU affinity of CPU-heavy tasks to a single processor, as Windows 2000 (which was current at the time) by default had a habit of swapping it between chips, resulting in a lot of cache-dirtying....
However, you could see some significant improvement in processing time on some non-parallelizable cpu-bound tasks.
I came to the opposite conclusion....
Running many compute-bound single-threaded benchmarks and apps - I saw how NT (pre Win2k) would balance across CPUs (that is, a "100%" compute-bound job would show each CPU running at 50%).
However, setting affinity so that one CPU was 100% and the other was 0% had no significant effect on the run times. (And by "significant" I mean statistically significant - I literally ran hundreds of runs in each configuration.)\\
By the way, with Win2k3 (and XP 64-bit, really the same system) you see much less "balancing" - a single-threaded app will stick to a CPU for much longer.
However, you could see some significant improvement in processing time on some non-parallelizable cpu-bound tasks.
I came to the opposite conclusion....
Running many compute-bound single-threaded benchmarks and apps - I saw how NT (pre Win2k) would balance across CPUs (that is, a "100%" compute-bound job would show each CPU running at 50%).
However, setting affinity so that one CPU was 100% and the other was 0% had no significant effect on the run times. (And by "significant" I mean statistically significant - I literally ran hundreds of runs in each configuration.)\\
By the way, with Win2k3 (and XP 64-bit, really the same system) you see much less "balancing" - a single-threaded app will stick to a CPU for much longer.
QCassidy352
Sep 13, 09:02 PM
arn very rarely posts info from his own sources. When he does, that info is always correct. I'd bet a good deal of my savings that the iphone will look very similar to that pic.
segfaultdotorg
Apr 22, 01:31 PM
Again, why bother unless they will include a coupon for a free OS upgrade when Lion comes out in a couple of months?
4God
Aug 28, 12:16 PM
Merom... (http://guides.macrumors.com/Merom)
Yeah for the portables, but Conroe for the desktop.
Yeah for the portables, but Conroe for the desktop.
zer0sum
Mar 22, 12:44 PM
I did read it. It doesn't answer why there are no viruses today, now that Mac OS has greater market share than ever, when there were viruses back when it had a much smaller market share. The market share theory is pure nonsense. It doesn't stand up to simple math.
The theory that OS X is completely secure is equally nonsense.
You definitely don't need an anti-malware solution installed right now, but it is only a matter of time.
There is a reason malware isn't prevalent and it's certainly not because there are no flaws to be leveraged into exploits.
Just look at the security fixes of 10.6.7 update released a few days ago: http://support.apple.com/kb/HT4581
Here's a list of some of the more serious 54 security fixes released
AppleScript
A format string issue existed in AppleScript Studio's generic dialog commands ("display dialog" and "display alert"). Running an AppleScript Studio-based application that allows untrusted input to be passed to a dialog may lead to an unexpected application termination or arbitrary code execution.
ATS
A heap buffer overflow issue existed in the handling of OpenType, TrueType and Type 1 fonts. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
Multiple buffer overflow issues existed in the handling of SFNT tables. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
bzip2
An integer overflow issue existed in bzip2's handling of bzip2 compressed files. Using the command line bzip2 or bunzip2 tool to decompress a bzip2 file may result in an unexpected application termination or arbitrary code execution.
ClamAV
Multiple vulnerabilities exist in ClamAV, the most serious of which may lead to arbitrary code execution. This update addresses the issues by updating ClamAV to version 0.96.5. ClamAV is distributed only with Mac OS X Server systems.
CoreText
A memory corruption issue existed in CoreText's handling of font files. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
File Quarantine
The OSX.OpinionSpy definition has been added to the malware check within File Quarantine.
ImageIO
A heap buffer overflow issue existed in ImageIO's handling of JPEG and XBM images. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A buffer overflow existed in libTIFF's handling of JPEG encoded TIFF images and CCITT Group 4 encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution.
An integer overflow issue existed in ImageIO's handling of JPEG-encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Image RAW
Multiple buffer overflow issues existed in Image RAW's handling of Canon RAW images. Viewing a maliciously crafted Canon RAW image may result in an unexpected application termination or arbitrary code execution.
Installer
A URL processing issue in Install Helper may lead to the installation of an agent that contacts an arbitrary server when the user logs in. The dialog resulting from a connection failure may lead the user to believe that the connection was attempted with Apple. This issue is addressed by removing Install Helper.
Kerberos
Multiple cryptographic issues existed in MIT Kerberos 5. Only CVE-2010-1323 affects Mac OS X v10.5.
Kernel
A privilege checking issue existed in the i386_set_ldt system call's handling of call gates. A local user may be able to execute arbitrary code with system privileges. This issue is addressed by disallowing creation of call gate entries via i386_set_ldt().
libxml
A memory corruption issue existed in libxml's XPath handling. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A double free issue existed in libxml's handling of XPath expressions. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Mailman
Multiple cross-site scripting issues existed in Mailman 2.1.13. These issues are addressed by updating Mailman to version 2.1.14.
PHP
PHP is updated to version 5.3.4 to address multiple vulnerabilities, the most serious of which may lead to arbitrary code execution.
QuickLook
A memory corruption issue existed in QuickLook's handling of Excel files. Downloading a maliciously crafted Excel file may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
A memory corruption issue existed in QuickLook's handling of Microsoft Office files. Downloading a maliciously crafted Microsoft Office file may lead to an unexpected application termination or arbitrary code execution.
QuickTime
Multiple memory corruption issues existed in QuickTime's handling of JPEG2000 images. Viewing a maliciously crafted JPEG2000 image with QuickTime may lead to an unexpected application termination or arbitrary code execution.
An integer overflow existed in QuickTime's handling of movie files. Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A memory corruption issue existed in QuickTime's handling of FlashPix images. Viewing a maliciously crafted FlashPix image may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A cross-origin issue existed in QuickTime plug-in's handling of cross-site redirects. Visiting a maliciously crafted website may lead to the disclosure of video data from another site. This issue is addressed by preventing QuickTime from following cross-site redirects.
A memory corruption issue existed in QuickTime's handling of panorama atoms in QTVR (QuickTime Virtual Reality) movie files. Viewing a maliciously crafted QTVR movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
Ruby
An integer truncation issue existed in Ruby's BigDecimal class. Running a Ruby script that uses untrusted input to create a BigDecimal object may lead to an unexpected application termination or arbitrary code execution. This issue only affects 64-bit Ruby processes.
Samba
A stack buffer overflow existed in Samba's handling of Windows Security IDs. If SMB file sharing is enabled, a remote attacker may cause a denial of service or arbitrary code execution.
Subversion
Subversion servers that use the non-default "SVNPathAuthz short_circuit" mod_dav_svn configuration setting may allow unauthorized users to access portions of the repository. This issue is addressed by updating Subversion to version 1.6.13. This issue does not affect systems prior to Mac OS X v10.6.
X11
Multiple vulnerabilities existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font. These issues are addressed by updating FreeType to version 2.4.3
The theory that OS X is completely secure is equally nonsense.
You definitely don't need an anti-malware solution installed right now, but it is only a matter of time.
There is a reason malware isn't prevalent and it's certainly not because there are no flaws to be leveraged into exploits.
Just look at the security fixes of 10.6.7 update released a few days ago: http://support.apple.com/kb/HT4581
Here's a list of some of the more serious 54 security fixes released
AppleScript
A format string issue existed in AppleScript Studio's generic dialog commands ("display dialog" and "display alert"). Running an AppleScript Studio-based application that allows untrusted input to be passed to a dialog may lead to an unexpected application termination or arbitrary code execution.
ATS
A heap buffer overflow issue existed in the handling of OpenType, TrueType and Type 1 fonts. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
Multiple buffer overflow issues existed in the handling of SFNT tables. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
bzip2
An integer overflow issue existed in bzip2's handling of bzip2 compressed files. Using the command line bzip2 or bunzip2 tool to decompress a bzip2 file may result in an unexpected application termination or arbitrary code execution.
ClamAV
Multiple vulnerabilities exist in ClamAV, the most serious of which may lead to arbitrary code execution. This update addresses the issues by updating ClamAV to version 0.96.5. ClamAV is distributed only with Mac OS X Server systems.
CoreText
A memory corruption issue existed in CoreText's handling of font files. Viewing or downloading a document containing a maliciously crafted embedded font may lead to arbitrary code execution.
File Quarantine
The OSX.OpinionSpy definition has been added to the malware check within File Quarantine.
ImageIO
A heap buffer overflow issue existed in ImageIO's handling of JPEG and XBM images. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A buffer overflow existed in libTIFF's handling of JPEG encoded TIFF images and CCITT Group 4 encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution.
An integer overflow issue existed in ImageIO's handling of JPEG-encoded TIFF images. Viewing a maliciously crafted TIFF image may result in an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Image RAW
Multiple buffer overflow issues existed in Image RAW's handling of Canon RAW images. Viewing a maliciously crafted Canon RAW image may result in an unexpected application termination or arbitrary code execution.
Installer
A URL processing issue in Install Helper may lead to the installation of an agent that contacts an arbitrary server when the user logs in. The dialog resulting from a connection failure may lead the user to believe that the connection was attempted with Apple. This issue is addressed by removing Install Helper.
Kerberos
Multiple cryptographic issues existed in MIT Kerberos 5. Only CVE-2010-1323 affects Mac OS X v10.5.
Kernel
A privilege checking issue existed in the i386_set_ldt system call's handling of call gates. A local user may be able to execute arbitrary code with system privileges. This issue is addressed by disallowing creation of call gate entries via i386_set_ldt().
libxml
A memory corruption issue existed in libxml's XPath handling. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution.
A double free issue existed in libxml's handling of XPath expressions. Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
Mailman
Multiple cross-site scripting issues existed in Mailman 2.1.13. These issues are addressed by updating Mailman to version 2.1.14.
PHP
PHP is updated to version 5.3.4 to address multiple vulnerabilities, the most serious of which may lead to arbitrary code execution.
QuickLook
A memory corruption issue existed in QuickLook's handling of Excel files. Downloading a maliciously crafted Excel file may lead to an unexpected application termination or arbitrary code execution. This issue does not affect systems prior to Mac OS X v10.6.
A memory corruption issue existed in QuickLook's handling of Microsoft Office files. Downloading a maliciously crafted Microsoft Office file may lead to an unexpected application termination or arbitrary code execution.
QuickTime
Multiple memory corruption issues existed in QuickTime's handling of JPEG2000 images. Viewing a maliciously crafted JPEG2000 image with QuickTime may lead to an unexpected application termination or arbitrary code execution.
An integer overflow existed in QuickTime's handling of movie files. Viewing a maliciously crafted movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A memory corruption issue existed in QuickTime's handling of FlashPix images. Viewing a maliciously crafted FlashPix image may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
A cross-origin issue existed in QuickTime plug-in's handling of cross-site redirects. Visiting a maliciously crafted website may lead to the disclosure of video data from another site. This issue is addressed by preventing QuickTime from following cross-site redirects.
A memory corruption issue existed in QuickTime's handling of panorama atoms in QTVR (QuickTime Virtual Reality) movie files. Viewing a maliciously crafted QTVR movie file may lead to an unexpected application termination or arbitrary code execution. For Mac OS X v10.5 this issue was addressed in QuickTime 7.6.9.
Ruby
An integer truncation issue existed in Ruby's BigDecimal class. Running a Ruby script that uses untrusted input to create a BigDecimal object may lead to an unexpected application termination or arbitrary code execution. This issue only affects 64-bit Ruby processes.
Samba
A stack buffer overflow existed in Samba's handling of Windows Security IDs. If SMB file sharing is enabled, a remote attacker may cause a denial of service or arbitrary code execution.
Subversion
Subversion servers that use the non-default "SVNPathAuthz short_circuit" mod_dav_svn configuration setting may allow unauthorized users to access portions of the repository. This issue is addressed by updating Subversion to version 1.6.13. This issue does not affect systems prior to Mac OS X v10.6.
X11
Multiple vulnerabilities existed in FreeType, the most serious of which may lead to arbitrary code execution when processing a maliciously crafted font. These issues are addressed by updating FreeType to version 2.4.3
jonnymo5
Mar 29, 12:57 PM
Hmmm looks like the analyst just took the current Symbian market share and gave it to Windows7 for 2015. I think that is very naive. I think that many more people will move to Android, iPhone and WebOS in the time it takes Nokia to ramp up the Windows phones.
freeny
Aug 23, 09:23 PM
100million to make a nagging itch go away? not bad and well worth it IMO.
If only the middle East were so diplomatic....
If only the middle East were so diplomatic....
arn
Apr 11, 01:59 AM
They'll change the key and force a firmware update on any airport express user who wants to update itunes.
Are the 3rd party AirPlay speakers firmware upgradable?
http://www.apple.com/itunes/airplay/
That will break compatibility with those speakers.
arn
Are the 3rd party AirPlay speakers firmware upgradable?
http://www.apple.com/itunes/airplay/
That will break compatibility with those speakers.
arn
jacollins
Apr 20, 12:02 PM
Password protect your phone. Password protect your computer. Nothing has changed.
That forensic software the police has can bypass the password on your phone.
That forensic software the police has can bypass the password on your phone.
caspersoong
Apr 22, 05:06 AM
Useless to me if it is just for iTunes purchases. Please focus on more important things, Apple.
MrFirework
Oct 27, 01:56 PM
I think that's pretty accurate (well observed) whichever side of this particular fence people are sitting.
Yeah, but what is currently out there that's better?
Yeah, but what is currently out there that's better?
iMeowbot
Sep 16, 01:29 PM
But then why would he say "Some people might be coming up with that soon" ?
The BG quote was "I don't carry an ipod. I think carrying music on my mobile phone is much better. Some people might be doing that in the future." (chuckles)"
"Carrying music on my mobile" would be the "future" thing (never mind that there are already phones that do this, and even phones and PDAs running Windows Mobile that do this...)
The BG quote was "I don't carry an ipod. I think carrying music on my mobile phone is much better. Some people might be doing that in the future." (chuckles)"
"Carrying music on my mobile" would be the "future" thing (never mind that there are already phones that do this, and even phones and PDAs running Windows Mobile that do this...)
cvaldes
Mar 29, 11:19 AM
I predict that in 2015, iOS handset users will still have the highest customer satisfaction and that Apple will be walking away with the lion's share of the smartphone industry's profits.
Meaning there will be more grumpy non-iPhone users and more grumpy HTC/Nokia/Samsung/Motorola/LG shareholders.
Meaning there will be more grumpy non-iPhone users and more grumpy HTC/Nokia/Samsung/Motorola/LG shareholders.
xMBPx
Mar 23, 04:59 PM
Tell them NO ! No ! NO ! The States/Cities do not enforce the Law to the extreme like they should after the 1st offense !!!!! What difference does it make if all you are going to do is smack their little hand the first few times !!!! The folks that are going to break the law are going to break the law no matter what !!! Also I might add that I have seen here in the greater Kansas City Mo area that the newspapers post the areas anyway ...
I live in KC too and whenever theres a checkpoint I get about 3-5 texts that day warning me and telling me to forward it to everyone I know. :rolleyes:
I live in KC too and whenever theres a checkpoint I get about 3-5 texts that day warning me and telling me to forward it to everyone I know. :rolleyes:
Vegasman
Mar 30, 12:43 PM
Quote:
Originally Posted by Vegasman
Examples of uses (Dvorak in his references to "killer app"):
2005: http://www.marketwatch.com/story/a-k...or-real-estate
2004: http://www.pcmag.com/article2/0,2817,1599324,00.asp
2003: http://www.pcmag.com/article2/0,2817,1191830,00.asp
What I understood is that the word "App" by itself is not the reason for the lawsuit, but the term "App Store" is; both words used together. .
Correct. I was simply providing additional evidence that "app" was used before the App Store. Something the poster I was replying to was saying and something a lot of other posters are claiming is not true.
Originally Posted by Vegasman
Examples of uses (Dvorak in his references to "killer app"):
2005: http://www.marketwatch.com/story/a-k...or-real-estate
2004: http://www.pcmag.com/article2/0,2817,1599324,00.asp
2003: http://www.pcmag.com/article2/0,2817,1191830,00.asp
What I understood is that the word "App" by itself is not the reason for the lawsuit, but the term "App Store" is; both words used together. .
Correct. I was simply providing additional evidence that "app" was used before the App Store. Something the poster I was replying to was saying and something a lot of other posters are claiming is not true.
mcrain
Apr 20, 02:56 PM
So, AFTER paying 30% in federal and state income taxes, whatever percentage in sales and property tax, you are still able give away an additional 50% or more to charity? So you are able to live on like 3% of your earnings? I would LOVE to be in that position! It's very admirable, but hardly reachable for the average person. I try to give whenever I can, but I can admit that's it's usually around $2k a year.
Actually, it is far more likely that they donate from pre-tax earnings, then use those donations to reduce their tax burden. The end result being a net tax rate of something like the 17-25% most high income taxpayers pay.
Actually, it is far more likely that they donate from pre-tax earnings, then use those donations to reduce their tax burden. The end result being a net tax rate of something like the 17-25% most high income taxpayers pay.
MacRumors
Apr 28, 03:17 PM
http://www.macrumors.com/images/macrumorsthreadlogo.gif (http://www.macrumors.com/2011/04/28/apple-beats-microsoft-in-first-quarter-profit/)
http://images.macrumors.com/article/2011/04/28/154057-microsoft_logo.jpg
trendy short haircuts 2011 for
Short Hair Styles 2011
http://images.macrumors.com/article/2011/04/28/154057-microsoft_logo.jpg
boncellis
Jul 14, 12:36 PM
From what I can tell Merom is just a Conroe that can operate at a lower TDP. They're all just fabricated off the same piece of silicon. (Someone posted an image on this.)
That's right. Even Woodcrest is part of the same family. They're just designed and engineered for different purposes (mobile, desktop, server).
What's missing to me is the uniform marketing scheme to help sell potential customers. Intel has Centrino Duo currently, presumably Centrino 2 Duo (terrible name, in my opinion) for Merom, Core 2 Duo/Extreme (equally terrible) for Conroe, but I haven't heard anything for Woodcrest. Xeon Duo? Xeon Core 2? I have no idea.
The point is that they all have a lot in common, but it's easy to get confused, and Intel isn't really helping at this point. Where are the marketing people to get it right? At least Apple's scheme is somewhat better--Mac Mini, iMac, Mac Pro--more clearly defined segmentation in my opinion.
That's right. Even Woodcrest is part of the same family. They're just designed and engineered for different purposes (mobile, desktop, server).
What's missing to me is the uniform marketing scheme to help sell potential customers. Intel has Centrino Duo currently, presumably Centrino 2 Duo (terrible name, in my opinion) for Merom, Core 2 Duo/Extreme (equally terrible) for Conroe, but I haven't heard anything for Woodcrest. Xeon Duo? Xeon Core 2? I have no idea.
The point is that they all have a lot in common, but it's easy to get confused, and Intel isn't really helping at this point. Where are the marketing people to get it right? At least Apple's scheme is somewhat better--Mac Mini, iMac, Mac Pro--more clearly defined segmentation in my opinion.
MacNewsFix
Apr 19, 09:31 AM
iOS 1 puts Android 2.2 to shame?
Now you are just talking out of your @ss. In all honesty the difference between iOS and Android is so subtle.
I've had an iPod Touch since its first release. Zero crashes in four years.
I've had the HTC Hero since Winter 2009. I have zero additional apps on the device and have to pull the battery out due to a freeze at least once a month. This is my third Hero.
Now you are just talking out of your @ss. In all honesty the difference between iOS and Android is so subtle.
I've had an iPod Touch since its first release. Zero crashes in four years.
I've had the HTC Hero since Winter 2009. I have zero additional apps on the device and have to pull the battery out due to a freeze at least once a month. This is my third Hero.
milo
Jul 20, 04:43 PM
Better be careful. I posted a similar idea in another thread and got flamed by a couple antagonistic people who have limited vision and are knashing for Woodcrest. I'm in agreement with you. I think having Conroes in the middle and lowend to replace the currently shipping Powermacs is feasible for Apple. Keep the G5 Quad until Kentsfield and maybe introduce a 3.0 Quad Woodcrest on the high-end workstation model to start a new professional line?
I can see why folks are clamoring for Woodcrest, but to me it seems a bit weird for Apple to adopt a chipset for 6 months or less. With Kentsfield shipping at the end of the year, why bother with Woodcrest now? If they would have begun selling last month when they first came out it would have made more sense. Now I'm thinking Apple is going to hold off simply because they haven't announced anything. Woodcrest has been out for around a month now, if Apple is/was going to use them, what's the hold up? I think they have been waiting for Conroe, not WWDC.
You don't think Apple would get raked over the coals if they released towers that were slower than the last generation? Conroe is fast, but no way it beats a quad G5. And I don't think a promise of a quad machine later on helps public relations any.
Also, doesn't the kentsfield have the same limitation as conroe? That you can only use it in single processor configs? A woodcrest chipset would have a longer life since you'd use the same one for multiple cloverton configs.
Next gen, conroe gets you 2 cores, woodcrest gives you 2 chips for 4 cores.
Gen after that, kentsfield gets you 4 cores, cloverton gets you 2 chips for 8 cores. There's room for both chipsets for at least the next two generations, and I wouldn't be surprised if it continues beyond that.
I can see why folks are clamoring for Woodcrest, but to me it seems a bit weird for Apple to adopt a chipset for 6 months or less. With Kentsfield shipping at the end of the year, why bother with Woodcrest now? If they would have begun selling last month when they first came out it would have made more sense. Now I'm thinking Apple is going to hold off simply because they haven't announced anything. Woodcrest has been out for around a month now, if Apple is/was going to use them, what's the hold up? I think they have been waiting for Conroe, not WWDC.
You don't think Apple would get raked over the coals if they released towers that were slower than the last generation? Conroe is fast, but no way it beats a quad G5. And I don't think a promise of a quad machine later on helps public relations any.
Also, doesn't the kentsfield have the same limitation as conroe? That you can only use it in single processor configs? A woodcrest chipset would have a longer life since you'd use the same one for multiple cloverton configs.
Next gen, conroe gets you 2 cores, woodcrest gives you 2 chips for 4 cores.
Gen after that, kentsfield gets you 4 cores, cloverton gets you 2 chips for 8 cores. There's room for both chipsets for at least the next two generations, and I wouldn't be surprised if it continues beyond that.
M2M
Apr 11, 06:55 AM
Because the 3rd party device could be in your neighbours house so your neighbour can see or hear anything that is played through AirPlay from your devices without you knowing. And you might be playing stuff that you wouldn't want your neighbour to see.
Only if i set my neighbors device as a speaker in iTunes...which would happen not too often without me knowing.
Only if i set my neighbors device as a speaker in iTunes...which would happen not too often without me knowing.
Str8edgepunker
Apr 25, 04:28 PM
Please no insane 15.6" screens with a 16:9 resolution ratio. I don't care whatever else happens.
puuukeey
Sep 5, 11:08 AM
sounds logical but fake
morespce54
Apr 4, 12:05 PM
What would you do if someone was shooting at you?
...Eh, shoot back? But not in the head... A head shot, geez... That wasn't meant to stop him, that was meant to kill him...
...Eh, shoot back? But not in the head... A head shot, geez... That wasn't meant to stop him, that was meant to kill him...