Since Claude Code exists, I have noticed a surprising phenomenon: more and more new applications are appearing on the App Store or coming to life as web applications accessible only to their creator-promoter. The process is called vibe coding. When I see people creating new applications with the help of artificial intelligence, I can’t help but think back to the era of the introduction of PageMaker, the LaserWriter laser printer, and the Macintosh. These three elements enabled the democratization of what became known as ‘Desktop Publishing.’ Many people who knew nothing about printing, layout, and design started creating posters, newsletters, etc. The results were not always of very high quality. Fast forward to today: artificial intelligence and tools like Claude Code are bringing us back into a similar context of high-velocity creation. It’s fascinating. The more things change…

This morning, I visited Reddit to answer a question about Craft. When I noticed five notifications, I clicked the bell icon. Two of them were about engagement stimulation, which I felt was manipulative and deceptive. I dislike being tricked this way. LinkedIn is also good at this. And Meta, the master of them all. Major platforms will likely face legal challenges in the future because their product design promotes toxic engagement tactics that manipulate users for growth. Om Malik won’t be around to see this unfold, sadly.

Federico Viticci is sharing an explanation about why MacStories resumed posting on X:

We want to be absolutely clear about something: returning to X does not represent a change in our values, what MacStories or we stand for, or an endorsement of Elon Musk. We abhor Musk’s politics, his rhetoric, his careless disregard for others, and the direction he has taken X. But we also disagree that participating on X means we have aligned ourselves with any of Musk’s views or actions. We reject Musk’s worldview and will continue to treat people with the kindness and respect they deserve wherever they are on the Internet.

That’s not enough. MacStories is contributing to the bad internet, the siloed internet. They are feeding the machine. I stopped reading MacStories long ago because it became something else I don’t really care about. Here’s another reason to stay away. MacStories is giving people more reasons to return to X, too. Sad that in today’s world you cannot stand by yourself and only depend on toxic platforms to thrive. Too bad, because the original MacStories was really great.

My sister, who discovered water painting late in life, is part of a group of artists who share the same passion for art and painting in general. She is really good. She has taken many art courses since COVID. Now, she’s part of a Facebook Group, and when she mentioned it, I suggested creating a website for her to showcase her work, separate from platforms like Meta. She inquired about discoverability. What can I say to her? Is discoverability always tied to rewards? Are likes part of a validation process? Can we be on the web without seeking discoverability or rewards (likes, reblogs, etc.)?

No One’s Happy recent blog post suggesting not to use native apps:

“Most native apps collect far more data than their website equivalents ever could. They request permissions to hardware, sensors, and background processes that browsers deliberately restrict. The third-party software embedded in these apps frequently transmits your location, device identifiers, and behavioral data to third parties before you even see a consent prompt. This data is in tandem bought, sold, and aggregated by brokers. It has been used to out individuals, track immigrants, and enable prosecution over reproductive healthcare.”

While this is true, refusing to use native apps is surprising advice. One might think the App Store submission process that every developer is subject to prevents bad actors, but it doesn’t. Coupled with the developer’s ordeal with the App Store review process, some developers are suggesting focusing development efforts on web applications instead. And finally, vibe coding might be another factor driving a move toward web application development. Yet the web is a jungle where user tracking is a standard “feature” that mines the browsing experience with bloated web pages that sell you ads and lead you to forced engagement.

I wanted to open a link pointing to a post on x.com. Clicked on it. After a few seconds, X website opened but right after the App Store launched to the download the app for reading content on X. I went back to the website, dismissing the App Store. Clicking to play the shared media again launched the App Store. I went back to watch the video. What an awful experience.

I wondered if installing the X app would make the experience more tolerable. The login / signin screen scared the shit out of me when I started remembering all the bad things about social networks, Musk, etc. but then I started thinking that even if things like the dark web is bad, some people still need to visit this place for investigation. Was I investigating this morning when opening up X? I certainly was looking to understand something.

Having to create a new X account, then being exposed to ads, tracking, etc. killed my desire to understand. It’s ok not to understand everything. I’m a happier ignorant.

What can I learn from the demise of EchoFeed? Earlier this year, when I heard about this service, I looked into it to see if it could be useful. It wasn’t, thanks to Micro.blog’s ability to cross-post to Bluesky, Mastodon and more. Plus, at first it looked like an experiment more than anything else. I didn’t know EchoFeed’s long-term goals. I was on the breaks.

I’m wary of one-person services like EchoFeed. Another example is FeedPress. I like this service a lot, but I think there is only one person behind it, and it’s owned by a parent company which I know nothing about. It’s not entirely clear from this post what their mission is. What happens if this guy decides, or the parent company says, it’s no longer viable? Moving off EchoFeed might be a pain for people who need cross-posting capabilities. I highly doubt these people are willing to move to Buffer.

The same could be said about moving off FeedPress. It would be a pain in the ass to reconfigure all my feeds. The same torment applies to Micro.blog itself (or Scribbles.page, for that matter!). What is the future of Micro.blog if something bad happens to its founder? What is the continuity plan? Micro.blog has done everything it can to enable data portability and ownership, but moving things around, even if you own most parts, is not as easy as it sounds. In today’s world, nothing is permanent, and planning for this is mandatory.