I just wish they would embrace the standards more consistently. Why aren’t the phones on USB-C yet?

You can do it with brid.gy (like this post). Need to automate the webmention, though

IMO, this is bad advice. https://meiert.com/en/blog/stop-using-resets/

Normalize.css fixes a number of odd browser bugs and provides behavior you almost certainly want like inputs and buttons inheriting font styles.

I’m coming to think there will be a place for preprocessor variables from here on out, separate from native vars. (@imports is vital, too)

Out of curiosity, what do you use for a reader?

Okay, backing up. Here’s the problem, as you define it: some developer somewhere adds CSS to your codebase that has unintended consequences. By packaging in a reusable component, you’ve isolated the problem.

I feel like a guy yelling, “don’t drive on the sidewalk because people should be able to walk there” and your response is “nobody walks on the sidewalk because everybody drives there.”

Great talk! I think more devs need to think of their CSS as a function of design principles 👍

now that’s just cool

Looks like I’ll have some more tooling to integrate into it from my indieweb site

I’d love to hear the takeaways from that

I’m more into one social network that spans all of the internet a la @SocialWebWG ;)

To be fair, I’m not fundamentally opposed to putting things in the same file (I love React & JSX!), but we need to ensure people w/ the relevant skills are reviewing the code we put out.

I just came across a fascinating approach to aspect ratios using an svg: http://codepen.io/aghassemi/pen/MpZpmM?editors=1100

Yeah. I complained loudly when Twitter floated the idea of lifting the character limit… but I’ve totally come around on that. I’m ready for longer tweets. 😬

You have a few options, but none are perfect. Honestly, this is what grid is for (though, in this instance, a sub-grid would be ideal, but that isn't implemented yet).

A couple possibilities w/ the current setup:

It’s about more than content ownership. It’s also about owning the experience: integrating “social network” into the browser, making it easy to share links and follow people. We’ve got an eye on user experience

Right now? Yes. But we’re building out the tooling. The same was true of the internet in 1993

Oh yeah, I wrote a bit more about it in this post

A decentralized social network called The Internet. Where you can reply to anything, like anything, and re-post anything. :) It’s an open standard backed by the W3C.

For example, I’m not replying to your tweet on Twitter… I’m replying on my blog (and then syndicating that to Twitter). I own my data.

You should get on the indieweb, dan 😉

I love that this appeared in my timeline immediately following my own tweet storm 😣

I’ve made the same argument. One response is these do cause problems for code maintenance and/or performance, though.

Also, congratulations, these are the first replies to twitter written in my Omnibear browser extension :)

Jealous! I miss Portland :)

This is a test reply from Omnibear

Yeah, I've switched back and forth b/t light and dark a few times over the years. Takes a day or so to get accustomed

Nice site

I definitely avoid using the microformat classes as hooks for CSS. That can lock you into HTML structures that you might need to change later on. Honestly, I’d prefer if microformats used a different attribute altogether, but I think that ship has sailed.