URI: 
       Add ads hackathon. - brcon2023-hackathons - Bitreichcon 2023 Hackathon Repository
  HTML git clone git://bitreich.org/brcon2023-hackathons git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/brcon2023-hackathons
   DIR Log
   DIR Files
   DIR Refs
   DIR Tags
       ---
   DIR commit 8309db59b4cc38d41dc05a7b9003e30f3a42c25c
   DIR parent 44127243c5322ca063472c7466e8c77ffd6a3352
  HTML Author: Christoph Lohmann <20h@r-36.net>
       Date:   Thu, 10 Aug 2023 19:50:44 +0200
       
       Add ads hackathon.
       
       Diffstat:
         A ads/description.md                  |      45 +++++++++++++++++++++++++++++++
       
       1 file changed, 45 insertions(+), 0 deletions(-)
       ---
   DIR diff --git a/ads/description.md b/ads/description.md
       @@ -0,0 +1,45 @@
       +# Ads should be moving.
       +
       +People know the ads showing at brcon2023:
       +
       +        gophers://bitreich.org/1/con/2023/ads
       +
       +There is already a subformat:
       +
       +        -before is played before the -after ad.
       +
       +But there is a reason, why those files end in .vtv. The last v stands for
       +video. It hasn't been implemented yet.
       +
       +It would be pretty simple:
       +
       +        $frame0
       +        $frame1
       +        ...
       +        $framen
       +
       +The frames have a hard-fixed size, so reading a frame and displaying it
       +is simple.
       +
       +## Making a video player.
       +
       +This should be a simple shell script.
       +
       +## Optimisations
       +
       +People know ncurses, the library. Why do we need this overcomplex
       +library? It knows buffering and can send the diff of one buffer over the
       +line, instead of sending the whole line. We have many vtXXX commands in
       +the virtual terminal to simply just replace parts of it.
       +
       +Can we do it and use it for the vt videos?
       +
       +## Compression
       +
       +This should be pretty simple, once we get the differences done. Then
       +compare the known compression formats against eachother.
       +
       +Have fun!
       +
       +
       +