203 stories
·
3 followers

Apple Might Discontinue the iPhone X This Summer

1 Comment
BGR shares a startling prediction from Ming-Chi Kuo, the Apple analyst at KGI securities: Kuo -- who we should note has an exemplary track record with respect to iPhone rumors -- adds that Apple may opt to discontinue the current iPhone X entirely if sales are underwhelming. "KGI also expects a trio of iPhone models in the fall of 2018," AppleInsider notes. "He predicts the iPhone X will be 'end of life' in the summer of 2018, instead of being retained as a lower-cost option in the following year." If Kuo's projection pans out, this would represent a marked shift in Apple's iPhone sales strategy. Going back nearly a decade, Apple has always positioned older iPhone models around as a wallet-friendly alternative for users who weren't keen on paying a premium for Apple's latest and greatest.

Read more of this story at Slashdot.

Read the whole story
Share this story
Delete
1 public comment
letssurf
30 minutes ago
reply
Oh Apple, how you are going so wrong. With the iPhone and Mac's. It maken' me sad.
Northampton, UK

Meltdown and Spectre

5 Comments and 23 Shares
New zero-day vulnerability: In addition to rowhammer, it turns out lots of servers are vulnerable to regular hammers, too.
Read the whole story
chrisminett
14 days ago
reply
Milton Keynes, UK
Share this story
Delete
5 public comments
reconbot
13 days ago
reply
hammer boom
New York City
taddevries
13 days ago
reply
Perfect!!!!!!
letssurf
14 days ago
reply
Awesome
Northampton, UK
cjheinz
14 days ago
reply
Install updates. By all means.
alt_text_bot
15 days ago
reply
New zero-day vulnerability: In addition to rowhammer, it turns out lots of servers are vulnerable to regular hammers, too.

The Impossible Dream of USB-C

1 Comment
Marco Arment, a prominent developer best known for co-founding Tumblr, explains things that are still crippling USB-C, despite being around for years and being used in mainstream products. Arment writes: While a wide variety of USB-C dongles are available, most use the same handful of unreliable, mediocre chips inside. Some USB-A dongles make Wi-Fi drop on MacBook Pros. Some USB-A devices don't work properly when adapted to USB-C, or only work in certain ports. Some devices only work when plugged directly into a laptop's precious few USB-C ports, rather than any hubs or dongles. And reliable HDMI output seems nearly impossible in practice. Very few hubs exist to add more USB-C ports, so if you have more than a few peripherals, you can't just replace all of their cables with USB-C versions. You'll need a hub that provides multiple USB-A ports instead, and you'll need to keep your USB-A cables for when you're plugged into the hub -- but also keep USB-C cables or dongles around for everything you might ever need to plug directly into the computer's ports. Hubs with additional USB-C ports might pass Thunderbolt through to them, but usually don't. Sometimes, they add a USB-C port that can only be used for power passthrough. Many hubs with power passthrough have lower wattage limits than a 13-inch or 15-inch laptop needs. Fortunately, USB-C is a great charging standard. Well, it's more of a collection of standards. USB-C devices can charge via the slow old USB rates, but for higher-powered devices or faster charging, that's not enough current.

Read more of this story at Slashdot.

Read the whole story
Share this story
Delete
1 public comment
letssurf
95 days ago
reply
USB-C fail
Northampton, UK

PSA: A new phishing attack could trick you into giving away your Apple ID password

1 Comment

If you’ve used an iOS device at all, you’ve almost certainly been presented with the above popup asking you to enter your Apple ID password. It often appears within the App Store and iTunes Store, but it also has a tendency to randomly popup from time to time due to something running in the background.

A new blog post from developer Felix Krause, however, explains how that popup could be used to easily trick someone into handing over their Apple ID and password…

more…





Read the whole story
Share this story
Delete
1 public comment
letssurf
101 days ago
reply
I've been saying this...
Northampton, UK

PhpStorm 2017.3 EAP 173.2941.8

1 Comment

The new PhpStorm 2017.3 EAP build (173.2941.8) is now available! You can download it here or via JetBrains Toolbox App. Or, if you have the previous PhpStorm 2017.3 EAP build (173.2463.17) installed, you should soon get a notification in the IDE about a patch update.

This build delivers new features, bug fixes, and improvements for PHP and the Web, and includes the latest improvements in IntelliJ Platform.

Performance Improvements

We’ve been working hard on performance improvements in the last two EAPs and we’ve managed to decrease typing latency in the very complex PHP files. For example, we’ve measured the following changes in mPDF main file (38k lines, a mix of PHP/JS/HTML):

