Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

⌥ Delicious Wabi-Sabi

By: Nick Heer
2 December 2024 at 05:32

Brendan Nystedt, reporting for Wired on a new generation of admirers of crappy digital cameras from the early 2000s:

For those seeking to experiment with their photography, there’s an appeal to using a cheap, old digital model they can shoot with until it stops working. The results are often imperfect, but since the camera is digital, a photographer can mess around and get instant gratification. And for everyone in the vintage digital movement, the fact that the images from these old digicams are worse than those from a smartphone is a feature, not a bug.

Om Malik attributes it to wabi-sabi:

Retromania? Not really. It feels more like a backlash against the excessive perfection of modern cameras, algorithms, and homogenized modern image-making. I don’t disagree — you don’t have to do much to come up with a great-looking photo these days. It seems we all want to rebel against the artistic choices of algorithms and machines — whether it is photos or Spotify’s algorithmic playlists versus manually crafted mixtapes.

I agree, though I do not see why we need to find just one cause — an artistic decision, a retro quality, an aesthetic trend, a rejection of perfection — when it could be driven by any number of these factors. Nailing down exactly which of these is the most important factor is not of particular interest to me; certainly, not nearly as much as understanding that people, as a general rule, value feeling.

I have written about this before and it is something I wish to emphasize repeatedly: efficiency and clarity are necessary elements, but are not the goal. There needs to be space for how things feel. I wrote this as it relates to cooking and cars and onscreen buttons, and it is still something worth pursuing each and every time we create anything.

I thought about this with these two articles, but first last week when Wil Shipley announced the end of Delicious Library:

Amazon has shut off the feed that allowed Delicious Library to look up items, unfortunately limiting the app to what users already have (or enter manually).

I wasn’t contacted about this.

I’ve pulled it from the Mac App Store and shut down the website so nobody accidentally buys a non-functional app.

Delicious Library was many things: physical and digital asset management software, a kind of personal library, and a wish list. But it was also — improbably — fun. Little about cataloguing your CDs and books sounds like it ought to be enjoyable, but Shipley and Mike Matas made it feel like something you wanted to do. You wanted to scan items with your Mac’s webcam just because it felt neat. You wanted to see all your media on a digital wooden shelf, if for no other reason than it made those items feel as real onscreen as they are in your hands.

Delicious Library became known as the progenitor of the “delicious generation” of applications, which prioritized visual appeal as much as utility. It was not enough for an app to be functional; it needed to look and feel special. The Human Interface Guidelines were just that: guidelines. One quality of this era was the apparently fastidious approach to every pixel. Another quality is that these applications often had limited features, but were so much fun to use that it was possible to overlook their restrictions.

I do not need to relitigate the subsequent years of visual interfaces going too far, then being reeled in, and then settling in an odd middle ground where I am now staring at an application window with monochrome line-based toolbar icons, deadpan typography, and glassy textures, throwing a heavy drop shadow. None of the specifics matter much. All I care about is how these things feel to look at and to use, something which can be achieved regardless of how attached you are to complex illustrations or simple line work. Like many people, I spend hours a day staring at pixels. Which parts of that are making my heart as happy as my brain? Which mundane tasks are made joyful?

This is not solely a question of software; it has relevance in our physical environment, too, especially as seemingly every little thing in our world is becoming a computer. But it can start with pixels on a screen. We can draw anything on them; why not draw something with feeling? I am not sure we achieve that through strict adherence to perfection in design systems and structures.

I am reluctant to place too much trust in my incomplete understanding of a foreign-to-me concept rooted in another country’s very particular culture, but perhaps the sabi is speaking loudest to me. Our digital interfaces never achieve a patina; in fact, the opposite is more often true: updates seem to erase the passage of time. It is all perpetually new. Is it any wonder so many of us ache for things which seem to freeze the passage of time in a slightly hazier form?

I am not sure how anyone would go about making software feel broken-in, like a well-worn pair of jeans or a lounge chair. Perhaps that is an unattainable goal for something on a screen; perhaps we never really get comfortable with even our most favourite applications. I hope not. It would be a shame if we lose that quality as software eats our world.

Private Systems for Public Services

By: Nick Heer
10 October 2024 at 04:28

Brendan Jones:

The rise of Mastodon has made me so much more aware of government services requiring us to use private companies’ systems to communicate with them and access services.

Sitting on a Dutch train just now I was shown on a screen “feeling unsafe in the train? Contact us via WhatsApp”.

Jones says the railway operator’s website also contains SMS reporting instructions, but that was not shown on the train itself.

One of the side effects of the decline of née Twitter is in the splintering of its de facto customer support and alert capabilities. Plenty of organizations still use it that way. But it should only be one option. Apps like WhatsApp should not be the preferred contact method, either. Private companies’ contact methods should be available, sure — meet people where they are — but a standard method should always be as easily available.

⌥ Permalink

Matt Mullenweg v. WP Engine escalates

25 September 2024 at 17:29
Matt Mullenweg v. WP Engine escalates

