Caleb Hailey

Just wrapping up day 1 of a @hypertemplates.net hack week with @blog.thoward.me! 💥

Been meaning to post about this. Google keeps promoting YouTube as a closed alternative to standards-based podcasting amid never-ending rumors about the death of podcasting. Meanwhile Apple continues to promote traditional podcasting!

Now if only Apple could wield its cultural influence (via the iPhone) by shifting Apple News more towards #RSS. Brand it as webcasting or @textcasting.org if necessary.

Apple has the ability to make "Wherever you follow websites" a thing™ like it did for podcasting.

A boy can dream!

I want so badly for this game to exist. The world needs a proper NBA Street Vol.2 successor! 🏀

Finally ready to outsource bookkeeping for @herd.works 🎉

#startups #AchievementUnlocked

Scored some sweet deals on the Prime Sale this year after mostly ignoring it for the past few years. I had my eye on this charger for a while and noticed it was $60 off, so I snagged one of these and massively simplified the device charging setup in my home office. This thing is an absolute beast.

PS - this is not an affiliate link. I’m just sharing out of the goodness of my nerdy little heart. 🤓

Is this thing on?!

I noticed my following feed was broken earlier this week. It turns out it's been broken since the updated site went live at the beginning of the year. Whoops! 😅

The issue was with my static site generator and how it was parsing OPML data files. With that fixed I can now drop a lightly modified OPML file (with paywalled #RSS feeds removed) into a data folder and get an auto-generated following page. 🤌🏽

This whole idea was inspired by this @anildash.com blog post that I think about way too often.

Office productivity is going to take a slight hit this week. ⚽️😅📉

The web needs more experimentation like this from @eieio.games. 👏👏👏

Cool to see @stripe.com jump in! Competition for payments on iOS?!

The comments on this Twitter thread from Stripe Product Manager Michael Lou are amazing. It reads like an FAQ, haha.

One comment replies "But using Apple Pay makes purchasing something way more likely for me." Lou responds "You can use Apple pay via Stripe!"

Another comment asks "Do users return to the app automatically after successful completion or is an action required?" Lou responds "They return automatically if [the developer has] Universal Links enabled".

🍿

I knew today was gonna be an exceptional Daily Update on @stratechery.com and I was not disappointed! 🔥

These might be the three most meaningful paragraphs of policy/legal mumbo jumbo I've experienced in my professional career.

From an inconspicuously titled "Updated guidelines now available" from @developer.apple.com:

3.1.1(a): On the United States storefront, there is no prohibition on an app including buttons, external links, or other calls to action, and no entitlement is required to do so.

3.1.3: The prohibition on encouraging users to use a purchasing method other than in-app purchase does not apply on the United States storefront.

3.1.3(a): The External Link Account entitlement is not required for apps on the United States storefront to include buttons, external links, or other calls to action.

The email opened with an acknowledgement of this week's monumental legal mandate:

The App Review Guidelines have been updated for compliance with a United States court decision regarding buttons, external links, and other calls to action in apps. These changes affect apps distributed on the United States storefront of the App Store

Three cheers for regulation?! 👩‍⚖️

The most exciting thing about this to me personally is how @apple.com itself might respond to these changes by actually competing for developers' business in an area where it hasn't had to in the past.

It's gonna be a fun #WWDC & summer! 🙌🏽

While asking @chatgpt.com to help me debug a SwiftUI issue, it offered a solution and then said "but that results in a janky experience"!

The AI has become self-aware! 😅

Looks like the @gohugo.io website got a refresh. 👌

Markdown: this is the way. 🤌

The web never rests. I love seeing stuff like this from @webkit.org in the roadmap! #HTML

Just got a Freshboi 💈

Setting up my HyperTexting… 🤌

is experimenting… 👨🏽‍🔬

It's happening!! 😱

Whoa! 🤯

Test post from a new tool I've been working on. I hope this works!

customElements.apply()

A (naive?) approach to workaround customElements.define() "same tag name" errors.

Web components have completely changed the way I write vanilla JavaScript. It turns out classes are quite useful for encapsulation (who knew?)! Complementary approaches like HTML web components (and CSS web components) have reduced the amount of JavaScript I'm writing by about 95%. These ideas from @adactio.com and @hawkticehurst.com together with a steady stream of web component content from @gomakethings.com have revived my interest in modern web development.

But recently I started running into a little speed bump. I've been exploring HTML templating workflows that enable me to compose sections and entire pages from a collection of layout "partials" (ala server side includes). This sometimes causes multiple <script> tags to be added for a given web component, resulting in redundant calls to customElements.define() and a "cannot define multiple custom elements with the same tag name" error.

My initial reaction to this was to move all <script src> tags into the <head>, but this inevitably resulted in failing to load a component's JavaScript on certain pages (dependency management fail). Then I read @jakelazaroff.com's excellent Define a custom element blog post and it opened my eyes to the many different approaches to managing custom elements. But I also felt like my challenge might have been slightly different than the problem Jake was solving. So I tried something different that has been working really well for me.

It started with reviewing the CustomElementsRegistry reference documentation and discovering that get() and getName() methods already existed. All that was needed was an idempotent method for registering custom elements. It turns out this was trivial to implement.

1CustomElementRegistry.prototype.apply = function(tag, component) {
2    if (!(!!component.constructor && component.toString().substring(0,5) == "class")) { return }; // guard
3    if (this.get(tag)) { return }; // lookup by tag name
4    if (this.getName(component)) { return }; // lookup by component class
5    try { this.define(tag, component) } catch(err) {
6        console.debug(`component ${component.name} already registered as <${tag}>`);
7    };
8};

This is already working so well for me that it's just about the only JavaScript I keep in main.js for new projects. I'm replacing calls to customElements.define with customElements.apply in all of my web component JavaScript.

1customElements.apply("my-element", class MyElement extends HTMLElement {
2    // this is where the magic happens 🪄
3});

In doing so, I can add <script src='/js/my-component.js'> tags in any layout partial without worrying about "same tag name" errors.

Do you find this helpful? Or is this a horrible idea? 😅 Send me an email and let me know what you think: hello [at] calebhailey.com

This post by @ia.net reminds me of a quote I used to have permanently written on the top of the whiteboard in my office:

The only intuitive interface is the nipple. Everything else is learned.

— Bruce "Tog" Tognazzini

My favorite quote from the interview is:

Speaking of #RSS, I love this piece by @anildash.com.

I've always wondered if one of the biggest differences in adoption between podcasts and text-based RSS feeds is that "podcast" has a catchy ring to it, and "really simple sindication" does not. Neither does "RDF site summary". It makes me further wonder if @textcasting.org (by @scripting.com) is more important as (re-)branding for text-based RSS feeds than it is as an actual new standard.

I've been looking for good resources to introduce people to #RSS and this looks like a great one by @interconnected.org!

I've thought about this @stephango.com blog post at least once per week for the last ~18 months.

Just added this to my inspired by hall of fame.

I still haven't used @htmx.org, but I've read the #HyperMedia book and I'm a big fan of their ideas and where the project is headed overall. 🚀

#html #htmx #javascript

This is hands-down my favorite craft cocktail website. 🍹

I'm loving the new @vw.com ID Buzz.

And my new scrolling image gallery. 😎

👈🏽 Swipe 👉🏽

More like fast trashion, amirite? 😅

Keep it on the markdown-low

First post with my custom #markdown parser.

Here's a little sample code block to show off the <code> syntax highlighting.

 1<!DOCTYPE html>
 2<html lang='en-US'>
 3    <head>
 4        <meta ht-include='partials/head.html'>
 5        <meta itemprop='template.name' content='default'>
 6
 7        <!-- Web Components -->
 8        <script src='/js/components/relative-time.js'></script>
 9    </head>
10    <body>
11        <nav ht-include='partials/nav.html'></nav>
12        <content-whitespace></content-whitespace>
13        <section id='post' data-color-scheme='light'>
14            <article ht-include='partials/post-article'></article>
15        </section>
16        <content-whitespace></content-whitespace>
17        <footer ht-include='partials/footer.html' data-color-scheme='dark'></footer>
18        <section ht-include='partials/tail.html'></section>
19    </body>
20</html>

This is all table stakes stuff, but I'm pumped to get it all wired up!

Just started reading "Filterworld", by @kylechayka.com, and it starts with a picture from one of my favorite Wikipedia pages of all time. I think I'm gonna like this book!

#NowReading

TIL about the #HTML <base> element!

Originally posted on @sheesh.blog.

As soon as you have 20 minutes to spare, I encourage you to go watch this short film about Sally Schmidt, produced by Oscar® award winning documentary filmmaker Ben Proudfoot, for the @nytimes.com¹.

Speaking of restaurants, Sally started a little establishment you might have heard of called The French Laundry. 🤌

Originally posted on @sheesh.blog.

Long time listener, first time caller

I can't remember the last time I read a book from front to back¹, but I am a voracious reader. The thing is, I prefer to read "the internet" instead of books.

At some point early on in my internet journey I discovered #RSS and I immediately fell in love². My RSS feed became like my own personal newspaper, where I was the curator. I could add and remove columnists blog feeds as my interest graph would change over time. I was one of the many³ who decried the death of Google Reader. RSS lives on, but it's not as ubiquitious as it once was.

For some years my feed shifted from RSS to social media — almost exclusively Twitter, and mostly via Twitter Lists — but a few trends in recent years have brought me back to RSS:

1. RSS services are great again⁴.
2. RSS apps are making a comeback!
3. "Doomscrolling" became a thing™️, prompting a renewed need to curate my feed.

With my newfound replacement for Google Reader's service (Feedbin.com), and my favorite old RSS reader app making a glorious (and open source!!) comeback, I decided to start the curation process from scratch. I created folders for "News", "People", "Portland" (my local happenings), "Products", "Startups", and "Tech".

And then I started subscribing. And I discovered that the very first feeds I added were the very same feeds I've been reading all along. A combination of overlapping interest graphs (I'm assuming) and writing styles have kept me reading certain blogs for over a decade now. These are the bloggers who's writing has both intimidated me – because I hold them in high esteem – and inspired me to start this blog.

I have feared that if I ever started a blog I would appear as a copy cat, a cheap imitation of these now-veterans who probably started like I am starting right now. But I decided that instead of shying away from writing, I should lean into it. Give credit where credit is due. Start my blog, in my own voice (however heavily "inspired by" it may be), and acknowledge those who went before me.

Starting a blog is easy. Buy a domain ✅ write an /about page ✅ write a "hello, world" ✅ smash the publish button. 💥 But for me, I could not have started this blog without acknowledging who this blog was inspired by.

✌️

Every new blog should start with an obligatory "hello, world" — so here I am doing just that. My experience with blogging has generally rhymed with the experience a former co-worker of mine once shared:

"I’ve started seven different blogs. Every one had one post."

— Derek Newsom

Something feels different this time, but only time will tell.

✌️