Hey Apple! I have a great idea for you.

Why not make iMessages available on the web as part of iCloud+? There is even a spot just waiting there on the iCloud site for the iMessages icon. The assumption that iOS, iPadOS, and macOS users will always have access to an internet connection on their device is short-sighted and flawed.

It is important for people to stay in contact wherever they are on whatever device they are using. Why limit access when it is really not necessary?

Let’s set the stage. You are a risk executive at a large commercial bank, and you receive a news alert that Silicon Valley Bank and Signature Bank are going into receivership.

You immediately turn to the device at your desk or in your hand or on your wrist and ask it to create data visualizations in Power BI showing your bank’s commitment and outstanding balance exposure to those two banks in relation to your overall portfolio.

You then ask it to embed those visualizations in a PowerPoint presentation with your notes from the meeting that just ended with other senior executives at the bank. You also ask it to write an executive summary, attach your presentation, and create and send an email with the two outputs to the executive team.

Knowing that you and the team will need more details, you then ask Microsoft Excel to create spreadsheets with information like which borrowers are impacted, what are the commitment details for facilities in the top 10 impacted industries, and what are the outstanding loan balances by loan officer and risk rating.

With the additional details in hand and the executive team on the same page, you ask Microsoft Teams to schedule a high-priority meeting with heads of each business unit that appeared in the Excel output to bring the wider team into the loop.

Today, this kind of response would take many hours and more likely several days to organize and complete, but if the promise of Microsoft 365 Copilot holds true, all of this could be done in minutes. Talk about a game-changer!

Of course, for all of this to work, the information you use to train the AI models must be well-defined in the context of your business. Each data point must have a business definition that is specific and unique, and these definitions need to be accessible to the models.

This is where I see one of the biggest challenges for making data from online transaction processing systems available to AI modeling tools. In my experience, very few systems have consistent naming conventions and certainly do not include detailed business definitions within the product’s metadata. Without those business definitions, it is difficult enough for a human to understand the data they query from a system. How can we expect anything more from a AI model? This change in system design should begin immediately to take advantage of what looks to be an incredible shift in the way we are able to work.

This former Microsoft Office programmer could not be more excited about what we are going to be able to do with Copilot. Let’s go!

I’ve always been fascinated by Jony Ive. No matter what you create, there is a lesson to be learned from his approach to design.

There is a great article in the latest issue of WSJ. Magazine about Mr. Ive that is absolutely worth the read or 18 minute listen.

Want to know why Musk’s Twitter is likely to be an unwelcoming place for most long-time Twitter users? Just look at the people that are most excited about the takeover. They are some of the most hateful and hurtful people in public-facing positions. Until there is something better, I’m sticking with my own blog.

Bluesky’s AT Protocol looks like an interesting concept and potentially a social media protocol that can be used across platforms. Imagine if Meta applications, Twitter, LinkedIn, etc. all used the same foundation. Wouldn’t it be great to be able to move data and migrate from one platform to another?

Pandora’s stock has been getting rocked lately with Apple Music and Spotify making it awfully hard to compete. When you can play practically any song on demand, “radio” seems too slow and out of touch. The idea of Internet radio is likely over at this point, but that does not mean Pandora has no value. In fact, the opposite is true. Pandora’s value is not in its ability to play music. The value is in its predictive engine. That is what it needs to license to others. No one can come close to its accuracy. Imagine Apple Music’s For You section with predictions from Pandora’s engine. People would play more new music bringing in revenue for Apple Music and lesser known artists. It is a win-win situation.

As part of my current Facebook hiatus, I have gone back to something I really enjoyed before I started spending far too much time on the social media site: reading blogs via an RSS reader and sharing my favorite stories with others.

My current RSS reader of choice is Fever, a self-hosted feed reader with a nice web and mobile web experience. Reeder 2 on iOS also supports Fever for those that like using an app instead of the mobile web interface. For me, using a reader makes it a lot easier to keep up with important sites and news outlets without having to filter through the noise of Twitter or Facebook. I also like that I have access to Fever’s database because I host it.

Fever includes sharing options within the web interface for Email, Delicious, Instapaper, and Twitter, but that still does not provide the ability for me to keep track of every link I have shared like Google Reader used to do. That is where a new web application created by Dave Winer comes in to play. Radio3 is a linkblogging tool that maintains an RSS feed of all shared links while providing the ability to automatically post to Twitter, Facebook, and WordPress. The RSS feed makes it possible to keep track of my shared links in a standard format that I will be able to read well into the future.

Radio3 includes a handy bookmarklet that makes it easy to share the current browser window, but what if Fever and Radio3 could work together so I did not have to leave my feed reader? Well, they can! Fever has the ability to add sharing options as long as the service provides a URL to add new items, and Radio3 does just that.

To add Radio3 as a sharing option in Fever, perform the following steps:

1. Select Preferences from the Fever menu.
2. Click the Sharing tab.
3. Click the plus (+) button to add a new service.
4. Enter Radio3 in the Service Name field.
5. Enter the following in the Service URL field:

%u represents the site URL, and %t represents the site title. Fever also has a shortcut to include the excerpt that I suppose could be used for the description portion of the Radio3 URL, but I have chosen to use the title which seems to be the default behavior of the bookmarklet when no text is selected in the browser.
6. Enter r in the Key field.
7. Click Save.


That’s all there is to it. Radio3 can now be selected as one of the sharing options directly in Fever.


This is a great example of two web apps working together to make reading and sharing a whole lot more enjoyable.