With Twitter limiting access to the API to users with a paid account, I guess it's time to run #tweetback update one last time before closing my Twitter account…
npm run fetch-new-data
See https://github.com/tweetback/tweetback/#fetch-additional-tweets-from-the-api-optional
Is there a way to fill webmention.io with mentions from the past?
Asking for a friend… 😅
Ok, so Mozilla won't help JPEG XL…
Overall, we don't see JPEG-XL performing enough better than its closest competitors (like AVIF) to justify addition on that basis alone. — https://github.com/mozilla/standards-positions/issues/522#issuecomment-1409539985
😭
I have a client site with a header that is hidden when the user scrolls down, but shown again when the user scrolls up, which seems pretty comon nowadays.
This triggers some CLS, even if the hide/show is done in less than 500 ms, as “continuous interactions such as scrolls, drags, or pinch and zoom gestures are not considered ‘recent input’”. 😞
Fellow photographers, where in EXIF/IPTC meta data would you (or are you already) put a description of the photo?
I'm not talking about the legend, more the description of the actual content of the image, how you would describe it to blind people.
Couldn't find anything yet in Lightroom's UI.
I updated the footer on https://nicolas-hoizey.photo/ with nice icons for the other platforms where I publish photos, and the services I use to build and deploy the site.
Some where hard to find, most were not optimized (thanks SGVOMG!).
The Pixelfed one is reaaaaaly heavy with all these gradients, masks and paths.
TIL IntersectionObserver's rootMargin only works if the observer is in the same origin, because of privacy concerns:
There is a risk that the API may be used to probe for information about the geometry of the global viewport itself, which may be used to deduce the user’s hardware configuration.
That's why this demo of a sticky navigation doesn't work in CodePen's default view… 😞
Large photos in photo pages of my photography site are now progressive JPEGs so that you can see them earlier, even if they weight more than with AVIF or WebP:
Thanks to Cloudinary and my responsive images plugin for Eleventy, it took me 10 seconds! 😍
I wish Google didn't kill JPEG-XL… 😭
I also wish Largest Contenful Paint didn't wait for the full progressive image to be downloaded and rendered.
For language changes inside a paragraph, MDN suggests we can use the i element:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/i
That's what I thought was one of the new use cases for i.
A @[email protected] page about “Declaring language in HTML” (so @[email protected] ?) says we should use a span, div or bdi:
https://www.w3.org/International/questions/qa-html-language-declarations.en#usingspan
So no i after all?
Which (stable, lightweight, maintained, etc.) npm package would you recommend to transform any RSS or Atom feeds to a standard JSON Feed format?
Filter by year and month to see more notes.