Update, September 26, 2024: WordPress.org has banned websites hosted on WP Engine from accessing its resources. As someone put it on X, this is Matt Mullenweg dropping a giant turd into the laps of millions of WordPress users. I can't recommend this software any more in good conscience.


The Matt Mullenweg v. WP Engine dispute seems to be escalating, which is a bit of a surprise because it was so ill-founded to begin with. Yet the escalation has also been exponential.

Mullenweg published his post disparaging WP Engine on the WordPress.org site (from where you can download the open source WordPress CMS) on September 21.

Matt Mullenweg v. WP Engine
Automattic CEO and WordPress co-developer Matt Mullenweg published a post on September 21 calling WP Engine a “cancer to WordPress”. For the uninitiated: WP Engine is an independent company that provides managed hosting for WordPress sites; WordPress.com is owned by Automattic and it leads the development of WordPress.org.
Matt Mullenweg v. WP Engine escalatesClose ReadVasudevan Mukunth
Matt Mullenweg v. WP Engine escalates

On September 23, WP Engine said it had sent WordPress.com parent company and WordPress lead developer Automattic, whose CEO is Mullenweg, a cease and desist letter. Excerpt:

Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers,and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X, YouTube, and even on the Wordpress.org site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses.

💥

Later on the same day, Automattic sent a cease and desist letter of its own to WP Engine. Excerpt:

As you know, our Client owns all intellectual property rights globally in and to the world-famous WOOCOMMERCE and WOO trademarks; and the exclusive commercial rights from the WordPress Foundation to use, enforce, and sublicense the world-famous WORDPRESS trademark, among others, and all other associated intellectual property rights.We are writing about WP Engine’s web hosting and related services that improperly use our Client’s WORDPRESS and WOOCOMMERCE trademarks in their marketing.We understand that our Client has contacted you about securing a proper license to use its trademarks, yet no such agreement has been reached. As such, your blatant and widespread unlicensed use of our Client’s trademarks has infringed our Client’s rights and confused consumers into believing, falsely, that WP Engine is authorized, endorsed, or sponsored by, or otherwise affiliated or associated with, our Client. WP Engine’s unauthorized use of our Client’s trademarks also dilutes their rights, tarnishes their reputation, and otherwise harms the goodwill they have established in their famous and well-known trademarks, and has enabled WP Engine to unfairly compete with our Client, leading to WP Engine’s unjust enrichment.

Now it's a trademark dispute. Automattic is alleging people at large are confusing WP Engine with WordPress itself and that that's leading to loss of revenue for Automattic. Hang on to this thought while we move on to the next detail. At 10.34 pm IST on September 4, Mullenweg shared this tidbit in a Reddit comment:

[WP Engine] had the option to license the WordPress trademark for 8% of their revenue, which could be delivered either as payments, people (Five for the Future .org commitments), or any combination of the above.

Put all these details together and we understand Mullenweg is alleging via Automattic that people are confusing WP Engine with WordPress itself to Automattic's detriment, that WP Engine has wrongfully used the WordPress trademark, that what WP Engine is selling isn't WordPress but something it has reportedly "butchered", and that WP Engine's enrichment is unjust.

I think it's starting to stink for Mullenweg. As detailed in the previous post, WP Engine didn't "butcher" WordPress. In fact they didn't change anything about WordPress's core composition. They turned off a setting, didn't hide it, and offered a way to get around it by other means. WordPress is open source software provided under a GPL license, which means others are allowed to modify it (and subsequently avail it under the same license). So even if WP Engine modified WordPress — which it didn't — it would've been operating within its rights.

An opportunity to understand the GPL license
Featured image: Matt Mullenweg, 2009. Credit: loiclemeur/Flickr, CC BY 2.0. Every December, I wander over to ma.tt, the blog of WordPress founder Matt Mullenweg, to check what he’s saying about how the CMS will be shaping up in the next year. Despite my cribbings as well
Matt Mullenweg v. WP Engine escalatesClose ReadVM
Matt Mullenweg v. WP Engine escalates

Second, WP Engine was founded in 2010. Why is Automattic alleging a trademark violation after 14 years of being okay with it? Even if consumers are currently confusing WP Engine with WordPress itself — which I doubt — that Automattic didn't pursue a legal dispute in all this time is very fishy. It also creates new uncertainty for all the many other WordPress hosting companies that have "WP" in their names. On a related note, WP Engine is selling WordPress hosting and not WordPress itself as well as claims to have emails from Automattic staff saying using the "WP" short form is okay.

Another point of note here is whether 'WP' is covered by trademark. At some point in the recent past, the wordpressfoundation.org website updated its 'Trademark Policy' page to include an answer as well as some gratuitous remarks:

The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.

Third, Mullenweg's demand that WP Engine cough up 8% of their revenue amounts to a demand for $40 million (Rs 334.5 crore). Considering Automattic has now pinned this demand to the wobbly allegation of wrongful trademark use, WP Engine seems increasingly in the right to dispute and not entertain his demands. Moreover, WP Engine's lawyers' letter suggests Mullenweg gave WP Engine a very small window within which to comply with this demand and, for added measure, allegedly threw in a threat. But then at 10.38 pm on September 24, Mullenweg said this on Reddit:

