Lmst

これから始める Cloudinary：画像アップロードから URL 加工までノーコードで体験
https://dev.classmethod.jp/articles/cloudinary-getting-started-no-code/

I've been stuck on this blog post for a long time, but I finally published it last week:

How I built dynamic social media images in Eleventy (11ty) using Cloudinary

https://chipcullen.com/how-i-built-dynamic-social-media-images-in-eleventy-using-cloudinary/

Hey #indeweb, anyone with experience hosting (open-sourced) personal sites with media files (images, PDF) on #Codeberg? I aim to make use of a #Hugo pipeline from Codeberg to Codeberg Pages, like from Github to Github Pages / Netlify / Vercel. I don't want to test the limits of the terms of use though. Also considering #Cloudinary, bit unsure how to manage the upload automatically.

Anyone out there using #11ty and #cloudinary in a magical way that lessens the work of doing the following for EVERY image:

1. upload to Cloudinary
2. copy URL
3. paste URL in your HTML

For example, some process of having a image on my computer and doing the above (somehow) automatically or with less steps/waiting/etc. and the end-result being a Cloudinary-hosted image referenced in my 11ty template? With full control over the usuals: alt, srcset, loading, class attributes, etc.?

CloudinaryのデータをAmazon S3に自動バックアップする
https://dev.classmethod.jp/articles/cloudinary-backup-amazon-s3/

#dev_classmethod #Cloudinary

I would like to move the photos for my 365 project from my #astro project to a DAM so that I don't have to add a new photo to my project every day but can put it in the DAM and access it in other places as well.

The Astro Docu refers to a direct #cloudinary integration based on Astro and Cloudinary Collections. Unfortunately, the limit for free accounts is 3 collections, 50 images each, which is not enough for me.

Does anyone have any ideas/suggestions on how I could approach this technically?

Cloudinaryが何を解決するのか
https://dev.classmethod.jp/articles/solution-cloudinary/

#dev_classmethod #Cloudinary #SaaS #画像処理 #CDN #AI

I'm excited that my contribution to #Vite was released in 6.0.0-beta.3. I'm using #Cloudinary for responsive images and transformations are separated by comma. But Vite incorrectly divided URLs in `srcset` HTML attribute and `image-set` CSS function, so they rendered broken and unusable. It was broken just for 8 months and nobody cared. https://github.com/vitejs/vite/pull/18242

I'm now using @eleventy's screenshot service for my links content, thanks a lot @zachleat!

But…

…it looks like many screenshots fail, so I get the default image — Eleventy's logo —, as you can see in my #Cloudinary Library… 😅

#screenshot

⚓️ https://nicolas-hoizey.com/notes/2024/09/06/1/

“GIFs Are Forever, Let’s Make Them Better” by @tylersticka

🔗 https://www.youtube.com/watch?v=VhOEcA-Ne44

> Everyone loves animated GIFs, right? Not if you have finite bandwidth, a shaky network connection or motion sensitivity! But fear not… modern browsers make it easier than ever to level up our GIF game!

Great talk by Tyler at CascadiaJS 2024!

If you prefer text over video, Tyler wrote earlier on CloudFour blog…

#GIF #video #accessibility #Cloudinary

⚓️ https://nicolas-hoizey.com/links/2024/09/04/gifs-are-forever-let-s-make-them-better/

Screenshot of GIFs Are Forever, Let’s Make Them Better

@akkerman саме так, з таким теж стикався. Це теж можливо, бо апстрім через #cloudinary працює та може змінювати адреси

Started to build out my #photography site. It's pretty basic at the moment, while I build out the functionality. Here is the current stack. #NextJS #TailwindCSS #Markdown #Cloudinary #Netlify

I have a bunch of things to do still like add lightbox, OG images, better looking post pages, etc.

It's so simple to add new albums though. I just create a simple .mdx file for every new album. Beware it's pretty bland!

Great Google Speed performance better, once SEO is set.

https://photos.bgarr.com

Geek, der schon mit 5.5 Jahren auf dem #ZX81 das #Programmieren anfing und mittlerweile auf 24 Jahre #Berufserfahrung zurück blicken kann, ist auf #Jobsuche als #BackEndDev oder #FullStackDev.
Aktueller Techstack/Aktuelles Können:
#JavaScript, #Typescript, Node.js, Next.js, React.js, #Kubernetes, #CircleCI, #ArgoCD, Helm Charts, #Docker, #Kafka, APIs, #GraphQL, #Microservices, #Commercelayer, #Plasmic, #Git, #GitOps, #Vercel, #Cloudinary, #Confluent

#HTML5, #CSS und #SASS sind keine Fremdwörter, jedoch ausbaufähig und der Wille dazu ist auf jeden Fall vorhanden! Rudimentäre Kenntnisse in #Python sind vorhanden. #CSharp Kenntnisse von vor 10 Jahren vorhanden, #PHP dann doch zu lange her, aber noch einigermaßen "lesbar".

Gesucht wird 100% remote! Kann auch gern zum Einarbeiten oder zwecks in-house Fortbildungen für ein paar Tage vorbei kommen, wenn hundefreies Office oder hundefreies Office (starker Allergiker) in oder um Fulda (max. 30km) als Hybrid.

Gern Boost.

Thanks and goodbye, Cloudinary • After my code exceeds the limits of an already overly generous Free Plan, I once again process all images locally.

https://www.brycewray.com/posts/2024/03/thanks-goodbye-cloudinary/

#WebDev #images #SSG #Hugo #Cloudinary

Another JPEG XL comparison and analysis has dropped. The encoder keeps getting better. :gutkato_kontenta:

Any thoughts, @mozilla?

#lang_en #Cloudinary #JPEG_XL #JPEGXL #JXL #Mozilla #salty #technology

If your website uses Cloudinary and you see browser warnings about third-party cookies being banned soon, it’s probably because you have previously accessed your Cloudinary dashboard and thus have a cookie from *that*. To confirm that a page with any Cloudinary images is actually OK re third-party cookies, view the page in “Private”/“Incognito” mode.

Source:
https://support.cloudinary.com/hc/en-us/community/posts/360009459300-Cookie-samesite-when-downloading-to-localhost-from-Cloudinary

#WebDev #Cloudinary #Images #Cookies #Browsers #InfoSec

#AVIF is useless in lossless (which #PNG and #WebP excel at) and pointless in lossy (which #JPEG beats in preserving sharpness and quality, as well as #JPEGXL which beats both JPEG and AVIF on pretty much all the quality levels that matter in real-world usage).

AVIF only "won" because of strong-arming and deception by #Google's AVIF and #Chrome teams, not through technical merits that JPEG XL through Google's #PIK team and #Cloudinary championed. I do not accept this bastardization of new #web #standards being written, and #photographers should resist the same as they did against lossy WebP in favor of #mozjpeg in the past.

I believe that #PaleMoon will not have any plans to support AVIF in the long future especially when it already has JPEG XL support in. :seija_coffee:

RE: https://pleroma.envs.net/objects/f8b52057-049f-4bf3-b909-14d5b25fac86