Posts in stories

iPadOS 18’s Smart Script: A Promising Start But Don’t Toss Out Your Keyboard Yet

Source: Apple.

Source: Apple.

The carefully controlled demos of Smart Script at WWDC reminded me of every time Apple shows off the Photos app, where each picture is a perfectly composed, beautiful image of smiling models. In contrast, my photo library is full of screenshots and random images like the blurry one I took the other day to capture my refrigerator’s model number.

Likewise, handwriting demos on the iPad always show someone with flawless, clear penmanship who can also draw. In both cases, the features demonstrated may work perfectly well, but the reality is that there’s always a gap between those sorts of perfect “lifestyle” demos and everyday use. So today, I thought I’d take iPadOS 18’s Smart Script for a spin and see how it holds up under the stark reality of my poor handwriting.

Smart Script, meet John's handwriting (auto-refine enabled).

Smart Script, meet John’s handwriting (auto-refine enabled).

The notion behind Smart Script is to make taking handwritten notes as easy and flexible as typing text. As someone who can touch type with my eyes closed, that’s a tall order, but it’s also a good goal. I’ve always been drawn to taking notes on an iPad with the Apple Pencil, but it’s been the constraints that held me back. It’s always been easier to move and change typed text than handwritten notes. Add to that the general messiness of my handwriting, and eventually, I abandoned every experiment with taking digital handwritten notes out of frustration.

Smart Script tries to address all of those issues, and in some cases, it succeeds. However, there are still a few rough edges that need to be ironed out before most people’s experience will match the demos at WWDC. That said, if those problem areas get straightened out, Smart Script has the potential to transform how the iPad is used and make the Apple Pencil a much more valuable accessory.

Read more


New Projects, New Setup

The past few months have been busy at MacStories. The release of new iPads was followed by our launch of new podcasts and then WWDC. Along the way, my gear setup has changed a little, too.

Portable Setup Changes

11” iPad Pro and Accessories

Leading up to Apple’s spring event and knowing that it would feature new iPads, I was on the fence about buying one. The Pencil Pro and the Tandem OLED display tipped the balance, though, and I ended up getting the 11” Wi-Fi-only model with a Magic Keyboard Case, a Smart Folio cover, and Apple Pencil Pro.

I was tempted by the nano-texture display but ultimately passed on it as well as cellular connectivity. I expect there’s a nano-texture device of some sort in my future, but even without it, the iPad Pro’s Tandem OLED display works better in sunlight than previous displays. I don’t use an Apple Pencil often, but with the new Pro model, I plan to play around with it more to see if I can find a place for it in my day-to-day computing. The lack of meaningful iPadOS 18 updates coming this fall is a letdown, but I’m still pleased with my purchase because the smaller form factor and fantastic display have led me to use my iPad Pro more.

Desk Setup Changes

Balolo's tablet holder accessory.

Balolo’s tablet holder accessory.

With the change in iPad sizes, the articulating arm I used for the 12.9” iPad Pro no longer worked for me. Instead, I’ve transitioned to another Balolo accessory, the Tablet Holder. It sits neatly in the center of my Desk Cockpit shelf, where I can set my iPad for use with Sidecar or Universal Control. If you’re a Club member and interested in Balolo’s Desk Cockpit setup, which I covered in detail this past February, there’s a coupon code for 10% off on the Club Discounts page.

My new video gear from Elgato.

My new video gear from Elgato.

I have been experimenting more with video in recent weeks, too. That led to the addition of an Elgato Facecam Pro and Key Light to my desk, along with an Elgato Mini Mount stand for the camera.

Read more


iOS 18 After One Month: Without AI, It’s Mostly About Apps and Customization

iOS 18 launches in public beta today.

iOS 18 launches in public beta today.

My experience with iOS 18 and iPadOS 18, launching today in public beta for everyone to try, has been characterized by smaller, yet welcome enhancements to Apple’s productivity apps, a redesign I was originally wrong about, and an emphasis on customization.

There’s a big omission looming over the rollout of these public betas, and that’s the absence of any Apple Intelligence functionalities that were showcased at WWDC. There’s no reworked Siri, no writing tools in text fields, no image generation via the dedicated Image Playground app, no redesigned Mail app. And that’s not to mention the AI features that we knew were slotted for 2025 and beyond, such as Siri eventually becoming more cognizant of app content and gaining the ability to operate more specifically inside apps.

