A lot has changed since I wrote Let Them Eat Cache in 2021. Here are some highlights:

Using a web server to dynamically serve content from a single geographical location is not fast nor stable to put it mildly.

This is the definitive list of the best ice cream in Orlando, Florida curated by an ice cream snob who has lived here for over a decade. I am excluding large chains that you can get outside of Orlando or the southwest United States like Dairy Queen and Culver's.

I've been thinking about how app developers will interact with silk floss. Having a triplestore where apps can save any data in a structured format seems great on the surface, but presents a privacy nightmare.

As Chickaree is coming along, I thought I should give a bit of an update of where we are headed and some new ideas I've had. One of the looming issues for this service is how to syncronize data between devices. At first, I was thinking I could create a stop-gap solution and let users sync their subscriptions with OneDrive (or something like that). I've realized that this is a waste of development time.

I was setting up the Schema.org Metatag module on this blog and it got me thinking about something I wrote about previously. When I originally wrote about a triplestore in Drupal, I was thinking that the user would be able to add Statements to anything, because, why not? However, the more I thought about it, the more I realized this didn't make any sense.

Earlier, I wrote about how not everything on the social web could be reduced to a stream of activity. After spending some time learning about offline-first apps, I've come to realize that Activity Streams provide a nice interface for conflict-free replicated data types (CRDT).

Lately, I have been trying to figure out what the restriction(s) on free accounts would be on Silk Floss. At first, I was thinking free accounts would only allow public content. Because public content can be cached for long periods of time on a CDN, there is little overhead in allowing only public content and making private content a "premium" (read: non-free) feature, since the costs in serving private content are much higher.

Based on Jack Dorsey's statement, I read a lot into ActivityPub which is mentioned in the replies multiple times. I imagine it's the inevitable standard that the bluesky team will choose as it does fit Twitter's use cases (unless they fall down a rabbit hole of decentralization tech). Although, I'm not convinced that Twitter will become an ActivityPub server, they may only be an ActivityPub client.

I hadn't really thought of it before, but essentially, Activity Streams is RSS or Atom on steroids. It is effectively the JSON-LD version of these formats. I mean this in the sense that it provides a stream of content (or "actions") in a machine-readable format.