I'm going to be a bit contrary and and say that you shouldn't try to do
everything with the CLI. It is possible to search videos and browse the
internet through the tty. It can be done. However, that does not mean that it
should be done.

As a comparison, consider biking versus driving a car. You might want to make
riding your bike feel a lot like driving a car. You say to yourself: \"Jeeze --
I miss the stereo in my car.\" So you get a little bluetooth speaker and stick
it on your bike. Now you can have some music while you bike. And then you say:
\"I miss the air conditioning in my car.\" So you get a little battery powered
fan and stick it on your bike. Okay, now your bike has cooling. You keep
getting bugs and stuff in your eyes when biking. The windshield on your car
protects you from those annoyances, so you get a little plexiglass screen for
the handle bars of your bike. This could go on and on and on. You could make
your bike feel really car-like and do all sorts of car-ish things. But doesn't
all this sort of miss the point of riding a bike?

I think that one of the big attracions of the tty / cli experience is that it
is different from the gui experience.  You get a different computing experience
if you stick to things that are easy / normal / simple with the cli. On my
bike, I can go off road and explore a forest. On the computer side, I tend to
do a lot more writing and programming when I'm in a cli-only mode. I'll slow
down and read man pages instead of browsing the internet. 

A bike is simple enough (compared to a car) that I can fix it myself. 
With the cli, I can tinker with my shell or tweak my editor.

Anyway -- I recommend trying out the cli experience but not striving too hard
to make it do all the things that gui stuff can do. Play with just using the 
cli to do cli-ish things for an hour a day or something. Try to experience 
your computer through text as opposed to graphics. It'll feel weird and different.