Introducing iPhone Pocket: a beau­ti­ful way to wear and carry iPhone

Born out of a col­lab­o­ra­tion be­tween ISSEY MIYAKE and Apple, iPhone Pocket fea­tures a sin­gu­lar 3D-knitted con­struc­tion de­signed to fit any iPhone

ISSEY MIYAKE and Apple to­day un­veiled iPhone Pocket. Inspired by the con­cept of “a piece of cloth,” its sin­gu­lar 3D-knitted con­struc­tion is de­signed to fit any iPhone as well as all pock­etable items. Beginning Friday, November 14, it will be avail­able at se­lect Apple Store lo­ca­tions and on ap­ple.com in France, Greater China, Italy, Japan, Singapore, South Korea, the UK, and the U. S.

iPhone Pocket fea­tures a ribbed open struc­ture with the qual­i­ties of the orig­i­nal pleats by ISSEY MIYAKE. Born from the idea of cre­at­ing an ad­di­tional pocket, its un­der­stated de­sign fully en­closes iPhone, ex­pand­ing to fit more of a user’s every­day items. When stretched, the open tex­tile sub­tly re­veals its con­tents and al­lows users to peek at their iPhone dis­play. iPhone Pocket can be worn in a va­ri­ety of ways — hand­held, tied onto bags, or worn di­rectly on the body. Featuring a play­ful color palette, the short strap de­sign is avail­able in eight col­ors, and the long strap de­sign in three col­ors.

“The de­sign of iPhone Pocket speaks to the bond be­tween iPhone and its user, while keep­ing in mind that an Apple prod­uct is de­signed to be uni­ver­sal in aes­thetic and ver­sa­tile in use,” shared Yoshiyuki Miyamae, de­sign di­rec­tor of MIYAKE DESIGN STUDIO. “iPhone Pocket ex­plores the con­cept of ‘the joy of wear­ing iPhone in your own way.’ The sim­plic­ity of its de­sign echoes what we prac­tice at ISSEY MIYAKE — the idea of leav­ing things less de­fined to al­low for pos­si­bil­i­ties and per­sonal in­ter­pre­ta­tion.”

“Apple and ISSEY MIYAKE share a de­sign ap­proach that cel­e­brates crafts­man­ship, sim­plic­ity, and de­light,” said Molly Anderson, Apple’s vice pres­i­dent of Industrial Design. “This clever ex­tra pocket ex­em­pli­fies those ideas and is a nat­ural ac­com­pa­ni­ment to our prod­ucts. The color palette of iPhone Pocket was in­ten­tion­ally de­signed to mix and match with all our iPhone mod­els and col­ors — al­low­ing users to cre­ate their own per­son­al­ized com­bi­na­tion. Its rec­og­niz­able sil­hou­ette of­fers a beau­ti­ful new way to carry your iPhone, AirPods, and fa­vorite every­day items.”

Crafted in Japan, iPhone Pocket fea­tures a sin­gu­lar 3D-knitted con­struc­tion that is the re­sult of re­search and de­vel­op­ment car­ried out at ISSEY MIYAKE. The de­sign drew in­spi­ra­tion from the con­cept of “a piece of cloth” and rein­ter­preted the every­day util­ity of the brand’s iconic pleated cloth­ing. The de­vel­op­ment and de­sign of iPhone Pocket un­folded in close col­lab­o­ra­tion with the Apple Design Studio, which pro­vided in­sight into de­sign and pro­duc­tion through­out.

iPhone Pocket is a spe­cial-edi­tion re­lease. The short strap de­sign is avail­able in lemon, man­darin, pur­ple, pink, pea­cock, sap­phire, cin­na­mon, and black; the long strap de­sign is avail­able in sap­phire, cin­na­mon, and black. iPhone Pocket in the short strap de­sign re­tails at $149.95 (U. S.), and the long strap de­sign at $229.95 (U.S.).

Customers can pur­chase iPhone Pocket be­gin­ning Friday, November 14, at se­lect Apple Store lo­ca­tions and ap­ple.com in France, Greater China, Italy, Japan, Singapore, South Korea, the UK, and the U. S. Just in time for the hol­i­days, Apple Specialists in stores and on­line can help cus­tomers mix and match dif­fer­ent lengths and col­ors with their iPhone, style iPhone Pocket, and pur­chase their new fa­vorite ac­ces­sory.

ISSEY MIYAKE was founded in 1971 by the name­sake de­signer, one year af­ter the es­tab­lish­ment of MIYAKE DESIGN STUDIO. The com­pany op­er­ates through an in­te­grated process for cloth­ing and re­lated items, en­com­pass­ing cre­ative con­cep­tion, de­vel­op­ment, man­u­fac­tur­ing, and re­tail op­er­a­tions. Guided by the phi­los­o­phy of “bringing un­prece­dented orig­i­nal­ity for ease in every­day life,” ISSEY MIYAKE prac­tices this com­mit­ment through prod­ucts con­ceived with so­ci­ety and the fu­ture in mind, thus en­sur­ing a last­ing cul­ture of in­no­v­a­tive de­sign and mak­ing.

Apple rev­o­lu­tion­ized per­sonal tech­nol­ogy with the in­tro­duc­tion of the Macintosh in 1984. Today, Apple leads the world in in­no­va­tion with iPhone, iPad, Mac, AirPods, Apple Watch, and Apple Vision Pro. Apple’s six soft­ware plat­forms — iOS, iPa­dOS, ma­cOS, watchOS, vi­sionOS, and tvOS — pro­vide seam­less ex­pe­ri­ences across all Apple de­vices and em­power peo­ple with break­through ser­vices in­clud­ing the App Store, Apple Music, Apple Pay, iCloud, and Apple TV. Apple’s more than 150,000 em­ploy­ees are ded­i­cated to mak­ing the best prod­ucts on earth and to leav­ing the world bet­ter than we found it.

