My pals in BBC World Service have been doing some awesome work on "lite" versions of their news articles (other page types to follow).
They essentially skip the Server-Side React hydration which means you end up with a simpler HTML+CSS page, no JS.
Page sizes drop significantly:
@tonypconway@kravietz Yep, spot on. It might be that this is a trailblazer which prompts the .co.uk stack to adopt it, the initial case is definitely compelling IMO.
Toby mentioned he'd be talking to you folks 👍🏻
@tdp_org This makes me so happy. I still shrink and compress images all the time for email, web, etc. because 99% of the time a huge multi-megabyte image just isn't needed.
The BBC is hiring 2x data-focussed Technical Architects ("senior" & "lead") for UK-based folks (due to boring tax/legal reasons).
Great & smart team (we work with them regularly) using mostly AWS-based tech. Flexible location (mainly remote by default but options to work from a number of offices). Solid pension & benefits.
Shares/boosts would be much appreciated. Closes May 16th.
Despite the very clever people working at Google & Fitbit, my Pixel Watch still marks me mowing the lawn as "Biking" every time.
I do get that the arm position will be pretty much identical but maybe they ought to consider metadata - how many people are cycling for an hour whilst in wifi range and within ~60 metres of their home location whilst moving at walking pace? 🤣
We're being force-migrated from Zoom to Teams (to save some Schekels) which was a bit of a wrench at first but I've found a few things which I prefer in Teams:
Dedicated "raise hand" vs "react" buttons on the toolbar
Visualised sequencing for people who raised their hand so you can go through in order
I do always struggle to find the "mute" button for some reason (seems to be common with lots of people) and the video quality is pretty poor compared to Zoom but I can live with it.
@tdp_org were you also force migrated to the electron app or do you actually use #teams in a browser? for me, using it in #firefox does not work because i refuse to accept 3rd party cookies. separate calls in a private window work for some minutes and then get increadibly slow and erratic. so much so that i start to suspect this might even be on purpose, because given that #jitsi and #bigbluebutton work flawlessly for hours i see no good reason to not make trams work in ff…
I just recieved this scam email purporting to be a TV Licensing renewal reminder. It's reasonably well done except for:
The sender email address
The trademark symbol - AFAIK that's never used by TVL
I believe they're using the data from the People's Energy data breach as the email address they sent this to used the unique plus alias I used on my account with PE.
The "sign in" link goes to an AWS S3 hosted file BTW.
@tdp_org Yeah there's little worse than signing up to something you have a feeling is really going to need it, then finding their validator doesn't think + is a valid email character 🤦♂️
Is it "no one is registering for our conferences so let's spam everyone and offer free tickets" week or something?
I must have had 5-10 every day so far.
Blocked every sender.
I enabled Brotli compression on the CDN which serves the main BBC websites (www.bbc.co.uk. www.bbc.com etc.) outside the UK this morning.
Over ~4 hours, we're seeing a mean of ~20% better compression (smaller responses) via Brotli & ~95% of responses being Brotli now.
I've not had time to look in detail at performance but there doesn't look to be a significant change (LMK if you see diferent!).
(the spikes are breaking news events linking to a large "live" pages) #Brotli#WebDev#BBC
@tdp_org nice. server CPU usage over that time would be an interesting thing to plot, to see what the practical impact is. Brotli is a lot slower than gzip but if we're talking about a computation time of 5us going to 100us it's essentially noise compared to other load sources.
Our stack is: Fastly -> GTM (BBC CDN) -> Belfrage (BBC routing) -> origins for most of our modern web pages.
Currently, only Fastly supports Brotli, the others do gzip, deflate & no compression.
Fastly strips gzip,deflate from the accept-encoding header sent to origin so our layers all return uncompressed content which means they're using more egress bandwidth. It's not a huge problem for us but something I thought might be useful for others to know. #WebDev#Brotli#CDN#Compression#BBC
Somehow, we never got round to enabling Brotli compression on www.bbc.co.uk & www.bbc.com so I am just in the final throws of deploying that.
So far in ~1 hour on our staging site, I'm seeing ~24% smaller files under Brotli (vs. gzip). 🤞this (or better) also happens on live which'll be tomorrow. #WebDev#Compression#Brotli#GZip
@sirber@tdp_org for decompression it's within the margin of error vs. gzip, both for time and power consumption.
for compression I seem to remember that it's quite a bit heavier than gzip (as much as 20x slower per kB of content, at least on the implementations that were around a few years ago) in terms of total computational load, but with the tradeoff that brotli has lower delivery latency due to the way it can stream content.
@sirber@tdp_org my favourite brotli fact is that its static dictionary feature produces such incredible compression ratios on web content (HTML, CSS, JS) that running your static content through a minifier and then gzipping it often produces larger data than simply applying brotli to non-minified content.
Any tried add trusted (I can search for recipes, looking for genuine recommendations) recommendations for a good, authentic Italian pizza dough recipe which is realistic for me to make at home?
(We have a mixer etc) #pizza#pizzadough#italian#cooking