As a result, these first public betas of iOS and iPadOS 18 may be – and rightfully so – boring for most people, unless you really happen to care about customization options or apps.

Fortunately, I do, which is why I’ve had a pleasant time with iOS and iPadOS 18 over the past month, noting improvements in my favorite system apps and customizing Control Center with new controls and pages. At the same time, however, I have to recognize that Apple’s focus this year was largely on AI; without it, it feels like the biggest part of the iOS 18 narrative is missing.

As you can imagine, I’m going to save a deeper, more detailed look at all the visual customization features and app-related changes in iOS and iPadOS 18 for my annual review later this year, where I also plan to talk about Apple’s approach to AI and what it’ll mean for our usage of iPhones and iPads.

For now, let’s take a look at the features and app updates I’ve enjoyed over the past month.

Read more


macOS Sequoia: The MacStories Public Beta Preview

Sequoia is not your typical macOS release. In recent years, new features of all Apple OSes have been increasingly meted out over time instead of dropping all at once in the fall. That’s been true of macOS, too, but this year, the magnitude of the staged release will be more pronounced, which has trickled through to the public beta released today.

macOS Sequoia will be a phased release. That means you won’t find everything announced at WWDC in the public beta. Some features, notably large parts of Apple Intelligence, won’t be available until 2025. That’s something worth keeping in mind if you’re thinking about installing the Sequoia public beta today. The beta is generally stable, but you’re likely to run into bugs, and with many features still to come in the months ahead, the upside of running it is more limited than in past years.

Apple Intelligence promises to round out Sequoia over time, but neither I nor anyone else outside of Apple has had a chance to try those features yet. So, for now, let’s focus on what you can expect if you install the macOS Sequoia public beta today.

Read more


watchOS 11: The MacStories Public Beta Preview

Last year, Apple declared watchOS 10 the biggest update to the Apple Watch’s software since its introduction. I don’t think that was actually the case, but there were undoubtedly some notable changes to how we interact with our watches every day, with the introduction of the Smart Stack being key among them.

While Apple hasn’t forgotten about UI enhancements like the Smart Stack, this year sees the company turning its focus back to health and fitness tracking with some significant new features in those areas. I’ll be saving a deeper dive into the software update – including all the tiny changes and fun additions – until the fall, but with the watchOS 11 public beta going live today via the Apple Beta Software Program, now is the perfect time to go over the key features Apple has in store for Apple Watch users.

Read more


LGBT and Marginalized Voices Are Not Welcome on Threads

As Twitter was crumbling under Elon Musk’s new leadership in 2023, various online circles found themselves flocking to alternative platforms. While some may have kept using Twitter (now known as… X), a non-negligible number of communities migrated over to Mastodon and other smaller platforms. Meanwhile, Meta shipped its own textual social media platform, Threads. The service initially launched in most parts of the world except for the European Union, but it’s been available in Europe for over six months now and has seen its usage soar.

For many, Threads understandably felt like a breath of fresh air following the chaos that engulfed Twitter. Unlike the latter, Threads is not run by someone that I and many others find to be an exceptionally despicable human. Its algorithmic timeline contrasts with Mastodon’s exclusively chronological feeds, and its integration with Instagram has attracted a number of big names and stars.

I’m an activist. In my daily life, I work and advocate for the advancement of trans people’s rights in France. As a result, my expanded online social circle mostly consists of LGBT people, and most of them are activists, too. However, in the span of a few months, almost everyone in that circle who was excited about Threads launching in Europe has now stopped using it and migrated back to Twitter, Mastodon, or elsewhere. When I ask around about why those people left Threads behind, their responses vary, but a trend persists: most felt like they were being shadow-banned by the platform.

Without hard data, it is difficult to investigate this feeling, to understand if it is truly widespread or specific to some online bubbles. But one thing is certain: Threads hasn’t felt like a breath of fresh air for all who tried to use it. In my experience as a trans woman, at its best, it has felt like Jack Dorsey’s old Twitter: a social platform overrun by an opaque moderation system, free-roaming hate speech, and a frustrating algorithm that too often promotes harmful content.

As months go by, incidents where Threads consistently failed to uphold its understood promise of a better-moderated Twitter-like platform have added up. Today, for many non-white, non-straight, non-male users, it is a repulsive social media experience, where their voices are silenced and where hate speech offenders who target them go unpunished.

