cflat

13 ms·

1.
by cflat 4y ago
This is pure politics. The AOM want proof of loyalty and shipping a competing image format threatens that loyalty pact. It’s also incrementalism at its finest. “We already shipped av1, adding a single frame decode is minor overhead” is the
2.
by cflat 5y ago
Find yourself a canadian VPN endpoint and check out the CBC coverage (website or "Gem" app). It's pretty complete and much more accessible.
3.
by cflat 6y ago
5.25" floppy disks are more likely to suffer physical damage at this point in history than a 3.5" disk. This would also contribute to the supply-demand curve biasing to 3.5" (on top of the ubiquity argument) 3.5" have a
4.
by cflat 6y ago
DNS is not content. HTTP caches were always problematic from a business perspective. Great for downloading large binaries (installs) but problematic when they don’t expire as expected, or if content needs to change for contractual reasons.
5.
by cflat 6y ago
This feels contrived. Rarely do I, as a brand or content creator, want it circulating without my control. It doesn’t make business sense.
6.
by cflat 6y ago
CDNs are a known commodity with business relationships. You can’t have an unknown CDN in the mix. They are an extension of your infrastructure and you can control if they are or aren’t in the path of control. They key here is that there is
7.
by cflat 6y ago
Yea, but the web server delivering them is now google. Google now gets the access logs and using the persistent tls socket can follow the users activity. Sure the content is signed, but the delivery is no longer private.
8.
by cflat 6y ago
Let’s call a spade a spade. The only real world problem that WebBundles (and Signed Exchanges) really solve is to allow AMP to impersonate your website. Google wants all the click data and the click through navigation data about users (by w
9.
by cflat 7y ago
Agree. Safari has already made moves for this[1], but Chrome seems to be resistant[2]. [1] https://calendar.perfplanet.com/2017/animated-gif-without-th... [2] https://bugs.chromium.org/p/chromium&#
10.
by cflat 7y ago
Totally agree. To be clear, I wasn’t trying to overhype the ‘cure’ but rather emphasize that the problem is way more complicated than many believe because of the islet regeneration. That’s why I’m a believer in the tech we have now because
11.
by cflat 7y ago
For those who aren't initiated in the world of T1D there is some amazing research coming out of the Faustman lab (MGH). There is both a promising cure (BCG vaccine), but also research which indicates that islet cells _do_ regenerate fo
12.
by cflat 7y ago
I wonder what would be necessary to spin up a device lab for proper TDD for the Loop? This is such an amazing story of classical "hacking". This is what makes technology fun.
13.
by cflat 8y ago
Teaching.
14.
by cflat 8y ago
FWIW, using M3.Mediums at Spot with AWS Batch, the per vcpu rate works out to 0.0067/hr. Fargate is still ~600% more expensive.
15.
by cflat 8y ago
A few clarifying points: * the author specifically said -1% Conversion. If this were AWS, that would mean a daily reduction of $6million in revenue! * the author specifically says this is for IE users. This implies two things: a) webp is n
16.
by cflat 8y ago
still doesn't scale efficiently. http based streaming is the only reliable way to get economies of scale. The cpu cost per webrtc socket is high compared to a cache-hit for a static resource. Not to mention that WebRTC is way more cpu
17.
by cflat 8y ago
Don’t use webrtc for live video. It doesn’t scale with CDNs. Use dash/hls.
18.
by cflat 8y ago
the biggest impact is all the navel-gazing time we have spent trying to decipher what _is_ personal data and what are our obligations to our customer's and to their user. The actual work has been the easy part. We will never get back a
19.
by cflat 9y ago
mp4s aren't HEIF. but this feature is certainly pre-lude to Safari supporting HEIF in the browser.
20.
by cflat 9y ago
cool. painful, but cool.
21.
by cflat 9y ago
in the context of <img> the audio track doesn't play anyway. dropping it ensures you save the bytes.
22.
by cflat 9y ago
This usually happens when you have colour pallet increases. If you had a simple animated Gif with only 256 colours and convert it to any video you instantly have more data to compress. The better use case is where you start with video and c
23.
by cflat 9y ago
Don't know if you need a spec change since this is technically now supported in Safari TP. (See the example) Really it's up to the browser to decide if it wants to use the media type or not.
24.
by cflat 9y ago
Chrome now has the same enforcement for <video> tags.
25.
by cflat 9y ago
the biggest draw back is the browser preloader and general performance. For cinemagraphs & clips this will be great. Anytime you want to add audio or pause/control playback, this will be the wrong solution.
26.
by cflat 9y ago
ya. sad times. mirrored here: https://medium.com/@colinbendell/evolution-of-img-gif-withou...
27.
by cflat 9y ago
Mirror: https://medium.com/@colinbendell/evolution-of-img-gif-withou...
28.
by cflat 9y ago
read the post
29.
by cflat 9y ago
the biggest challenge I've run into is big/legacy CMSes that simply can't get the templates updated to use <video> instead of <img>. It's why we can't have nice things.
30.
by cflat 9y ago
still ridiculously large file compared to webm/mp4. The alpha support is cool though.

More ›