I was eight years old when I first tried to hack the in­tro screens of Commodore-64 games. I found a BASIC pro­gram­ming book and opened it with all the en­thu­si­asm of a kid who thought he was about to un­lock the se­crets of the uni­verse. Page af­ter page of mys­te­ri­ous com­mands, strange sym­bols, promises of power.

And then I saw it:

10 X = 5

20 X = X + 1

30 PRINT X

X equals X plus one? That’s not math. That’s a lie. Zero can’t equal one. This was non­sense, and I wanted noth­ing to do with it.

Little did I know that this mo­ment of con­fu­sion would de­fine the next two decades of my life.

Years passed. I played games, broke things, learned just enough to be dan­ger­ous.

Then uni­ver­sity hap­pened. First year, sit­ting in the li­brary, and there it was: The C Programming Language by Brian W. Kernighan and Dennis M. Ritchie. The fa­mous K&R book. The Bible.

void swap(int *a, int *b) {

int temp = *a;

*a = *b;

*b = temp;

What is `a? Why the as­ter­isks? What doesvoid` mean? Why are there two stars?*

But some­thing was dif­fer­ent this time. Instead of clos­ing the book, I started cook­ing. I did­n’t un­der­stand the recipe, but I started mix­ing in­gre­di­ents any­way.

This led to what I now call my “Linux for­mat­ting era.” I had two par­ti­tions on my home com­puter:

I for­mat­ted Linux so many times that I could do it in my sleep. Every ex­per­i­ment, every com­pi­la­tion er­ror, every seg­men­ta­tion fault was a les­son. I was learn­ing by de­stroy­ing and re­build­ing, over and over.

X = X + 1 was start­ing to make sense, but only in the most me­chan­i­cal way. I could write loops. I could in­cre­ment coun­ters. But I still did­n’t feel it.

During those years, while I was for­mat­ting Linux par­ti­tions and de­bug­ging seg­faults, I had an­other life: com­pet­i­tive bridge. I was good enough to make the na­tional team, spend­ing week­ends at tour­na­ments, play­ing hands with peo­ple who could cal­cu­late odds in their sleep.

One of my part­ners was an older en­gi­neer. Between games, af­ter a par­tic­u­larly bru­tal hand, he asked me a sim­ple ques­tion:

“How can you sum the num­bers from 1 to 10 with­out us­ing a loop?”

“Without a loop? I just learned x = x + 1. Are you kid­ding?”

Not long af­ter, I found a Prolog book. And there it was: re­cur­sion.

sum(0, 0).

sum(N, Result) :-

N > 0,

N1 is N - 1,

sum(N1, Sum1),

Result is N + Sum1.

?- sum(10, X).

X = 55.

This was­n’t X = X + 1. This was Y = X + 1. This was a re­la­tion­ship. This was math telling the truth again.

Suddenly, that en­gi­neer’s ques­tion made sense. You don’t need loops. You don’t need mu­ta­tion. You just need to de­scribe what some­thing is, not how to com­pute it step by step.

For the first time since that Commodore-64 book, I felt like some­one was talk­ing to me in a lan­guage I could un­der­stand.

Bridge tour­na­ments are funny places. You’re com­pet­ing against peo­ple one mo­ment, shar­ing sto­ries the next. During a break at one tour­na­ment, I got to talk­ing with a player from Sweden. The usual stuff at first—tough hands, bad luck, that feel­ing when you know your part­ner’s about to make a mis­take and you can’t stop them.

Then, some­how, we got to pro­gram­ming.

“Have you heard of Erlang?” he asked.

“Erlang? No. What is it?”

“It’s from Sweden. From Ericsson. It’s for tele­com sys­tems. You can build dis­trib­uted, fault-tol­er­ant sys­tems. It’s func­tional, like Prolog.”

Those were the days when we fi­nally had in­ter­net at home. I was try­ing to write a mul­ti­player socket-based bridge game for our home net­work—some­thing so my friends and I could play with­out be­ing in the same room.

Let me show you what blew my mind. What made me stay up un­til 4am, what made me skip bridge prac­tice, what made me re­al­ize I’d found some­thing spe­cial.

-module(ping).

-export([start/0, ping/​1]).

start() ->

reg­is­ter(ping, spawn(fun() -> ping(0) end)).

ping(Count) ->

re­ceive

{pong, Pong_PID} ->

io:for­mat(“Ping re­ceived pong (~p)~n”, [Count]),

Pong_PID ! {ping, self()},

ping(Count + 1)

end.

-module(pong).

-export([start/0, pong/​0]).

start() ->

reg­is­ter(pong, spawn(fun pong/​0)).

pong() ->

re­ceive

{ping, Ping_PID} ->

io:for­mat(“Pong re­ceived ping~n”),

Ping_PID ! {pong, self()},

pong()

end.

% Terminal 1

erl -sname ping -setcookie se­cret

(ping@localhost)1> c(ping).

(ping@localhost)2> ping:start().

% Terminal 2

erl -sname pong -setcookie se­cret

(pong@localhost)1> c(pong).

(pong@localhost)2> pong:start().

(pong@localhost)3> {ping, ‘ping@localhost’} ! {pong, self()}.

% Watch them talk to each other across nodes!

Two sep­a­rate Erlang nodes. On dif­fer­ent ma­chines, dif­fer­ent net­works, dif­fer­ent con­ti­nents if I wanted. And they could just… talk. No HTTP. No REST API. No se­ri­al­iza­tion headaches. Just mes­sage pass­ing. Just ac­tors do­ing their thing.

This was func­tional (no mu­ta­tion, just re­cur­sion and pat­tern match­ing) and dis­trib­uted (processes on dif­fer­ent nodes) and fault-tol­er­ant (if one crashes, the other keeps run­ning).

This was every­thing I’d been search­ing for since I was eight years old and could­n’t un­der­stand why X could equal X plus one.

I was good at bridge. National team level. But when I found Erlang, the choice was easy.

I stopped go­ing to tour­na­ments. Stopped spend­ing week­ends cal­cu­lat­ing card prob­a­bil­i­ties. This strange, beau­ti­ful lan­guage from Sweden had shown me some­thing more in­ter­est­ing than any hand of cards ever could.

Erlang was­n’t just a pro­gram­ming lan­guage. It was a phi­los­o­phy:

Let it crash (don’t try to han­dle every er­ror)

Processes are cheap (spawn mil­lions if you want)

It was func­tional pro­gram­ming and dis­trib­uted sys­tems and fault tol­er­ance all in one el­e­gant pack­age.

If you want to un­der­stand why Erlang cap­tured my imag­i­na­tion, why it changed the way I think about build­ing sys­tems, watch this:

This video, made by the peo­ple who cre­ated Erlang at Ericsson, cap­tures the spirit of what made me fall in love. The phi­los­o­phy. The el­e­gance. The sheer fun of build­ing sys­tems that don’t fall apart.

This is where I’ll share what I’ve learned over 30+ years of build­ing soft­ware sys­tems. From that con­fused 8-year-old clos­ing a BASIC book to now.

I’ll write about Erlang, Elixir, func­tional pro­gram­ming, dis­trib­uted sys­tems, and all the things I wish some­one had ex­plained to me when I was young.

P. S.: Next posts will cover Clojure (JVM—you know why), then Scala, F#, and back to Elixir/Erlang with prac­ti­cal pat­terns and war sto­ries. Stay tuned.

“If you want to go fast, go alone; if you want to go far, go to­gether”

This phrase will slowly kill your com­pany and I’m here to prove it.

Imagine you are dri­ving a car. It’s of­ten use­ful to have some­one give you di­rec­tions, point out gas sta­tions, and rec­om­mend stops for snacks. This is a help­ful amount of col­lab­o­ra­tion.

An un­help­ful amount of col­lab­o­ra­tion is get­ting out of your car to ask pedes­tri­ans if they like your car, swap­ping dri­vers every 10 min­utes, or hav­ing some­one con­stantly com­ment­ing on your dri­ving.

In the first sce­nario, you get the right amount of feed­back to get to your des­ti­na­tion as fast as pos­si­ble. In the sec­ond, you get more feed­back, but it slows you down. You run the risk of not mak­ing it to the place you want to go.

The sec­ond sce­nario is also the one most star­tups (or com­pa­nies, re­ally) end up in be­cause of ✨ col­lab­o­ra­tion ✨.

As PostHog grows, I’ve seen more and more col­lab­o­ra­tion that does­n’t add value or adds far too lit­tle value for the time lost col­lab­o­rat­ing. So much so we made “collaboration sucks” the topic of the week dur­ing a re­cent com­pany all hands.

“You’re the dri­ver” is a key value for us at PostHog. We aim to hire peo­ple who are great at their jobs and get out of their way. No dead­lines, min­i­mal co­or­di­na­tion, and no man­agers telling you what to do.

In re­turn, we ask for ex­tra­or­di­nar­ily high own­er­ship and the abil­ity to get a lot done by your­self. Marketers ship code, sales­peo­ple an­swer tech­ni­cal ques­tions with­out backup, and prod­uct en­gi­neers work across the stack.

This means there is al­most al­ways some­one bet­ter at what you are do­ing than you are. It is tempt­ing to get them, or any­body re­ally, in­volved and ✨ col­lab­o­rate ✨, but col­lab­o­ra­tion forces the dri­ver to slow down and ex­plain stuff (background, con­text, their think­ing).

This ten­dency re­veals it­self in a few key phrases:

* “Would love to hear Y’s take on this”

* “We should work with Z on this”

This some­times leads to valu­able in­sights, but al­ways slows the dri­ver down. It erodes their mo­ti­va­tion, con­fi­dence, and ef­fec­tive­ness, and ul­ti­mately leads us to ship less.

Everyone is to blame.

* People want to be help­ful. For ex­am­ple, when some­one posts their work-in-progress in Slack, oth­ers feel obliged to give feed­back be­cause we have a cul­ture of feed­back.

* On the flip side, peo­ple don’t ask for feed­back from spe­cific peo­ple be­cause it does­n’t feel in­clu­sive, even though it would help.

* People aren’t spe­cific enough about what feed­back they need. This cre­ates more space for col­lab­o­ra­tion to sneak in. A dis­cus­sion about build­ing a spe­cific fea­ture can de­volve into reeval­u­at­ing the en­tire prod­uct roadmap if you let it.

* When some­one has a good idea, the re­sponse of­ten de­faults to “let’s dis­cuss” rather than “ok, do it.” As proof, we have 175 men­tions of “let’s dis­cuss” in Slack.

* People just want to talk about stuff be­cause they can’t be both­ered to act on it. We drift from our ideal of a pull re­quest to an is­sue/​RFC to Slack (we are mostly here) to “let’s dis­cuss”.

* It’s not clear who the owner is (or no one wants to own what’s be­ing dis­cussed).

* It is an­noy­ing, but some­times a sin­gle per­son can’t ship cer­tain things front to back to a high-enough qual­ity and we can’t just ship and it­er­ate. We can fix bro­ken code, but we can’t re­send a newslet­ter.

So if col­lab­o­ra­tion is your en­emy, how do you de­feat it? Here’s what we say:

* Every time you see ✨ col­lab­o­ra­tion ✨ hap­pen­ing, speak up and de­stroy it. Say “there are too many peo­ple in­volved. X, you are the dri­ver, you de­cide.” (This is a great way to make friends btw).

* Tag who you specif­i­cally want in­put from and what you want from them, not just throw things out there into the void.

* Prefer to give feed­back af­ter some­thing has shipped (but be­fore the next it­er­a­tion) rather than re­view­ing it be­fore it ships. Front-loading your feed­back can turn it into a quasi-ap­proval process.

* If you are a team lead, or leader of leads, who has been asked for feed­back, con­sider be­ing more you can just do stuff.

* When it’s your thing, you are the “informed cap­tain.” Listen to feed­back, but know it’s ul­ti­mately up to you to de­cide what to do, not the peo­ple giv­ing feed­back.

Unfortunately for me, not all col­lab­o­ra­tion can be rooted out, and even I will ad­mit that some col­lab­o­ra­tion is use­ful. Ian and Andy edited this newslet­ter af­ter all.

The point is, if you aren’t ac­tively at­tempt­ing to col­lab­o­rate less, you are prob­a­bly col­lab­o­rat­ing too much by de­fault and hurt­ing your abil­ity to go far, fast.

Words by Charles Cook, who also hates sparkling wa­ter, pre­sum­ably be­cause the bub­bles are too col­lab­o­ra­tive.

SoftBank said Tuesday it has sold its en­tire stake in U. S. chip­maker Nvidia for $5.83 bil­lion as the Japanese gi­ant looks to cap­i­tal­ize on its “all in” bet on ChatGPT maker OpenAI.

The firm said in its earn­ings state­ment that it sold 32.1 mil­lion Nvidia shares in October. It also dis­closed that it sold part of its T-Mobile stake for $9.17 bil­lion.

“We want to pro­vide a lot of in­vest­ment op­por­tu­ni­ties for in­vestors, while we can still main­tain fi­nan­cial strength,” said SoftBank’s chief fi­nan­cial of­fi­cer, Yoshimitsu Goto, dur­ing an in­vestor pre­sen­ta­tion.

“So through those op­tions and tools we make sure that we are ready for fund­ing in a very safe man­ner,” he said in com­ments trans­lated by the com­pany, adding that the stake sales were part of the fir­m’s strat­egy for “asset mon­e­ti­za­tion.”

The sale of Nvidia shares, par­tial sale of T-Mobile shares and the mar­gin loan on SoftBank’s hold­ing in Arm, are all “sources of cash that will be used to fund the $22.5 bil­lion in­vest­ment in OpenAI,” a per­son fa­mil­iar with the mat­ter told CNBC. They added that this cash will fund other pro­jects the firm is work­ing on such as its ac­qui­si­tion of ABB’s ro­bot­ics unit.

The of­fload­ing of the Nvidia stake had noth­ing to do with con­cerns about ar­ti­fi­cial in­tel­li­gence val­u­a­tions, the per­son said.

While the Nvidia exit may come as a sur­prise to some in­vestors, it’s not the first time SoftBank has cashed out of the American AI chip dar­ling.

SoftBank’s Vision Fund was an early backer of Nvidia, re­port­edly amass­ing a $4 bil­lion stake in 2017 be­fore sell­ing all of its hold­ings in January 2019. Despite its lat­est sale, SoftBank’s busi­ness in­ter­ests re­main heav­ily in­ter­twined with Nvidia’s.

With Firefox 145, we’re rolling out ma­jor pri­vacy up­grades that take on browser fin­ger­print­ing — a per­va­sive and hid­den track­ing tech­nique that lets web­sites iden­tify you even when cook­ies are blocked or you’re in pri­vate brows­ing. These pro­tec­tions build on Mozilla’s long-term goal of build­ing a health­ier, trans­par­ent and pri­vacy-pre­serv­ing web ecosys­tem.

Fingerprinting builds a se­cret dig­i­tal ID of you by col­lect­ing sub­tle de­tails of your setup — rang­ing from your time zone to your op­er­at­ing sys­tem set­tings — that to­gether cre­ate a “fingerprint” iden­ti­fi­able across web­sites and across browser ses­sions. Having a unique fin­ger­print means fin­ger­print­ers can con­tin­u­ously iden­tify you in­vis­i­bly, al­low­ing bad ac­tors to track you with­out your knowl­edge or con­sent. Online fin­ger­print­ing is able to track you for months, even when you use any browser’s pri­vate brows­ing mode.

Protecting peo­ple’s pri­vacy has al­ways been core to Firefox. Since 2020, Firefox’s built-in Enhanced Tracking Protection (ETP) has blocked known track­ers and other in­va­sive prac­tices, while fea­tures like Total Cookie Protection and now ex­panded fin­ger­print­ing de­fenses demon­strate a broader goal: pri­or­i­tiz­ing your on­line free­dom through in­no­v­a­tive pri­vacy-by-de­sign. Since 2021, Firefox has been in­cre­men­tally en­hanc­ing anti-fin­ger­print­ing pro­tec­tions tar­get­ing the most com­mon pieces of in­for­ma­tion col­lected for sus­pected fin­ger­print­ing uses.

Today, we are ex­cited to an­nounce the com­ple­tion of the sec­ond phase of de­fenses against fin­ger­print­ers that linger across all your brows­ing but aren’t in the known tracker lists. With these fin­ger­print­ing pro­tec­tions, the amount of Firefox users track­able by fin­ger­print­ers is re­duced by half.

Drawing from a global analy­sis of how real peo­ple’s browsers can be fin­ger­printed, Mozilla has de­vel­oped new, unique and pow­er­ful de­fenses against real-world fin­ger­print­ing tech­niques. Firefox is the first browser with this level of in­sight into fin­ger­print­ing and the most ef­fec­tive de­ployed de­fenses to re­duce it. Like Total Cookie Protection, one of our most in­no­v­a­tive pri­vacy fea­tures, these new de­fenses are de­but­ing in Private Browsing Mode and ETP Strict mode ini­tially, while we work to en­able them by de­fault.

These fin­ger­print­ing pro­tec­tions work on mul­ti­ple lay­ers, build­ing on Firefox’s al­ready ro­bust pri­vacy fea­tures. For ex­am­ple, Firefox has long blocked known track­ing and fin­ger­print­ing scripts as part of its Enhanced Tracking Protection.

Beyond block­ing track­ers, Firefox also lim­its the in­for­ma­tion it makes avail­able to web­sites — a pri­vacy-by-de­sign ap­proach — that pre­emp­tively shrinks your fin­ger­print. Browsers pro­vide a way for web­sites to ask for in­for­ma­tion that en­ables le­git­i­mate web­site fea­tures, e.g. your graph­ics hard­ware in­for­ma­tion, which al­lows sites to op­ti­mize games for your com­puter.  But track­ers can also ask for that in­for­ma­tion, for no other rea­son than to help build a fin­ger­print of your browser and track you across the web.

Since 2021, Firefox has been in­cre­men­tally ad­vanc­ing fin­ger­print­ing pro­tec­tions, cov­er­ing the most per­va­sive fin­ger­print­ing tech­niques. These in­clude things like how your graph­ics card draws im­ages, which fonts your com­puter has, and even tiny dif­fer­ences in how it per­forms math. The first phase plugged the biggest and most-com­mon leaks of fin­ger­print­ing in­for­ma­tion.

Recent Firefox re­leases have tack­led the next-largest leaks of user in­for­ma­tion used by on­line fin­ger­print­ers. This ranges from strength­en­ing the font pro­tec­tions to pre­vent­ing web­sites from get­ting to know your hard­ware de­tails like the num­ber of cores your proces­sor has, the num­ber of si­mul­ta­ne­ous fin­gers your touch­screen sup­ports, and the di­men­sions of your dock or taskbar. The full list of de­tailed pro­tec­tions is avail­able in our doc­u­men­ta­tion.

Our re­search shows these im­prove­ments cut the per­cent­age of users seen as unique by al­most half.

Firefox’s new pro­tec­tions are a bal­ance of dis­rupt­ing fin­ger­print­ers while main­tain­ing web us­abil­ity. More ag­gres­sive fin­ger­print­ing block­ing might sound bet­ter, but is guar­an­teed to break le­git­i­mate web­site fea­tures. For in­stance, cal­en­dar, sched­ul­ing, and con­fer­enc­ing tools le­git­i­mately need your real time zone. Firefox’s ap­proach is to tar­get the most leaky fin­ger­print­ing vec­tors (the tricks and scripts used by track­ers) while pre­serv­ing func­tion­al­ity many sites need to work nor­mally. The end re­sult is a set of lay­ered de­fenses that sig­nif­i­cantly re­duce track­ing with­out down­grad­ing your brows­ing ex­pe­ri­ence. More de­tails are avail­able about both the spe­cific be­hav­iors and how to rec­og­nize a prob­lem on a site and dis­able pro­tec­tions for that site alone, so you al­ways stay in con­trol. The goal: strong pri­vacy pro­tec­tions that don’t get in your way.

If you open a Private Browsing win­dow or use ETP Strict mode, Firefox is al­ready work­ing be­hind the scenes to make you harder to track. The lat­est phase of Firefox’s fin­ger­print­ing pro­tec­tions marks an im­por­tant mile­stone in our mis­sion to de­liver: smart pri­vacy pro­tec­tions that work au­to­mat­i­cally — no fur­ther ex­ten­sions or con­fig­u­ra­tions needed. As we head into the fu­ture, Firefox re­mains com­mit­ted to fight­ing for your pri­vacy, so you get to en­joy the web on your terms. Upgrade to the lat­est Firefox and take back con­trol of your pri­vacy.

Take con­trol of your in­ter­net

Discover a unique col­lec­tion of lap­tops adorned with cre­ative stick­ers from around the world. This pro­ject cel­e­brates the art and cul­ture of lap­top per­son­al­iza­tion each lap­top tells a story through its stick­ers and gives us a glimpse of the per­son­al­ity of the own­ers.

It be­came quickly clear that the erup­tion would be fol­lowed by an im­pres­sive coro­nal mass ejec­tion (CME). The re­sult­ing coro­nal wave fol­low­ing the so­lar ex­plo­sion as well as the coro­nal dim­ming ob­served as the CME was pro­pelled into space were of a spec­tac­u­lar mag­ni­tude as can be seen in the an­i­ma­tion be­low pro­vided by halocme.

Another erup­tion from AR12474, as­so­ci­ated with an X5.1 flare. It has be­come a full halo CME. I am truly im­pressed by how fast and global this coro­nal wave is. The CME will ar­rive on November 13, but be­cause of ear­lier CMEs it will be chal­leng­ing to iso­late the ICME from this. pic.twit­ter.com/​H6eN­jzQUGz— Halo CME (@halocme) November 11, 2025

Taking a look at coro­n­a­graph im­agery pro­vided by GOES-19 CCOR-1 we see the gor­geous fast halo coro­nal mass ejec­tion as it prop­a­gates away from the Sun. It does­n’t take a rocket sci­en­tist to come to the con­clu­sion that this plasma cloud of course has an earth-di­rected com­po­nent and it is pretty clear that this will be a strong im­pact when it ar­rives at our planet. This right­fully so prompted the NOAA SWPC to is­sue a G4 or greater ge­o­mag­netic storm watch for to­mor­row as the cloud could im­pact our planet as early as 16 UTC on 12 November. Not only is the CME fast but it will also travel trough an area with high am­bi­ent so­lar wind speed and low den­sity thanks to two other CMEs re­leased ear­lier by this re­gion. More about that be­low.

If the so­lar wind and in­ter­plan­e­tary mag­netic field val­ues at Earth are fa­vor­able this could re­sult in a ge­o­mag­netic storm which is strong enough for au­rora to be­come vis­i­ble from lo­ca­tions as far south as north­ern France, Germany, Ukraine, Switzerland and Austria. In the US it could be­come vis­i­ble as far south as Nevada and Arkansas. No guar­an­tees of course, this is space weather we are talk­ing about but be sure to down­load the SpaceWeatherLive app to your mo­bile de­vice, turn on the alerts and keep an eye on the so­lar wind data from ACE and DSCOVR!

We also want to re­mind you that we still have two coro­nal mass ejec­tions on their way to Earth. These are not as im­pres­sive as this X5.1 CME but these two plasma clouds will likely ar­rive within the next 6 to 18 hours. This is a tricky one as they could ar­rive as one im­pact or two im­pacts close in­till each other. More in­for­ma­tion in yes­ter­day’s news.

Thank you for read­ing this ar­ti­cle! Did you have any trou­ble with the tech­ni­cal terms used in this ar­ti­cle? Our help sec­tion is the place to be where you can find in-depth ar­ti­cles, a FAQ and a list with com­mon ab­bre­vi­a­tions. Still puz­zled? Just post on our fo­rum where we will help you the best we can! Never want to miss out on a space weather event or one of our news ar­ti­cles again? Subscribe to our mail­ing list, fol­low us on Twitter and Facebook and down­load the SpaceWeatherLive app for Android and iOS!

Canada’s out­break be­gan last October, with health of­fi­cials at­tribut­ing it to fewer peo­ple be­ing vac­ci­nated against measles.

The US, how­ever, risks los­ing its sta­tus as well if it does not stop an on­go­ing out­break by January. Related cases have now been re­ported in Utah, Arizona and South Carolina.

Because Canada is no longer deemed measles-free, the Americas re­gion as a whole has lost its elim­i­na­tion sta­tus, al­though in­di­vid­u­ally the other coun­tries are still con­sid­ered to have stamped out the dis­ease.

Canada has lost its measles elim­i­na­tion sta­tus, said the Pan American Health Organization (Paho) on Monday, af­ter fail­ing to curb an out­break of the virus for 12 con­sec­u­tive months.

Canada’s out­break be­gan last October, with health of­fi­cials at­tribut­ing it to fewer peo­ple be­ing vac­ci­nated against measles.

The US, how­ever, risks los­ing its sta­tus as well if it does not stop an on­go­ing out­break by January. Related cases have now been re­ported in Utah, Arizona and South Carolina.

Because Canada is no longer deemed measles-free, the Americas re­gion as a whole has lost its elim­i­na­tion sta­tus, al­though in­di­vid­u­ally the other coun­tries are still con­sid­ered to have stamped out the dis­ease.

Canada has lost its measles elim­i­na­tion sta­tus, said the Pan American Health Organization (Paho) on Monday, af­ter fail­ing to curb an out­break of the virus for 12 con­sec­u­tive months.

At a news con­fer­ence on Monday, Paho of­fi­cials ap­pealed to Canadian gov­ern­ments and the pub­lic to ramp up vac­ci­na­tions, not­ing that 95% of the pop­u­la­tion needs to be im­mu­nised to stop the spread of measles.

“This loss rep­re­sents a set­back, but it is also re­versible,” said Dr Jarbas Barbosa, the health or­gan­i­sa­tion’s di­rec­tor.

The Public Health Agency of Canada said in its own state­ment that it is col­lab­o­rat­ing with Paho and re­gional health au­thor­i­ties to im­prove vac­cine rates and strengthen data shar­ing.

Prior to Monday, Canada had been de­clared measles-free for three decades. It can re­gain its elim­i­na­tion sta­tus if it can curb spread of the measles strain as­so­ci­ated with the cur­rent out­break for at least 12 months.

The coun­try has re­ported more than 5,000 measles cases in 2025, with most of them in the provinces of Ontario and Alberta. That is three times the 1,681 cases re­ported in the US, de­spite Canada’s much smaller pop­u­la­tion.

The bulk of the out­break has been in “under-vaccinated com­mu­ni­ties”, Canadian health of­fi­cials have said.

Vaccination rates in Alberta, one of the provinces hit hard by the out­break, are lower than the 95% thresh­old, ac­cord­ing to provin­cial data.

One re­gion, the South Zone, lo­cated south of the province’s largest city Calgary, re­ported only 68% of chil­dren un­der the age of two were im­mu­nised against measles as of 2024.

The MMR vac­cine is the most ef­fec­tive way to fight off the dan­ger­ous virus, which can lead to pneu­mo­nia, brain swelling and death. The jabs are 97% ef­fec­tive and also im­mu­nise against mumps and rubella.

Canadian im­mu­nol­o­gist Dawn Bowdish told the BBC that there are many rea­sons be­hind the low vac­ci­na­tion rates, in­clud­ing lack of ac­cess to gen­eral prac­ti­tion­ers, the ab­sence of a na­tional vac­ci­na­tion reg­istry that Canadians could use to check their im­mu­ni­sa­tion sta­tus, and the spread of mis­in­for­ma­tion.

She also noted a lack of pub­lic health out­reach to com­mu­ni­ties that have been hes­i­tant or dis­trust­ful of vac­cines.

“It high­lights how many of our sys­tems broke down to get us to this point,” said Prof Bowdish of McMaster University in Hamilton, Ontario.

“I hope that it will be a wake-up call to pol­i­cy­mak­ers, and that it will be enough of a na­tional em­bar­rass­ment that we rem­edy some of those sys­temic is­sues,” she added

The Americas is the first and only re­gion in the world to have been de­clared measles-free, start­ing in 2016. That sta­tus was then briefly lifted af­ter out­breaks in Venezuela and Brazil. The two coun­tries re­gained elim­i­na­tion sta­tus in 2024, in part through co­or­di­nated vac­cine ef­forts where mil­lions were im­mu­nised.

But measles has since spread again, now in North America.

Along with Canada and the United States, Mexico has also seen a surge in cases and now ranks among the top 10 coun­tries with the largest out­breaks, ac­cord­ing to the US Centers for Disease Control and Prevention.

The R47 is a pow­er­ful, RPN-based pro­gram­ma­ble sci­en­tific cal­cu­la­tor with an ex­ten­sive fea­ture set. Its soft­ware has been re­fined over many years, born from the vi­sion of a dream cal­cu­la­tor de­vel­oped by a team of en­gi­neers and math­e­mati­cians, all ded­i­cated cal­cu­la­tor en­thu­si­asts.

Community-developed and man­u­fac­tured by SwissMicros, the R47 runs firmware that is func­tion­ally iden­ti­cal to that of the C47, which of­fers a way to trans­form a DM42n into a fea­ture-rich RPN cal­cu­la­tor us­ing a ded­i­cated key­pad over­lay.

The C47/R47 firmware orig­i­nated as a fork of the WP43 pro­ject, it­self de­rived from the WP34S. A core com­po­nent car­ried through this lin­eage is the dec­Num­ber li­brary by Mike Cowlishaw, also used in GCC for pre­cise dec­i­mal arith­metic.

Inspired by the HP‑41C and HP‑42S, the R47 builds on this foun­da­tion with a re­designed key­pad fea­tur­ing two shift keys, pre­serv­ing a fa­mil­iar feel while be­ing en­tirely new in ex­e­cu­tion.

* Advanced Math Capabilities:Provides 34 dig­its of pre­ci­sion; ex­po­nents to ±6144; up to 1000 named vari­ables.

* Provides 34 dig­its of pre­ci­sion; ex­po­nents to ±6144; up to 1000 named vari­ables.

* Programming and Editing:

* Engineering and Utilities:Conduct fi­nan­cial and date-based cal­cu­la­tions, in­clud­ing time value of money op­er­a­tions.Per­form date and time math as well as built-in clock.Equa­tion writer with sup­port for solv­ing, nu­meric in­te­gra­tion and de­riv­a­tives, and ba­sic plot­ting.

* Conduct fi­nan­cial and date-based cal­cu­la­tions, in­clud­ing time value of money op­er­a­tions.

* Perform date and time math as well as built-in clock.

* Equation writer with sup­port for solv­ing, nu­meric in­te­gra­tion and de­riv­a­tives, and ba­sic plot­ting.

* Display and User Interface:Features a high-res­o­lu­tion dis­play with 4 stack lev­els, 3 rows of menus, and sta­tus bar al­ways shown.

* Features a high-res­o­lu­tion dis­play with 4 stack lev­els, 3 rows of menus, and sta­tus bar al­ways shown.

* Data Management:I/O to built-in flash mem­ory or via USB for back­ing up and restor­ing states, pro­grams, and con­fig­u­ra­tion.

* I/O to built-in flash mem­ory or via USB for back­ing up and restor­ing states, pro­grams, and con­fig­u­ra­tion.

Yesterday af­ter re­ceiv­ing my yearly flu vac­cine at the phar­macy I was of­fered a blood pres­sure test, which re­ported a read­ing that made the young phar­ma­cist who had just given me my vac­cine a bit wor­ried.

Off the back of this she of­fered me a 24 hour study, and then strapped a cuff to my arm plumbed into a lit­tle de­vice which I had to wear in a lit­tle caddy - the cuff would in­flate every 30 min­utes dur­ing the day and every 60 min­utes dur­ing the night, and then to­mor­row I would bring it back for analy­sis.

“Can I read the mea­sure­ments?” I asked, as it was be­ing strapped to me.

“Oh, no, that will just stress you out. We turn that off”. Fair enough.

Thing is, this de­vice had a lit­tle mi­cro-USB port on the side.

I had started re­search­ing the de­vice - a Microlife WatchBP O3 - be­fore I got out of the chemist, and once I’d got back to the of­fice I down­loaded the soft­ware that’s freely avail­able to in­ter­act with it, set­ting up a Bottles in­stance to run the soft­ware since I don’t (knowingly) have a Windows ma­chine within 100 me­tres of me.

Unfortunately it did­n’t seem to be able to ac­cess the de­vice, and I had no clue why. In Linux it was just pre­sent­ing as a stan­dard hidraw de­vice:

[33301.736724] hid-generic 0003:04D9:B554.001E: hid­de­v96,hidraw1: USB HID v1.11 Device [USB HID UART Bridge] on usb-0000:c5:00.0-1/​in­put0

After dodg­ing around Microsoft’s idea of UX, and then for­ward­ing the USB de­vice to the VM (I used Gnome Boxes for this, works nicely), I fi­nally got to see WatchBP Analyzer with the data down­loaded from the de­vice.

WatchBP Analyzer with my first three mea­sure­ments

But I don’t want to open a Virtual Machine run­ning Windows to see this data, and any­way - I’m pretty sure that re­verse-en­gi­neer­ing this will be good for my blood pres­sure.

Since I’m run­ning this in a Virtual Machine I can just rely on Wireshark in Linux to get the traf­fic be­tween the host and the de­vice. us­b­mon is al­ready in­stalled and we know that the de­vice is on Bus 3, so we can se­lect us­b­mon3 on startup and start cap­tur­ing.

I’m very much out of my depth at this point but, be­ing one of those who could land a plane in an emer­gency (why would you talk your­self out of it?!) I de­cided to crack on re­gard­less. I know that the in­ter­est­ing stuff is sent af­ter I press “Download”, and I know that some­thing in there is gonna say “my blood pres­sure is 137/113″ - so let’s look for that. Just con­vert to show bytes as dec­i­mal and..

My blood pres­sure seems to be en­coded in this packet

..that looks like a blood pres­sure! Let’s copy that out as hex:

05 0a 89 71 43 9b

I’m not sure if this is “valid” HID Data (Wireshark seems con­vinced that only the first byte is the Vendor Data, with the rest be­ing padding) but it seems like the data is be­ing sent in 32-byte “chunks”, of which the first byte tells you the num­ber of sig­nif­i­cant (SIG) fol­low­ing bits in the chunk (I deleted the rest - all ze­roes - for clar­ity). The third byte is my Systolic blood Pressure (SYS), the fourth is my Diastolic blood pres­sure (DIA), and the fifth is my heart rate (HR) - no clue what the sec­ond or last byte is, but let’s find all other bytes with my blood pres­sure in them (in dec­i­mal this time, be­cause I can’t read hex with­out help):

SIG ??? SYS DIA HR ??? ??? ???

5 10 137 113 67 155

5 0 132 86 68 155

6 0 126 84 82 155 83

6 10 128 80 61 155 83

7 0 148 93 65 155 83 64

7 0 121 92 74 155 83 94

7 0 123 83 65 155 83 95

7 0 123 79 78 155 83 129

Hmm. So we’re still look­ing for the Oscillometric sig­nal peak pres­sure (OPP)as well as some time­stamps (we can cal­cu­late Mean ar­te­r­ial pres­sure - MAP - as (2*DIA+SYS)/3, ac­cord­ing to the man­ual, and Pulse Pressure (PP) is just SYS-DIA). We can see the OPP in the pack­ets that come af­ter each of those above, but they don’t seem to con­sis­tently come in on the same line:

10 82 195 80 *121 0 0 0 0 0 0

10 82 223 80 *95 0 0 0 0 0 0

9 1 80 *90 0 0 0 0 0 0

9 35 80 *86 0 0 0 0 0 0

8 80 *103 0 0 0 0 0 0

8 80 *106 0 0 0 0 0 0

8 80 *90 0 0 0 0 0 0

10 80 *88 0 0 0 0 0 0 29 251

Oh. Maybe if I stick them to­gether?

??? SYS DIA HR ??? ??? ??? ??? OPP ??? ??? ??? ??? ??? ??? ??? ???

10 137 113 67 155 82 195 80 121 0 0 0 0 0 0

0 132 86 68 155 82 223 80 95 0 0 0 0 0 0

0 126 84 82 155 83 1 80 90 0 0 0 0 0 0

10 128 80 61 155 83 35 80 86 0 0 0 0 0 0

0 148 93 65 155 83 64 80 103 0 0 0 0 0 0

0 121 92 74 155 83 94 80 106 0 0 0 0 0 0

0 123 83 65 155 83 95 80 90 0 0 0 0 0 0

0 123 79 78 155 83 129 80 88 0 0 0 0 0 0 29 251

Right, time­stamps. I first guessed that the four pop­u­lated con­tigu­ous bytes be­tween HR and OPP are a 32-bit unix time­stamp, but that would make the first one 9B52C350; ei­ther Jul 29 2052 or Dec 08 2012 de­pend­ing on which en­di­an­ness the pro­to­col is into. The 8 read­ings we have here are all from November 10th, at 11:03, 11:31, 12:01, 12:35, 13:00, 13:30, 13:31 and 14:01, which is­n’t.. is­n’t that.

But note that the num­ber in the 6th col­umn flips from 82 to 83 when we switch from AM to PM - that’s some­thing, and when it does the 7th col­umn re­sets. And hey - 1, 35, 64, 94, 95.. that seems dan­ger­ously close to 12:01, 12:35, 13:00, 13:30 and 13:31 if you were just to count the min­utes. What’s go­ing on?

I tried feed­ing a lot of this into var­i­ous Als (Kagi gives you ac­cess to a few with a nice in­ter­face) and I found that they mostly were stu­pid in ways that made me think. A few times I thought they had “cracked the case” but ac­tu­ally they just made me waste time. But they did re­mind me e.g. of en­di­an­ness, so I did get a bit out of them.

I also spent quite a bit of time try­ing to write some Python that em­u­lated the ini­tial hand­shake and down­load but­ton of the in­ter­face so that it could push out the data as a stream in­stead of me hav­ing to wres­tle it out of Wireshark - again, Al had a habit of giv­ing me in­cor­rect code (although it did turn me on to py­hi­dapi).

But ul­ti­mately I had a dead­line, and I had to re­turn the de­vice even though I wanted to spend more time with it. Possibly for the best - while it did give me some re­verse en­gi­neer­ing prac­tice (which it turns out I re­ally en­joy), I should do some work in­stead of pro­cras­ti­nat­ing.

My fi­nal les­son was a new word - Normotension, nor­mal blood pres­sure - and a new phrase - White Coat Hypertension, the phe­nom­ena of high blood pres­sure in a clin­i­cal set­ting. Turns out that when you check some­one’s blood pres­sure af­ter giv­ing them an in­jec­tion, it’s higher than nor­mal.

I don’t think I’d rec­om­mend get­ting your blood pres­sure tested af­ter your next flu jab. But then, I’m not a doc­tor.