XSF Communications Team - 2022-04-15

Good morning and happy Easter holidays to whom it applies! almost exactly mid-of month - Newsletter reminder time! I will be limited available till 24th - but you know: Feel free to illustrate the online pad: https://yopad.eu/p/xmpp-newsletter-365days Until then, emus ✏

I added a paragraph on poezio 0.14. I'm not sure how you handle pictures generally. In my article I have a <figure> block (in ~html~markdown) and I provide avif and png fallback, so I copied it in for now, tell me if you need something else

Also I guess pictures are gonna be copied to xmpp.org?

yes, its a markdown string

just maybe reference the direct picture link

or do you create a PR?

it's a markdown string?

markdown is an html superset so this should work

If it's allowed in the static-site generator I guess

I have the following in my hugo config: [markup.goldmark] [markup.goldmark.renderer] unsafe = true xhtml = true

well, we did upload the pictures to the image folder in the github repo. then we referenced to that picture with this markdown notation. if you have a better solution thats fine to me as well. however. we wanted to prevent putting the load to peoples server

I see

wurstsalat:

I would have done that for privacy reasons, but ok :P

pep.: maybe take a look at the prvious release

> pep. escribió: > I would have done that for privacy reasons, but ok :P what exactly?

"we wanted to prevent putting the load to peoples server"

I'm not asking where to host pictures, xmpp.org is good.

Just asking how to present them

>  ✏

pep.: ah ok

No way to provide different formats? :/

well if you want to do the effort and prepare this as we ususally do, it would be appreciated

creating the new image folder for april release uploading the picture

etc

I guess we're talking past each other :p

😅 I think so too

can you state your question again?

I guess I already have my answer though. I'd like to provide different image format and this is what I have in the pad atm: <figure> <picture> <source srcset="https://bouah.net/2022/04/poezio-full.avif" type="image/avif" /> <img decoding="async" src="https://bouah.net/2022/04/poezio-full.png" alt="Poezio example screenshot" /> </picture> <figcaption>Release chat in the poezio chatroom.</figcaption> </figure>

I know it works, that's what I use in my blog, but you might not have the options enabled.

Ok, but I cannot evaluate what this means regarding traffic and privacy and also not the mail yet. lets see end of the month

traffic?

The links to bouah.net are just temporary, we'll move that to xmpp.org

But it's certainly reduced traffic to provide avif, it's half the size of the png

And clients shouldn't download the first picture if they can't read that format

pep., we've disabled inline html for the whole website. if you'd like to have images linked with multiple sources, you'd have to create a shortcode for that, then use it in the markdown file

something like this https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/shortcodes/figure.html

it's not exactly <figure> that I want, it's <picture> and <source>

Why not enable html? Everything goes through PRs anyway

How does one use this kind of shortcode?

because there can't be any html slipping through when reviewing PRs. shortcodes let you reuse that html on the page, which has resulted in much easier maintenance so far. no copy paste, no search and replace, just edit the shortcode and that's it. you use it with {{< shortcode >}} while shortcode.html is your html container

Ok I'll have a look

pep.: Could split the difference and use webp which is supported everywhere but much smaller than png

Hey guys, I am Berry sorry. I had to create a new PR for the german translation.

I am to dump to check the PR out. I am in holidays and don't want to waste more oft my holy vacation time.

I hope you can work with it :) Not nice to work on a small notebook ;D

emus:

Why does `make serve` listen on 0.0.0.0?

wh0: ok thx

pep.: I used that to test from other devices as well. For local testing with a mobile device for example. Listening to 127.0.0.1 won't let you do that

Ok