Min Delay (ms) Max Delay (ms) Average Delay (ms)
PhpStorm 2017.3 EAP 15.4 46.2 27.3
PhpStorm 2017.2 124.9 210.4 134.6

The measurement was performed using the amazing tool, Typometer, that captures the delay between key press action and its appearance on the screen. As you see the delays have decreased by a factor of 4.

The work is still in progress and we hope to boost performance even further.  If you have particular examples of files that are sluggish in PhpStorm, please comment or create an issue in YouTrack.

Composer Log

In this build, we’ve implemented a Composer Log console. Before all the messages about composer actions and related settings changes were shown in the Event Log, which was overwhelming and not always informative. Now we’ve made a dedicated Composer Log for all Composer related actions and notifications in the project. As a bonus, you can also rerun all actions right from the Log. The Composer Log can be opened from the composer.json editor panel or from the Event Log when you get a first Composer notification. Check it out and let us know what you think!

composer

From the platform side the update brings:

  • Better synchronization of your settings across devices (more details here)
  • Mocha test runner: support –watch option (WEB-11104)

Apart from new features, this build has many bug fixes, including these:

  • Parse exception while converting JSON to object class working with GitHub (IDEA-178764)
  • Only some foreign key edges are shown in the diagram (DBE-2130)
  • Postgres: Database console sets different timezone in session that PGAdmin (DBE-2996)

See the full list of bug-fixes and improvements in our issue tracker and the complete release notes.

Download PhpStorm 2017.3 EAP 173.2941 for your platform from the project EAP page or click “Update” in your JetBrains Toolbox App. And please do report any bugs and feature request to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

Read the whole story
Share this story
Delete
1 public comment
letssurf
107 days ago
reply
At last, some performance love 💕
Northampton, UK

Apple fixes the Disk Utility APFS bug: What you need to know!

1 Comment

If you create an additional, secure APFS container on an existing APFS drive using Disk Utility, and set a password hint, there's a bug that will show your actual password instead. But a fix is already on its way.

Apple has just pushed out a macOS High Sierra Supplemental Update to fix an issue with Disk Utility, APFS encrypted containers, and password hints.

From Matheus Mariano:

This week, Apple released the new macOS High Sierra with the new file system called APFS (Apple File System). It wasn't long before I encountered issues with this update. Not a simple issue, but a potential vulnerability.

The issue, as best as I understand it, was as follows:

  1. If you have an APFS formatted SSD drive and:
  2. You create a new container on that drive using the Disk Utilities GUI and:
  3. You make it an encrypted container and:
  4. You add a password hint for the container

Then the GUI would mix up the fields and store the container password in the plain-text password hint field and display the password as the hint whenever you re-mount the container.

If you didn't use the Disk Utility GUI and created the container through Terminal, or if you used the Disk Utility GUI but didn't set a password hint, you wouldn't be affected by the bug.

As bugs go, it was super dumb. But Mariano had already reported it to Apple, and Apple is already deploying a fix.

The number of people affected — those with physical access to a device with an existing APFS container that also has an additional, encrypted APFS container who wouldn't also have the password to that container — is probably tiny. Still, Apple has provided the following instructions for how to roll back even under those circumstances:

  1. Install the macOS High Sierra 10.13 Supplemental Update from the App Store updates page.
  2. Create an encrypted backup of the affected encrypted APFS volume.
  3. Open Disk Utility and select the affected encrypted APFS volume in the sidebar.
  4. Click Unmount to unmount the volume.
  5. Click Erase.
  6. When asked, type a name for the volume in the Name field.
  7. Change Format to APFS.
  8. Then change Format again to APFS (Encrypted).
  9. Enter a new password in the dialog. Enter it again to verify the password, and if you'd like to, provide a hint for the encrypted APFS volume. Click Choose.
  10. Click Erase. You can see the progress of the Erase process.
  11. Click Done when the process is complete.
  12. Restore the data that you backed up in Step 1 to the new encrypted APFS volume that you just created.

The macOS High Sierra 10.13 Supplemental Update should be live by the time you read this, and you can access and update to it via the Mac App Store.

Also note, if you used the same password for your encrypted APFS container as any other accounts (for example, your Mac user account), change those accounts. Better safe than sorry.

Read the whole story
Share this story
Delete
1 public comment
letssurf
107 days ago
reply
Oh dear Apple. Poor show.
Northampton, UK
Next Page of Stories