extracting from a display buffer is something i realized while working with LCD panels but the principal is similar.
There are two approaches reading the data structure, or reading the logic state on the physical connections to the display device and converting to ascii strings, its a display version of analog hole recording of a locked media file.
so instead of defeating DRM by elegance, a brute force approach is used to capture the data that has been unlocked by DRM services for human eye consumption.

you want a device that will not cost too much if you screw up ripping it apart. There was a good sized discussion regarding multiline LCD displays here on HN if we dig about we may find it. I think you should have an idea how its done but i dont want to extrapolate too much for the sake of the platform [HN] you could make a PIC device or any other stamp computer like arduino to manipulate the control switching and read the data bus out to a file thus translating one character at a time. it could be done in the 50's way using a row of toggle switches and a debounced "doit" button to send a binary command to the display controller but 10 fingering is slow in return for simplicity, thus automate the task with a device such as arduino or pic F84

SERVER-- if you can set up a local webpage and know how to code html as a minimum you can set up a local server, the next thing is if you want to let it touch the internet connection, so operational security is a first consideration. next is your ISP and how they filter your connection [or not] with some ISPs they want to "protect you from the web" so you have to workaround that, often using a nonstandard port will do it like setting your webserver or ftp server or smb[carefull!] server to ports like 1337 or 21337 as an example.
You will also need to port forward your router to whatever internal IP your server is using, one port per IP for each server. next is working with DNS or not.
If you have static address you can just memorize the public IP that leadsto your router and tack the port number on the end such as 192.168.1.80:1337 as an example for an internal address or the public address such as 2o7.1o7.o7.7:1337 {not a real IP!} for example.
if you want a kewl DNS there are places where you can get a DNS subdomain or real domain if you have money for it.
i use http://freedns.afraid.org/ often for this so i can use a name and it helps with the issue of dynamic IP.

Instead of figuring out what the public IP is for my router every time the lease goes stale, freedns will update the DNS entry to point to the new public IP.

Its not a massive undertaking as i can rip it all down and put it back up in about 15mins [slow but i hate running],
by hand, but it is an undertaking until you get settled in the topography and commit it to memory.

>> Something i didnt mention is the topic of HTTPS.
when you send anything across the internet there are a number of machines in the middle that can read or manipulate the information when your server is HTTP, so you have two choices other than open coms. One being some homerolled encryption or something like https://letsencrypt.org/

You can set up for an HTTPS certificate and lock things down a somewhat for MITM attacks that dont have time to break the encryption. <<