KeeLoq, a cipher used widely in car key fobs, was broken by researchers who showed both cryptanalytic and side‑channel attacks could extract “manufacturer keys” and enable cloning from only two intercepted messages (even at distances up to about 100 meters). Automakers noted as using KeeLoq-based systems include Chrysler, Daewoo, Fiat, Ford, GM, Honda, Mercedes‑Benz, Toyota, Volvo, Volkswagen Group, and Jaguar. The research—first cryptanalyzed by KU Leuven and later completely broken via power-analysis by Ruhr University Bochum—turned a common convenience technology into a cross‑brand security risk for remote keyless entry as well as garage and building access systems.
CurioWire Answers
Technology questions and answers
A focused collection of clear answers connected to CurioWire technology stories and nearby search topics.
Showing 83 technology questions.
Rolling code systems change the accepted code with every button press, preventing a simple replay of a previously captured transmission from unlocking a vehicle. However, the RollJam attack showed that a small device can jam the receiver while recording two consecutive fob presses, forward the first code to open the car, and store the second for later use—defeating the rolling scheme by banking a valid “future” code. Microchip’s HCS301 KeeLoq‑based rolling code chips popularized this approach, but RollJam highlighted protocol‑level pitfalls in real‑world implementations, reminding owners and engineers that rolling codes mitigate basic replay yet require robust anti‑jamming and resynchronization designs to resist more advanced attacks.
BMW says Digital Key Plus uses Ultra‑Wideband (UWB) precise ranging between phone and vehicle so relay attacks—where radio signals are jammed or intercepted—are not possible. The feature launched on the BMW iX and lets owners unlock and start the car without taking out the iPhone. BMW also notes it worked with Apple through the Car Connectivity Consortium to align this with Digital Key 3.0, establishing a UWB‑based standard for secure passive entry. By confirming proximity with fine‑grained distance measurements, UWB helps the vehicle verify the key is truly nearby rather than a relayed signal, strengthening defense against common keyless theft techniques.
KU Leuven researchers found Tesla Model S key fobs (from supplier Pektron) used a weak 40‑bit cipher; by capturing two responses and using a precomputed key table, they could derive the fob’s key in roughly 1.6–2 seconds and then unlock and drive the car. Tesla responded by adding a PIN‑to‑Drive option, allowing owners to disable passive entry, and upgrading Model S key fob encryption for cars sold after June 2018. Tesla also issued an over‑the‑air update enabling earlier owners to switch to the more secure fobs, steps intended to reduce the risk from key cloning beyond typical relay‑style thefts.
The Newton’s early handwriting recognition was widely derided in media such as The Simpsons and Doonesbury, and the device’s tendency to misread text hurt its reputation; later versions, including Newton OS 2.0, substantially improved recognition, but the negative first impression persisted. The article notes how cultural mockery like “Eat up Martha” became shorthand for the problem and emphasizes that recognition quality did get much better in later software. Despite those improvements, sales lagged and the platform was ultimately discontinued in 1998, illustrating how early perception can overshadow technical progress.
Quikwriting is a continuous stylus-based system that keeps the pen on the screen and steers through a flower-like layout of eight “petals” around a center to form letters and words, rather than lifting after each character as in Graffiti. Developed by Ken Perlin and presented at UIST ’98, it was described as quicker than Graffiti but with a steeper learning curve. Characters and punctuation are allocated to zones, and users learn word shapes over time. As an alternative to Graffiti’s per-character strokes, Quikwriting trades initial simplicity for potentially faster, uninterrupted gestural input.
CIC’s Jot was licensed for Ericsson’s R380 smartphone, where it shipped alongside the company’s QuickNotes software. The agreement brought Jot’s handwriting recognition to the EPOC-based R380, demonstrating use of the technology outside Palm’s ecosystem. This deployment highlights Jot’s broader commercial footprint in late‑1990s mobile devices and shows how third‑party pen-input solutions spread across platforms before capacitive touch and on‑screen keyboards dominated mobile text entry.
T9 let users enter words with a single keypress per letter on a 3×4 keypad, using a built‑in dictionary to disambiguate letter groups—an improvement over multi‑tap, which often required multiple presses per character. Originally developed by Tegic (later part of Nuance), T9 was widely deployed by manufacturers such as Nokia, Samsung, Siemens and others in the late 1990s. By matching key sequences to likely words and ordering results by frequency, T9 sped up SMS and text entry on non‑touch phones and influenced later predictive typing systems.
PCI MPoC combines and extends earlier mobile standards by allowing a single COTS device to accept both PIN and contactless cardholder data, using a modular, objective-based security framework. It builds on SPoC and CPoC, adds flexibility in how solutions are developed, deployed, and maintained, and supports multiple acceptance channels and consumer verification methods. By contrast, CPoC focused only on contactless acceptance via a device’s built‑in NFC without an external reader. MPoC’s program also recognizes SDKs, applications, and complete solutions, reflecting its broader scope for vendors, acquirers, and merchants.
It replaces your primary account number with a unique payment token that can be scoped to a device, merchant, or transaction type, reducing the value of stolen data. EMV payment tokens travel end‑to‑end across the payment network—from point of purchase through issuer authorization—so their benefits apply throughout the transaction. EMVCo notes tokens help merchants lower exposure and costs tied to storing PANs, and allow issuers to control or replace tokens without reissuing cards. Tokenization supports both face‑to‑face and remote transactions, strengthening security for mobile wallets and e‑commerce alike.
Tap to Pay on iPhone uses the device’s Secure Element to read and protect contactless card data; the PAN isn’t visible to the merchant device, and Apple doesn’t store card numbers or collect transaction information tied to the payer. Card data is encrypted and signed by the Secure Element and remains protected until it reaches the merchant’s Payment Service Provider, which is the only party that can decrypt it. The solution has been evaluated by an accredited lab, approved by accepted payment networks, and on iOS 18.4 or later is PCI MPoC–validated and listed by PCI SSC. Apple’s servers also monitor device security in a PCI MPoC‑compatible manner.
A Secure Element is a tamper‑resistant environment (removable, embedded, or integrated) designed to securely host applications and cryptographic data, while a Trusted Execution Environment is an isolated execution area within the device’s main chip that protects code and data from the rest of the system. GlobalPlatform standardizes both and their APIs so services can build on a hardware root of trust and create attestable chains of trust from device to cloud. The organization reports tens of billions of Secure Elements and TEEs deployed across sectors like payments, identity, and mobile.
By validating the attestation certificate chain and checking the key description’s attestationSecurityLevel field. Google explains you should confirm the chain is signed by the Google attestation root and that the security level is TrustedEnvironment or StrongBox to trust hardware‑backed storage. Implementers retrieve the X.509 certificate chain from the hardware‑backed keystore, validate signatures and revocation status off‑device, and then inspect extension data that describes the key’s properties. Devices launched with Android 7.0+ and Google Play typically use Google’s attestation root; newer Android releases phase in Remote Key Provisioning for attestation keys.
Use ImageMagick’s -auto-orient operator to read the image’s EXIF Orientation, rotate the pixels to the correct viewing position, and reset the orientation tag, permanently fixing sideways photos. The manual explains that -auto-orient performs the needed quarter‑turn rotation based on the tag so the image displays upright (“top‑left”). If the EXIF profile was previously stripped, -auto-orient does nothing, so you may need to set rotation another way. By contrast, the -orient setting only changes metadata and doesn’t modify pixels, which won’t resolve mismatches in software that ignores the tag.
They map to specific rotations or flips: 1 = top‑left (no change), 2 = top‑right (mirror horizontally), 3 = bottom‑right (rotate 180°), 4 = bottom‑left (flip vertically), 5 = left‑top (rotate 90° plus mirror horizontally, i.e., transpose), 6 = right‑top (rotate 90° clockwise), 7 = right‑bottom (rotate 90° plus flip vertically, i.e., transverse), 8 = left‑bottom (rotate 270° clockwise). Viewers that honor this tag apply the correct transform on display. Tools that only set orientation metadata without rotating pixels can still yield sideways or mirrored images in apps that ignore EXIF.
Yes. Using CSS image-orientation: from-image tells the browser to use a photo’s embedded EXIF data to rotate it appropriately, and from-image is the property’s initial default. MDN notes the feature is widely available across modern browsers and is intended only for correcting camera‑captured orientation, not for general design rotations. Setting image-orientation: none prevents EXIF-based correction, which can expose the file’s stored orientation. For arbitrary effects or UI-driven spins, use CSS transforms (for example, transform: rotate) rather than image-orientation.
In Photos on iPhone or iPad, tap Share, then Options, and turn Location off before sending so recipients don’t receive geotags. You can also remove a photo’s stored location by choosing Adjust Location and selecting No Location. To stop new photos from embedding location, go to Settings > Privacy & Security > Location Services > Camera and set access to Never. Apple’s guide also shows how to review geotagged items, hide location from Photos on Mac via Image > Location, and generally limit what others learn from shared images.
Color shifts usually come from differences in color management and ICC profile handling. Modern browsers like Safari, Chrome, Firefox, and Edge support color‑managed images, but many applications still don’t manage color consistently, and video is often unmanaged. Platform features such as Windows 11’s Auto Color Management and device display profiles also influence results. When an app ignores embedded profiles or assumes sRGB incorrectly, colors can render oversaturated or dull compared with fully color‑managed viewers that convert between profiles accurately.
Beyond the three-line icon, Xerox Star helped standardize the desktop metaphor with icons and folders, WYSIWYG document editing, uniform object-based commands, and property sheets. These concepts framed the interface as a virtual office, where users manipulated documents and folders directly and called up settings via property sheets. The approach influenced later systems including Apple Lisa, the Macintosh, and Microsoft Windows, carrying Star’s object–action model and icon-driven desktop into mainstream computing. This lineage shows how Star’s broader interface philosophy—not just a single icon—seeded core GUI conventions adopted across commercial platforms.
Apple uses the ⌘ symbol because designer Susan Kare chose the Nordic “place of interest” sign after Steve Jobs rejected putting the Apple logo in menus. The looped-square glyph, encoded as Unicode U+2318, appeared on the original Macintosh in 1984 and has identified the Command modifier ever since. Kare found the emblem in a symbol reference, noting its prior use on Scandinavian signage. This swap reduced logo clutter while giving a distinctive, compact mark for keyboard shortcuts—an origin story that explains both the symbol’s shape and its enduring presence on Apple keyboards and menus.
Material Design recommends bottom navigation when an app has three to five top‑level destinations that require direct access. If there are more than six primary destinations, additional items should be available through a navigation drawer, while bottom navigation continues to expose the most important ones. The guidance also notes bottom navigation is primarily for mobile; larger screens often use side navigation to achieve a similar effect. This pairing of visible bottom tabs for core sections and a drawer for overflow helps balance immediacy with space constraints in responsive app navigation.
In Android, the three vertical dots indicate “more options” and tapping it opens a menu of additional actions. Official developer guidance shows the icon (MoreVert) used as an IconButton that triggers a drop‑down menu, often housing actions that don’t fit in the app bar. This standard overflow affordance helps keep primary controls visible while still providing access to less‑frequent commands in a consistent, compact way across screens and layouts.
The floppy disk persists as the save icon because it became a widely understood skeuomorphic symbol, and many programs continue to use a floppy-shaped save icon well into the 21st century. Even though floppy disks have been superseded by flash drives, cloud storage, and other media, the established visual metaphor remains effective as a conventional cue for “save.” This durability reflects how interface symbols can outlast their original technologies once users learn and recognize them at a glance.
Blu-ray uses three regions (A, B, and C) and verifies region coding in the player software rather than in the optical drive’s firmware, unlike DVDs. According to the Blu-ray Disc Association, players must enforce region coding, but content providers are not required to use it on their discs. The standard’s three-zone scheme maps continents and subregions into A, B, and C, and some titles are released without region restrictions at all. This design and policy mix explains why Blu-ray region behavior can differ from DVD practices and why some Blu-ray discs play worldwide while others remain locked to one of the three regions.
Console regional lockout was enforced through physical and technological means, including hardware differences and software checks using identifying codes, and was sometimes compounded by unintentional factors like NTSC/PAL video format incompatibilities. The approach aimed to control distribution, release timing, and pricing across markets. Platform examples show both strict region policies and later shifts toward region‑free models; bypasses also existed via adapters or software on some systems. This combination of hardware design, firmware rules, and regional standards made console games from one market often unplayable on hardware sold in another without modification.
The Second Circuit held in Universal City Studios, Inc. v. Corley (2001) that publishing and linking to DeCSS—a program that circumvents DVD encryption—could be enjoined under the DMCA’s anti‑circumvention provisions, even though computer code is speech. The court agreed that the restriction targeted the code’s functional effect of bypassing access controls, not its expressive content, and it affirmed the district court’s injunction against 2600 Magazine publisher Eric Corley. The decision became a leading precedent establishing that disseminating tools designed to defeat access controls can violate the DMCA, shaping later disputes over distribution of circumvention software.
Streaming platforms enforce geo‑blocking by determining a user’s location with Internet geolocation techniques, primarily mapping IP addresses to countries or regions, and may also use GPS queries on mobile devices, account information, and even network‑delay measurements to estimate physical location. These technical checks let services allow or deny access to catalogs and streams by jurisdiction, supporting licensing and legal compliance. Because the methods rely on network‑level signals rather than disc or device firmware settings, geo‑blocking is dynamic and can be adjusted quickly as rights or regional policies change.
DMCA Section 1201’s triennial exemptions allow circumvention of access controls on computer programs in certain lawfully acquired devices when necessary for diagnosis, maintenance, or repair. The current classes include programs controlling consumer devices, motorized land vehicles and marine vessels, and medical devices or systems, with conditions such as not using the access to reach other copyrighted works. These limited, time‑bound exemptions are renewed and updated through a rulemaking the Copyright Office administers, which in recent cycles has expanded repair‑related allowances while keeping them confined to specific use cases.
JTAG is used for boundary‑scan testing, in‑circuit debugging, and firmware programming of embedded systems. The IEEE 1149.1 standard defines a dedicated test/debug port that provides low‑overhead access to internal circuitry without exposing system buses. Manufacturers and technicians use it to verify interconnects on populated boards, flash devices in‑system, and debug processors from the first instruction after reset. Because it’s widely implemented across ICs, JTAG offers a common method to diagnose board faults and bring up hardware long before any high‑level interface is available, complementing but differing from serial consoles focused on text I/O.
U‑Boot provides a serial console that displays early boot messages and accepts commands to load images, read or write flash, configure environment variables, and control auto‑boot behavior. Its command set supports transferring kernels or boot images over serial or network links and adjusting device‑tree and environment settings stored in persistent memory. Because this console operates before an operating system loads, it’s valuable for bring‑up, recovery, and low‑level troubleshooting on embedded boards where no UI exists yet, letting technicians intercept boot, inspect state, and change parameters from a simple serial terminal.
Manufacturers add test points to PCBs so they can monitor signals or inject test stimuli during production and service. These dedicated pads or headers give automated testers and technicians direct electrical access to circuits, enabling bed‑of‑nails fixtures to validate assemblies and route failing boards to rework. Test points are a core part of design‑for‑test practices and may remain on shipped hardware for reliability and cost reasons. They’re typically labeled (e.g., TP1, TP2) and serve functions ranging from continuity checks to voltage measurements, mirroring why hidden service headers appear on many embedded devices.
Exposed or improperly controlled UART/JTAG debug ports can allow attackers to read or modify memory, execute unauthorized code, and bypass on‑chip protection mechanisms. MITRE classifies this as CWE‑1191 and explains that debug/test interfaces which lack proper authentication or authorization expose internal registers and test modes, enabling high‑likelihood impacts on confidentiality, integrity, and access control. The entry also notes that simply hiding pins on the board does not address the underlying risk; robust access control or disabling the interface is needed. Recommended mitigations include disabling the interface entirely or adding strong authentication and clearing sensitive data when entering debug mode.
New York’s Digital Fair Repair Act requires manufacturers to make diagnostic and repair information, parts, and many tools available to consumers and independent repair shops on fair and reasonable terms. The Attorney General explains that documents must be provided at no charge, and parts and certain tools must be offered at the same cost as to authorized providers. The law applies to digital electronic equipment over $10, covers items like phones, computers, and televisions, and applies to products made or sold in New York after July 1, 2023. It excludes categories such as motor vehicles and major appliances, and the Attorney General’s office enforces compliance.
JTAG is the IEEE 1149.1 standard interface that enables boundary‑scan testing and provides a common method to access, diagnose, and program integrated circuits and boards. Originally created for board‑level test, it defines a Test Access Port (TAP) and instructions such as EXTEST and SAMPLE to exercise and observe pins via a boundary‑scan register. Beyond manufacturing test, JTAG is widely used for embedded system debugging and in‑system programming, often with device‑specific extensions. The standard is supported across many processors and ICs, with implementations described by BSDL files that tools use to generate diagnostics and pinpoint interconnect faults.
U‑Boot supports recovery and maintenance through features like Device Firmware Upgrade (DFU), a network console, PXE/network boot, and an extensive command set for reading, writing, and booting from storage and network sources. Its usage documentation lists capabilities to manage environment variables, load images via TFTP/serial (loadx/loady/loadb), interact with MMC, SPI flash (sf), and filesystems, and present boot menus for fallback options. These tools let technicians reflash images, adjust boot parameters, or switch boot sources when an OS fails, making U‑Boot a practical foundation for field recovery and update workflows across many embedded platforms.
MITRE’s EMB3D guidance recommends disabling or removing physical development and debug ports (such as JTAG and UART) on production devices, ideally by engaging hardware security fuses or, at minimum, with software controls. It cautions that simply depopulating headers is not sufficient and advises that if any diagnostic capability must remain, re‑enabling a port should require an authenticated administrative action. The mitigation underscores protecting against firmware extraction and command shell access via these ports, and aligns with industrial control security mappings like IEC 62443 4‑2 to reduce embedded‑device attack surface in the field.
Investigators used yellow printer tracking dots on the leaked NSA report to help identify Reality Winner. CBS News reports the document’s nearly invisible ‘DocuColor’ dot grid encodes the printer’s date, time, and serial number. Security researcher Rob Graham read the code on the published pages and determined they were printed on May 9 at 6:20 p.m. from a machine with serial number 29535218. According to the criminal complaint and CBS’s summary, an internal audit then narrowed who had printed the report, and only Winner had also emailed The Intercept from her work computer, leading agents to her door.
The EURion constellation is a pattern of five small circles on many banknotes that allows scanners and image‑editing software to detect currency and prevent reproduction. Wikipedia notes researcher Markus Kuhn identified the motif in 2002 after a color copier refused to duplicate a 10‑euro note, and that in some devices the mere presence of five circles is enough to stop processing. The pattern appears in varied forms on currencies including the euro, U.S. dollar, and Japanese yen, and software modules associated with the Central Bank Counterfeit Deterrence Group also incorporate banknote detection.
EXIF metadata can reveal the camera make and model, capture date and time, and, when geotagging is enabled, the GPS coordinates of where a photo was taken. According to Wikipedia’s EXIF overview, these tags are embedded in the image file (commonly in the APP1 segment of JPEG/TIFF) and include technical details like exposure, aperture, and focal length. Manufacturers may add device‑specific information, including a serial number, in proprietary MakerNote fields. Because EXIF can expose location and device identifiers by default, the page highlights associated privacy risks for journalists, whistleblowers, and ordinary users.
Shine a blue LED light on the color print and examine it with a magnifying glass or microscope. EFF explains the dots are tiny, yellow, and repeated across each page, and that a blue light, a magnifying glass, or a microscope makes the pattern easier to see. Under blue illumination, the yellow marks become conspicuous, revealing a structured, repeating grid on the paper that signals the presence of a tracking pattern. This practical method lets consumers determine whether their color laser print includes machine‑identifying dots.
EFF warns that tracking dots threaten privacy and anonymous speech because no law limits their use strictly to anti‑counterfeiting. Its analysis says decoded dots can yield a printer’s serial number and manufacturer, which distributors can match to a purchaser; it cautions that agencies beyond the Secret Service—or even foreign governments and private entities—could exploit this to unmask pamphleteers or other speakers without notice or judicial oversight. EFF calls for legal protections and transparency around these marking technologies to preserve free expression and prevent misuse.
Netflix replaced its five‑star ratings with thumbs up/down in April 2017 to gather clearer, simpler feedback and make recommendations more personally relevant. Instead of public star averages, titles now display a personalized “percentage match” that reflects how likely Netflix thinks you’ll enjoy them based on your viewing habits and behavior. The company framed the shift as a way to get direct signals about taste—thumbs indicating whether Netflix’s prediction was right or wrong—so its algorithms can adjust. In practice, the experience emphasizes private, individualized matching over crowd scores, with the thumbs acting as explicit inputs while the percentage match communicates predicted fit for each member.
Explicit feedback is when users actively state preferences—for example, rating an item, ranking choices, or selecting one of two options—while implicit feedback is inferred from behavior, such as what you view, how long you watch (dwell time), what you click, or what you purchase. Recommender systems commonly leverage both: explicit signals are clearer but sparse, and implicit signals are abundant but noisier and require interpretation as preference indicators. Typical explicit examples include 1–5 ratings or creating a favorites list; implicit examples include watch history and viewing duration. Many systems blend these approaches within hybrid recommenders to improve accuracy and mitigate issues like data sparsity and cold start.
The 2017 settlement required Vizio to pay $2.2 million and to prominently disclose and obtain affirmative express consent before collecting or sharing smart‑TV viewing data. The stipulated federal court order also mandated deletion of data gathered before March 1, 2016 and the implementation of a comprehensive privacy program with biennial assessments. According to the FTC’s complaint, Vizio had installed software that captured second‑by‑second information from 11 million TVs and appended demographic details, then sold the information to third parties for uses including targeted advertising. The order bars misrepresentations about privacy and codifies consent and programmatic safeguards around television viewing data.
Yes. YouTube states that likes help its system predict your interest in similar videos, while dislikes (and “Not interested” or “Don’t recommend channel”) signal what to avoid recommending in the future. These are among the primary signals YouTube lists—along with watch history, search history, subscriptions, and satisfaction surveys—that personalize Home and Up Next suggestions. Different parts of YouTube emphasize different signals: the video you’re currently watching is the main input for what plays next, whereas Home relies more on your watch history. Using these controls, viewers can directly influence which topics and channels appear less or more frequently in recommendations.
Thumbs on Pandora directly steer a station’s playlist. A Thumbs Up indicates you like a track and leads Pandora to play similar songs and artists on that station, while a Thumbs Down both skips the track immediately and tells the system to avoid that song (and similar material) on the station going forward. Pandora’s station model applies these signals to refine the mix, using your explicit inputs to broaden or narrow what you hear. The platform’s features note that repeated downvotes can exclude tracks or even an artist from a given station, aligning the station’s output with your stated preferences.
Yes—many modern LCD TVs still ship with overscan enabled by default, but you can usually disable it in the TV’s on‑screen settings. Overscan is when the television crops the outer edge of the active picture, a legacy behavior from the analog CRT era. Although flat‑panel displays generally don’t require overscan, some models retain it, which can hide interface elements near the borders. Turning overscan off tells the TV to show the full transmitted image rather than a slightly zoomed, edge‑trimmed version. If your set offers a menu option to modify this behavior, disabling it ensures that graphics and text at the edges remain visible.
Android’s TV guidelines say some TV devices may clip the outer edge of app layouts, so any elements that must always be visible should be placed within an overscan‑safe area. If you build with the AndroidX Leanback toolkit, you shouldn’t add your own extra margins, because Leanback’s templates already include overscan‑safe padding. This prevents critical text or controls from being cropped by specific set behaviors while avoiding redundant spacing that would push content too far inward. The advice is particularly relevant for playback screens, where transport controls, titles, and metadata need to remain readable from couch distance on varied living‑room displays.
Microsoft’s Xbox app guidance recommends keeping interactive or essential UI within a TV‑safe area roughly 48 pixels from the left and right edges and 27 pixels from the top and bottom after drawing content to full screen. The Windows Developer Blog explains that some televisions hide the extreme edges, so once you extend your app to the screen bounds, you should inset key controls into this safe region. Following these margins helps focus navigation behave reliably and keeps text and buttons consistently visible across different TVs and viewing arrangements, without leaving obvious borders when content is allowed to reach the screen edge.
In iOS, the safe area is exposed via UIView’s safeAreaLayoutGuide, which defines the portion of a view not covered by the status bar or other visible bars, and developers create constraints to keep content inside it. Apple’s documentation notes that for a view controller’s root view, the guide automatically accounts for system bars and any additional insets you specify via additionalSafeAreaInsets. Constraining to this guide adapts layouts across different device configurations without hard‑coding offsets, helping ensure tappable and readable elements don’t collide with system UI while maintaining consistent, edge‑aware spacing throughout an app.
LG’s webOS TV developer guide specifies a 20‑pixel margin around all four screen edges as the overscan‑safe area, and it recommends placing essential content within this region. This practice anticipates that certain TVs or modes may clip the extreme perimeter, so reserving this margin helps ensure buttons, menus, and text remain readable and fully visible in living‑room viewing. Because webOS defines this screen‑level safe area, app layouts should be designed to respect it consistently across scenes rather than adding ad‑hoc padding only for specific views or components.
The Bell System adopted all-number calling to expand numbering capacity and replace exchange-name prefixes, starting in 1958. Numbers became fully numeric (area code, central office code, and line number), increasing the pool of assignable prefixes and averting the exhaustion forecast under the older 2L–5N scheme. Field tests showed fewer dialing errors with the new format. The shift drew public resistance—groups such as the Anti‑Digit Dialing League opposed it—and AT&T produced explanatory materials to ease adoption. Despite backlash in some big cities, the plan expanded during the 1960s as carriers standardized dialing to support growth and direct distance dialing.
ITU‑T Recommendation E.161 defines the standard mapping of letters to digits on telephone keypads, including PQRS on 7 and WXYZ on 9, and also specifies keypad arrangement and symbols. In force since 1988 (version 02/2001), it supports uses such as phonewords and multi‑tap text entry. Earlier practice varied: until the 1990s many layouts omitted Q and Z, placed them on the 1 key, or used PRS on 7 and WXY on 9. As texting and phonewords required the full alphabet, E.161 resolved these inconsistencies so devices display a consistent alphabet‑to‑number mapping today.
Phone keypads use 1–2–3 on the top row because Bell Labs’ human‑factors testing in the late 1950s found that layout worked best for dialing, and it became standard with DTMF push‑button phones. Calculators and computer numpads retained the adding‑machine tradition with 7–8–9 on top, optimized for rapid numeric entry. Bell Labs evaluated multiple arrangements and selected the current telephone pattern after extensive user studies; subsequent networks and services adopted it. The difference reflects separate design histories and tasks—the telephone’s layout optimized casual dialing accuracy and ease of use, while calculators optimized professional data‑entry speed.
“PEnnsylvania 6‑5000” was the Hotel Pennsylvania’s main number written in New York’s 2‑letters‑5‑numbers style and became famous via the Glenn Miller Orchestra’s 1940 hit of the same name. The letters PE mapped to 7 and 3, making the number 736‑5000 (later with Manhattan’s 212 area code). The hotel long claimed it was New York City’s oldest continuously used telephone number, and callers for years heard a greeting that included the song. The Pennsylvania exchange served the area around Penn Station. Although the hotel closed in 2020, the number’s exchange‑name origin and musical tie cemented its cultural resonance.
Vanity numbers are telephone numbers selected for memorability and branding, often expressed as phonewords like 1‑800‑FLOWERS, to make a business easier to reach and recall. They may be toll‑free or local and can also rely on repeated digits or patterns (for example, 1‑800‑800‑8000) as mnemonic devices. Companies request such sequences specifically for marketing so advertisements can feature a word or distinctive pattern instead of arbitrary digits. Beyond phonewords, memorable numeric sequences tied to brands, industries, or even broadcast frequencies are also used as vanity numbers to reinforce recognition across media.
South Korea’s Telecommunications Technology Association (TTA) set a 60–68 dB shutter‑sound standard for camera phones. The industry rule was created to curb privacy invasions, and it specifies that new camera‑phone models must emit an audible click in that range whenever a photo is taken. The standard followed a government camera‑phone use initiative and was developed with input from handset makers, mobile carriers, and academics before being finalized as a TTA standard. It applied to devices released from July 1, 2004, anchoring today’s region‑specific behavior on many Korean‑market smartphones.
Apple explicitly states that FaceTime isn’t available in the United Arab Emirates. On its support page covering wireless carrier features for the Middle East and India, Apple notes the UAE restriction and clarifies that in that country or region the wireless provider, not Apple, handles iPhone support, reflecting local regulations. This is a clear example of region‑specific feature availability in mainstream devices, where a core app can be restricted or disabled depending on where a device is sold or used.
Japan enacted a nationwide offense of photographing or filming on July 13, 2023, criminalizing the non‑consensual taking of sexually explicit images or videos. The statute also covers cases where someone is deceived into believing images will not be shown to others and includes provisions allowing prosecution of certain offenses committed abroad by Japanese nationals. The reform provides a clear, uniform legal basis to address voyeuristic acts across the country, distinct from any device‑level camera sound practices.
Saudi Arabia banned the sale of camera phones nationwide in April 2004, then reallowed their sale in December 2004. The move reflected privacy and security concerns surrounding early mobile cameras and contrasts with other markets that permitted camera phones but relied on audible shutter cues or industry standards. The quick reversal underscores how early camera‑phone policies varied by country and evolved rapidly as the technology spread.
Twitter set tweets to 140 characters so a post could fit in a single 160‑character SMS, reserving 20 characters for the sender’s username. This constraint was present at launch in 2006 and quickly became part of Twitter’s identity, encouraging speed and brevity in how people wrote and read updates. The SMS-rooted cap linked early tweeting to mobile texting conventions, shaping a concise, headline-like style that persisted even as the service later adjusted what counted toward the limit and expanded the maximum length.
Emoji began in 1999 when Shigetaka Kurita designed a 176‑icon, 12×12‑pixel set for NTT DoCoMo’s i‑mode mobile platform in Japan. Intended to streamline mobile communication and differentiate the service, the pictographs gained traction domestically and were later standardized and propagated as major platforms incorporated emoji support. Subsequent work by Unicode and vendors like Google and Apple helped align and broaden the sets, turning a localized, carrier‑specific idea into a global visual language used across messaging apps, operating systems, and keyboards.
SMS falls to 70 characters when the message uses 16‑bit Unicode (UCS‑2/UTF‑16) encoding instead of the default GSM 7‑bit alphabet. An SMS payload fits 140 bytes; with 7‑bit encoding that allows up to 160 characters, but with 16‑bit encoding only 70 characters fit. Handsets switch encoding when a message includes characters outside the GSM 7‑bit set (for example, many non‑Latin scripts or certain symbols), which reduces the per‑message character capacity and may trigger segmentation for longer texts.
Telegrams were billed by the word, so writers compressed messages to minimize cost, creating a clipped “telegram style.” Telegraph companies enforced word rules (e.g., up to 15 characters per plain‑language word and 10 for coded words), which reinforced brevity and omission of nonessential words. This economic pressure produced a distinctive shorthand—abbreviations, compressed phrasing, and minimal punctuation—that influenced later concise forms of communication and remains a reference point for terse, information‑dense writing.
RCS upgrades SMS by operating over mobile data and adding modern features like read receipts, group chats, typing indicators, and higher‑quality media sharing. Critically, unlike SMS’s 160‑character cap, RCS does not innately impose a text character limit, enabling much longer messages within the same conversation flow. This makes RCS functionally closer to internet chat apps while remaining integrated with a phone’s default messaging experience, provided both parties and their networks support RCS.
Spotify’s Fewer Repeats shuffle generates several mathematically random orders, scores each one for “freshness” based on how recently you’ve listened to the tracks, then picks the sequence with the highest freshness score—so recently played songs are nudged later and you hear fewer repeats. Standard Shuffle, which assigns random values to tracks and orders them purely at random, remains available, but Fewer Repeats is the default for Premium. This approach preserves randomness while aligning with listener intuition by selecting among random sequences rather than deterministically reordering your playlist.
The Fisher–Yates shuffle is a list-shuffling algorithm that produces an unbiased permutation, meaning every possible ordering is equally likely. It works by iterating through the array and swapping each element with a randomly chosen element from the remaining positions, yielding uniform results when paired with a good random number source. The article contrasts this with naïve methods (like swapping with any index each time), which are provably biased, and notes common implementation pitfalls such as off‑by‑one errors and modulo bias that can reintroduce skew if not handled carefully.
The clustering illusion is the tendency to mistakenly view the inevitable streaks or clusters in small samples from random processes as non‑random. People underpredict how much variability appears in small samples and rely on heuristics like representativeness, which makes natural clumps look suspicious. Classic illustrations include analyses of WWII bombing maps and perceived patterns in stock prices. The bias helps explain everyday misunderstandings of chance: random data often contains apparent runs, but our cognition expects smoother dispersion than genuine randomness produces.
Apple’s iTunes 5 added Smart Shuffle, a setting that lets users change the “randomness” of shuffled songs. Apple described it as giving listeners greater control over random playback, alongside other 2005 updates like a new Search Bar and playlist folders. In practice, Smart Shuffle allowed adjusting how likely similar songs might appear in succession, reflecting Apple’s response to user perceptions of random playback while keeping the experience easy to tailor.
Play Something isn’t random shuffle; it starts a title Netflix thinks you’ll like based on your interests and prior viewing. At launch, Netflix said it may select something you’re already watching, a show or film on your list, an unfinished title to resume, or a new recommendation from its personalization algorithms. The feature evolved from earlier “Shuffle Play” tests and rolled out globally on TVs in April 2021, later reaching Android, as a way to move users from browsing to watching without playing a random selection.
Motorola’s iTap differed from T9 by offering one‑keypress word completions, phrase predictions, and a distinct interface that surfaced suggestions immediately. iTap could guess the remainder of a word once several letters were entered and presented alternatives in order of common usage. It stored unknown words for later selection and emphasized completions and common phrases to speed input. Developed by Motorola as a direct T9 competitor, it relied on a built‑in dictionary and contextual prediction while leaving UI choices that contrasted with many T9 implementations, making the experience feel more like autocompletion than simple disambiguation.
German engineer Friedhelm Hillebrand set the 160‑character limit for SMS after experiments showed that length was sufficient for short text messages. As chairman of the GSM non‑voice services committee in 1985, he evaluated how much space typical messages needed and concluded that 160 characters captured the essence of most communications. That figure became foundational to the GSM standard and later influenced early digital communication norms, including Twitter’s original 140‑character cap. The limit tied message design to concise expression and shaped how early mobile users wrote and shared information.
Swype is a virtual keyboard that lets users enter words by sliding a finger from the first to the last letter, lifting only between words, and it was created by Swype Inc. founder Cliff Kushler. The software combines error‑correction and a language model to predict the intended word and enabled typing speeds competitive with traditional tapping. Swype debuted on devices like Samsung’s Omnia II, was acquired by Nuance in 2011, and its mobile apps were discontinued in 2018 after years of influence on gesture‑based text input.
Modern keyboards like Gboard predict words with on‑device machine learning, using a neural spatial model and finite‑state transducers to interpret noisy taps and generate suggestions and corrections efficiently. Google describes a character‑level spatial model that maps touch points to intended keys and compact neural components tuned to run quickly on phones. These techniques power next‑word suggestions, autocorrect, and multilingual support while keeping latency low and functionality available offline, showing how predictive text evolved from simple dictionaries to advanced, device‑optimized language models.
Look for the Thunderbolt icon plus the number 4 on the cable’s connectors. Intel states that all Thunderbolt 4 connectors are marked with the Thunderbolt symbol and the numeral 4, making genuine TB4 cables easy to recognize. Intel also notes Thunderbolt cables are certified and that Thunderbolt 4 cables can provide top transfer speeds at lengths up to 2 meters, which helps distinguish them from many earlier high‑speed USB or Thunderbolt options. These markings and certification cues reduce guesswork about compatibility with TB4 docks, displays, and high‑speed storage connected through USB‑C ports on modern systems.
USB Power Delivery 3.1’s Extended Power Range allows up to 240 W by using 48 V at 5 A, and Type‑C cables generally must include E‑Marker chips that report their capabilities. Wikipedia notes that all Type‑C cables, except the minimal combination of USB 2.0 and only 3 A, must contain E‑Markers identifying current limits, signaling support, and whether the cable is passive or active. This identification enables safe negotiation for higher voltages and currents under EPR. In short, 240 W operation relies on compliant Type‑C cables with E‑Markers and appropriate 5 A support, while basic 3 A USB 2.0‑only cables do not require E‑Markers and won’t support EPR levels.
USB4 Version 2.0 can achieve 80 Gbit/s over existing passive “USB 40Gbps” cables using a new PAM3 encoding scheme, so new passive cables aren’t strictly required. However, active cables are not forward‑compatible in the same way; the specification adds a new speed grade for active cables to support the higher rates. USB4 Version 2.0 also upgrades DisplayPort tunneling to DisplayPort 2.1, enabling higher‑bandwidth video carriage within the same link. Practically, many passive 40Gbps USB‑C cables can deliver the new 80Gbps mode, while active cables may need to be the newer grade to realize full performance.
DisplayPort Alt Mode 2.0 brings full DisplayPort 2.0 capabilities to USB‑C and provides seamless interoperability with USB4. VESA explains it enables beyond‑8K resolutions and up to 80 Gbps of DisplayPort video data over the USB‑C connector, or 40 Gbps with simultaneous SuperSpeed USB data. The spec integrates with USB4 for discovery, configuration, and power management, and DisplayPort can also be tunneled over USB4 and Thunderbolt. Together, these updates make USB‑C a single‑cable path for very high‑resolution displays, data, and power, spanning use cases from docking and gaming to AR/VR and pro HDR workflows.
HDMI Alternate Mode for USB‑C is listed as “Not being updated.” Wikipedia’s USB‑C Alternate Modes table shows HDMI Alt Mode (announced in 2016 and based on HDMI 1.4b) is no longer being updated, while DisplayPort Alt Mode remains current. The same section notes that DisplayPort signals can be carried either directly via DisplayPort Alt Mode or encapsulated in Thunderbolt, and that DisplayPort 2.0 can run alongside USB4 over USB‑C. These status notes clarify why USB‑C display solutions typically center on DisplayPort technologies rather than native HDMI Alt Mode.
UEFI standardizes removable-media boot by defining a firmware boot manager and a default loader path, so devices like USB sticks can boot automatically via \EFI\BOOT\BOOT .EFI (for example, \EFI\BOOT\BOOTX64.EFI on x86‑64). Unlike legacy BIOS, which relied on boot sectors and device‑specific quirks, UEFI discovers OS loaders by path and executes them directly. The firmware reads the EFI System Partition, supports FAT12/16/32 for this partition, and can detect loaders for multiple architectures. This approach removes many historical inconsistencies and makes booting from USB or other removable media predictable across systems.
PXE is a client‑server boot framework that starts a system by fetching a software image over the network on PXE‑enabled hardware. A PXE‑capable NIC and firmware use standard protocols like DHCP to obtain configuration and TFTP to download a network bootstrap program, which then loads the operating system components. Originating in Intel’s Wired for Management, PXE became part of UEFI and is widely used in data centers for OS installation and deployment. It enables diskless booting, consistent imaging workflows, and centralized control when removable media are impractical or unavailable.
Hybrid ISO images embed both an El Torito boot record (for optical discs) and a master boot record (for hard‑disk–like media), allowing the same ISO to boot from a CD/DVD or when written directly to a USB flash drive. ISOLINUX, part of the Syslinux project, added support for creating such “hybrid ISO” images so a single distribution image can serve both use cases. This improves installation reliability and convenience by eliminating the need for separate optical and USB images while preserving compatibility with legacy BIOS and modern systems.
Phasing out the Compatibility Support Module (CSM) removes legacy BIOS‑style booting, leaving systems to boot natively via UEFI’s boot manager and standardized loader paths. UEFI firmware can automatically find loaders on removable media using default paths such as \EFI\BOOT\BOOTX64.EFI, and vendors have announced CSM retirement timelines, reducing availability of legacy boot modes. As a result, install and recovery media need to provide UEFI‑compatible loaders and file systems rather than relying on BIOS boot sectors or compatibility modules.