I would have happily negotiated from there, but they refused to even take a call. Their entire strategy has been to obscure and delay, which they tried to do on Friday. "Can we get the right folks together early next week?" They've been stringing us along for years, I'm the dummy for believing that they actually wanted to do anything. But making it right, now.

The reply to this comment by Reddit user u/ChallengeEuphoric237 is perfect:

If they don't believe they needed to pay, then why would they?

1/ If the fees were for the trademark, why weren't they going to the WordPress Foundation instead of Automattic?

2/ Why do they need to license the WordPress trademark? Stating they allow hosting as a product isn't a violation of trademark law, neither is using WP. You guys used to be an investor in the company for crying out loud.

WordPress and Automattic seem incredibly petty in all of this. Why did you *need* to do it during the keynote? Why did you *need* to make a huge stink at the booth? If this was a legal issue, let the lawyers sort it out instead of dragging the community through the mud. Everyone expected much more from you. I don't use WP Engine's products, but if someone came to me trying to extort 8% of my revenue on some flimsy trademark issue, I wouldn't be very responsive either.

"Can we get the right folks together early next week?"

Did you honestly expect them to agree to a nearly 40 million dollar annual charge via text message when you literally gave them what seems like an hour notice right before your keynote? Would you agree to that? I'm no lawyer, but that whole exchange seems like an exercise in extortion - threatening to destroy someones reputation unless they agree to something monetarily, which is a felony.

Let's see what the courts say, but you've lost a ton of clout in the community over this.

The subtext of Mullenweg's September 21 post seemed to be that private equity is cutting costs in a way that's eating into the aspirations and dues of open source software development. Then again, as many observers in the sector have said, this couldn't be the real issue because private equity is almost everywhere in the WordPress hosting space and singling out WP Engine made little sense. So the sub-subtext seemed to be that Mullenweg was unhappy about WP Engine eating into the revenue streams of WordPress.com and WordPress VIP (Automattic's elite hosting service). But after the events of the three days that followed, that sub-subtext seems likelier to be the whole issue.

On a final note, many people are kicking back with 🍿 and speculating about how this dispute could escalate further. But it's difficult for me personally to be entertained by this. While Mullenweg's September 21 post didn't in hindsight do a good job of communicating what his real argument was, he did suggest there was a problem with a model in which for-profit entities could springboard off the efforts of open-source communities that have volunteered their time and skills without the entities giving back. But dovetailing to u/ChallengeEuphoria237's concluding remark, conversations about that issue vis-à-vis WP Engine are now more unlikely to happen than they were before Mullenweg launched into this "making it right" campaign.

Research as Leisure Activity

By: Nick Heer
10 June 2024 at 22:22

Celine Nguyen:

But this isn’t really about the software. It’s about what software promises us — that it will help us become who we want to be, living the lives we find most meaningful and fulfilling. The idea of research as leisure activity has stayed with me because it seems to describe a kind of intellectual inquiry that comes from idiosyncratic passion and interest. It’s not about the formal credentials. It’s fundamentally about play. It seems to describe a life where it’s just fun to be reading, learning, writing, and collaborating on ideas.

This is a wonderful essay, albeit one which leaves me with a question of how a reader distinguishes between an amateur’s interpretation of what they read, and an expert’s more considered exploration of a topic — something I have wondered about before.

The amateur or non-professional has their place, of course; I am staking mine on this very website. The expert may not always be correct. But adjudicating the information from each is not a realistic assignment for a layperson. Consider the vast genre of multi-hour YouTube essays, or even short but seemingly authoritative TikTok digests of current events. We are ingesting more information than ever before with fewer gatekeepers — for good and otherwise.

⌥ Permalink

The Rise and Fall of Preview

By: Nick Heer
4 June 2024 at 23:17

Howard Oakley:

Prior to Mac OS X, Adobe Acrobat, both in its free viewer form and a paid-for Pro version, were the de facto standard for reading, printing and working with PDF documents on the Mac. The Preview app had originated in NeXTSTEP in 1989 as its image and PDF viewer, and was brought across to early versions of Mac OS X, where it has remained ever since.

The slow decline of Preview — and Mac PDF rendering in general — since MacOS Sierra is one of the more heartbreaking products of Apple’s annual software churn cycle. To be entirely fair, many of the worst bugs have been fixed, but some remain: sometimes, highlights and notes stop working; search is a mess; copying text is unreliable.

Unfortunately, the apps which render PDF files the most predictably and consistently are Adobe Acrobat and Reader. Both became hideous Electron Chromium-based apps at some point and, so, are gigantic packages which behave nothing like Mac software. It is all pretty disappointing.

Update: A Hacker News commenter rightly pointed out that Acrobat and Reader are not truly Electron apps, and are instead Chromium-based apps. That is to say both are generic-brand shitty instead of the name-brand stuff.

⌥ Permalink

❌
❌