←back to thread

Facebook adds 5 divs, 9 spans and 30 CSS classes to every post in the timeline

(twitter.com)
550 points polskibus | 1 comments | 08 Feb 19 16:04 UTC | HN request time: 0s | source
Show context
sly010 ◴[08 Feb 19 17:05 UTC] No.19116255[source]▶
I wonder at which point will we just stream pages as interactive video content with a text optimized codec. Most pages on the internet are bloated to the point where it might just make sense. (I am not advocating, I am predicting)
replies(6): >>19116385 #>>19116508 #>>19116649 #>>19116887 #>>19117501 #>>19117692 #
bastawhiz ◴[08 Feb 19 17:16 UTC] No.19116385[source]▶
At a previous job in the not-too-distant past, we needed to support IE7 for contractual reasons. I'd unironically floated the idea of launching a VM on the server running Firefox, and starting a VNC session, streamed over frames of a GIF. Clicks and keypresses would be transmitted with AJAX calls.

In a later project, we played with the idea of using an asm.js-compiled Webkit to render SVG (with embedded HTML) into a canvas due to mixed browser support.

Long story short, it's not inconceivable.

replies(7): >>19116406 #>>19116420 #>>19116540 #>>19116688 #>>19116721 #>>19117542 #>>19118357 #
1. Eli_P ◴[08 Feb 19 17:43 UTC] No.19116721[source]▶
Facebook should try to adapt screamer-prank tech[0] for ads. Even if an ad missed your attention, you'd still have to pay 1 laundry bill and 1 bill for stuttering-aid couching.

Jokes aside, even with rendering to canvas, ad can be blocked with image recognition. Long time ago I used Sikuli Script for UI testing automation, Sikuli recognized parts of screen and worked very fast; combine it with an app like CinemaDrape and voila.

[0] (loud noises warning) https://youtu.be/469zNXTCHdk?t=10