Let’s talk about this.

Read more


AI Companies Need to Be Regulated: An Open Letter to the U.S. Congress and European Parliament

Federico: Historically, technology has usually advanced in lockstep with opening up new creative opportunities for people. From word processors allowing writers to craft their next novel to digital cameras letting photographers express themselves in new ways or capture more moments, technological progress over the past few decades has sustained creators and, perhaps more importantly, spawned industries that couldn’t exist before.

Technology has enabled millions of people like myself to realize their life’s dreams and make a living out of “creating content” in a digital age.

This is all changing with the advent of Artificial Intelligence products based on large language models. If left unchecked without regulation, we believe the change may be for the worse.

Over the past two years, we’ve witnessed the arrival of AI tools and services that often use human input without consent with the goal of faster and cheaper results. The fascination with maximization of profits above anything else isn’t a surprise in a capitalist industry, but it’s highly concerning nonetheless – especially since, this time around, the majority of these AI tools have been built on a foundation of non-consensual appropriation, also known as – quite simply – digital theft.

As we’ve documented on MacStories and as other (and larger) publications also investigated, it’s become clear that foundation models of different LLMs have been trained on content sourced from the open web without requesting publishers’ permission upfront. These models can then power AI interfaces that can regurgitate similar content or provide answers with hidden citations that seldom prioritize driving traffic to publishers. As far as MacStories is concerned, this is limited to text scraped from our website, but we’re seeing this play out in other industries too, from design assets to photos, music, and more. And top it all off, publishers and creators whose content was appropriated for training or crawled for generative responses (or both) can’t even ask AI companies to be transparent about which parts of their content was used. It’s a black box where original content goes in and derivative slop comes out.

We think this is all wrong.

The practices followed by the majority of AI companies are ethically unfair to publishers and brazenly walk a perilous line of copyright infringement that must be regulated. Most worryingly, if ignored, we fear that these tools may lead to a gradual erosion of the open web as we know it, diminishing individuals’ creativity and consolidating “knowledge” in the hands of a few tech companies that built their AI services on the back of web publishers and creators without their explicit consent.

In other words, we’re concerned that, this time, technology won’t open up new opportunities for creative people on the web. We fear that it’ll destroy them.

We want to do something about this. And we’re starting with an open letter, embedded below, that we’re sending on behalf of MacStories, Inc. to U.S. Senators who have sponsored AI legislation as well as Italian members of the E.U. Special Committee on Artificial Intelligence in a Digital Age.

In the letter, which we encourage other publishers to copy if they so choose, we outline our stance on AI companies taking advantage of the open web for training purposes, not compensating publishers for the content they appropriated and used, and not being transparent regarding the composition of their models’ data sets. We’re sending this letter in English today, with an Italian translation to follow in the near future.

I know that MacStories is merely a drop in the bucket of the open web. We can’t afford to sue anybody. But I’d rather hold my opinion strongly and defend my intellectual property than sit silently and accept something that I believe is fundamentally unfair for creators and dangerous for the open web. And I’m grateful to have a business partner who shares these ideals and principles with me.

With that being said, here’s a copy of the letter we’re sending to U.S. and E.U. representatives.

Read more


Wired Confirms Perplexity Is Bypassing Efforts by Websites to Block Its Web Crawler

Last week, Federico and I asked Robb Knight to do what he could to block web crawlers deployed by artificial intelligence companies from scraping MacStories. Robb had already updated his own site’s robots.txt file months ago, so that’s the first thing he did for MacStories.

However, robots.txt only works if a company’s web crawler is set up to respect the file. As I wrote earlier this week, a better solution is to block them on your server, which Robb did on his personal site and wrote about late last week. The setup sends a 403 error if one of the bots listed in his server code requests information from his site.

Spoiler: Robb hit the nail on the head the first time.

Spoiler: Robb hit the nail on the head the first time.

After reading Robb’s post, Federico and I asked him to do the same for MacStories, which he did last Saturday. Once it was set up, Federico began testing the setup. OpenAI returned an error as expected, but Perplexity’s bot was still able to reach MacStories, which shouldn’t have been the case.1

Yes, I took a screenshot of Perplexity's API documentation because I bet it changes based on what we discovered.

Yes, I took a screenshot of Perplexity’s API documentation because I bet it changes based on what we discovered.

