Tags: ep



Thursday, October 22nd, 2020

Replying to

Yeah, that’s fair—if I had a time machine, I’d love to go back and make cookies same-origin only.

And JavaScript!


Replying to

Yeah …spicy!

Replying to

It’s that emphasis on “between origins” that gets me (though I understand the security concerns, of course). Jake’s original proposal seemed more focused on same-origin page-level transitions …which is most single page apps today.

Replying to

You’re right. I don’t have any in-depth knowledge here. I was trying to describe a proposal being incubated. I used an example. It was a bad example, I guess.

From now on I’ll just describe portals as “spicy iframes” and leave it at that.

Replying to

Jake, I’m not saying that if a technology is useful for AMP then it must be bad—see rel=”prerender”, as you say.

I was honestly, genuinely trying to give an example of where portals could be used based on the description in the explainer.

Replying to

Note that I didn’t say that portals came from AMP; I said they would help the AMP use case.

But I think I must be misunderstanding portals because it sounds to me like it would work great for the AMP top stories carousel.

Replying to

Apologies. I thought the use-case sounded a lot like AMP’s top stories:

…show another page as an inset, and then activate it to perform a seamless transition to a new state, where the formerly-inset page becomes the top-level document.

Replying to

Don’t get me wrong: it would be great if portals led to navigation transitions, but right now it looks like the focus is more on “like making an iframe go full page” e.g. an item in a news carousel on a search engine.

Replying to

My description of portals was genuine. I gave a use case (AMP) and a comparison (iframes). I didn’t pass any judgement (although I can see how just mentioning AMP implies ickiness by association).

Replying to

Portals are a proposal from Google that would help their AMP use case (it would allow a web page to be pre-rendered, kind of like an iframe).


Wednesday, October 21st, 2020

Chrome exempts Google sites from user site data settings

Collusion between three separate services owned by the same company: the Google search engine, the YouTube website, and the Chrome web browser.

Gosh, this kind of information could be really damaging if there were, say, antitrust proceedings initiated.

In the meantime, use Firefox

Tuesday, October 20th, 2020

Replying to

Are you saying he should grow a pair of test articles?

Fnarr, and indeed, fnarr.

Replying to

Yay! Welcome to the indie web!

I feel like there should be a website equivalent of a housewarming party—a homepage-warming party or something!

Sunday, October 18th, 2020

Replying to

Oh, that looks soooo goooood!

Friday, October 16th, 2020

The (extremely) loud minority - Andy Bell

Dev perception:

It’s understandable to think that JavaScript frameworks and their communities are eating the web because places like Twitter are awash with very loud voices from said communities.

Always remember that although a subset of the JavaScript community can be very loud, they represent a paltry portion of the web as a whole.

Replying to


Thursday, October 15th, 2020

Replying to

Sounds like you need more roughage in your diet. Or you could try drinking prune juice.

When it finally happens, just imagine how satisfying that blog post is going to be!

Monday, October 12th, 2020

Replying to

I’m just saying what everyone else is thinking, Ethan.

Sunday, October 11th, 2020

Replying to

crashes through wall

Tagliatelle al ragù alla bolognese!


Thursday, October 8th, 2020

Replying to

I don’t know anymore. What are words, even?