That began a deep dive to try to figure out what was going on. Robb’s code checked out, blocking the user agent specified in Perplexity’s own API documentation. What we discovered after more testing was that Perplexity was hitting MacStories’ server without using the user agent it said it used, effectively doing an end run around Robb’s server code.

Robb wrote up his findings on his website, which promptly shot to the top slot on Hacker News and caught the eye of Dhruv Mehrotra and Tim Marchman of Wired, who were in the midst of investigating how Perplexity works. As Mehrotra and Marchman describe it:

A WIRED analysis and one carried out by developer Robb Knight suggest that Perplexity is able to achieve this partly through apparently ignoring a widely accepted web standard known as the Robots Exclusion Protocol to surreptitiously scrape areas of websites that operators do not want accessed by bots, despite claiming that it won’t. WIRED observed a machine tied to Perplexity—more specifically, one on an Amazon server and almost certainly operated by Perplexity—doing this on wired.com and across other Condé Nast publications.

Until earlier this week, Perplexity published in its documentation a link to a list of the IP addresses its crawlers use—an apparent effort to be transparent. However, in some cases, as both WIRED and Knight were able to demonstrate, it appears to be accessing and scraping websites from which coders have attempted to block its crawler, called Perplexity Bot, using at least one unpublicized IP address. The company has since removed references to its public IP pool from its documentation.

That secret IP address—44.221.181.252—has hit properties at Condé Nast, the media company that owns WIRED, at least 822 times in the last three months. One senior engineer at Condé Nast, who asked not to be named because he wants to “stay out of it,” calls this a “massive undercount” because the company only retains a fraction of its network logs.

WIRED verified that the IP address in question is almost certainly linked to Perplexity by creating a new website and monitoring its server logs. Immediately after a WIRED reporter prompted the Perplexity chatbot to summarize the website’s content, the server logged that the IP address visited the site. This same IP address was first observed by Knight during a similar test.

This sort of unethical behavior is why we took the steps we did to block the use of MacStories’ websites as training data for Perplexity and other companies.2 Incidents like this and the lack of transparency about how AI companies train their models have led to a lot of mistrust in the entire industry among creators who publish on the web. I’m glad we’ve been able to play a small part in revealing Perplexity’s egregious behavior, but more needs to be done to rein in this sort of behavior, including closer scrutiny by regulators around the world.

As a footnote to this, it’s worth noting that Wired also puts to rest the argument that websites should be okay with Perplexity’s behavior because they include citations in their plagiarism. According to Wired’s story:

WIRED’s own records show that Perplexity sent 1,265 referrals to wired.com in May, an insignificant amount in the context of the site’s overall traffic. The article to which the most traffic was referred got 17 views.

That’s next to nothing for a site with Wired’s traffic, which Similarweb and other sites peg at over 20 million page views that same month. That’s a mere 0.006% of Wired’s May traffic. Let that sink in, and then ask yourself whether it seems like a fair trade.


  1. Meanwhile, I was digging through bins of old videogames and hardware at a Retro Gaming Festival doing ‘research’ for NPC↩︎
  2. Mehrotra and Marchman correctly question whether Perplexity is even an AI company because they piggyback on other company’s LLMs and use them in conjunction with scraped web data to provide summaries that effectively replace the source’s content. However, that doesn’t change the fact that Perplexity is surreptitiously scraping sites while simultaneously professing to respect sites’ robot.txt file. That’s the unethical bit. ↩︎

How We’re Trying to Protect MacStories from AI Bots and Web Crawlers – And How You Can, Too

Over the past several days, we’ve made some changes at MacStories to address the ingestion of our work by web crawlers operated by artificial intelligence companies. We’ve learned a lot, so we thought we’d share what we’ve done in case anyone else would like to do something similar.

If you read MacStories regularly, or listen to our podcasts, you already know that Federico and I think that crawling the Open Web to train large language models is unethical. Industry-wide, AI companies have scraped the content of websites like ours, using it as the raw material for their chatbots and other commercial products without the consent or compensation of publishers and other creators.

Now that the horse is out of the barn, some of those companies are respecting publishers’ robots.txt files, while others seemingly aren’t. That doesn’t make up for the tens of thousands of articles and images that have already been scraped from MacStories. Nor is robots.txt a complete solution, so it’s just one of four approaches we’re taking to protect our work.

Read more